Is your German travel e‑invoice‑ready?

What Do New German E-Invoicing Mandates Mean for Your Corporate Travel Program?

Nadav Ravid

•June 25, 2026•

8 minute read

Get started Request a demo

Summarize with:

ChatGPT Gemini Grok Claude Perplexity

Germany’s Wachstumschancengesetz (Growth Opportunities Act) is reshaping how every domestic business-to-business (B2B) transaction gets invoiced, and corporate travel is squarely in scope. The mandate requires all German B2B invoices to use structured electronic formats by 2028, replacing the PDFs and paper documents that finance teams have relied on for decades. For companies with European travel spend, the implications go beyond a format change: hotel invoices, your largest source of reclaimable VAT on travel, are fully subject to the mandate, while air and rail tickets are exempt.

This article breaks down what Germany’s e-invoicing mandate requires, where corporate travel breaks the standard compliance playbook, and what finance teams need to do before the deadlines hit.

What does Germany’s e-invoicing mandate require?

Germany’s e-invoicing obligation, known formally as the E-Rechnungspflicht, rolled out in three phases under the Wachstumschancengesetz. The European Commission’s Digital Building Blocks factsheet and the German Federal Ministry of Finance (BMF) both confirm the same timeline.[1][2]

January 1, 2025: Every German business must be able to receive structured e-invoices. Reception capability is mandatory with no exceptions.
January 1, 2027: Businesses with prior-year annual turnover exceeding €800,000 must issue structured e-invoices for all domestic B2B transactions.
January 1, 2028: All remaining businesses must issue structured e-invoices. The transition period ends.

What counts as an e-invoice in Germany?

Only invoices in a structured format that complies with the European standard EN 16931 qualify. The BMF recognizes two national formats.[2]

XRechnung is Germany’s pure XML standard, originally designed for public-sector invoicing and now extended to B2B. It contains only machine-readable structured data and requires a separate viewer for human readability.

ZUGFeRD (version 2.0.1 and above) is a hybrid format that combines a human-readable PDF with an embedded XML data layer. ZUGFeRD’s dual readability makes it the more common choice in the private sector, particularly for partners who haven’t yet invested in dedicated e-invoicing infrastructure.[3]

A standard PDF emailed by a supplier no longer qualifies as an e-invoice under German law. PDFs, Word documents, and scanned images are classified as “other invoices” (sonstige Rechnungen) and don’t meet the mandate’s structural requirements.[2]

Germany uses a post-audit model

Germany’s enforcement approach differs from clearance countries like Italy, Poland, and Romania, where invoices must transit a government platform before reaching the buyer. In Germany, e-invoices flow directly between trading partners. The tax authority (Finanzamt) audits the records after the fact. There’s no central government portal for B2B invoices.[1]

This distinction matters for corporate travel programs. In clearance countries, the government acts as a gatekeeper: if the invoice doesn’t pass the platform, it doesn’t legally exist. In Germany, the invoice is valid the moment it’s issued in the correct format, but non-compliance surfaces during audits, often months later.

Why does corporate travel break the standard e-invoicing playbook?

Most e-invoicing guidance assumes a straightforward procurement relationship: a buyer orders from a seller, the seller invoices the buyer, and both parties have a pre-existing relationship with known prices. Corporate travel breaks every one of these assumptions.

Breaking Point #1: The traveler isn’t the buyer

When an employee checks into a Berlin hotel, the hotel sees the traveler’s name. But the company needs the invoice addressed to its legal entity, with its Umsatzsteuer-Identifikationsnummer (USt-IdNr.) in the buyer field. If the company’s tax identification number doesn’t reach the hotel before or at check-in, the hotel’s invoice either addresses the wrong entity or defaults to a B2C receipt. Under the e-invoicing mandate, that means the structured document doesn’t connect supplier to buyer, and input VAT (Vorsteuerabzug) deduction may be denied.[4]

Breaking Point #2: Prices aren’t final at booking time

Hotel rates frequently change between booking and check-out. Minibar charges, room service, late check-out fees, and split VAT rates (7% for accommodation, 19% for extras like breakfast or parking) all get added after the initial reservation. The final invoice can’t be issued as a structured e-invoice until the guest departs and all charges are settled.

Breaking Point #3: One trip produces multiple documents under different rules

A single business trip to Germany can generate an airline ticket (exempt from e-invoicing), a Deutsche Bahn rail booking (also exempt), a hotel folio (fully subject to the mandate), a taxi receipt (potentially below the €250 threshold), and a restaurant bill (subject if B2B). Each document follows different rules, different formats, and potentially different compliance pathways.

What is the Fahrausweise exemption and what doesn’t it cover?

Germany’s e-invoicing mandate carves out several permanent exemptions, and the one most relevant to corporate travel is the Fahrausweise exemption. Passenger transport tickets (Fahrausweise) that meet the simplified invoice requirements under §34 UStDV are permanently exempt from the mandate’s structured format requirements.[5][6]

What qualifies as a Fahrausweise?

The German VAT Implementation Ordinance defines Fahrausweise as documents that grant a right to passenger transport.[7] This includes:

Airline tickets
Deutsche Bahn and regional rail tickets
Surcharge tickets for premium rail services (ICE supplements, seat reservations, sleeper car tickets)
Bus and tram tickets for scheduled services

Taxi receipts and rental car invoices are explicitly excluded from the Fahrausweise definition. They don’t qualify for the exemption and follow standard invoice rules.

