Peppol vs SDI in Italy

Italy was the first big EU country to mandate B2B e-invoicing, but it did not use Peppol. It built SDI, a centralised national platform run by the tax authority. Peppol still has a role here, mostly as a bridge for foreign sellers.

By Peppol Validator · Last updated

Two networks, one country

Italy is the European e-invoicing oddity. Most EU countries with mandatory or upcoming mandates have either chosen Peppol as the channel (Belgium, Norway, the Nordics) or are building Peppol-aligned national systems (France, Germany). Italy did neither. It built SDI in 2014, made it mandatory for B2G that same year, and then rolled it out to all B2B transactions on 1 January 2019. SDI is the only legal channel for a domestic Italian invoice today. It is run by the tax authority and every invoice flows through it in real time.

That does not mean Peppol is absent in Italy. AgID, the Italian Digital Agency, is the Italian Peppol Authority and there are certified Italian Peppol Service Providers. Peppol coexists with SDI for cross-border flows, certain procurement use cases, and as a bridge for foreign sellers who already have Peppol but no SDI integration.

Practically, the question for any business that has to invoice an Italian customer is not which network do I use, it is how do I get my invoice into SDI. For Italian businesses, the answer is the SDI intermediary you use through your accounting software. For foreign sellers, the answer is often a Peppol-to-SDI bridge.

How SDI works

SDI is a five-corner system. The seller hands the invoice to its intermediary (corner 1 to corner 2), the intermediary submits it to SDI (corner 3), SDI validates and routes it to the buyer's intermediary (corner 4), which delivers it to the buyer (corner 5). SDI is the centre of the network and every document passes through it.

The format is FatturaPA, an Italian XML schema. FatturaPA is broadly aligned with EN 16931 but adds Italian-specific extensions: detailed VAT codes, support for ritenuta (withholding tax), the codice destinatario buyer routing code, and mandatory qualified electronic signature on B2G invoices. The seller signs the invoice (qualified e-signature) when required, packages it as a FatturaPA XML, and submits it to SDI through their intermediary.

SDI validates the document: schema check, signature verification, formal field checks, codice destinatario lookup. If valid, it routes the invoice to the buyer's intermediary and stores a copy. The Agenzia delle Entrate uses that copy for real-time VAT reporting; this is what makes SDI a five-corner / digital reporting system rather than just a delivery network. The buyer's intermediary delivers the FatturaPA file to the buyer's accounting system.

Every step is mandatory and SDI is the only valid route. There is no “PDF as fallback” the way there still is in many other countries. An Italian-to-Italian B2B invoice that does not go through SDI is not legally valid and will be rejected for VAT purposes.

Where Peppol fits

Even though SDI is mandatory inside Italy, Peppol is not absent. There are three main scenarios where Peppol matters in Italy:

  1. Cross-border invoices to Italian buyers. Foreign sellers, especially in countries with mature Peppol adoption (Belgium, the Netherlands, the Nordics), can send their invoices over Peppol BIS Billing 3.0. Italian Peppol Service Providers operate a bridge that converts the Peppol UBL invoice into FatturaPA and submits it to SDI on the recipient's behalf. From the foreign seller's point of view it is a normal Peppol delivery; from the Italian buyer's point of view it arrives through SDI like any other invoice.
  2. Cross-border invoices from Italian sellers. An Italian business that wants to invoice a Belgian, Dutch or Norwegian buyer in Peppol format can do so via a Peppol-capable intermediary, while still meeting the SDI obligation for the domestic-side reporting via the EsteroMeteo / TD-17 / TD-18 / TD-19 mechanisms.
  3. Public procurement and special use cases. AgID has specified Peppol for some procurement scenarios where an EN 16931-compliant invoice in UBL form is preferred over FatturaPA, particularly for cross-border procurement covered by EU Directive 2014/55/EU.

In all three cases the Peppol leg is real and certified, and the SDI leg is real and mandatory. They coexist rather than compete.

For foreign sellers: which route to pick

If you are a non-Italian business with Italian customers, you have three practical options:

  • Use a Peppol-to-SDI bridge provider. Send the invoice via your existing Peppol Access Point. The bridge provider converts to FatturaPA and submits to SDI for you. This is the path of least resistance if you already have Peppol capability.
  • Onboard directly with SDI through an Italian intermediary. Contract with an Italian SDI provider, generate FatturaPA documents, submit them through their channel. This is more direct but requires implementing FatturaPA in your accounting system or relying entirely on the intermediary's tooling.
  • If your sales to Italy are very low volume, talk to your Italian customer about their preferred route. Many large Italian buyers will accept Peppol via a bridge they have already set up; smaller customers may prefer that you use their own SDI provider.

