What Is E-Invoicing? The Complete Guide for Corporate Finance Teams

The first time most corporate finance teams encounter e-invoicing, they assume it means what it sounds like: an invoice sent electronically.

But that's not what European tax authorities mean.

Under the mandates now live or phasing in across the EU, an e-invoice is a machine-readable XML dataset, validated against a specific schema, and in many countries cleared by the government before the buyer receives it. A PDF attached to an email doesn't qualify.

For companies managing European travel spend, the distinction matters because documents that fall outside the mandate's definition lose their legal standing for VAT reclaim.

What is e-invoicing?

E-invoicing (electronic invoicing) is the exchange of invoice data in a structured, machine-readable format between a supplier's and buyer's financial systems through a regulated transmission channel. The European standard for e-invoicing is EN 16931, published by the European Committee for Standardization (CEN), which defines the core data model that all compliant e-invoices must follow.[1]

Companies that haven't encountered e-invoicing mandates yet often face the consequences through failed VAT reclaim challenges that grow more costly as mandates expand.

Three characteristics separate an e-invoice from a traditional invoice:

• Format: E-invoices use structured XML or Universal Business Language (UBL), not PDF, Word, or scanned images. The data is tagged so that accounting systems can read, validate, and process it without human interpretation.
• Transmission: E-invoices travel through certified networks (such as Peppol) or government-mandated platforms, not via email attachments or postal mail.
• Validation: In many EU countries, a government platform or certified service provider validates the e-invoice against the mandated schema before it becomes legally valid.

How e-invoicing differs from digital invoicing

A PDF invoice emailed to a client is digital, but it isn't an e-invoice. The PDF is an image that requires a human or OCR software to extract data. An e-invoice contains structured data fields that flow directly into the buyer's ERP or accounting system. Under most live EU mandates, a PDF emailed by the supplier isn't legally compliant and can't support VAT reclaim for in-scope domestic transactions.

Why governments mandate e-invoicing

The EU's motivation is straightforward: close the VAT gap. The European Commission estimates that EU member states collectively lose tens of billions of euros annually to VAT fraud and reporting errors.[2] E-invoicing gives tax authorities real-time or near-real-time visibility into commercial transactions. In clearance countries, the government validates each invoice before the buyer receives it, making underreporting structurally difficult.

How do the four EU e-invoicing models work?

EU member states haven't adopted a single approach. Four distinct regulatory models govern how e-invoices are created, transmitted, and validated. Understanding which model applies in each country matters for corporate travel because it determines who can issue the invoice, when it becomes legally valid, and how it reaches the buyer's ERP. Navan tracks these models across all countries where its customers travel and adapts its document delivery to match each mandate's requirements.

Model 1: Clearance (Continuous Transaction Controls)

Continuous Transaction Controls (CTCs) require suppliers to submit invoice data to a government platform for verification before or during the actual issuance of the invoice to the buyer. Instead of auditing tax data months after the fact, the tax authority acts as a real-time gatekeeper. The government platform validates the document format, stamps it with a unique digital signature or tracking code, and only then allows it to be forwarded to the recipient. Under this model, if an invoice fails clearance, it does not legally exist, and the buyer cannot use it to claim tax deductions or VAT reclaims.

Countries: Italy (live since 2019), Poland (KSeF), Romania (e-Factura, penalties active), Croatia

Model 2: Post-audit (decentralized)

The e-invoice goes directly from the supplier to the buyer in the mandated structured format. The government doesn't intercept the invoice but audits records afterward.

Countries: Germany (phasing in 2027-2028 via ZUGFeRD/XRechnung), Belgium (Peppol Big Bang, live since 2025), Spain, Denmark

Model 3: Hybrid

Blends elements of clearance and post-audit. France's Y-model requires invoices to pass through a government-accredited platform (Plateforme de Dématérialisation Partenaire, or PDP) that reports data to the tax authority while routing the invoice to the buyer.

