Manage country-specific configurations for Italy

Configure e-invoicing in Sovos for Italy

To configure e-invoicing for invoice clearance in Italy, you must create a company profile in Sovos. Zuora handles the configuration process on your behalf in Sovos, ensuring a seamless setup. You have to provide the following information required for the configuration to Zuora:

Company Name: Legal name of your business
Trade Name: Doing business as (DBA) name
VAT Number: Your VAT identification number

Manage field mapping for e-invoice file templates

In the e-invoicing clearance process in Italy, ensure that the field mapping for e-invoice file templates is complete and correct. The following fields are used in the default e-invoice file template. Remember that you might have to customize the default e-invoice file template if the default field mapping does not align with your business requirements.

Configure e-invoicing business regions for Italy

In the e-invoicing clearance process in Italy, you must configure business regions according to Italy-specific requirements.

The business region objects can be looked up according to the country and state, and their related fields can be mapped accordingly within the e-invoicing template. You must configure e-invoicing business regions for Italy according to Italy-specific requirements.

The following table lists the business region settings you must configure in the Add Business Region dialog.

UI section	UI field	API field	Required	Description
Basic Info	Country	country	Yes	From the Country list, select a country or region where you must comply with e-invoicing requirements.
	Legal Business Name	businessName	Yes	In the Legal Business Name field, specify the full official name of the Seller registered with the relevant legal authority.
	Legal Business Number	businessNumber	Yes	In the Legal Business Number field, specify the unique identifier number of the legal entity or person you do business with. For Italy, the value is the tax identification number for VAT purposes. The first two characters represent the country (IT, DE, ES, and so on), and the remaining characters (up to a maximum of 28) are the actual code which, for Italian residents, corresponds to their VAT number. For example, IT99999999999.
	Business Number Schema Id	businessNumberSchemeId	No	In the Business Number Schema Id field, specify the identification scheme identifier that an official registrar issues to identify the Seller as a legal entity or person.
	Trade Name	tradeName	Yes	In the Trade Name field, specify the name that the Seller is known as, other than the legal business name.
	Tax Register Number	taxRegisterNumber	No	In the Tax Register Number field, specify the Seller's VAT identifier (also known as Seller VAT identification number) or the local identification (defined by the Seller’s address) of the Seller for tax purposes, or a reference that enables the Seller to state the registered tax status.
	E-Invoice Destination Code	endpointId	No	In the E-Invoice Destination Code field, specify the Seller's electronic address, to which the application-level response to the e-invoice file might be delivered.
	E-Invoice Destination Code Schema Id	endpointSchemeId	No	In the E-Invoice Destination Code Schema Id field, specify the identification scheme identifier of the Seller’s electronic address.
Business Address	Address 1	addressLine1	Yes	In the Address 1 field, specify the first line of the Seller’s address, which is often a street address or business name. For Italy, Address 1 is the name of the street, road, avenue, way, and so on, to which the number of the corresponding building is attached.
	Address 2	addressLine2	Yes	In the Address 2 field, specify the second line of the Seller’s address, which is often the name of a building. For Italy, Address 2 is an additional street name used to further clarify the address.
	Postal Code	postalCode	Yes	In the Postal Code field, specify the short code that can identify the business address. For Italy, the value is the postal identifier for this address according to the relevant national postal service, such as a ZIP code or post code.
	City	city	Yes	In the City field, specify the name of the city where the business is located. For Italy, the value is the name of a city, town, or village.
	State/Province	state	Yes	In the State/Province field, specify the name of the state or province where the business is located. For Italy, the value must be an abbreviation code of the province, to which the municipality belongs (only to be entered if the registered office is in Italy). The field value must be two characters, such as RM, MI, and so on.
Contact Info	Contact Name	contactName	No	In the Contact Name field, specify the name of the Seller contact to receive e-invoicing data.
	Email	email	No	In the Email field, specify the email address of the Seller contact to receive e-invoicing data.
	Business Phone Number	phoneNumber	No	In the Business Phone Number field, specify the business phone number of the Seller contact to receive e-invoicing data.

Configure e-invoicing profiles for accounts in Italy

According to Italy-specific requirements, you must configure e-invoicing profiles for customer accounts involved in the e-invoicing business.

The following table lists the e-invoicing profile settings to configure for a customer account in Italy.

