eInvoicing Compliance 2026: What CFOs Actually Need to Do

France's eInvoicing mandate hits September 2026. Germany is drafting its own. And if your inbox looks anything like ours, every AP vendor on the planet has already emailed you about it.

The pitch is always the same: new regulation, massive complexity, you need a specialized solution or you'll be non-compliant. We've watched this playbook run for GDPR, for PSD2, for every regulation that touches finance operations. Vendors treat compliance deadlines the way mattress stores treat holidays. As a reason to manufacture urgency.

Here's what's actually happening. And what you actually need to do.

What the regulation says

France's Loi de Finances requires B2B invoices to use structured electronic formats starting September 2026 for large companies, with SMBs following in 2027. Germany's BMF published a draft discussion paper in 2024 proposing mandatory B2B eInvoicing. Italy has required it since 2019. The EU's ViDA (VAT in the Digital Age) directive pushes all member states toward real-time digital reporting by 2030.

The core requirement across all of these: invoices must be machine-readable. Structured data. XML-based formats like Factur-X, ZUGFeRD, or UBL, transmitted through networks like Peppol.

That's it. That's the regulation.

You're not being asked to rebuild your finance stack. You're being asked to send invoices in a format that computers can read without OCR.

Misconception 1: "You need a dedicated eInvoicing solution"

What vendors say: eInvoicing is a new category. It requires a new product. That product has its own pricing page with three tiers and an enterprise "contact us" button.

What's actually true: eInvoicing is a data format requirement. If your system can output structured data, you already have most of what you need. The "dedicated solution" pitch is like selling a special printer because the government changed the paper size. You don't need a new printer. You need to load different paper.

The vendors pushing hardest for standalone eInvoicing products are often the ones whose core platform can't produce structured output natively. They're building a new product to patch an architectural gap in their old one. Then charging you for both.

What to do: Check whether your current AP/AR tool supports Factur-X or ZUGFeRD output. If it does, enable it. If it doesn't, that's a feature gap in your existing tool, not a reason to buy a second one. Ask your vendor directly: "When will you support EN 16931 output?" If the answer involves a separate SKU, start looking elsewhere.

Misconception 2: "It's technically complex"

What vendors say: Every pitch deck includes a slide with overlapping circles, arrows between acronyms, and a footnote about "implementation timelines." Peppol, UBL, CII, EN 16931, XRechnung, Chorus Pro. It looks like you need a PhD in XML to comply.

What's actually true: These are XML schemas. They define which fields go where in a structured file. Your invoice already contains all the required data: supplier name, VAT number, line items, amounts, payment terms. eInvoicing means putting that data into a standardized XML structure instead of (or alongside) a PDF.

The technical complexity is real for the people building the standards and the transmission infrastructure. For the people using them, it's a configuration setting in software that handles it for you.

Here's a useful comparison: you don't need to understand SMTP to send an email. You don't need to understand UBL to send an eInvoice. You need software that does.

What to do: Ask your finance tool vendor one question: "Do you generate EN 16931-compliant invoices?" Yes or no. If the answer involves a six-week implementation project, a scoping workshop, or the phrase "it depends on your setup," find a different vendor. Format compliance in 2026 is a table-stakes feature, not a consulting engagement.

Misconception 3: "You'll need consultants"

What vendors say: Every business is different. Your chart of accounts, your approval chains, your VAT setup. You need a compliance audit, a gap analysis, and a phased implementation plan. Budget three to six months.

What's actually true: Format conversion is exactly what AI does well. Taking structured data from one schema and outputting it in another is a solved problem. It has been a solved problem for years. The consulting pitch works because it sounds reasonable: of course your business is unique. But the regulation doesn't care about your approval chain. It cares whether your invoice XML validates against a schema.

If your tool uses AI for invoice processing already (reading invoices, extracting data, matching to purchase orders), it can generate compliant formats too. The same technology that reads a messy scanned PDF and extracts line items can output a clean Factur-X file. This is not a stretch. It's the same pipeline running in reverse.

What to do: Before engaging any consultant, verify what your current software handles automatically. Most modern AP tools can generate compliant XML without human intervention. If yours can't, the fix is better software, not a consulting retainer.

Misconception 4: "It changes everything"

What vendors say: Your workflows will break. Your team needs retraining. Your integrations need rebuilding. Start preparing now or face chaos in September.

What's actually true: eInvoicing changes the output format of a document. That's it. Your approval workflows stay the same. Your GL coding stays the same. Your three-way matching stays the same. Your payment runs stay the same. The invoice arrives as structured data instead of a PDF and leaves as structured data instead of a PDF.

For most SMBs, the daily workflow change is zero. Your software handles the format conversion. You handle the business decisions. The people approving invoices won't even notice the difference.

Italy made eInvoicing mandatory for all B2B transactions in 2019. Seven years later, Italian businesses still approve invoices, still code expenses, still run payments. The format changed. The work didn't.

What to do: Nothing dramatic. Confirm your tool supports the required formats for your country. Set a calendar reminder three months before your deadline to run a test. Move on to problems that actually need your attention.

What actually matters

Strip away the vendor noise and the real story here is about data quality.

When every invoice is structured by default, you get clean data without trying. No more OCR errors from a scanner that read a 3 as an 8. No more manual entry mistakes from an intern mistyping an IBAN. No more reconciliation headaches caused by a misread digit on line 47 of a 200-line invoice.

Countries that adopted eInvoicing early saw measurable results. Italy's VAT gap dropped by an estimated 8 billion euros in the first three years after its mandate. Not because businesses became more honest overnight, but because structured data eliminates the ambiguity where errors and fraud hide.

For your finance team, this translates to faster processing, better matching rates, and fewer exceptions hitting the queue. That's not a marketing claim. That's arithmetic.

The CFOs who benefit most from eInvoicing mandates won't be the ones who bought the fanciest compliance tool. They'll be the ones who recognized that structured data was coming and chose systems built to work with it natively.

The vendor test

Here's a filter for evaluating any eInvoicing pitch you receive between now and September 2026.

If a vendor talks mostly about the regulation, the penalties, and the risks of non-compliance, they're selling fear. If a vendor shows you how their existing product already handles the format and talks about data quality improvements, they're selling something real.

The vendors spending the most on eInvoicing alarm campaigns are usually the ones whose products require the most work to become compliant. They're not warning you about your problem. They're describing their own.

How Well handles it

Well processes invoices using AI from the ground up. Reading structured formats, extracting data, generating compliant output. This isn't a feature we're bolting on for 2026. It's how the product works.

When France's mandate lands, Well users won't receive a migration guide or an upgrade invoice. The system will output Factur-X because it already reads and generates structured data as its default mode of operation. Format compliance is a configuration change, not a product overhaul. That's what it means to be built on AI-native document processing rather than PDF-first with AI added later.

The timeline

French companies: September 2026 for receiving eInvoices (all sizes). September 2026 for issuing (large enterprises). September 2027 for issuing (SMBs and mid-size).

German companies: Draft legislation circulating since 2024. Mandatory B2B eInvoicing expected 2027 or 2028. Timeline still shifting.

All EU member states: ViDA directive targets 2030 for cross-border real-time reporting convergence.

You have time. Not unlimited time, but enough to evaluate properly rather than react to the next vendor email that lands this week.

Check what your current tools support. Ask the one-question test. And if you need to switch, pick a tool built on structured data processing, not one that added an eInvoicing checkbox to its feature list six months before the deadline.