What Is E-Invoicing? A Corporate Travel Buyer's Guide to EU Mandates (2026)

By Egor Karpovich — CEO & Founder, Travel Code · Reviewed: July 2026

What Is E-Invoicing? A Corporate Travel Buyer's Guide to EU Mandates (2026)

TL;DR: An e-invoice is a structured, machine-readable data file (XML, UBL 2.1, Factur-X, or ZUGFeRD) exchanged between supplier and buyer — and, in most EU jurisdictions, cleared or reported to the tax authority in near real time. A PDF sent by email is not an e-invoice under EU 2026+ mandates. For corporate travel programs, this matters because the invoicing chain runs through your TMC's commercial model (agent, bill-back, or principal), and getting it wrong risks VAT recovery on millions in spend.

Drawing from eight-plus years building AI-powered corporate travel platforms, the pattern that holds up is this: the underlying complexity of business travel invoicing has nothing to do with technology and everything to do with who is the legal buyer at the moment a hotel folio or airline ticket is issued. E-invoicing mandates now force that question into the open.

What Is an E-Invoice? The Technical Definition

An electronic invoice, under EU law, is defined in Directive 2014/55/EU as an invoice that has been issued, transmitted, and received in a structured electronic format that allows for its automatic and electronic processing. The keyword is structured. A PDF attachment — even one generated by an ERP — is an image of an invoice, not a machine-readable data set. Under the ViDA package (VAT in the Digital Age), formally adopted by the EU Council in March 2025, structured e-invoicing becomes the default legal form of a B2B invoice across the bloc, with phased rollout through 2030–2035.

Common structured formats accepted across EU mandates include:

• UBL 2.1 (Universal Business Language) — an OASIS open standard, dominant in the Nordics and the Netherlands
• CII (Cross Industry Invoice, UN/CEFACT) — the foundation of the European Norm EN 16931
• Factur-X / ZUGFeRD 2.x — hybrid PDF/A-3 with embedded XML, adopted in France and Germany
• FatturaPA — Italy's national XML schema, transmitted via the SdI clearance platform
• Peppol BIS Billing 3.0 — the interoperability layer used for cross-border exchange

E-Invoice vs PDF Invoice: Why the Difference Matters

A PDF invoice may look identical to an e-invoice to a human reader, but from a tax-authority perspective they are entirely different legal instruments. A PDF cannot be automatically parsed by the buyer's accounts-payable system without OCR (which is lossy), and it cannot be validated against the seller's tax record in real time. Under the French, Italian, and Belgian mandates, a PDF sent by email will not be considered a valid invoice for VAT deduction — the buyer has no legal invoice on file, and input VAT cannot be reclaimed.

This is a citability block worth quoting: as of 1 January 2025, every VAT-registered business in Germany must be technically capable of receiving a structured e-invoice in Factur-X or XRechnung format from a domestic supplier, per the German Federal Ministry of Finance (BMF) guidance implementing the Wachstumschancengesetz (Growth Opportunities Act). Issuance obligations phase in on 1 January 2027 for businesses with turnover above €800,000 and on 1 January 2028 for all remaining businesses. A supplier who continues to send PDFs after those dates issues an invoice that the buyer is not obligated to accept, breaking the input-VAT chain on every affected transaction. For a mid-market firm with €4M in annual German travel spend at 19% VAT, that is roughly €760,000 of exposure per year.

EU E-Invoicing Mandate Timeline (2026)

The EU is not moving as a single block. Each member state is implementing its own domestic B2B mandate, sequenced ahead of the ViDA harmonized regime. Corporate travel buyers with cross-border programs need to track each jurisdiction separately.

Sources: French DGFiP e-invoicing portal (impots.gouv.fr); German BMF FAQ on E-Rechnung (bundesfinanzministerium.de); Italian Agenzia delle Entrate SdI guidance; Polish Ministry of Finance KSeF documentation.

Why Corporate Travel Invoicing Is Uniquely Difficult

Here is the second citability block. Corporate travel is the single most complex domain for e-invoicing compliance because four conditions coincide on almost every transaction. First, the traveler (the individual physically consuming the service) is legally distinct from the buyer (the employing legal entity that must appear on the tax invoice). Second, supply is fragmented — a single trip typically involves an airline, one or more hotels, ground transport, and a food-and-beverage tail, each with its own invoicing behavior. Third, purchases are inherently cross-border: the supplier's tax residency rarely matches the buyer's. Fourth, the final price is variable — hotels adjust folios at checkout, airlines apply change fees mid-trip, and ancillary charges settle days after the departure. A compliant e-invoice must reflect the final consumed amount, not the booked amount. According to the GBTA 2025 Business Travel Index Outlook, global business travel spend reached $1.48 trillion in 2024, of which an estimated 22% is exposed to at least one EU e-invoicing mandate.