Countries: France (phasing in 2026-2027 via Factur-X)

Model 4: CTC reporting

The invoice goes directly to the buyer, but a copy must be reported to the tax authority. The government sees the data but doesn't gate the invoice's legal validity on prior approval.

Countries: Greece, Hungary

Comparison of regulatory models

Which EU countries have live e-invoicing mandates?

E-invoicing mandates are rolling out across the EU on different timelines. Finance teams managing travel spend in multiple countries need to track which mandates are live, which are phasing in, and when the EU-wide cross-border requirement takes effect.

For country-specific guidance, see our detailed guides to e-invoicing in France and e-invoicing in Germany.

What is Peppol?

The Pan-European Public Procurement Online (Peppol) is a four-corner network of accredited access points that route structured invoices between trading partners. It's the de facto infrastructure for e-invoicing in Northern and Western Europe. Belgium's mandatory B2B e-invoicing runs entirely on Peppol, and France's accredited platforms connect to the Peppol network. Access points on the Peppol network send and receive e-invoices through a standardized protocol, meaning the buyer and supplier don't need to use the same software.

What does ViDA mean for e-invoicing?

VAT in the Digital Age (ViDA) is the EU Council legislative package that will harmonize cross-border B2B reporting across all member states. It mandates near-real-time digital reporting for intra-EU transactions using the EN 16931 format. ViDA doesn't force countries to converge on a single transmission model (each keeps its own platform), but it standardizes the data layer. The first obligations are expected to phase in from 2028.[3]

Why does e-invoicing affect corporate travel differently?

E-invoicing mandates were designed for procurement: a buyer orders goods from a known seller, the seller ships and invoices the buyer, and both parties have a pre-existing commercial relationship with registered VAT numbers. Corporate travel inverts nearly every assumption.

The three structural misalignments:

• The buyer isn't the traveler. A hotel front desk interacts with the employee checking in, but the company 200 kilometers away is the legal buyer for the invoice. Without the company's VAT number and e-invoicing identifier passed to the supplier at booking time, the invoice routes nowhere useful.
• The price isn't fixed at booking. Hotel rates often change at checkout (minibar charges, room upgrades, extended stays). The e-invoice can't be issued at booking time the way a purchase order for office supplies can. The final amount isn't known until the service is consumed.
• One trip produces multiple documents under multiple mandates. A three-day business trip from Munich to Milan might generate a Deutsche Bahn rail ticket (Germany's post-audit model), a hotel folio in Milan (Italy's clearance model), and two taxi receipts below the simplified invoice threshold. Each document has different e-invoicing eligibility, different format requirements, and different VAT reclaim implications.

Why standard e-invoicing tools don't solve corporate travel

Standard accounts payable e-invoicing platforms assume the buyer and seller have a direct relationship, the price is known at invoicing, and one transaction produces one document. According to Lisa Dowling, Chief Tax and Compliance Officer at Fintua, companies in early mandate markets like Italy and Romania "chose to treat T&E as B2C or simply skip VAT recovery altogether" rather than solve the complexity.[4] Navan's approach addresses this by passing the company's VAT number and e-invoicing credentials to the supplier at the point of booking, before the traveler arrives at the property.

For a deeper analysis of why standard compliance tools fall short for corporate travel, see our dedicated guide.

How does your TMC's commercial model determine VAT reclaim?

The most consequential variable in corporate travel e-invoicing isn't the mandate model or the format standard. It's the travel management company's (TMC's) commercial model, which determines the invoice chain and whether VAT reclaim is structurally possible.

Three TMC commercial models

• Agent pass-through: The TMC arranges the booking on the company's behalf without becoming the legal seller. The supplier invoices the company directly. The company's VAT number appears on the invoice. VAT reclaim rights are preserved.
• Bill-back: The TMC pays the supplier out of its own pocket and bills the company later. The supplier's invoice is addressed to the TMC, not the company. The invoice chain that enables reclaim is broken.
• Reseller / Merchant of Record (TOMS): The TMC buys inventory from the supplier and resells it to the company. Under the EU's Tour Operators' Margin Scheme (TOMS), the VAT on the underlying supply is consumed inside the margin scheme. The company receives an invoice from the TMC, but it can't reclaim the supplier's input VAT.

