Electronic invoice in Italy
Italy operates a comprehensive clearance system where all B2G, B2B and B2C invoices must be transmitted through the government platform Sistema di Interscambio (SdI).
Italy operates the most mature mandatory e-invoicing regime in the European Union. Every domestic invoice — B2B, B2G and B2C alike — must pass through Sistema di Interscambio (SdI), the central platform run by the Agenzia delle Entrate. An invoice that SdI rejects is treated as never having been issued.
This is a centralised clearance model, not a Peppol network. Peppol exists in Italy as an interoperability layer for public procurement and cross-border exchange, but it does not replace SdI for tax purposes. Anyone planning an Italian rollout needs to design around that distinction from the start.
Italy started earlier than anyone else in the EU and has been extending scope ever since. The mandate is fully in force — what remains ahead is alignment with the EU framework.
Central government from June 2014, all remaining public bodies including regional and local authorities from March 2015. All supplier invoices to public administration route through SdI.
Invoices between parties resident or established in Italy may be issued only in electronic form through SdI. The same applies to consumer invoices where an invoice is required or actually issued.
The old quarterly esterometro return is replaced by transaction-by-transaction reporting through SdI for dealings with parties not established in Italy.
The flat-rate scheme (regime forfettario) and the remaining small taxpayers are brought in, regardless of the turnover thresholds that previously exempted them. Scope is now effectively universal.
EU-wide e-invoicing and Digital Reporting Requirements apply to intra-community B2B transactions, on the European standard rather than on FatturaPA.
Existing national real-time reporting systems, Italy's included, must be brought into line with the European model. How far FatturaPA converges towards EN 16931 is the open question of the decade.
SdI technical specifications are revised periodically — version 1.9.1 took effect on 15 May 2026. Schema updates are not optional: an invoice built against a withdrawn version will be rejected. Confirm with your provider that the current specification is implemented.
The flow is deliberately linear: supplier → SdI → recipient. There is no direct exchange between trading partners for in-scope transactions, and no way to agree a bilateral alternative.
Generated in your ERP or through a provider, in the national schema. Not UBL, not CII, not PDF.
Structural and formal checks run centrally. A failed invoice comes back with a rejection notice and is legally not issued — it must be corrected and resubmitted within the statutory window.
Routing uses the recipient's codice destinatario or certified email address (PEC). Where neither is available, the invoice is made available in the recipient's tax portal.
SdI issues machine-readable notices for acceptance, delivery, failed delivery and rejection. These receipts are the evidence that the invoice exists.
Is this clearance or reporting? Both, in effect. SdI does not approve the commercial substance of the transaction, but it does decide whether the invoice legally exists — which puts Italy firmly in the clearance camp rather than alongside the Peppol reporting models used in Belgium or Slovakia.
The test is whether you are resident or established in Italy. A non-established business with only an Italian VAT registration is outside the domestic issuing mandate — but its Italian counterparties will still report the transaction through SdI, and a permanent establishment brings you fully into scope.
This is where most international implementations go wrong. Italy has a national format, not a national flavour of the European standard.
The mandatory format for every domestic invoice through SdI. A distinct national XML schema — not a syntax of EN 16931.
Used for European B2G invoices and Peppol exchange. AgID publishes Italian Peppol BIS Billing specifications with national rules and translation schemes to FatturaPA.
None of these substitute for SdI: a PDF by email, a UBL file sent directly, a CII file, a Peppol invoice without SdI integration, or proprietary EDI straight to the buyer. Any of them may exist alongside as a commercial document, but for an in-scope domestic transaction the only valid invoice is the FatturaPA file accepted by SdI.
Transactions with parties not established in Italy are not invoiced through SdI — but their data is reported through it, one transaction at a time. This replaced the old quarterly esterometro filing in July 2022.
Outbound sales are reported on issuing, purchases through a self-billing or integration document within the statutory deadline. In practice this means an Italian business runs two parallel data flows — full invoices domestically, structured reports across the border — and both have to be right.
Peppol matters in Italy, but not in the way it does elsewhere. It is an interoperability layer for public procurement and international exchange; it is not the tax compliance channel.
A foreign EU-certified Access Point can exchange Peppol invoices with Italy without additional national onboarding. AgID has confirmed this explicitly.
Operating as an AP or SMP within the Italian domain, or handling Italian-specific scenarios such as Peppol receipts for public administration, does require separate AgID qualification.
The point that catches people out: Peppol certification does not grant access to SdI. A direct machine-to-machine SdI channel is a separate accreditation with its own technical and contractual requirements. Most providers therefore reach SdI through an accredited intermediary rather than building their own channel.
The penalty regime was reformed, and much of the commentary online still quotes the old figures. These are the current rules under Article 6 of Legislative Decree 471/1997.
The base sanction for breaching documentation and registration obligations on VAT-taxable transactions.
If the breach had no effect on the correct determination of VAT, the fixed range applies instead.
The heavier consequence is not the fine. An in-scope invoice issued outside SdI is deemed not to have been issued at all — which puts your customer's input VAT deduction, and the commercial relationship, at risk.
Invoices must be retained for ten years. Italy goes further than most countries here: electronic retention has to follow the certified digital preservation rules — conservazione a norma — set out in the national digital administration framework and AgID guidelines.
Because the tax authority holds a copy, retention feels solved — but the legal obligation still sits with the business. Deciding early whether preservation runs through the state service or a provider avoids an awkward conversation during an audit.
As a certified Peppol Access Point we cover the European side of Italian invoicing and connect your systems to the national channel:
Italy is the reference case for mandatory e-invoicing in Europe: universal scope since 2024, B2C included, and a central platform that decides whether an invoice legally exists. Businesses trading in Italy have had years to adapt, and the operational questions have shifted from "how do we comply" to "how do we keep up with schema versions".
The strategic tension is the format. FatturaPA is a national schema, not a European syntax, so an Italian implementation cannot simply reuse a Peppol pipeline. The workable approach is a canonical internal model on EN 16931, with FatturaPA generated on the Italian output layer — which is also the architecture that will survive the ViDA convergence expected between 2030 and 2035.
Two mistakes account for most failed Italian rollouts: assuming Peppol certification opens SdI, and treating retention as solved because the tax authority holds a copy. Neither is true, and both surface late.