The Fahrausweise exemption covers the travel categories with the lowest per-transaction VAT exposure. Domestic flights in Germany carry 19% VAT but are typically booked through channels that produce structured ticket data. Rail carries a reduced 7% VAT rate on most routes.

Hotel invoices, by contrast, are not Fahrausweise and receive no exemption. They’re the single largest per-transaction VAT exposure in most European corporate travel programs, with the accommodation portion taxed at 7% and ancillary services at 19%. Finance teams that see the Fahrausweise exemption and assume their travel program is largely unaffected are missing the category that matters most for VAT reclaim.

How does your TMC’s commercial model affect e-invoicing compliance?

The relationship between your travel management company (TMC) and e-invoicing compliance isn’t immediately obvious, but it determines whether the mandate’s structured invoice chain connects supplier to buyer at all. Navan’s TMC commercial models and VAT reclaim explains three commercial models that apply here.

Model 1: Disclosed agent (pass-through)

In a disclosed agent model, the TMC arranges the booking on the company’s behalf. The hotel invoices the company directly: the hotel’s USt-IdNr. in the seller field, the company’s USt-IdNr. in the buyer field. The TMC doesn’t appear on the invoice as a counterparty. Under the e-invoicing mandate, this means the structured e-invoice flows from supplier to client, and input VAT reclaim rights remain intact.

Navan operates exclusively as a disclosed agent. The company is always the legal buyer in Navan-facilitated transactions.

Model 2: Merchant of record (reseller/TOMS)

In a merchant-of-record model, the TMC buys inventory from the supplier and resells it to the company. The TMC is the legal seller, and the EU’s Tour Operators’ Margin Scheme (TOMS) applies. Under TOMS, only the TMC’s margin is subject to VAT, and the company can’t reclaim input VAT on the underlying supplier charges.

Under the e-invoicing mandate, this model produces a structured e-invoice from the TMC to the company, but it’s a margin-scheme invoice. The supplier’s VAT is absorbed inside the margin. The company’s VAT reclaim opportunity on the hotel stay is permanently lost.

Model 3: Bill-back

In a bill-back model, the TMC pays the supplier directly, then invoices the company later. The supplier’s original invoice is addressed to the TMC, not the company. The e-invoice chain between supplier and end buyer is broken. VAT reclaim on the underlying supply is typically not available.

How does Navan handle e-invoicing for corporate travel in Germany?

Navan’s approach to e-invoicing in corporate travel is built on two structural decisions: always operating as a disclosed agent, and always passing the client’s tax credentials to the supplier at booking time.

Your USt-IdNr. reaches the supplier before you arrive

When a traveler books a hotel through Navan, the platform passes the company’s Umsatzsteuer-Identifikationsnummer and entity details to the supplier as part of the booking flow. The hotel receives the company’s tax credentials before or at check-in, not as a retroactive correction. This means the hotel can address its e-invoice to the correct legal entity from the start.

Authorized suppliers: Navan issues the e-invoice directly

For suppliers that have authorized Navan to issue invoices on their behalf, Navan generates the e-invoice in the mandated format and transmits it through Eezi, Navan’s certified access point, to the client’s ERP system via the Peppol network or direct integration. Authorized suppliers include Lufthansa Group airlines and Deutsche Bahn.

The flow: Navan → Eezi (access point) → e-invoicing network → client’s access point → client ERP.

Other suppliers: the hotel sends the e-invoice directly

For most hotels and other suppliers where Navan isn’t authorized to issue on their behalf, the supplier issues its own e-invoice and sends it through the regulated channel. Navan’s role in this scenario is upstream: passing the company’s VAT credentials and routing information so the supplier’s e-invoice reaches the right entity.

The fallback: Receipt with XML

When a supplier can’t issue a proper e-invoice, Navan issues a Receipt with XML in ZUGFeRD format. This structured document preserves the corporate income tax (CIT) deduction and provides a clean audit trail. It doesn’t support VAT reclaim (that requires the supplier’s e-invoice), but it makes sure no booking goes undocumented. A Big 4 firm has reviewed and confirmed this approach in a formal memorandum.

How to prepare your travel program for Germany’s e-invoicing mandate

The phased timeline gives companies until January 2028 before full issuance obligations take effect. But the real preparation isn’t about the deadline: it’s about whether your invoicing chain is structurally capable of producing the documents the mandate requires. Three actions matter most.

Confirm your TMC operates as a disclosed agent. If your TMC uses a merchant-of-record or bill-back model, the e-invoice chain between supplier and your entity is structurally broken. This isn’t a compliance gap you can fix with software; it’s a commercial model question that determines whether VAT reclaim is even possible.

Verify your USt-IdNr. reaches every hotel supplier at booking time. Without it, the hotel defaults to a B2C receipt. Navan handles this automatically through its booking flow. If your current TMC doesn’t, your traveler or your finance team is responsible for correcting every hotel invoice after the fact.

Check your ERP can receive ZUGFeRD and XRechnung. At minimum, your system needs to process XML attachments from e-invoices. The BMF has confirmed that a simple email inbox is sufficient for reception, but processing and archiving require EN 16931-compliant workflows. Navan integrates directly with major ERP systems including NetSuite, QuickBooks, and Xero, and feeds verified invoice data into reconciliation workflows automatically.

See how Navan helps finance teams stay compliant with evolving European e-invoicing mandates. Request a demo.