Validate the Peppol leg of your Italian flow

Whether you reach Italy via a Peppol bridge or send Peppol cross-border to Italian buyers, the UBL invoice still has to pass EN 16931 and Peppol BIS schematron rules before the bridge converts it. Validate it for free, no signup.

Frequently asked questions

Is Peppol used in Italy?

Italy is on the Peppol network and AgID (the Italian Digital Agency) is the Italian Peppol Authority. But Italy does not use Peppol as its primary domestic invoicing channel. The Italian B2B and B2G e-invoicing mandate runs on SDI (Sistema di Interscambio), a centralised five-corner system operated by the Agenzia delle Entrate. Peppol is used in Italy for cross-border invoices, for some procurement scenarios, and as a bridge for foreign trading partners who do not want to connect directly to SDI.

What is SDI?

SDI (Sistema di Interscambio, the Interchange System) is the centralised electronic invoicing platform operated by Italy's tax authority, the Agenzia delle Entrate. Every business invoice issued in Italy has to go through SDI. The seller submits the invoice to SDI in the FatturaPA XML format, SDI validates it, applies the seller's qualified digital signature check, and forwards it to the buyer. SDI is also where the data is captured for VAT reporting in real time. It pre-dates Peppol's B2B push by several years and has been live for B2G since 2014 and for all B2B since 1 January 2019.

What is the difference between Peppol and SDI?

Peppol is a four-corner network: seller, sender Access Point, receiver Access Point, buyer. There is no central platform in the middle. SDI is a five-corner system: seller, seller intermediary, SDI itself, buyer intermediary, buyer. SDI is the central authority that all invoices must pass through. Peppol uses Peppol BIS Billing 3.0 (UBL 2.1) as the format. SDI uses FatturaPA, an Italian XML schema based on EN 16931 but with country-specific extensions and a digital signature requirement. Peppol is international and decentralised. SDI is national and centralised.

When did Italy mandate e-invoicing?

Italy was the first major EU country to mandate e-invoicing. B2G via SDI became mandatory on 6 June 2014. The B2B mandate followed on 1 January 2019, making Italy the first EU member state with a fully mandatory B2B electronic invoicing regime. The mandate covers virtually all VAT-registered businesses with the exception of some small forfettario taxpayers who were brought in via subsequent amendments. By 2025, e-invoicing through SDI was the only legal way to invoice in Italy for the vast majority of business transactions.

Can I use Peppol to invoice an Italian customer from another country?

It depends on the route. Several Italian Peppol Service Providers act as a bridge: you send the invoice over Peppol, they translate it from Peppol BIS Billing 3.0 / UBL into FatturaPA and submit it to SDI on behalf of the recipient. From the foreign seller's perspective the workflow looks like a normal Peppol delivery; from the Italian buyer's perspective the invoice arrives via SDI as if it had been native FatturaPA. This is the most common path for foreign vendors who already have Peppol capability and do not want to onboard directly with SDI.

Do I need both a Peppol Access Point and an SDI intermediary?

If you operate in Italy and your customers are mainly Italian, the answer is usually no: you only need an SDI intermediary (often your accounting software vendor or a dedicated SDI provider), and the rest of your trading partners can be reached via the same provider with a Peppol bridge. If you are a foreign vendor with occasional Italian customers, the easiest path is the reverse: keep your Peppol Access Point and pick a provider that handles the Peppol-to-SDI bridge. Either way, you do not need to maintain two separate technical stacks.

What is FatturaPA?

FatturaPA is the Italian XML invoice format that SDI accepts. It is based on the Italian implementation of the EN 16931 European standard but with country-specific extensions: detailed VAT breakdown by Italian VAT codes, support for the Italian withholding tax (ritenuta), the codice destinatario (buyer SDI code) routing field, mandatory qualified digital signature for B2G, and other Italian peculiarities. FatturaPA is not interchangeable with Peppol BIS Billing 3.0 / UBL: a translator is needed to convert between the two formats, which is what Italian Peppol bridges do.

What is the Italian Peppol Authority?

AgID (Agenzia per l'Italia Digitale, the Italian Digital Agency) is the Italian Peppol Authority. It certifies Italian Peppol Service Providers and represents Italy in OpenPeppol governance. AgID is a separate body from the Agenzia delle Entrate, which runs SDI. The two coexist: AgID covers Peppol, the Agenzia delle Entrate covers SDI, and several Italian providers are accredited with both so that documents can flow between the networks.