If you invoice freight into the European Union, 2026 is the year the paperwork stops being your choice. Belgium requires structured business-to-business e-invoicing from 1 January 2026. Poland's KSeF becomes mandatory on 1 February 2026 for companies whose 2024 sales exceeded 200 million zloty and on 1 April 2026 for every other VAT-registered business except micro-entrepreneurs. France requires every company to be able to receive a structured e-invoice from 1 September 2026, with large and intermediate-sized businesses also issuing from that date.
None of those are pilots. They are dates on which a PDF attached to an email stops being a valid invoice in that country, and freight invoicing is unusually exposed because a single carrier invoice can carry a dozen accessorial lines, a fuel surcharge that moves weekly, and a customs disbursement that is not really a sale at all.
The 2026 mandate calendar
| Country | What changes | Effective | Format or channel |
|---|---|---|---|
| Belgium | Structured B2B e-invoicing becomes mandatory | 1 January 2026 | Peppol BIS as the default route |
| Poland | KSeF mandatory for large taxpayers, above 200 million zloty of 2024 sales | 1 February 2026 | KSeF national platform, structured XML |
| Poland | KSeF mandatory for all remaining VAT-registered businesses, micro-entrepreneurs excluded | 1 April 2026 | KSeF national platform |
| Poland | KSeF reaches micro-entrepreneurs | 1 January 2027 | KSeF national platform |
| Spain | Verifactu certified billing software for corporate income taxpayers, after a second delay | 1 January 2027 | Certified billing software, records to the tax authority |
| Spain | Verifactu for all remaining taxpayers, including the self-employed | 1 July 2027 | Certified billing software |
| France | All companies must be able to receive structured e-invoices; large and intermediate-sized companies must issue | 1 September 2026 | Accredited platform, now called a PA and formerly a PDP, or the public portal |
| France | Small and micro companies must issue | 1 September 2027 | Accredited platform, a PA |
| Germany | Issuing becomes mandatory above 800,000 euro of turnover | 1 January 2027 | XRechnung or ZUGFeRD, per EN 16931 |
| Germany | Issuing becomes mandatory for all businesses | 1 January 2028 | XRechnung or ZUGFeRD |
| European Union | Digital reporting for intra-EU B2B transactions under the ViDA package | 1 July 2030 | Structured e-invoice to the EU standard |
Two earlier mandates already bite and are easy to forget because they are old news. Italy has required B2B e-invoicing through its SdI platform since 2019, and Romania's RO e-Factura has covered domestic B2B since 1 July 2024. Germany's receiving obligation started on 1 January 2025, which means a German customer can already refuse to process anything that is not a structured invoice.
What the ViDA package actually changed
The Council adopted the EU VAT reform known as ViDA on 11 March 2025, and most commentary fixated on the 2030 date. For a freight business the more immediate change is quieter. Member states no longer need a derogation from the Council to impose a domestic e-invoicing mandate, and they no longer need the buyer's consent for an invoice to be issued electronically.
That is why the calendar above is filling up rather than waiting for 2030. The legal brake came off, so national tax authorities are setting their own dates. It also means the list will keep growing, and I would not build a 2027 plan on the assumption that the countries missing from this table stay missing.
The second structural point is the standard. The European norm EN 16931 defines the semantic model that national formats have to express, which is why XRechnung, ZUGFeRD, FatturaPA and Peppol BIS can all be described as compliant while looking nothing alike on screen. Pre-existing national systems are expected to match the European model by 2035.
Why freight invoices break these systems
Every mandate assumes a reasonably simple commercial transaction. Freight invoices are not that, and these are the failure modes I keep meeting:
- Accessorials without stable codes. Waiting time, re-delivery, lift charges and demurrage arrive as free-text lines. Structured formats want coded, priced items, and free text is where automated matching dies.
- Disbursements versus supply. Duty and VAT that a forwarder pays on a client's behalf, including amounts later recovered through duty drawback, are not the forwarder's own supply. Coding them as ordinary invoice lines overstates turnover and creates a VAT position nobody intended.
- Agent or principal. The same shipment can be a forwarder acting as agent on one leg and principal on the next, and the two produce different invoices from the same operational file.
- Self-billing and consolidated settlement. Large shippers often self-bill carriers or settle weekly against a rate table. National platforms have specific rules about who issues the document, and a self-billing arrangement that worked on paper may need re-papering.
- Goods description and classification. A freight invoice line describes a service rather than goods, so any HS code your customer expects on the document has to come from the customs file rather than from your rate table.
- Currency and surcharge timing. A bunker or currency adjustment fixed after the invoice date is a credit-note pattern, and every mandate has an opinion about credit notes.
- Cross-border place of supply. Transport services have their own place-of-supply rules, so the country whose mandate applies is not always the country your operations team thinks of as the origin.
The mistake that costs the most
The expensive error is treating this as a finance project. Almost every field a structured invoice needs originates in operations: the consignment reference, the weight actually charged, the customs entry number behind a cleared import, the party that ordered the service. When finance builds a compliant invoice on top of a transport management system that never captured those fields cleanly, someone ends up typing them in, and the throughput cost of manual entry outweighs the compliance cost.
The practical order of work I recommend is unglamorous. Start by mapping which of your entities invoice into which countries, because that single table tells you your real deadline. A Polish subsidiary invoicing domestically has a February or April 2026 problem. A German entity has had a receiving obligation since January 2025 and an issuing obligation coming in 2027. A business selling into France but established elsewhere needs to check whether the French obligation reaches it at all, since establishment drives the answer.
Then check your master data before your software. Buyer tax identifiers, addresses in structured fields, and a stable code list for your own charges do more for a successful go-live than any platform choice. I have seen a rollout stall for weeks over customer VAT numbers held as free text with country prefixes missing.
Choosing a route to the tax authority
There are broadly two shapes of national system, and they demand different things from you. Clearance models put the tax authority in the middle: Italy's SdI and Poland's KSeF receive the invoice, validate it and pass it on, and the platform's copy is the legal original. Network models move the document between accredited providers, with Peppol as the common example and France's accredited-platform model built on that idea. Belgium leans on Peppol BIS in UBL format, while Germany requires EN 16931 semantics without prescribing Peppol as the transport, so one provider has to cover both patterns.
For a carrier or forwarder operating in several countries, the sensible target is one internal invoice format that is rich enough to satisfy EN 16931, with country-specific output handled by a provider rather than by your own developers. Building direct connections to each national platform is possible and I have watched teams do it, but every mandate change then becomes your engineering backlog rather than someone else's product roadmap.
Two questions worth asking any provider: which of the 2026 mandates are already in production for their existing customers, and how they handle credit notes and self-billing for transport. The second question separates genuine freight experience from a generic accounts-receivable tool.
What to do before January
If you invoice into Belgium, Poland, Spain or France, the work that has to happen this year is short and specific. List the invoicing entities and their countries. Confirm you can receive a structured invoice today, because your customers' mandates hit you before your own. Fix the charge-code list so accessorials stop travelling as prose. Agree with your largest counterparties which of you issues the document. Then pick the delivery route, since that is the easiest part to change later and the hardest to fix under a deadline.
Some of these dates will move and the direction will not. Poland delayed KSeF once, then landed on February and April 2026 with an 11 month penalty-free window rather than a softer rule. Spain slipped twice: Royal Decree-Law 15/2025 of 2 December 2025 pushed Verifactu out of 2026 entirely, to January and July 2027. France restructured its platform model in October 2024 and kept September 2026. Plan for the sequence rather than for any single line, and treat 1 January 2026 as the real start, because Belgium, Poland and France all land inside 12 months of it.