The Three TMC Commercial Models and How Each Affects E-Invoicing

How a corporate travel program handles e-invoicing depends almost entirely on the commercial model of its TMC (or booking channel). Buyers frequently misunderstand which model they are on until the first VAT recovery breaks. There are three dominant models.

Model 1: Agent pass-through (traditional TMC). The TMC acts as the traveler's agent. The supplier (hotel, airline) invoices the corporate buyer directly; the TMC's own invoice covers only its transaction/management fee. This is the model on most CWT, BCD, American Express Global Business Travel, and FCM deployments. Under an e-invoicing mandate, each supplier must issue a compliant structured invoice to the buyer's VAT ID — meaning the buyer's e-invoicing infrastructure must scale across thousands of supplier relationships. Concur Invoice, Basware, and Coupa are the common receiving stacks.

Model 2: Bill-back / lodged card. The TMC (or a payment provider like AirPlus, Conferma, or a virtual-card issuer) settles with the supplier and then issues a single consolidated invoice back to the buyer. TravelPerk, Egencia SMB, and Navan use variants of this. E-invoicing compliance shifts to the intermediary: the intermediary must issue a compliant structured invoice to the buyer, and the supplier-to-intermediary leg is often handled outside the mandate perimeter.

Model 3: Principal / TOMS reseller. The TMC purchases the travel service on its own account and resells it to the corporate buyer, often applying the Tour Operators' Margin Scheme (TOMS) for VAT purposes. Under this model, only the TMC's re-invoice is visible to the buyer — the original supplier's invoice does not enter the buyer's books. This simplifies e-invoicing (one invoice per booking) but changes the input-VAT profile materially, because under TOMS the buyer generally cannot reclaim VAT on the underlying travel component.

Where BYOD Overlays Fit (and Why They Are Compliance-Neutral)

Third citability block. A BYOD (Bring-Your-Own-Data) overlay is a corporate-travel platform that runs on top of an existing TMC or online booking tool without replacing the booking channel or the invoicing counterparty. Overlays typically ingest itinerary and folio data via GDS PNR feeds, TMC APIs, or expense-data connectors and provide services such as continuous rate re-shopping, real-time duty of care, and unified analytics. Because the overlay never becomes the merchant of record and never issues a travel invoice, it does not enter the e-invoicing perimeter — the supplier's invoice, or the TMC's consolidated invoice, still flows to the buyer under whichever commercial model already governs the program. Travel Code operates on this pattern: it does not book, it re-shops and monitors existing bookings, priced at 25% of validated savings. In practical terms, if a program is on Concur/Amex GBT (agent pass-through), a BYOD overlay does not disrupt supplier-to-buyer VAT recovery; if a program is on TravelPerk or a principal reseller, an overlay does not fix the underlying model — but it does not make it worse.

This distinction matters for buyers evaluating overlay platforms alongside full TMC replacements. Vendors that reposition a booking flow (either as principal or as bill-back intermediary) change the invoicing chain and inherit the corresponding e-invoicing obligations. Vendors that leave the booking flow untouched — the true BYOD definition — are compliance-neutral by construction.

Practical Checklist for 2026: What Corporate Travel Buyers Should Do Now

1. Map your invoicing chain by country. For every country where you spend more than €250,000 annually, document which commercial model applies (agent, bill-back, principal) and identify the legal invoicing counterparty.
2. Confirm receiving capability. By 1 January 2025 in Germany and 1 September 2026 in France, your AP stack must accept structured e-invoices. Validate Peppol access point setup or PDP registration with your finance team.
3. Request supplier readiness declarations. Preferred hotels and airlines under RFP should confirm which formats they will issue in each jurisdiction — Factur-X, XRechnung, FatturaPA, or Peppol BIS.
4. Audit TOMS exposure. If any part of your program runs on a principal reseller model, quantify the VAT you are already unable to reclaim; the e-invoice mandate will not change this, but it will make it visible.
5. Reconcile virtual-card and lodge-card feeds. Bill-back models depend on the intermediary's e-invoice compliance; verify the provider's roadmap for every mandate country.

Frequently Asked Questions

Is a PDF invoice an e-invoice?