UI field	API field	Required	Description
Business Number Schema Id	businessNumberSchemeId	No	In the Business Number Schema Id field, specify the identification scheme identifier that an official registrar issues to identify the Buyer as a legal entity or person.
Trade Name	tradeName	No	In the Trade Name field, specify the name that the Buyer is known as, other than the legal business name.
Tax Register Number	taxRegisterNumber	No	In the Tax Register Number field, specify the Buyer's VAT identifier (also known as the Buyer's VAT identification number) or the local identification (defined by the Buyer’s address) of the Buyer for tax purposes, or a reference that enables the Buyer to state the registered tax status.
E-Invoice Destination Code Schema Id	endpointSchemeId	No	In the E-Invoice Destination Code Schema Id field, specify the identification scheme identifier of the Buyer’s electronic address.
Generate E-Invoice for Customer	enabled	Yes	Enable the e-invoicing profile for the customer account. If the following conditions are met, all billing documents for one account can be submitted to an e-invoicing service provider to be generated in electronic format: The account must be configured to generate e-invoice files for billing documents. The billing document must be in Posted status. A business region must be created for the billing country contact, and be linked to an e-invoicing service provider.
Legal Business Name	businessName	Yes	In the Legal Business Name field, specify the full official name that the Buyer is registered with the relevant legal authority.
Legal Business Number	businessNumber	Yes	In the Legal Business Number field, specify the unique identifier number of the legal entity or person that you do business with. For Italy, the value is the tax identification number for VAT purposes. The first two characters represent the country (IT, DE, ES, and so on), and the remaining characters (up to a maximum of 28) are the actual code which, for Italian residents, corresponds to their VAT number. For example, IT99999999999.
E-Invoice Destination Code	endpointId	Yes	In the E-Invoice Destination Code field, specify the Buyer's electronic address, to which the application-level response to the invoice/billing document might be delivered. For Italy, use CD as the reception method for the reception of the invoice. The CD enables the identification of the communication channel between the SDI and the recipient.
Name	name	Yes	In the Name field, specify the name on the Account object. The value is used as the trading name or company name of the Buyer/Orderer to be entered for a non-natural person.

Configure sold-to contacts for accounts in Italy

You must configure sold-to contacts for customer accounts involved in the e-invoicing business in Italy.

The following table lists the contact-related fields involved in the e-invoicing business in Italy.

UI field	API field	Required	Description
Country	country	Yes	From the Country list, select Italy.
Address 1	addressLine1	Yes	In the Address 1 field, specify the first line of the Buyer’s address, which is often a street address or business name. For Italy, Address 1 is the name of the street, road, avenue, way, and so on, to which the number of the corresponding building is attached.
Address 2	addressLine2	Yes	In the Address 2 field, specify the second line of the Buyer’s address, which is often the name of a building. For Italy, Address 2 is an additional street name used to further clarify the address.
Postal Code	postalCode	Yes	In the Postal Code field, specify the short code that can identify the business address. For Italy, the value is the postal identifier for this address according to the relevant national postal service, such as a ZIP code or post code.
City	city	Yes	In the City field, specify the name of the city where the business is located. For Italy, the value is the name of a city, town, or village.
State/Province	state	Yes	In the State/Province field, specify the name of the state or province where the business is located. For Italy, the value must be an abbreviation code of one province, to which the municipality belongs (only to be entered if the registered office is in Italy). The field value must be two characters, such as RM, MI, and so on. The field value must be an abbreviation code of one province in Italy. If you use another field to store the abbreviation code of the state, you have to customize the template.

Specify the type and number for an additional document

You must create and manage custom fields to store country-specific information for mapping to Sovos. The e-invoicing in Italy requires an identifier for the referenced document for credit memos and debit memos.

The e-invoicing in Italy requires an additional document about a billing document. The following values are allowed for the additional document:

OrdineAcquisto : Purchase Order
Contratto : Contract
Convenzione: Convention
Ricezione : Reception
FattureCollegate : Connected Invoices

The default e-invoice file template mapping utilizes the following types and reference numbers for additional documents:

For purchase orders associated with invoices, the default e-invoicing mapping uses OrdineAcquisto (Purchase Order) as the type, and the purchase order number of the corresponding account serves as the reference number for the invoice.
For credit memos and debit memos connected to an invoice, regardless of whether they are created from the invoice or generated from subscriptions, FattureCollegate (Connected Invoices) is used. The invoice number is used as the reference for the additional document.
For standalone credit memos and debit memos created from product rate plan charges, OrdineAcquisto (Purchase Order) is used as the type. the purchase order number of the corresponding account serves as the reference number for the additional document.

