Germany's E-Invoicing Mandate Takes Effect January 2027

Germany mandates structured e-invoicing from January 2027. See what it changes for carrier invoice processing and what shippers must map before then.

Germany's phased e-invoicing mandate reaches its next milestone on 1 January 2027, when companies with annual turnover above €800,000 must start issuing invoices in structured, EN 16931-compliant format rather than PDF. Sovos confirms the threshold and date, and the rule applies to every B2B invoice a German entity sends, including the freight bills your carriers issue to you. If you run multi-carrier operations across Germany, France, Belgium and Poland, this is the first of four overlapping country mandates you'll need to map into your AP and TMS systems before the deadlines hit, not after.

What's happening, and when

Germany already requires all businesses to be able to receive structured e-invoices, a rule that has been in force since January 2025. The new piece is the obligation to issue them. Sending and receiving e-invoices will become mandatory in Germany from 1 January 2027, applying to companies with an annual turnover exceeding EUR 800,000. A second wave follows in 2028: mandatory issuing for all remaining businesses from January 2028.

This sits inside the EU's wider ViDA (VAT in the Digital Age) reform. ViDA itself doesn't force domestic e-invoicing on anyone by 2027, but it removed the legal barrier that used to require Brussels' sign-off, which is exactly why Germany, France, Belgium and Poland have each gone ahead on their own timelines. The EU-wide piece, cross-border B2B digital reporting built on structured invoices, from 1 July 2030, e-invoicing becomes the default for intra-EU B2B transactions, and invoice data must be reported to tax authorities. As one analysis puts it, Germany's B2B mandate is scheduled for January 2027, and that date is effectively what locks in your invoicing architecture well before the 2030 EU deadline arrives.

Why this is a carrier-invoice problem, not just a finance problem

Most shippers file e-invoicing under "something Accounts Payable handles." That's a mistake for exactly the invoice category this blog covers. Carrier invoices from DHL, DPD, GLS or a DSV/Schenker entity are high-volume, recurring B2B documents, precisely the profile these mandates target. A carrier that keeps emailing PDF freight bills to a German entity above the threshold will simply stop producing a valid tax document on 1 January 2027. If your AP or TMS stack can't ingest the structured version instead, you're back to manual re-keying, or paying for a conversion layer, on top of every other carrier-side format change you already track.

The multi-country fragmentation problem

The real headache isn't Germany alone. It's that Germany, France, Belgium and Poland are each running their own mandate, on their own calendar, with different formats and transport rules.

CountryObligationKey dateMandated format/network
BelgiumIssue & receive, all VAT-registered businessesJanuary 1, 2026Peppol network mandated
PolandIssue & receive via KSeFLarge taxpayers from February 2026; most businesses from April 2026KSeF government portal, no private network
FranceReceive (all); issue (large/mid)All businesses must receive from September 2026; large enterprises must issue from the same dateFactur-X/UBL/CII via certified PDP, not Peppol
France (SMEs)IssueSmaller businesses have until September 2027 to comply with the sending requirementSame as above
GermanyIssue, >€800k turnover1 January 2027EN 16931 (XRechnung, ZUGFeRD); no network mandated
Germany (all)Issue, all businessesJanuary 2028EN 16931
EU (ViDA)Cross-border B2B digital reporting1 July 2030EN 16931-based, network open

A shipper with carriers and legal entities across all four countries is reconciling four separate legal formats at once. It's the same parallel-migration problem you already deal with when carriers switch from SOAP to REST on different schedules, except this time there's a tax authority on the other end instead of a webhook.

What format actually lands in your systems

EN 16931 is the underlying semantic data standard, not a file format. Germany typically expects that standard delivered as XRechnung (pure XML) or ZUGFeRD (a hybrid PDF with embedded XML), while France's certified platforms work in Factur-X, UBL or CII. ViDA mandates EN 16931-compliant structured invoicing and reporting, not a specific network, which is why Germany mandates the format only rather than forcing everyone onto Peppol. Practically, your AP or TMS middleware needs a parsing layer that validates and extracts EN 16931 fields regardless of which syntax a given carrier sends, the invoice equivalent of normalizing tracking webhooks across carrier APIs.

What vendors are already building for this

Invoice automation is becoming a selling point among multi-carrier platforms rather than a back-office afterthought. nShift's recently launched invoice audit tool checks each carrier invoice against both the contracted tariff and the shipment record, with the first invoice in a new carrier format validated manually before later invoices in the same format process automatically, a clear sign vendors expect structured carrier invoice data to become the norm, not the exception. Expect similar structured-invoice handling from other multi-carrier platforms as the mandates force the issue. TMS systems that already build carrier connectivity natively, such as Cargoson, are better placed to absorb structured invoice feeds as a native data type than platforms bolting on a parser after the fact.

What to do before January 2027

  1. Inventory which carriers invoice you from German entities above the €800,000 threshold, finished by December 2026.
  2. Ask each carrier's account manager now whether they're shipping XRechnung or ZUGFeRD, and when.
  3. Test ingestion and field extraction in your AP or TMS middleware before 1 January 2027, not on the day itself.
  4. Repeat the exercise for France, Belgium and Poland on their own staggered deadlines above.
  5. Flag intra-EU cross-border carrier invoices now for ViDA's 1 July 2030 digital reporting requirement, even though that deadline sits further out.

This won't be the last country-specific mandate you need to track alongside carrier API deprecations. Treat it the same way: one line item per carrier, per country, with a date attached.