Why this matters under e-invoicing mandates

Under a live e-invoicing mandate, only the legal seller can issue the compliant e-invoice. If the TMC operates as a merchant of record, the e-invoice flows from the TMC to the company under a margin scheme, and VAT reclaim is structurally blocked. If the TMC is a disclosed agent, the supplier issues the e-invoice directly to the company's entity, preserving reclaim rights.

Navan operates as a disclosed agent (pass-through) on every booking. The supplier invoices the client directly, and Navan passes the company's VAT number and routing credentials to the supplier at booking time so the e-invoice is correctly addressed.[5]

For a detailed comparison of TMC commercial models and their VAT implications, see our guide.

What documents does each travel booking produce?

Not every travel booking produces a proper e-invoice. The document a company receives depends on the supplier, the booking channel, the country, and whether the TMC has authorization to issue on the supplier's behalf.

Understanding the document hierarchy helps finance teams know which documents carry specific recovery rights -- differentiating between Corporate Income Tax (CIT) deductions and value-added tax (VAT) reclaims -- complementing Navan's broader travel expense reconciliation automation.

How Navan handles the document chain

Navan issues the best document legally available for each booking. When Navan is authorized to issue on a supplier's behalf (e.g., Lufthansa Group, Deutsche Bahn, ÖBB), the e-invoice flows through Navan's access point (Eezi) to the client's ERP. When the supplier issues directly, Navan passes the client's VAT number and routing credentials so the e-invoice reaches the right entity.

When no supplier e-invoice is obtainable, Navan issues a receipt with XML in the local mandate's format (e.g., Factur-X, ZUGFeRD, Peppol BIS). This structured receipt preserves the corporate income tax (CIT) deduction and audit trail. It explicitly does not claim tax invoice status, so finance teams know exactly what they're working with.

How to prepare your corporate travel program for e-invoicing

E-invoicing mandates aren't optional and they aren't distant. Italy has enforced them since 2019, Belgium went live in 2025, and France's receiving mandate begins in September 2026. Companies with European travel spend can't afford to wait for a single unified deadline because the deadlines are already arriving country by country.

Four steps put a corporate travel program on solid ground:

• Map travel spend to mandate timelines. Identify which countries your travelers visit most frequently and when each mandate takes effect. Prioritize countries where your booking volume is highest and the mandate is live or imminent.
• Verify your TMC's commercial model. Confirm whether your TMC operates as a disclosed agent or a merchant of record. The answer determines whether your e-invoices will preserve VAT reclaim rights.
• Check ERP access point readiness. Your ERP needs to receive structured e-invoices through at least one access point network (Peppol is the most common). If your ERP can't accept XML invoices, they'll pile up in a queue nobody reads.
• Align travel policy with document requirements. Train travelers on what to request at hotel check-out (a company-name invoice, not a personal receipt) and update booking policies so the company's VAT number is passed to suppliers at booking time.

Navan's agent pass-through model and direct access point connections handle the infrastructure side of this equation, building on the same platform that powers automated travel expense reporting across the organization. The company's role is to verify the TMC model, connect the ERP, and update the travel policy so suppliers have the information they need to issue compliant documents.

See how Navan handles e-invoicing compliance for corporate travel programs.

Sources

• European Commission, "What Is eInvoicing -- Digital Building Blocks," 2024
• European Commission, "VAT Gap in the EU 2024 Report," 2024
• EY Tax News, "EU Council Approves VAT in the Digital Age (ViDA) Package," 2025
• Fintua, "eInvoicing and the VAT Recovery Challenge -- ELEVATE 2026 Conference," 2026
• Navan, "Why Reclaiming VAT Is So Challenging," 2026