If you run a restaurant in Germany, France, Belgium, or Poland, the way you handle invoices is about to change. Not optionally. By law.
Multiple EU countries are mandating that businesses send and receive invoices in structured electronic formats — not PDFs, not scanned paper, but machine-readable XML files that meet specific technical standards. For restaurants that process dozens of vendor invoices weekly, this is a significant operational shift.
What's Actually Changing
The EU is standardizing how businesses exchange invoices. The goal is tax transparency and fraud reduction, but the practical impact falls on every business that sends or receives invoices — which means every restaurant.
The key standard is EN 16931, a European norm that defines what an electronic invoice must contain and how it must be structured. Several country-specific formats implement this standard:
- ZUGFeRD / Factur-X: Used in Germany and France. A hybrid format that embeds structured XML data inside a PDF, so humans can still read it while machines can process it automatically.
- XRechnung: Germany's government invoicing format, pure XML.
- PEPPOL BIS 3.0: Used across multiple EU countries (Belgium, Netherlands, and others) for standardized cross-border invoicing.
- FatturaPA: Italy's format, which has been mandatory since 2019.
The important thing to understand: a regular PDF invoice will no longer be legally sufficient for B2B transactions in these countries.
Country-by-Country Timeline
Italy — Already mandatory since January 2019. If you operate in Italy, you're already familiar with the FatturaPA format and the SDI clearance platform.
Belgium — January 2026. All B2B invoices must use the PEPPOL network and structured format.
Poland — February 2026 for large firms, April 2026 for smaller businesses. The KSeF (National e-Invoicing System) becomes mandatory.
France — September 2026 for large and mid-sized companies (receiving and sending). September 2027 for SMEs and micro-businesses.
Germany — Companies must already accept e-invoices as of January 2025. Mandatory sending begins January 2027 (small businesses get an additional year).
Why Restaurants Are Especially Affected
Restaurants deal with a high volume of relatively small invoices. A typical restaurant might process invoices from 15-30 different vendors every week — produce suppliers, beverage distributors, cleaning supplies, equipment maintenance, linen services, and more.
Most restaurants currently handle this through a combination of paper invoices, PDFs in email, and manual entry into accounting software or spreadsheets. That workflow will break when vendors start sending structured XML files that your systems can't process, or when your vendors require structured invoices from you.
The challenge is compounded by the fact that restaurant margins are thin. You can't afford the downtime of a poorly planned transition, and you can't afford to overspend on enterprise software designed for companies ten times your size.
Three Options for Getting Compliant
1. Upgrade Your Existing POS or Accounting Software
If you're already using a modern cloud-based POS or accounting system, check whether your vendor is adding e-invoicing compliance. Many are. This is the lowest-effort path if your current software handles it. The risk: your POS vendor may charge significantly more for compliance features, and the implementation may not fit your specific workflows.
2. Buy an Off-the-Shelf ERP with E-Invoicing
Solutions like SAP Business One, Oracle NetSuite, or Odoo offer e-invoicing modules. The advantage is that these are proven systems. The disadvantage is cost and complexity. SAP Business One, for example, typically starts at $3,200 per user plus implementation fees that can reach $50,000-$100,000. For a restaurant with 20 employees, that's significant overkill.
3. Build a Custom System
If your restaurant has specific workflows — recipe costing, multi-vendor procurement, specific approval chains, offline operation in the kitchen — a custom ERP can be built around exactly how you work, with e-invoicing compliance included from day one. Modern tech stacks (Next.js, cloud databases, serverless hosting) have brought the cost of custom development down dramatically compared to five years ago. A focused system with 3-4 core modules can be built for less than what a SAP implementation costs, and it will actually match your operations.
What to Do Right Now
If your deadline is 2026: You need to be actively implementing a solution now. Belgium and Poland deadlines are imminent. France's large-company mandate hits in September.
If your deadline is 2027: You have time to plan, but not as much as you think. Start by auditing your current invoice flow — how many vendors, what formats they use, what your accounting software can handle. Then evaluate your options.
Regardless of timeline: Talk to your accountant. Make sure they understand the format requirements. Many accounting firms are still catching up on the technical details of EN 16931 compliance.
The restaurants that prepare early will have a smoother transition and avoid the rush of last-minute implementations that will inevitably drive up costs and reduce vendor availability as deadlines approach.
If you're running a restaurant in the EU and need help preparing your systems for e-invoicing compliance, I'd be happy to discuss your specific situation. I've built restaurant ERP systems that handle purchases, inventory, recipe costing, accounts, and HR — adding compliant invoicing is a natural extension of that work.