Country deep dive
Italy has the longest continuous track record of any e-invoicing regime in the EU — the interesting news today is schema maintenance, not a new mandate.
Italy pioneers e-invoicing for government suppliers, establishing the technical infrastructure, XML format, and clearance model that would later extend to the entire domestic economy.
Every domestic invoice, regardless of transaction type or business size, must pass through SDI — making Italy the most mature e-invoicing system in Europe, years ahead of France, Germany, or Poland.
The Agenzia delle Entrate issues an updated technical specification: revised code lists, tighter validation controls, and updated field definitions.
From this date, the SDI rejects any invoice that doesn't conform to the new specification — a firm compliance milestone, not a soft target, given SDI's zero-tolerance validation model.
FatturaPA predates EN 16931 entirely — it's Italy's own schema, not a national implementation of the European standard.
Don't assume EN 16931 tooling built for France, Germany, or Poland will map cleanly onto FatturaPA — the schema has its own lineage and its own rules.
The most common rejection cause across every source on FatturaPA is the same: an invalid Codice Fiscale or Partita IVA on either party. Validate these before anything else.
Unlike Poland's KSeF or Croatia's fiscalisation model, Italy requires the invoice XML itself to be digitally signed — this sits at the document level, not just the transport layer.
"Conservazione sostitutiva" (digital preservation) is a distinct legal regime from simple file storage — it has its own integrity and accessibility requirements under Italian law.
SDI is a true clearinghouse: an invoice sent directly to a buyer, bypassing SDI, simply has no legal validity in Italy.
Every invoice moves through the same sequence:
The full cycle typically completes in seconds to minutes, though SDI formally allows up to 5 days for processing.
Non-Italian companies typically obtain a Codice Destinatario through an intermediary or their ERP's SDI connectivity module, rather than registering directly with the Agenzia delle Entrate.
Build your pipeline to handle both receipt types explicitly — a Notifica di Scarto means the invoice was never legally issued at all, not just delayed.
These document types absorbed the old standalone "Esterometro" reporting system — it's now fully integrated into SDI rather than a separate filing.
Since Italy's system has run for over a decade, most of the "registration" work is really about choosing the right channel and getting the technical detail right.
Italian businesses can register directly with the Agenzia delle Entrate via the Fatture e Corrispettivi portal. Non-Italian businesses typically go through an intermediary or their ERP's SDI module instead.
Validate against the current schema specifically — the 15 May 2026 cut-over means anything still targeting an older version will be rejected outright.
Use XAdES or CAdES (.p7m) format — this is a document-level requirement that applies before transmission, not something SDI adds on your behalf.
Pick from PEC, web upload, SFTP, or SDICoop web services based on your volume and existing infrastructure — SDICoop suits higher-volume automated integrations best.
Set up workflows to catch Notifica di Scarto rejections quickly (check Codice Fiscale/Partita IVA validity first) and to confirm Ricevuta di Consegna delivery for every invoice sent.
This is a distinct digital preservation regime under Italian law — confirm your archiving solution meets its specific integrity and accessibility requirements, not just general file storage.
Build the 12-day reporting window into your process for services from abroad and goods from EU/non-EU sources.
Italy separates substantive VAT violations from purely formal ones — the two carry very different consequences.