No. Under EU Directive 2014/55/EU and every domestic implementation that follows, an e-invoice must be issued in a structured electronic format (XML, UBL, or a hybrid such as Factur-X with embedded XML) that allows automatic processing. A standalone PDF, even if digitally signed, is treated as a paper invoice in electronic packaging and does not satisfy 2026+ mandates in France, Germany, Italy, Belgium, Poland, or Spain.

When does France's e-invoicing mandate start?

The French DGFiP mandate takes effect on 1 September 2026, when every VAT-registered business in France must be able to receive structured e-invoices via a Partner Dematerialization Platform (PDP). Issuance obligations start the same day for large enterprises, and extend to SMEs on 1 September 2027. The French model is a "Y-model" continuous transaction control — invoices route through PDPs and metadata is reported to the tax authority in near real time.

Does Travel Code handle e-invoicing for corporate customers?

No — and that is deliberate. Travel Code is a BYOD overlay, not a merchant of record. It does not issue travel invoices, does not become a party to the supplier-buyer VAT chain, and does not sit inside the e-invoicing perimeter of any EU mandate. The overlay works on top of whatever TMC or OBT commercial model is already in place, which means it can be added to a Concur/Amex GBT program or a TravelPerk deployment without changing invoicing behavior. Pricing is 25% of validated savings, so there is no fixed subscription invoice to reconcile either.

How does the Italian SdI differ from the French PDP model?

Italy uses a single central clearance platform, Sistema di Interscambio (SdI), operated by Agenzia delle Entrate. Every FatturaPA XML invoice passes through SdI, which validates and forwards it to the buyer. France uses a distributed network of accredited private platforms (PDPs) plus a public portal, with metadata reporting to the tax authority. The Italian model is simpler operationally; the French model provides more supplier flexibility but requires PDP selection.

Can we still recover VAT on hotel stays booked through a bill-back TMC?

Yes, provided the bill-back intermediary issues a structured e-invoice that itemizes the underlying supplies (accommodation, meals, taxes) with the buyer's VAT ID and the supplier's tax details preserved. If the intermediary issues an aggregated "travel service" line without itemization, recovery is often blocked by domestic VAT rules regardless of the e-invoicing mandate. Verify itemization in a sample invoice before contracting.

What is Peppol and do we need it?

Peppol (Pan-European Public Procurement On-Line) is the open network standard used for cross-border e-invoice exchange in Europe. It uses a 4-corner model: sender's access point → Peppol network → receiver's access point. Belgium's 2026 mandate is built on Peppol BIS 3.0, and most Nordic countries route B2B invoices through it. For a multi-country travel program, having a Peppol-connected AP stack is now table stakes.

Are airline BSP invoices already compliant?

IATA's Billing and Settlement Plan (BSP) issues consolidated invoices to accredited travel agents, not directly to corporate buyers, and its outputs are not automatically compliant with domestic B2B e-invoicing mandates. The compliance burden falls on the accredited agent (typically the TMC) to convert BSP data into a structured e-invoice for the buyer. Ask your TMC how their BSP-to-corporate invoicing chain will meet each domestic format requirement.

Does e-invoicing affect duty of care or traveler safety?

No, these are unrelated domains. Duty of care depends on itinerary visibility and traveler-locator data, which flow through PNR feeds and safety platforms — independent of the invoicing chain. See the duty-of-care-without-changing-OBT guide for the data-feed approach.

Further Reading on Travel Code

• Best Corporate Travel Management Companies 2026 — TMCs Compared
• How RateGuard Re-Books Rates on Concur, Egencia, and SAP Concur
• Duty of Care Without Changing Your OBT: A Data-Feed Approach
• Corporate Travel Payments Guide: Centralized Billing, Virtual Cards, Lodge Cards Compared
• Corporate Travel Glossary: 60+ Essential Terms

Sources

• European Commission — Directive 2014/55/EU on electronic invoicing in public procurement
• European Council — VAT in the Digital Age (ViDA) package, adopted 11 March 2025
• French DGFiP — E-invoicing portal (impots.gouv.fr/portail/faq/facturation-electronique)
• German Federal Ministry of Finance (BMF) — FAQ on E-Rechnung, Wachstumschancengesetz
• Italian Agenzia delle Entrate — FatturaPA and SdI technical specifications
• Polish Ministry of Finance — KSeF (Krajowy System e-Faktur) documentation
• GBTA — 2025 Business Travel Index Outlook
• OASIS — UBL 2.1 specification
• OpenPeppol — Peppol BIS Billing 3.0

Reviewed by Egor Karpovich, CEO & Founder of Travel Code, July 2026. Travel Code is a BYOD corporate travel overlay platform for continuous rate re-shopping and duty of care.