Why one AP template can’t meet every e-invoicing mandate (and what to do)
Every multinational finance team is now living through the same problem at once. A wave of national e-invoicing mandates is landing across Europe and beyond, and the understandable instinct is to treat each one as a tweak to the existing Accounts Payable (AP) template: adjust a few fields, remap a format, move on. It rarely holds, because the mandates don’t just change the paperwork; they change the rules underneath it, and those rules are different in every country.
The work that needs doing sits in two places at once. There’s the global logic that routes and approves an invoice inside your business and there’s the local compliance layer each country imposes beneath it, with its own data fields, formats and validation steps. Standardize the first, localize the second, and keep the two working together. When enterprises master that architecture, a new mandate becomes a configuration job rather than a fire drill.
How e-invoicing mandates went global
The idea behind all of this is a clever Latin American innovation for closing the tax gap. When Brazil first rolled out the Nota Fiscal Eletrônica (NF-e) back in 2006, it put the tax authority in the middle of every transaction, and the country’s revenue rose noticeably as a result. It was successful enough that the model spread across the region and then well beyond it.
In 2019, Italy was the first European country to make this kind of real-time clearance mandatory and reported a first-year gain in domestic VAT of around €3.6 billion. The benefit went beyond the money, though. Because every invoice flowed through the tax authority as it was issued, the Italian government could see exactly how Covid was hitting each part of the economy and steer support to the businesses that needed it most, something that unfortunately the mostly paper-based UK simply couldn’t do, which is part of why its pandemic grants ended up spread evenly across firms whether they needed the help or not.
From there, we all watched the domino effect in play. Belgium made B2B e-invoicing mandatory over the Peppol network on January 1st 2026, and more than 1.1 million companies are now registered to exchange invoices through it. Poland’s National e-Invoice System (KSeF) followed on February 1st, Germany’s regime is phasing in through 2028, and France is next on the list. The direction of travel is settled; what differs, country by country, is the detail.
Why a single global AP template breaks
The trouble is that different laws demand genuinely different data architectures, so one ERP setup can’t quietly absorb them all. A global SAP configuration that works perfectly in Germany won’t satisfy KSeF validation in Poland, FATOORA clearance in Saudi Arabia, or the ViDA reporting fields the EU is introducing for cross-border transactions. Each of those is its own schema with its own required fields, in its own format and sequence, and none of them is a simple tick-box excerise on a generic workflow.
Germany shows how specific this gets: its B2B mandate began with mandatory receiving in 2025 and extends to mandatory issuing by 2028, and it requires structured invoices in an EN 16931-compliant format – either XRechnung, which is pure XML, or the ZUGFeRD hybrid, a PDF with the data embedded inside it. The move away from plain PDFs to machine-readable data is exactly the kind of detail that breaks a template built for somewhere else.
The EU’s VAT in the Digital Age (ViDA) package, in force since April 14th 2025, makes the scale of the problem plain: coordinating across 27 separate tax authorities means meeting 27 sets of reporting expectations. Saudi Arabia’s FATOORA mandate adds real-time clearance and cryptographic requirements on top, which hits smaller companies hardest. And while none of these challenges should be interpreted as insurmountable, it is true that none will survive a copy-paste from one country to the next.
A quick mandate comparison
Country or region | Mandate | Status | Format or network | Poland | KSef | Mandatory from 1 February 2026 for large taxpayers, 1 April 2026 for all other VAT-registered businesses | FA(3) XML via KSeF |
|---|---|---|---|
Belgium | B2B e-invoicing | Mandatory from January 1st 2026 | Peppol BIS 3.0 |
Germany | B2B e-invoicing | Mandatory receiving since 2025, mandatory issuing phasing in through 2028 | XRechnung or ZUGFeRD, EN 16931 |
Italy | SDI real-time clearance | In force since 2019 | SDI |
Saudi Arabia | FATOORA | Phased rollout, real-time clearance | Cryptographically signed e-invoice |
European Union | ViDA | In force since April 14th 2025, cross-border reporting phasing in later this decade | EN 16931 |
What to standardize for global e-invoicing compliance (and what to localize)
So what actually belongs in each layer? Multinational companies preparing for the new mandates should look hard at four things:
- workflow routing logic
- approval thresholds
- ERP integration architecture
- regulatory schemas
Workflow routing is the part that should stay internal so that companies can avoid adding both unnecessary compliance complications and to keep the business in control of its own approvals.
The regulatory schema is where the two layers meet. It dictates which data fields must be present, and in what format and sequence, for an invoice to be machine-readable under each set of rules. Because the designs of KSeF, FATOORA and ViDA are all different, an AP platform that handles all three must carry each schema as encoded knowledge, rather than as a manual setup repeated every time a new mandate goes live otherwise you’ve got a process that just doesn’t scale.
Protecting working capital with multi-country, multi-currency AP automation
Getting the architecture right is ultimately about protecting working capital. When a mandate trips a company up, say when an invoice can’t reach the tax system for validation, the customer can’t pay it, and that’s cash you can’t collect.
Susie West, Founder and CEO at sharedserviceslink, emphasized the positives for governments and firms alike, “Global B2B mandates are a huge opportunity for governments to reduce tax fraud and waste, and for businesses to modernize Finance. But they can initially disrupt AP processes. Legal invoices are often a more limited data set than the commercial invoices AP teams are used to receiving. When compliant invoices arrive without information such as a purchase order number or unit of measure, discrepancies can arise and match rates can fall. This is where AI solutions like Invoicetrack add real value, enriching invoice data using historic records to help maintain high invoice match rates.”
Automating the submission rules and the country-by-country tracking directly into the software is what keeps you compliant everywhere at once, protects your supplier relationships, and heads off those cash-flow shocks before they land.
This is where being built for the problem matters. Invoicetrack handles multi-entity, multi-currency invoice processing across more than 75 countries, with parameters configurable by entity and a single audit trail running across all of them. It comes already mapped to each jurisdiction’s rules rather than reconfigured by hand each time, and it’s likely the only AP automation platform built AI-native from the ground up, with its automation logic drawn from each customer’s own operational data. That makes the behavior traceable and governed in the architecture itself, rather than bolted on top of a generic workflow engine.
Getting ready for what's next, starting with France
France is next in line, and the lesson from the rollouts so far is that the hardest part usually isn’t the technology but capacity. Most teams simply won’t have the people to absorb a new mandate on top of business as usual, especially in the first months after go-live. That’s the gap a good partner is there to close, taking on the heavy lifting in advance and building automation up over time, rather than leaving you to staff up for a scramble.
What you want is an experienced invoicing partner across your AP processes – and ideally also in your Accounts Receivable (AR) too – who prepares you for what’s coming and smooths out any cash-flow knocks along the way. Much of that preparation can happen before a mandate even goes live: mapping each country’s requirements, pre-configuring the rules, and connecting to the government gateways so the data the AP department needs is captured. Those gateways don’t always ask suppliers for everything you’ll need downstream, so closing that gap early is part of the job.
The support matters most after launch, not before it. The post-live window is when the real exceptions start to surface and it’s the period of time that you’ll most benefit from having a dedicated team, on hand around the clock to help. This makes the difference between a manageable transition and a long, expensive cleanup.
One workflow, many mandates
Handled this way, e-invoicing stops being a recurring threat to your AP workflow and becomes something much closer to routine. You end up where you wanted to be from the start: one global system running your routing and approvals, with each country’s compliance rules sitting cleanly beneath it – not a stack of templates you’re forever patching by hand, one mandate at a time.
Frequently asked questions about e-invoicing in 2026
What is the difference between XRechnung and ZUGFeRD?
Both satisfy Germany’s EN 16931 requirement, but they carry the data differently. XRechnung is pure XML with no human-readable layer, built for direct system-to-system exchange. ZUGFeRD is a hybrid: a standard PDF with the same structured data embedded inside it, so a person can open and read the invoice while an ERP extracts the machine-readable version from the same file. With ZUGFeRD, compliance depends on the profile: only the EN 16931 profile and above qualify as a valid e-invoice; MINIMUM and BASIC WL do not meet the mandate. Which one a supplier sends often depends on their own system’s capability rather than a free choice.
Does the EU’s ViDA framework replace national mandates like KSeF or Germany’s e-invoicing rules?
No. ViDA sets the direction for cross-border reporting and long-term harmonization across the European Union, but national mandates such as Poland’s KSeF, Belgium’s Peppol requirement, and Germany’s XRechnung rules remain in force on their own timelines. Cross-border e-invoicing under ViDA is expected to become mandatory EU-wide later in the decade, but domestic mandates are arriving well ahead of that and are not waiting for EU-level convergence.
Can one AP platform handle multiple countries’ e-invoicing formats without a separate build for each country?
Yes, provided the platform separates two things: a single global routing and approval layer, and a library of country-specific compliance schemas that plug into it. Invoicetrack maintains this separation across more than 70 countries, so adding a new mandate is a configuration change to the schema layer rather than a rebuild of the workflow underneath it.
Is the Peppol network the same in every country that uses it?
The underlying network is shared, but the rules on top of it are not. Belgium mandates Peppol BIS 3.0 for domestic B2B transactions from 1 January 2026. Other countries using Peppol apply their own extensions, validation rules, or additional reporting layers on the same network. Using Peppol in one country is not a guarantee of compliance in another.
For the operational side of this and what actually happened inside AP teams after the Poland go-live, drawn from our Shared Services Link webinar with Avalara and read more at E-invoicing mandates and AP automation: why compliance is not enough.