If you want to modify these default mappings, you must customize the e-invoice file template. For example, you can use the purchase order number as the reference number for an additional document specific to an individual invoice. You can store the purchase order number on either subscriptions, charges, or invoices.

Testing recommendations

Zuora has tested e-invoicing on various billing document types and operations with the default e-invoice file templates.

The following table lists the test cases for your reference.

Billing document type	Document source	Case category	Description
Invoice	Subscription	One charge	Create a subscription containing one rate plan charge with taxation, generate a draft invoice from the subscription, and then post the invoice.
Credit Memo	Invoice	One charge	Create a credit memo from the invoice, and post the credit memo.
Debit Memo	Invoice	One charge	Create a debit memo from the invoice, and post the debit memo.
Credit Memo	Invoice	One charge	Generate an invoice from the subscription, and reverse the invoice to create a credit memo from the invoice.
Credit Memo	Invoice	One charge	Generate an invoice from the subscription, and write off the invoice to create a credit memo from the invoice.
Credit Memo	Subscription	One charge	Generate a credit memo from the subscription cancellation, and post the credit memo.
Debit Memo	Credit Memo	One charge	Reverse the credit memo to create a debit memo from the invoice.
Invoice	Subscription	Multiple charges	Create a subscription containing multiple charges with taxation, generate a draft invoice from the subscription, and then post the invoice.
Credit Memo	Invoice	Multiple charges	Create a credit memo from the invoice, and post the credit memo.
Debit Memo	Invoice	Multiple charges	Create a debit memo from the invoice, and post the debit memo.
Credit Memo	Invoice	Multiple charges	Generate an invoice from the subscription, and reverse the invoice to create a credit memo from the invoice.
Credit Memo	Invoice	Multiple charges	Generate an invoice from the subscription, and write off the invoice to create a credit memo from the invoice.
Credit Memo	Subscription	Multiple charges	Generate a credit memo from the subscription cancellation, and post the credit memo.
Debit Memo	Credit Memo	Multiple charges	Reverse the credit memo to create a debit memo from the invoice.
Invoice	Standalone	Multiple charges	Create a standalone invoice containing multiple items from product rate plan charges, and post the invoice.
Credit Memo	Standalone	Multiple charges	Create a standalone credit memo containing multiple items from product rate plan charges, and post the credit memo.
Debit Memo	Standalone	Multiple charges	Create a standalone debit memo containing multiple items from product rate plan charges, and post the debit memo.

Note that the testing was performed in the Sovos Sandbox environment with a testing account, and the following assumptions apply:

Zuora uses testing tax identification numbers for both the Seller and Buyer, which are not real.
All billing documents have Taxation enabled. Zuora does not test scenarios where billing documents have no taxation.
The taxation addresses are testing address data and do not represent the addresses of real business entities. The same testing address data is used for B2B and B2G business categories.
The billing documents cover only regular charges, without discount charges. If you use Zuora discount charges, you must customize the e-invoice file template.
Zuora has confirmed that document data has been successfully submitted through the Sovos Sandbox environment using a testing CD. However, note that Zuora does not validate the successful delivery of e-invoice files to the client through Sovos.

For more details on scenarios that Zuora has not tested, see the next sections. It is best practice to include these scenarios in your testing if they align with your business requirements.

Business Category

The e-invoice data transmitted to SDI supports two types of business categories, identified by the following codes:

FPA12 for public administrations (B2G communication)
FPR12 for private companies and professionals (B2B communication)

Zuora's default e-invoice file template is configured for B2B. If you operate in both B2B and B2G scenarios, you must customize the default e-invoice file template according to business requirements.

Zuora's e-invoicing testing covers the B2G business category, utilizing the same testing data as B2B, including the address, VAT numbers of the Seller and Buyer, and CD of the Buyer.

FatturaPA

The FatturaPA is a type of electronic invoices that are accepted by Public Administrations. As the only type supported by the Sovos solution, the FatturaPA supports about 19 types of doucments being transimtted. Zuora currently only supports the following types of documents using the default e-invoice file template:

TD01: Invoice
TD04: Credit Note
TD05: Debit Note

