Europe has a common standard for electronic invoices. So why does implementation still feel like an alphabet soup?
EN 16931 defines the European semantic invoice model. UBL 2.1 and UN/CEFACT CII provide XML syntaxes.
Sounds straightforward? Unfortunately, that’s only the beginning.
National specifications, XML formats, PDF/XML hybrids, delivery networks, government platforms and tax reporting systems create a surprisingly fragmented landscape.
The European e-invoicing alphabet soup
A quick, non-exhaustive overview:
- Peppol BIS Billing 3.0 — EN 16931-based invoice specification using UBL. The Peppol network provides the exchange infrastructure.
- XRechnung (Germany) — National EN 16931 specification supporting UBL and CII.
- ZUGFeRD (Germany) — Hybrid PDF/A-3 invoice with embedded CII XML.
- Factur-X (France) — Essentially the same hybrid approach as ZUGFeRD.
- France: UBL and CII — Additional structured formats used alongside Factur-X.
- Belgium — Peppol BIS Billing 3.0 for mandatory domestic B2B e-invoicing.
- Italy: FatturaPA — National XML format exchanged through the central SdI platform.
- Poland: KSeF / FA(3) — National XML invoice structure and government platform.
- Romania: RO e-Factura — National RO_CIUS rules and central exchange system.
- Spain: Facturae — National XML invoice format, with FACe for public-sector invoicing.
- Denmark: OIOUBL — National UBL-based format, with NemHandel infrastructure.
- Finland: Finvoice / TEAPPSXML — Established national XML invoice formats.
- Austria: ebInterface — National XML invoice standard.
- Netherlands: NLCIUS / SI-UBL — National specifications alongside Peppol BIS.
- Slovenia: e-SLOG — National structured invoice format.
- Czechia: ISDOC — National electronic invoice format.
- Norway: EHF — National e-invoicing specifications closely aligned with Peppol.
And the list continues.
Then add NAV Online Számla (Hungary), myDATA (Greece), SAF-T (Portugal) and VERI*FACTU (Spain).
These are primarily tax reporting or invoice-recording systems rather than interchangeable e-invoice formats. Yet they frequently appear in the same discussions.
Where is the real problem?
These names don’t even describe the same technical layer.
EN 16931 defines invoice semantics. UBL and CII define XML structures. Factur-X combines PDF and XML. Peppol provides business document specifications and a delivery network. SdI and KSeF are government exchange platforms.
And every country may introduce additional validation rules, identifiers, obligations and deadlines.
Producing a technically valid XML invoice does not automatically mean it can be accepted, delivered or processed in another country.
Europe is moving toward interoperability, but the practical implementation remains complex.
Where does PLslash fit today?
At PLslash, our current focus is Factur-X and ZUGFeRD processing directly inside Oracle Database.
Our PL/FACTUR component supports:
- Generating and importing CII invoice XML
- EN 16931 and supported Factur-X profile validation
- Embedding XML into existing PDF/A-3B invoices
- Pure Oracle PL/SQL integration
Combined with PL/PDF for document generation and PL/SIGN for digital signatures, it provides an Oracle-native foundation for hybrid electronic invoicing.
We do not claim to support every national standard or provide a universal Peppol gateway today. There is still plenty of work ahead.
Learn more about PL/FACTUR:
#eInvoicing #EN16931 #FacturX #ZUGFeRD #Peppol #Oracle #PLSQL
