← All guides · Country mandates
Italy's SdI e-invoicing: the mandate that has run since 2019
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
Italy is Europe's proof that structured invoicing works at national scale: B2B e-invoicing through the SdI platform has been mandatory since 2019, and in the words of this product's mandate table, a plain PDF is not an invoice. If you invoice Italian business clients, the structured invoice is not a future requirement — it is the only kind of invoice their system has accepted for years.
What is SdI?
SdI (Sistema di Interscambio) is Italy's national invoice exchange platform: B2B invoices are issued in the structured FatturaPA format and routed through SdI to the buyer. EInvoice Translator's mandate table models Italy as: channel SdI (FatturaPA), phase 2019-01-01 for all businesses, basis 'B2B e-invoicing via SdI mandatory since 2019; a plain PDF is not an invoice' — and the checker returns structured required for Italian buyers at any current date.
The oldest mandate, and what it proved
Italy did in 2019 what the rest of Europe is doing between 2026 and 2030: it made the structured invoice the only invoice. Every B2B invoice is created in the national format, transmitted through SdI, validated by the platform, and delivered to the buyer from there. The experiment's results are why ViDA exists — structured invoicing at scale reduced the VAT gap and the manual handling that PDFs impose, so the model was generalised.
For a supplier, Italy's maturity cuts both ways. There is no transition to hide in: Italian clients' processes assume structured input completely. But there is also no ambiguity: the requirement is settled, the client's finance team knows exactly what it needs, and an invoice with clean data flows through a system refined by years of volume.
FatturaPA and SdI: your client's world
FatturaPA is the structured format SdI carries; SdI is the exchange that validates and routes it, using the recipient's code or certified email address to deliver. Your Italian client lives inside that system: their invoices arrive from SdI, are booked from its data, and are archived as structured files. Anything you send outside that flow is, to their process, a picture of an invoice that someone must reconcile by hand.
This product produces EN 16931 invoices — UBL 2.1 XML and Factur-X PDF — and its mandate model is honest about channels: Italy's channel is SdI/FatturaPA, a national format, not the UBL file itself. What transfers completely is the data discipline: the parties, identifiers, line-level VAT treatment and reconciled totals that any platform demands. Agree with your client how your supply is issued into their SdI flow; bring invoice data that would pass validation anywhere.
What 'a plain PDF is not an invoice' means in practice
It means the PDF has no operative status. If you email a PDF to an Italian business client, their payable process cannot book it as the invoice — the invoice, for their system and their tax position, is the structured document delivered through SdI. Your PDF becomes correspondence about an invoice that, in their world, does not yet exist. Payment terms do not run on correspondence.
This is the sharpest version of the pattern now spreading across Europe, and the reason the acceptance checker's Italian verdict is unconditional: structured required, at every current date, for every buyer size. When clients in other countries begin saying the same sentence — Belgium's systems already do — Italy is the preview of how completely the expectation settles in.
Invoice data discipline, Italian style
Years of platform validation have made Italian finance teams precise about invoice data, and suppliers feel it: complete legal names and addresses, correct VAT identifiers, line-level detail, and totals that reconcile exactly. SdI validates on intake; errors return as rejections with codes, and the correction cycle runs through the platform, not around a clerk's desk.
That is the environment the EN 16931 rules rehearse you for. The validator here checks the same families — presence, codes, VAT category-rate agreement, cross-border identifiers, BR-CO arithmetic — before your invoice goes anywhere. An invoice that passes these checks carries the data quality SdI-era clients expect, whatever channel finally delivers it. Sloppy data fails in Rome exactly as it fails in Brussels; clean data is the universal adapter.
Cross-border supplies to Italian clients
Cross-border B2B services to Italy typically run under reverse charge: your lines category AE at 0%, the buyer's VAT identifier on the invoice, yours likewise — the identifier pair validation requires for cross-border reverse charge. Italian buyers are accustomed to stating their identifiers and recipient details precisely; return the courtesy by recording them exactly in your client file, character for character.
Also expect the conversation about how the invoice enters their SdI flow to be specific and early — Italian clients raise it at onboarding, not at payment time. Have your validated invoice data ready and the conversation is short. The suppliers who struggle in Italy are the ones who treat the structure as paperwork after the sale; in Italy, the structure is the sale's completion.
Lessons Italy holds for the rest of your client list
Italy demonstrates the end-state every mandate in the table is heading toward: structured-only, platform-validated, PDF as mere copy. Belgium arrived in 2026, Poland and France are mid-journey, Germany and Spain phase through 2027–2028, and ViDA sets the intra-EU floor at 1 July 2030. A supplier who learns to invoice the Italian way — data first, validated always — is not preparing for one country; they are preparing for the decade.
So treat your Italian invoices as the template for your whole practice. Convert through validation, keep identifiers exact, compute totals from lines, archive the structured file as the operative record. When the next client's country crosses its date, your process will not notice — and neither will your cash flow.
Invoicing Italian clients: 5 steps
- Accept the premise: in Italy the structured invoice is the invoice — a PDF alone does not exist for your client's system.
- Ask the client how your supply is issued into their SdI flow and what recipient details they require.
- Build the invoice data to validation standard: complete parties, exact VAT identifiers, per-line VAT treatment.
- Convert and validate here so totals and rules are proven before the invoice travels.
- Archive the structured invoice data as the operative record alongside any readable copy.
Worked example: the PDF that did not exist
A photographer invoices an Italian publisher EUR 900.00 for a shoot — reverse charge, category AE, payable EUR 900.00 — and emails a tidy PDF. The publisher's accounts team replies that no invoice has been received: their process books from SdI-delivered structured invoices, and the PDF is correspondence, not an invoice. The payment clock has not started.
The photographer rebuilds the same EUR 900.00 invoice through the converter — validated data, both VAT identifiers present, totals reconciled — and issues it through the route the publisher specifies for their SdI flow. This time the invoice exists in the client's system on arrival. Same work, same fee: in Italy, format is not presentation, it is existence.
Frequently asked questions
Since when is e-invoicing mandatory in Italy?
Since 2019 for B2B — the mandate table here models Italy's phase as 2019-01-01 for all businesses, via SdI (FatturaPA).
Is a PDF invoice valid in Italy?
No — the mandate basis recorded here is explicit: a plain PDF is not an invoice. The operative invoice is the structured document delivered through SdI.
Does this product send invoices through SdI?
No. It builds and validates your EN 16931 invoice (UBL XML and Factur-X PDF) and models Italy's mandate in the checker. SdI issuance runs through your client's specified route, with invoice data held to validation standard.
What data does SdI-era invoicing demand?
The same families this validator checks: complete parties and addresses, exact VAT identifiers, line-level VAT categories and rates, and totals that reconcile under the BR-CO rules.
Why does Italy matter if I have no Italian clients?
It is the end-state preview: structured-only invoicing, platform validation, PDFs as copies. Every other mandate in the table is travelling to the same place.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- PDF invoice vs e-invoice: why a PDF is no longer an invoice in much of the EU
- ViDA 2030: intra-EU B2B e-invoicing becomes mandatory on 1 July 2030
- Poland's KSeF e-invoicing mandate: dates, phases and what suppliers must send
- Cross-border invoices: when seller and buyer VAT identifiers are required
- Belgium's Peppol e-invoicing mandate: what B2B suppliers must do from 2026