E-Invoicing in the EU: What It Means, Why It Matters, and What's Changing

What Is E-Invoicing?

E-invoicing — short for electronic invoicing — refers to the exchange of invoice data in a structured, machine-readable format between the seller's and the buyer's systems.

A PDF attached to an email is not an e-invoice. Neither is a scanned paper invoice. These are electronic documents, but they are not structured data. A human can read them; a computer cannot reliably extract their contents without OCR or manual data entry.

A proper e-invoice is typically an XML or JSON file that follows a defined standard. It contains all the fields a traditional invoice would — supplier, customer, line items, amounts, VAT, payment terms — but in a format that accounting software, ERP systems, and tax authorities can process automatically.

The distinction matters because the EU is progressively mandating that businesses exchange invoices in these structured formats. The goal is to reduce fraud, improve tax collection, close the VAT gap, and modernise business-to-business transactions across the single market.

Why Is the EU Pushing E-Invoicing?

The EU loses an estimated €60 billion per year to VAT fraud. Paper and PDF invoices are easy to fabricate, difficult to cross-reference at scale, and invisible to tax authorities until an audit occurs.

Structured e-invoices solve several problems at once:

• Real-time visibility — Tax authorities can monitor invoice data as transactions occur, rather than waiting for quarterly or annual filings
• Automated validation — Invoices can be checked for errors, duplicate numbers, and incorrect VAT treatment before they enter the system
• Reduced processing costs — The European Commission estimates that e-invoicing saves businesses between €1 and €3 per invoice in processing costs compared to paper or PDF workflows
• Interoperability — A German freelancer's invoice can be automatically imported into a Spanish client's accounting software without manual re-keying

The EU has been working toward this through the European standard EN 16931, which defines a common semantic data model for e-invoices. Individual member states are now implementing national mandates based on this standard, each with their own timelines and additional requirements.

The European Standard: EN 16931

At the foundation of EU e-invoicing sits EN 16931, a standard published by the European Committee for Standardization (CEN) in 2017.

EN 16931 defines:

• The required and optional data fields for an invoice (seller, buyer, line items, tax, payment details, etc.)
• The relationships between those fields
• Business rules for validation

It does not define a file format. Instead, it specifies two official syntaxes:

1. UBL 2.1 (Universal Business Language) — An OASIS standard widely used internationally
2. CII (Cross Industry Invoice) — A UN/CEFACT standard

Both are XML-based. An invoice that conforms to EN 16931 and uses either syntax is considered a valid European e-invoice.

In practice, most EU countries and the Peppol network have converged on UBL 2.1 as the primary syntax.

Key E-Invoice Formats in the EU

While EN 16931 provides the common foundation, several specific formats have emerged across member states and trading networks.

Peppol BIS Billing 3.0

Peppol (Pan-European Public Procurement OnLine) is both a standard and a delivery network. It was originally developed for public procurement but is increasingly used for B2B transactions.

• Based on UBL 2.1 with additional Peppol-specific business rules
• Each participant has a Peppol ID used to route invoices through the network
• Invoices are exchanged through certified Access Points, similar to how email flows through SMTP servers
• Supported across all EU and EEA countries, plus Singapore, Australia, and others

For cross-border invoicing within the EU, Peppol is the closest thing to a universal standard.

XRechnung (Germany)

XRechnung is Germany's national e-invoice format, maintained by KoSIT (Koordinierungsstelle für IT-Standards).

• Conforms to EN 16931 with German-specific business rules (additional validations, required fields)
• Supports both UBL 2.1 and CII syntaxes
• Mandatory for business-to-government (B2G) invoicing since November 2020
• Being extended to B2B: German businesses must be able to receive e-invoices from January 2025, and must send them from January 2027

XRechnung invoices can be transmitted via Peppol, email, or dedicated portals.

Factur-X / ZUGFeRD (France / Germany)

Factur-X (France) and ZUGFeRD (Germany) are the same specification under different names. They take a hybrid approach:

• A PDF/A-3 document contains the human-readable invoice
• An XML file (CII syntax) is embedded inside the PDF as an attachment

The result is a single file that works for both humans and machines. A recipient without e-invoicing software sees a normal PDF. A recipient with compatible software extracts the XML and processes it automatically.

Factur-X/ZUGFeRD defines several profiles ranging from basic (minimal structured data) to extended (full EN 16931 compliance):

For businesses already generating PDFs, Factur-X/ZUGFeRD is often the most practical first step toward e-invoicing compliance.

FatturaPA (Italy)

Italy was the first EU country to mandate B2B e-invoicing, starting in January 2019.

• All invoices between Italian businesses must be transmitted through the SDI (Sistema di Interscambio), operated by the Italian tax authority
• The format is FatturaPA, an Italian-specific XML schema
• Invoices are validated in real-time by the SDI before being delivered to the recipient

Italy's system is often referenced as a model for other member states considering real-time reporting requirements.

Country-by-Country Timeline

E-invoicing mandates are rolling out at different speeds across the EU. The following table summarises the current state as of early 2026:

The trend is clear: mandatory B2B e-invoicing is expanding from early adopters (Italy, Romania) to the largest economies (Germany, France, Spain, Poland). The European Commission's ViDA (VAT in the Digital Age) proposal aims to establish an EU-wide framework by 2030.

What Does an E-Invoice Actually Look Like?

