Italian electronic invoicing is one of the most advanced digital VAT control systems in Europe. For foreign companies, however, it is also one of the most misunderstood areas of Italian compliance. Many businesses hear that Italy has mandatory e-invoicing and assume that every invoice connected with Italy must be issued through the Italian SDI system. Others assume the opposite: that a foreign company can always continue to issue ordinary PDF invoices from abroad. Both assumptions can be wrong.
The correct answer depends on a practical analysis of the transaction: whether the supplier is resident or established in Italy, whether the foreign company has only an Italian VAT number, whether the customer is Italian or foreign, whether the transaction is domestic or cross-border, whether reverse charge applies, whether the invoice must be reported through SDI, and whether the document must be digitally archived under Italian rules.
This guide is written for foreign companies, CFOs, tax managers, marketplace sellers and international groups that need a practical understanding of Italian e-invoicing. It does not treat e-invoicing as a purely technical XML issue. It explains how the SDI system affects VAT compliance, accounting workflows, document collection, customer relationships and tax risk in Italy.
Electronic invoicing should not be analysed in isolation. It is connected with VAT registration, fiscal representation, accounting, payroll, contracts, imports and the overall structure used to operate in Italy.
Continue with the ISY pillar guide:
→ Doing Business in Italy: Complete Guide for Foreign Companies
This guide helps foreign companies understand the legal, tax and operational steps needed to enter and manage the Italian market.
What is Italian e-invoicing?
Italian e-invoicing is the system under which invoices are issued in a structured electronic format and transmitted through the Italian exchange system known as Sistema di Interscambio, usually abbreviated as SDI. The standard format is generally known as FatturaPA, an XML format used for invoices to public administrations and, more broadly, for Italian e-invoicing workflows.
The practical difference from a traditional invoice is important. An ordinary PDF sent by email is simply a visual document. An Italian electronic invoice is a structured data file that must contain specific fields, VAT codes, counterparty information and transmission data. The SDI system checks the file and routes it to the recipient or makes it available through the relevant Italian channels.
Practical point: where Italian e-invoicing is mandatory, the invoice is not the PDF attached to an email. The legally relevant document is the structured XML invoice transmitted through SDI.
Why foreign companies should care about SDI
Foreign companies usually encounter Italian e-invoicing in one of four ways. They sell to Italian customers. They buy from Italian suppliers. They open an Italian VAT position. Or they create a more substantial Italian presence, such as a branch, subsidiary, fixed establishment, warehouse-based operation or recurring local activity. Each scenario creates different invoice and reporting consequences.
The mistake is to treat e-invoicing as a software question only. The first question is legal and VAT-related: who is issuing the invoice, where is the supplier established, who is the customer, where is the transaction located for VAT purposes and which reporting obligation applies? Only after this analysis should the company decide how to issue, receive, transmit, book and archive invoices.
| Scenario | Typical issue | Operational consequence |
|---|---|---|
| Foreign company sells to an Italian customer | Is the supplier obliged to issue through SDI or does the Italian customer manage reverse charge/reporting? | Invoice wording, VAT treatment and customer instructions must be checked. |
| Foreign company buys from Italian supplier | The Italian supplier may issue an e-invoice or a cross-border invoice depending on the customer status. | The foreign company may receive an XML, courtesy PDF or foreign-addressed invoice. |
| Foreign company has an Italian VAT number | VAT identification alone must be distinguished from being established in Italy. | Do not assume that every transaction follows domestic Italian e-invoicing rules. |
| Foreign group opens an Italian branch or subsidiary | The Italian entity may be fully inside the SDI regime. | ERP, accounting and invoice approval flows must be adapted to Italian requirements. |
Who is obliged to issue Italian electronic invoices?
As a general rule, Italian e-invoicing obligations apply to VAT taxable persons resident or established in Italy. This includes Italian companies and Italian fixed establishments of foreign companies when they carry out transactions falling within the Italian e-invoicing regime. The system is also mandatory for invoices to Italian public administrations and broadly covers domestic B2B and B2C transactions.
For foreign companies, the key distinction is between being established in Italy and being merely identified for Italian VAT purposes. A company may have an Italian VAT number through direct identification or a fiscal representative without necessarily being established in Italy. This distinction is essential because non-resident and non-established taxable persons are not automatically treated in the same way as Italian established operators for all e-invoicing purposes.
A foreign company with an Italian VAT number is not automatically an Italian established business. Before deciding the invoicing workflow, verify whether the company is resident, has a fixed establishment, is merely VAT identified, or is completely outside the Italian VAT registration system.
Foreign company status: practical matrix
The following matrix is a practical starting point. It is not a substitute for transaction-level advice, but it helps foreign companies avoid the most common misunderstanding: confusing Italian VAT registration with full domestic e-invoicing status.
| Company status | Typical position | E-invoicing impact |
|---|---|---|
| Italian subsidiary | Italian resident company with Italian VAT number. | Normally fully within Italian SDI obligations for domestic transactions. |
| Italian branch or fixed establishment | Foreign legal entity with an Italian establishment. | Transactions attributable to the Italian establishment may fall within Italian e-invoicing workflows. |
| Direct VAT identification | Foreign company registered for Italian VAT without establishment. | Requires careful analysis. VAT registration does not automatically mean the company is established in Italy. |
| Fiscal representative | Non-EU or other foreign company represented for Italian VAT. | Invoices, VAT ledgers and reporting should be coordinated with the representative and Italian advisor. |
| No Italian VAT number | Foreign supplier or customer operating from abroad. | Italian e-invoicing may affect the Italian counterparty, but the foreign company may not issue through SDI. |
How the SDI workflow works in practice
The SDI process is often described in technical terms, but foreign companies should understand it as an operational workflow. The invoice is created in the required XML format. It is transmitted to SDI directly or through a service provider. SDI performs formal checks. If the invoice passes the checks, SDI routes it to the recipient or makes it available through the appropriate channel. If it is rejected, the invoice must be corrected and resent.
The invoice is prepared in FatturaPA XML format with correct VAT and counterparty data.
The file is sent through an accredited channel, software provider, PEC or Revenue Agency tool.
SDI performs formal controls and accepts or rejects the invoice.
The invoice is routed to the recipient and stored according to compliant archiving rules.
For a foreign company, the weakest point is often not the XML generation itself. It is the upstream data. If the customer master data, VAT number, country code, VAT nature code, payment terms or invoice description are wrong, the invoice may be rejected or, worse, formally accepted but tax incorrect.
FatturaPA data fields foreign companies should understand
Foreign companies do not need to become XML developers, but they should know the commercial and tax meaning of the main data fields. The accounting team should be able to explain who the supplier is, who the customer is, which VAT treatment applies, whether the transaction is taxable, exempt, outside the scope, reverse charge or non-taxable, and which supporting documents are available.
| Field or concept | Why it matters | Common risk |
|---|---|---|
| Supplier and customer data | Identifies the parties and determines routing and VAT treatment. | Using a foreign head office instead of the correct Italian entity or VAT position. |
| Codice Destinatario or PEC | Allows SDI delivery to the recipient channel. | Invoice is not delivered correctly or must be retrieved manually. |
| VAT rate or Natura code | Explains whether VAT is charged or why it is not charged. | Incorrect code creates VAT ledger and reporting problems. |
| Document type | Identifies invoices, credit notes, self-invoices and integration documents. | Wrong document type affects reporting and reconciliation. |
| Dates and numbering | Controls issuance timing, VAT period and accounting sequence. | Late issuance or inconsistent numbering creates audit exposure. |
| Reference to orders, CIG/CUP or public procurement data | Often relevant for B2G invoices and public entities. | Public administration invoice rejection or payment delay. |
Domestic invoices and cross-border invoices are different
Italian domestic transactions and cross-border transactions must be separated. Domestic Italian e-invoicing is mainly about issuing and receiving invoices through SDI. Cross-border transactions often involve reporting data to the Italian Revenue Agency, even when the foreign counterparty does not issue an Italian electronic invoice.
This is why foreign companies should not ask only: “Do we have to issue an e-invoice?” They should also ask: “Does someone have to report this invoice through SDI or another Italian digital flow?” For example, an Italian customer receiving an invoice from abroad may have its own obligation to integrate or report the transaction, depending on the case.
Esterometro and cross-border reporting through SDI
The old idea of a separate periodic esterometro report has evolved into a more transaction-based workflow. For many cross-border operations, Italian operators transmit data through SDI using specific document types. This means that even when the foreign supplier does not issue an Italian e-invoice, the transaction may still enter the Italian digital reporting environment through the Italian counterparty.
For foreign companies, this matters in practice because Italian customers may request specific invoice details, correct VAT wording, reverse charge references or supplier information to allow them to report the transaction correctly. A foreign invoice that is acceptable in the supplier's country may still create problems for the Italian counterparty if it lacks the information needed for Italian VAT compliance.
When selling to Italian business customers from abroad, invoice wording and VAT treatment should be agreed before recurring invoicing begins. Otherwise the customer may ask for corrections after the invoice has already entered its Italian reporting workflow.
B2B, B2C and B2G invoices in Italy
Italian e-invoicing covers different transaction types, but each has its own operational features. B2B invoices depend heavily on the VAT status of the customer and the domestic or cross-border nature of the transaction. B2C invoices may still require e-invoicing when issued by Italian operators, although delivery to the consumer is handled differently from business recipient delivery. B2G invoices to public administrations have specific data requirements and rejection risks.
| Transaction | Practical focus | Foreign-company issue |
|---|---|---|
| B2B | VAT number, recipient code, VAT treatment and reverse charge analysis. | Italian customers often require precise invoice wording and data for their SDI reporting. |
| B2C | Consumer invoices may follow Italian electronic workflows, but delivery is different from B2B. | E-commerce businesses must coordinate invoices, receipts, marketplace data and VAT filings. |
| B2G | Public administration invoices require strict FatturaPA data and often CIG/CUP or order references. | Foreign suppliers to Italian public bodies need a dedicated workflow before issuing the first invoice. |
Does an Italian VAT number make e-invoicing mandatory?
An Italian VAT number is relevant, but it is not the only factor. Foreign companies often obtain an Italian VAT number because they store goods in Italy, import goods, sell through Amazon FBA, make domestic supplies, appoint a fiscal representative or need to recover VAT. This VAT position creates Italian compliance obligations, but the invoicing route still depends on the status of the operator and the transaction flow.
The practical recommendation is simple: when a foreign company obtains an Italian VAT number, it should not simply activate generic Italian invoicing software and start issuing every invoice through SDI. It should first map the transaction flows: Italian domestic sales, intra-EU movements, imports, exports, marketplace sales, B2B services, B2C e-commerce and internal stock transfers. Each flow may require different invoice codes, documents and reporting treatment.
Amazon, marketplaces and e-commerce
Marketplace sellers are a high-risk category because invoice data, VAT data and payment data are often fragmented. Amazon or another marketplace may provide order reports, VAT calculation reports, settlement reports, refund reports and stock movement reports. The Italian VAT advisor must reconcile these data with invoices, credit notes and VAT filings.
For sellers storing goods in Italy, Italian VAT registration may be required, but the e-invoicing implications still need to be checked by transaction type. Domestic B2B sales, B2C sales, marketplace-facilitated transactions, cross-border distance sales, stock movements and returns do not all follow the same logic. A software export is not a VAT analysis.
Digital archiving and document retention
Electronic invoicing does not end when an invoice is sent. The company must also consider compliant digital archiving. Italian e-invoices should be retained in a way that preserves authenticity, integrity, readability and retrieval over time. In practice, many companies use a certified provider, accounting software or the Revenue Agency services where available.
Foreign companies should avoid a common mistake: downloading only a PDF copy and treating it as the invoice archive. Where the XML invoice is the legal document, the archive must preserve the correct electronic file and related receipts or status messages. This is especially important when the company needs to support VAT deductions, defend invoices during checks or reconcile annual VAT positions.
Implementation checklist before issuing Italian e-invoices
Before starting Italian e-invoicing, the company should complete a practical setup review. This review should involve the Italian VAT advisor, the finance team, the ERP or invoicing software provider, the logistics or marketplace team and, where relevant, the Italian customer or public administration.
| Checklist item | Question to answer | Owner |
|---|---|---|
| Legal and VAT status | Is the company resident, established, VAT identified or non-resident only? | Tax advisor / legal team |
| Transaction mapping | Which flows are domestic, intra-EU, import, export, B2B, B2C or B2G? | Finance / operations |
| Software capability | Can the system generate valid FatturaPA XML and handle rejections? | IT / software provider |
| Recipient data | Are customer VAT numbers, tax codes, PEC addresses and recipient codes collected? | Sales admin / master data |
| VAT codes | Are taxable, non-taxable, exempt and reverse charge cases coded correctly? | Tax advisor / accounting |
| Archiving | Will XML files and SDI receipts be stored in a compliant digital archive? | Finance / provider |
| Approval workflow | Who checks unusual invoices before transmission? | Finance / tax advisor |
Common mistakes made by foreign companies
Most e-invoicing errors are not caused by an inability to create an XML file. They are caused by poor planning. Foreign companies often start invoicing before they have mapped transaction flows, collected customer recipient data, agreed VAT codes or clarified who will monitor SDI receipts and rejection notices.
| Mistake | Why it happens | Possible consequence |
|---|---|---|
| Assuming a PDF is the invoice | The foreign finance team is used to PDF workflows. | Missing legally relevant XML and SDI receipts. |
| Confusing VAT identification with establishment | The company has an Italian VAT number and assumes it is treated as Italian resident. | Wrong invoicing channel or incorrect VAT treatment. |
| Using generic VAT codes | ERP settings are designed for another country. | Incorrect VAT ledgers and inconsistent filings. |
| Ignoring SDI rejection notices | No one monitors the transmission channel. | Invoices may not be validly issued on time. |
| Not collecting Codice Destinatario or PEC | Customer master data is incomplete. | Delivery problems and manual follow-up. |
| Not archiving XML and receipts | The company keeps only PDFs or ERP images. | Weak evidence during VAT checks or audits. |
| Treating marketplace reports as invoices | Platform data is confused with formal invoice documents. | VAT reconciliation gaps and missing credit notes. |
How ISY supports foreign companies
ISY assists foreign companies with Italian e-invoicing as part of a wider tax and operational compliance workflow. The objective is not only to transmit XML files, but to make sure that the invoicing process is aligned with the company's VAT position, business model and recurring compliance obligations in Italy.
At the start of the engagement, ISY reviews the company's Italian activity: whether it has an Italian company, branch, fixed establishment, direct VAT identification or fiscal representative; whether it sells goods or services; whether it imports goods; whether it uses marketplaces or warehouses; and whether it invoices Italian public bodies, businesses or consumers.
ISY can coordinate e-invoicing with broader services such as VAT management in Italy, VAT representation, accounting services, tax compliance, payroll services and business support for foreign companies in Italy.
Need an Italian e-invoicing assessment?
If your company sells to Italian customers, has an Italian VAT number, works with Italian suppliers, imports goods into Italy or plans to open an Italian entity, ISY can review your transaction flow and indicate which e-invoicing, VAT and document controls are likely to be required.
Related guides and services
This guide is part of the ISY knowledge cluster for foreign companies operating in Italy.
Expert Review
This article has been prepared for foreign companies that need to understand Italian e-invoicing, SDI, FatturaPA XML, VAT registration, non-resident status, cross-border reporting and compliant invoice workflows in Italy.
Content reviewed by Mariacarla D'Amico
Chartered Accountant and Tax Advisor, with experience in VAT compliance, accounting and recurring tax workflows for companies operating in Italy.
Legal and cross-border context reviewed by Roberto De Santis
Attorney at Law admitted before the Italian Supreme Court, with experience in legal and contractual support for cross-border business matters.
Italian e-invoicing is only one part of operating in Italy. Foreign companies should also assess VAT registration, fiscal representation, company formation, payroll, accounting, legal structure, banking, imports and ongoing compliance.
→ Doing Business in Italy: Complete Guide for Foreign Companies
FAQ: Italian e-invoicing for foreign companies
Do foreign companies have to issue Italian electronic invoices?
It depends on their Italian status and transaction flow. A foreign company established in Italy or operating through an Italian entity may fall within Italian SDI obligations. A non-resident and non-established company is not automatically subject to the same rules merely because the transaction involves Italy.
What is SDI?
SDI, Sistema di Interscambio, is the Italian exchange system used to receive, check and route electronic invoices in the FatturaPA XML format.
Is a PDF invoice valid for Italian e-invoicing?
Where Italian e-invoicing is mandatory, a PDF is not the electronic invoice. It may be a courtesy copy, but the relevant document is the XML invoice transmitted through SDI.
What is FatturaPA?
FatturaPA is the structured XML format used in the Italian e-invoicing system, especially for invoices transmitted through SDI.
Does direct VAT identification in Italy create an SDI obligation?
Direct VAT identification is relevant but not decisive by itself. The company must verify whether it is established in Italy and how each transaction must be invoiced or reported.
What happens if SDI rejects an invoice?
The invoice should be corrected and transmitted again according to the applicable timing and procedural rules. Companies should monitor rejection notices carefully because an uncorrected rejected invoice may create issuance and accounting problems.
Do Italian public administrations require e-invoices?
Yes. Invoices to Italian public administrations follow specific electronic invoicing rules and often require additional administrative data, such as procurement references, office codes or project codes.
Can ISY help with Italian e-invoicing setup?
Yes. ISY can help foreign companies review their Italian VAT status, map invoice flows, coordinate SDI workflows, check VAT treatment and integrate e-invoicing with recurring VAT compliance in Italy.