If your company sells software, services, or physical goods to customers in Belgium, France, Germany, or Poland, a compliance deadline is bearing down on you right now — and unlike most tax deadlines, this one doesn't care whether you've heard of it. Starting January 1, 2026, Belgium requires structured electronic invoices for domestic B2B transactions. France follows on September 1, 2026. Poland's KSeF system phases in between February and April 2026. Germany's mandate arrives in 2027 and 2028. None of these countries are waiting for a global standard to catch up, and none of them are exempting foreign sellers just because the invoice originates in Ohio instead of Antwerp.
For a US-based exporter or SaaS company, "e-invoicing" sounds like a back-office IT problem that someone else will solve. It isn't. It's a legal requirement to generate invoices in a specific machine-readable format, transmit them through a government-approved network, and prove you did it correctly — or face penalties that, in at least one country, can double the VAT you owe on a single invoice.
What "E-Invoicing" Actually Means (It's Not a PDF)
The term is misleading. Emailing a customer a PDF invoice is not e-invoicing in the regulatory sense — it's just a digital picture of a paper invoice. Real e-invoicing means:
- Structured data formats: XML-based schemas like UBL (Universal Business Language), Germany's XRechnung or ZUGFeRD, France's Factur-X, or Poland's FA(3) schema — formats a computer can parse without a human reading it.
- Clearance or transmission through a government platform: many mandates route invoices through a national exchange (Poland's KSeF) or a shared network like Peppol, which Belgium, the Netherlands, Sweden, and Denmark all use as their primary transmission layer.
- Real-time or near-real-time validation: the invoice is checked, stamped with a unique reference number, and confirmed before or as the transaction happens — not reconciled weeks later at filing time.
This is the EU's VAT in the Digital Age (ViDA) package, formally adopted in March 2025, working its way through member states. The EU-wide Digital Reporting Requirement for cross-border B2B transactions doesn't fully land until July 2030, but — and this is the part that catches US companies off guard — individual member states are free to roll out domestic mandates years ahead of that EU-wide deadline. Belgium, France, Germany, and Poland all did exactly that.
The Deadlines That Matter Right Now
Belgium — January 1, 2026. All Belgian VAT-registered businesses must issue and receive structured e-invoices for domestic B2B transactions via Peppol, in the EN 16931 standard (Peppol BIS in UBL format is the default). There's a three-month tolerance window through March 31, 2026, but it isn't automatic — you have to be able to show you already took concrete steps toward compliance before the mandate hit. "We hadn't heard about it" doesn't count as a step.
France — September 1, 2026. Every VAT-registered business in France must be able to receive e-invoices from that date, with acceptable formats including UBL 2.1, UN/CEFACT CII, and Factur-X (a hybrid PDF/XML format). Issuing obligations phase in on a staggered schedule by company size shortly after. Non-compliance carries a €15 penalty per invoice, capped at €15,000 per year — not catastrophic for one invoice, but it adds up fast if your invoicing process is systematically non-compliant across hundreds of customers.
Poland — February and April 2026. Large taxpayers (annual turnover above PLN 200 million) must issue invoices through the KSeF platform starting February 1, 2026; every other VAT-registered business follows on April 1, 2026; micro-entrepreneurs get until January 1, 2027. Poland is giving a full-year grace period on penalties through the end of 2026 — but once that expires on January 1, 2027, invoices issued outside KSeF face penalties up to 100% of the VAT amount shown on the invoice. That's not a typo. Get it wrong and you can effectively double your VAT liability on that transaction.
Germany — 2027 and 2028. Every German company has had to be able to receive EN-compliant e-invoices since January 1, 2025. Issuing becomes mandatory for businesses with turnover above €800,000 starting January 1, 2027, and for everyone else by January 1, 2028. The applicable formats are XRechnung and ZUGFeRD, under the same EN 16931 standard as Belgium.
Why a US Company Can't Just Ignore This
The instinct is to assume a US entity invoicing from outside the EU is somehow out of scope. That's a costly assumption to test the hard way.
If you have a local entity, the mandate applies directly. A German GmbH subsidiary, a French SAS, or a Belgian branch office is treated exactly like any domestic business — no carve-out for having a US parent company.
If you're invoicing cross-border from a US entity, the rules get murkier and country-specific. Some jurisdictions push the compliance burden onto the receiving company to convert and validate the invoice; others require the sending party — you — to issue a compliant format from the start. This is exactly the kind of ambiguity that gets resolved against the seller when a tax authority audits the transaction.
If you sell digital services (SaaS, downloads, subscriptions) to EU consumers, you're already on the hook for VAT with no safety net. Non-EU sellers get no minimum-revenue threshold the way EU-based small businesses sometimes do. From your very first sale to an EU consumer, you're required to charge that customer's local VAT rate and remit it — and increasingly, to do so through a compliant e-invoicing channel. There's no "we're too small to worry about this yet" grace period for foreign sellers.
An 8-Step Approach to Getting Ahead of This
You don't need to solve every country's mandate simultaneously, but you do need a system that scales as more countries turn on their requirements. A reasonable sequence:
- Inventory where your revenue actually comes from. Pull the last 12 months of invoices by customer billing country. If Belgium, France, Germany, or Poland show up, you have a live deadline, not a hypothetical one.
- Identify your legal footprint in each country. A local entity means direct compliance; a US-only entity selling cross-border means you need to determine which party bears the formatting obligation.
- Ask whether your invoicing tool can generate structured formats today. If your current stack only produces PDFs, that's your first gap — UBL, XRechnung, Factur-X, and FA(3) are not features most standard invoicing tools have by default.
- Check whether you need Peppol network access. If you're transacting with Belgian, Dutch, Swedish, or Danish counterparties, Peppol connectivity (directly or through an access-point provider) is likely required.
- Map country-specific deadlines against your fiscal calendar, not against the calendar year — a deadline that lands mid-quarter changes when you need systems live, not just when the law technically takes effect.
- Decide: point-to-point integrations, or a centralized hub? Building a separate connection per country works for one market. It breaks down fast once you're compliant in three or four jurisdictions with different formats and validation rules.
- Assign ongoing regulatory monitoring to someone. These mandates keep moving — formats get revised, tolerance periods expire, new countries join. A rule you implemented correctly in January can be out of date by year-end.
- Run a test invoice through each required channel before the deadline, not after. Discovering a formatting rejection on your first live invoice after the mandate takes effect is the expensive way to learn the rules.
Where This Connects Back to Your Books
E-invoicing mandates are ultimately a record-keeping problem wearing a tax-compliance costume: every structured invoice you issue or receive needs to reconcile cleanly against your general ledger, in a format that survives an audit trail years later. Businesses that already keep clean, versioned financial records tend to adapt to these mandates faster — because the hard part isn't generating one compliant XML file, it's proving a consistent, auditable chain from invoice to ledger entry to VAT filing, across every jurisdiction you touch.
That's a much easier problem to solve when your books aren't locked inside a proprietary format you'd need special software to even read.
Keep Your Books Audit-Ready as Compliance Gets More Complex
As e-invoicing mandates spread across more countries, the businesses that adapt fastest are the ones whose financial records are already transparent and easy to reconcile. Beancount.io provides plain-text accounting that's fully version-controlled and auditable — every transaction lives in a format you can inspect, diff, and trace, with no vendor lock-in and no black box between your invoices and your ledger. Get started for free and see why finance teams navigating growing cross-border complexity are moving to plain-text accounting.