If you sell food or drink anywhere in the EU, some version of “you’ll need e-invoicing soon” has probably reached you already — from an accountant, a supplier, or a software vendor. The trouble is that “e-invoicing” means different things in different countries, on different dates, and the answer to “do I need this now” depends entirely on where you and your customers are registered. Here’s what’s actually confirmed, as of mid-2026, and what it means in practice for a small producer.
The EU e-invoicing wave, in plain language
The EU-wide framework behind all of this is VAT in the Digital Age (ViDA), a legislative package the EU formally adopted on 11 March 2025. ViDA doesn’t itself force every business to switch to e-invoicing overnight — it rolls out in phases, and the piece that will eventually make electronic, EN 16931-format invoicing mandatory for cross-border (intra-EU) B2B transactions doesn’t take effect until 1 July 2030, under ViDA’s Digital Reporting Requirements (vatcalc.com).
What ViDA does do right now is give individual member states clear legal cover to introduce their own domestic mandatory e-invoicing rules ahead of that 2030 date — and several have. This is the part that actually matters for a small producer today: your obligation depends on your own country’s timeline, not the EU-wide one, and those timelines vary a lot. As of mid-2026:
- Belgium made structured B2B e-invoicing mandatory from 1 January 2026, built on the Peppol BIS 3.0 network, with a three-month grace period (no penalties) through the end of March 2026 for businesses that could show they were working toward compliance (EY).
- Poland’s KSeF system becomes mandatory in two waves: large taxpayers (over PLN 200 million annual revenue) from 1 February 2026, and everyone else from 1 April 2026, with enforcement penalties for micro-entrepreneurs following from 1 January 2027 (EY).
- Germany already requires all domestic businesses to be able to receive structured e-invoices since 1 January 2025. Issuing structured invoices for domestic B2B becomes mandatory from 1 January 2027 for businesses with turnover above €800,000, extending to all businesses from 1 January 2028 (European Commission).
- France requires all VAT-registered businesses to be able to receive e-invoices from 1 September 2026, with issuing mandatory for large and medium enterprises from that same date, and for small and micro-enterprises from 1 September 2027 (EY).
- Latvia, by contrast, postponed its B2B e-invoicing mandate — originally planned for January 2026 — to 1 January 2028, after the Saeima approved amendments to the Accounting Law on 5 June 2025 citing readiness gaps in the national e-invoicing infrastructure. In the meantime, Latvia does require e-invoice data reporting for B2G/G2G transactions with budget institutions from 1 January 2026 (KPMG; European Commission).
Two things fall out of this list. First, B2G came first everywhere — public-sector buyers across the EU have accepted structured e-invoices since 2019 under the earlier EU directive that preceded ViDA. Second, B2B is arriving country by country, not as a single EU switch-flip — which means the actual answer to “when do I need this” is “check your own country’s tax authority, and your major trading partners’ countries too,” not a single EU-wide date. If any of the above has moved since this was written, that’s expected — several of these dates have already shifted once; verify against your national tax authority before treating a deadline as fixed.
What an EN 16931 invoice actually is
This is the part that trips people up conceptually: an EN 16931 e-invoice is not a PDF, and it is not an invoice emailed as an attachment. EN 16931 is a European standard — published by CEN, originally mandated for B2G use by EU Directive 2014/55/EU — that defines a semantic data model: roughly 170 defined business terms (invoice number, seller VAT ID, line amounts, tax category codes, and so on) and the rules for what values each one can legally hold. It’s the structure an invoice’s data has to follow, independent of how that data gets serialized into a file.
For the actual file, EN 16931 recognizes two compatible XML syntaxes: UBL (Universal Business Language, from OASIS) and CII (Cross Industry Invoice, from UN/CEFACT). Either is valid; most European tooling and several national mandates (Belgium’s Peppol network, for instance) standardize on UBL. The practical upshot: a compliant e-invoice is a structured XML document a machine can parse and post directly into accounting software with no manual re-entry — a human-readable PDF can still exist alongside it for your own records, but the PDF isn’t the legal artifact anymore.
The fields small producers trip on
Once you’re actually generating EN 16931 XML rather than a PDF, a handful of fields cause the most rejected invoices for small producers who’ve never had to think about them before:
- VAT category codes. Every invoice line needs a coded VAT category (standard rate, reduced rate, exempt, reverse charge, and so on), not just a percentage. A domestic sale at 21% and a reduced-rate 12% line need distinct, correctly coded categories — get the code wrong and validators reject the whole invoice, not just the line.
- Buyer references. Many receiving systems — especially government and larger corporate buyers — require a specific buyer reference or purchase order number on the invoice for it to route correctly. Miss it and the invoice can be technically valid but still bounce back for manual handling.
- Country-prefixed VAT identifiers. VAT numbers in EN 16931 invoices need their two-letter country prefix (
LV,DE,FR, and so on) even when your own internal records store them without one. This is a small formatting detail that fails validation surprisingly often. - Missing seller/buyer address detail. The structured model expects a complete, correctly split address (street, city, postal code, country code) rather than a single free-text block — a format many small businesses’ existing invoice templates simply don’t have.
A practical compliance checklist
- Confirm your own country’s mandate date against its tax authority or an EU Commission country page — not a vendor’s marketing page — since these have already shifted for more than one country covered above.
- Check your largest trading partners’ countries too. If you invoice a French or Belgian business, their receiving obligations affect what you need to be able to send, even before your own country’s mandate lands.
- Confirm whether your accounting or invoicing tool can emit valid UBL or CII XML, not just a nicely formatted PDF — this is the single most common gap for small producers moving off spreadsheet-based invoicing.
- Audit your VAT category codes, buyer reference handling, and address data against the checks above before your mandate date, not after the first rejected invoice.
- Keep the legal PDF too — most regimes still expect a human-readable rendering alongside the structured XML, and your own team and customers will want to read invoices without opening an XML file.
How OakNex handles this
OakNex generates EN 16931-compliant UBL 2.1 invoices and credit notes alongside the legal PDF for every posted sales invoice — the structured XML and the human-readable document come from the same record, so they can’t drift apart. Every invoice is validated against the official EN 16931 conformance rules before it’s treated as complete, covering the trip-up fields above: correctly coded VAT categories, country-prefixed VAT identifiers, and full structured address data, pulled from your seller and customer records rather than retyped per invoice.
VAT handling itself — category resolution, cross-border treatment, VIES validation of buyer VAT numbers — is driven by OakNex’s built-in EU VAT engine, so the same invoice that satisfies EN 16931’s structural rules also gets its tax treatment right for domestic, intra-EU and export sales. See pricing for what’s included at each plan level if you want to see whether this fits your setup before your country’s mandate date arrives.