The 2026 E-Invoice Formats

E-invoicing began as a simple way to end the mess of paper invoices. Lost documents, typing mistakes, late payments, and tax fraud cost governments billions every year. 

By 2026, the scale has exploded. Systems now handle 125 billion invoices a year, according to recent reports. The EU's ViDA rules push even harder for digital reporting. Product managers at software firms deal with a tangle of invoice types: B2B, B2G, B2C. Add in formats like UBL or CII, plus country-specific codes, and it's easy to see why wrong choices lead to trouble. 

Why Picking the Right E-Invoice Format Matters

E-invoice formats are not interchangeable. Each transaction type, B2G, B2B, or B2C, has specific structural requirements, and government systems validate against them automatically. A mismatch means an instant rejection, not a manual review.

The reasons are technical. Italy's SdI only accepts FatturaPA-structured files. Germany's public sector routing requires an 11-digit Leitweg-ID in the correct field. France's Chorus Pro checks both the format profile and sender registration. A missing VAT identifier or incorrectly coded invoice type fails validation the same way.

Wrong format choices also break ERP system integrations and create reconciliation gaps. Checking format compatibility, syntax, and routing IDs before submission can reduce rejections by up to 80%.

E-invoice Format Requirements by Transaction Types

The type of transaction sets the rules. Here's what fits each one.

B2G (Business-to-Government): These face the toughest demands. Governments require formats that match EN16931 standards, like UBL or CII, tied to exact country routing IDs. Germany's Leitweg-ID routes to the right authority. Italy's SdI system uses FatturaPA and rejects anything off. France's PDP does the same. One small error in meaning or structure, and the invoice fails instantly.

B2B (Business-to-Business): More room to move here. UBL or CII works well over Peppol or EDI networks. These handle extras such as multiple currencies, discounts, large volumes, and custom terms between partners.

B2C (Business-to-Consumer): No need for heavy B2B details. Focus on easy payments and data privacy under GDPR.

E-Invoice Formats and Compliance Standards

EN16931 lays down the base rules for Europe, key data fields and meanings that all must follow. It's required for B2G and spreading to B2B. Here are the formats that meet it:

Country Codes and Routing IDs

Every country adds its own codes for invoice kinds, like standard bills, credit notes, or corrections, plus tax rules and paths to send them.

In 2026, with ViDA and mandates everywhere, these details matter more than ever. Teams often spend hours chasing updates.Here's a close look at key examples:

• Malaysia: Runs 45 types through MyInvois. Codes cover VAT invoices, debit/credit notes, and self-billed ones, all linked to GST rules.
• Poland: KSeF sorts types like JPK_FA for regular invoices, VAT fixes, and advances. Each gets a schema ID for the central system.
• Spain: SII tracks "tickets" and series, T01 for simple invoices, R01 for changes. These feed real-time VAT records.
• France: Factur-X needs profile codes (full EXTENDED for EN16931) and Chorus Pro IDs for government sends.
• Germany: Pair ZUGFeRD profiles with a valid Leitweg-ID routing ID. Miss it, and the Bundesnetzagentur blocks you.
• Italy: SdI uses FatturaPA for all invoices, B2B, B2C, and B2G, each requiring the correct Document code. Wrong code means auto-reject.
• Others on the Rise: Latvia's RTIR, Hungary's Online Invoice bolt each type code onto UBL or CII. 

Manual tracking fails fast as rules shift. A single API with built-in libraries changes that.

Unify Global E-Invoicing with DDD Invoices API

The 2026 e-invoicing world mixes B2B, B2G, B2C rules with UBL, CII, hybrids, EN16931 needs, and ever-changing country codes. 

DDD Invoices stands as the proven, API-first platform trusted by global SaaS providers, ERPs, and enterprises. 

With one secure integration, it automatically handles format conversions, real-time validation APIs, CTC/Peppol network routing, and centralised code updates, eliminating routing errors, ERP gaps, and rejection risks while ensuring ViDA-ready scalability.

DDD Invoices delivers uninterrupted compliance as regulations evolve. Design once with our unified API, then issue, receive, and archive flawless e-invoices worldwide. 

FAQ

What sets UBL apart from CII?

UBL packs detailed XML for Peppol B2B flows across borders and full info on parties and items. CII stays lean for chains and blends, focusing on speed with core EN16931 rules.

How do ViDA and EN16931 change things in 2026?

EN16931 locks in EU data standards for B2G buys via profiles like Peppol BIS or FatturaPA. ViDA pushes it to B2B, making formats work across countries and cutting failed sends.

Which type has the hardest rules?

B2G. It forces exact syntax like UBL/CII with IDs such as Germany's Leitweg-ID or Italy's SdI/FatturaPA. One miss means an instant block, far stricter than B2B networks or basic B2C.

Why do country codes cause so many e-invoice rejections, and how can teams avoid them?

Country codes define invoice types (like bills vs. credits), tax rules, and routing paths; mismatches lead to instant blocks, as seen in Malaysia's 45 MyInvois types or Poland's KSeF schemas. Teams avoid this by using APIs like DDD Invoices, which pull live code libraries and auto-map them to formats, preventing fines and ERP disruptions.