For your reference, the following allowed values are available as types of documents being transmitted in Italy:

TD01: Invoice
TD02: Advance/down payment on invoice
TD03: Advance/down payment on fee
TD04: Credit Note
TD05: Debit Note
TD06: Fee
TD16: Reverse charge internal invoice integration
TD17: Integration or self-invoicing for purchase services from abroad
TD18: Integration for purchase of intra UE goods
TD19: Integration or self-invoicing for purchase of goods ex art.17c.2 DPR 633/72
TD20: Self-invoicing for regularisation and integration of invoices (ex art.6 c.8 and 9-bis d.lgs 471/97 or art.46 c.5 D.L.331/93)
TD21: Self-invoicing for splaphoning
TD22: Extractions of goods from VAT Warehouse
TD23: Extractions of goods from VAT Warehouse with payment of VAT
TD24: Deferred invoice ex art.21, c.4, third period lett. a) DPR 633/72
TD25: Deferred invoice ex art.21, c.4, third period lett. b) DPR 633/72
TD26: Sale of depreciable assets and for internal transfers (ex art.36 DPR 633/72)
TD27: Self-invoicing for self consumption or for free transfer without recourse
TD28: Purchases from San Marino with VAT (paper invoice)

SDI

With the Sovo solution, the document is transfered to FatturaPA and transimitted to Sistema di Interscambio (SDI). SDI is an electronic system capable of:

Receiving invoices in the form of files with the characteristics of the FatturaPA.
Performing checks on the files received.
Forwarding invoices to the addressee Administrations.

The identification of the identification schemes supports the following types:

IdFiscaleIVA
CF: CodiceFiscale
EORI: CodEORI
CD: CodiceDestinatario
Using both IdFiscaleIVA and CD

Italy introduces the codice destanitario (CD) that plays an essential role in its e-invoicing model. The CD acts as a recipient's tax code that defines the address to which the invoice must be transmitted to through the SDI. The following types of ways are available to deliver e-invoice files:

CD - most common
Certified Electronic Mail or PEC
CD with "0000000"

Zuora's testing covers the following scenarios using the default e-invoice file template:

Use IdFiscaleIVA for the identifier for both the Seller and Buyer.
Use CD for the consumer party as the reception method for the reception of the invoice. The CD enables the identification of the communication channel between the SDI and the recipient.
- It is assumed that a single client has only one CD for SDI. If they have multiple SDIs, you must customize the default e-invoice file template according to business requirements.
- Zuora uses a faked CD called OUTBOU provided by Sovos for the testing. The CD only verifies that document data is submitted successfully through the Sovos Sandbox environment. The testing cannot verify the reception of billing documents through the communication channel between the SDI and the recipient.
Zuora does not test other e-invoice file delivery through Certified Electronic Mail or PEC.

Accepted means of payment

The e-invoice data transmitted to SDI supports various means of payment, including:

MP01: Cash
MP02: Cheque
MP03: Banker's draft
MP04: Cash at treasury
MP05: Bank transfer
MP06: Money order
MP07: Pre-compiled bank payment slip

To specify the payment channel for a particular means of payment, the following values are allowed:

TP01: Payment by instalments
TP02: Full payment
TP03: Advance payment

In Zuora's testing, only one means of payment is specified, defaulting to MP05 (bank transfer) and TP02 (full payment). If you use different means of payment or have multiple means of payment, you must customize the e-invoice file template according to business requirements.

Retrieve e-invoicing results

You can use the Retrieve e-invoicing results operation to retrieve e-invoice results according to the ID of a billing document. The document ID can be the ID of an invoice, a credit memo, or a debit memo.

The e-invoicing result fields might be different by country.

The e-invoicing result fields on EInvoiceData include the following fields for Italy:

QrCode: This field is empty for Italy.
ReferenceNumber: This field stores a unique number generated by the tax authority. In Italy, it is a unique identifier assigned to each electronically submitted invoice by the Italy tax authority, known as Agenzia delle Entrate. The information is obtained from the IdentificativoSdI field in the cleared document.
DocumentId: This field stores the ID of the billing document, for which the e-invoice file is generated.
DocumentType: This field indicates the type of the billing document, for which the e-invoice file is generated.

The eInvoiceFileId field on the Invoice object stores the ID of the Base64-encoded e-invoice file, a cleared document in the format of FatturaPA (XML).