Under the hood, a UBL e-invoice is an XML document. A simplified example:

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
  <ID>INV-2026-042</ID>
  <IssueDate>2026-03-04</IssueDate>
  <DueDate>2026-04-03</DueDate>
  <InvoiceTypeCode>380</InvoiceTypeCode>
  <DocumentCurrencyCode>EUR</DocumentCurrencyCode>

  <AccountingSupplierParty>
    <Party>
      <PartyName><Name>Freelance Studio GmbH</Name></PartyName>
      <PostalAddress>
        <CityName>Berlin</CityName>
        <Country><IdentificationCode>DE</IdentificationCode></Country>
      </PostalAddress>
      <PartyTaxScheme>
        <CompanyID>DE301234567</CompanyID>
        <TaxScheme><ID>VAT</ID></TaxScheme>
      </PartyTaxScheme>
    </Party>
  </AccountingSupplierParty>

  <AccountingCustomerParty>
    <Party>
      <PartyName><Name>Client Corp S.L.</Name></PartyName>
      <PartyTaxScheme>
        <CompanyID>ESB12345678</CompanyID>
        <TaxScheme><ID>VAT</ID></TaxScheme>
      </PartyTaxScheme>
    </Party>
  </AccountingCustomerParty>

  <PaymentMeans>
    <PaymentMeansCode>58</PaymentMeansCode>
    <PayeeFinancialAccount>
      <ID>DE89370400440532013000</ID>
    </PayeeFinancialAccount>
  </PaymentMeans>

  <TaxTotal>
    <TaxAmount currencyID="EUR">190.00</TaxAmount>
  </TaxTotal>
  <LegalMonetaryTotal>
    <TaxExclusiveAmount currencyID="EUR">1000.00</TaxExclusiveAmount>
    <PayableAmount currencyID="EUR">1190.00</PayableAmount>
  </LegalMonetaryTotal>

  <InvoiceLine>
    <ID>1</ID>
    <InvoicedQuantity unitCode="HUR">10</InvoicedQuantity>
    <LineExtensionAmount currencyID="EUR">1000.00</LineExtensionAmount>
    <Item><Name>Web Development</Name></Item>
    <Price>
      <PriceAmount currencyID="EUR">100.00</PriceAmount>
    </Price>
  </InvoiceLine>
</Invoice>

Note the payment means code 58 — this is the code for SEPA credit transfer, which maps directly to the bank transfer details (including IBAN) that most EU invoices already include.

The data is the same information that appears on any invoice. The difference is that it is structured and labelled so that software can read it without ambiguity.

How Does This Affect Freelancers and Small Businesses?

For most freelancers and small businesses, the practical impact depends on where they operate and who their clients are.

If you invoice German businesses

From January 2027, you will need to send invoices in a structured e-invoice format (XRechnung or Factur-X). Even before that deadline, your German clients must already be able to receive e-invoices as of January 2025, so sending in Factur-X format today means your invoices are easier for them to process.

If you invoice across EU borders

Peppol adoption is growing. Larger companies and public sector bodies already require or prefer Peppol invoices. Being able to send a structured invoice can set you apart from competitors who only offer PDFs.

If you primarily invoice domestically outside Germany, France, or Italy

The timeline is more relaxed, but the direction is set. The EU's ViDA proposal will eventually require all B2B transactions to use structured e-invoices. Adopting early avoids a rushed migration later.

The key practical changes

• Your invoicing tool needs to generate XML in addition to (or embedded within) PDF
• You may need to include additional data fields: tax category codes, payment means codes, seller/buyer identifiers
• Your VAT number and your client's VAT number become essential structured data, not just text on a page
• For Peppol delivery, you would need a Peppol ID and send invoices through an Access Point

Factur-X: The Practical First Step

For businesses that currently generate PDF invoices, Factur-X/ZUGFeRD offers the most natural transition:

1. You keep your PDF — The invoice still looks exactly as it does today
2. Structured data is embedded — An XML file is attached inside the PDF following the CII syntax
3. Recipients choose — Those with compatible software extract the XML; everyone else opens the PDF as usual
4. Compliance-ready — The EN 16931 profile meets the European standard

This hybrid approach means you do not need to abandon PDF workflows overnight. You enhance them with structured data, satisfying both human readers and automated systems.

What to Look for in Invoicing Software

If you are evaluating tools for e-invoicing readiness, consider:

• Does it generate structured XML in addition to PDF? (Factur-X, XRechnung, or UBL)
• Can it embed XML in PDF for the hybrid Factur-X approach?
• Does it include the required fields — tax category codes, payment means codes, business identifiers?
• Does it validate against EN 16931 business rules before sending?
• Can it connect to Peppol or export in a Peppol-compatible format?

Not all of these are necessary today for every user. But the trend is unmistakable: structured e-invoicing is becoming the European default, and tools that support it will be better positioned than those that rely solely on PDF.

Key Takeaways

• E-invoicing means structured, machine-readable invoice data — not just a PDF
• The EU standard EN 16931 defines the common data model, with UBL and CII as official syntaxes
• Peppol is the pan-EU delivery network; XRechnung and Factur-X are national implementations
• Germany mandates B2B e-invoicing from 2027; France and others are following closely
• Factur-X/ZUGFeRD (PDF + embedded XML) is the easiest adoption path for businesses currently using PDF invoices
• The EU's ViDA proposal will eventually require e-invoicing for all B2B transactions across the single market
• Start preparing now — even if your country's mandate is not yet in force, your clients in other countries may already require it

Snaply is building e-invoicing support to help EU freelancers and small businesses stay compliant as regulations evolve. Create your account and simplify your invoicing workflow.