Why It May Be Time to Revisit Your E-Invoicing Strategy

Almost every organization dealing with e-invoicing mandates has a strategy already. The catch is that almost nobody actually chose it.

What usually happened instead: IT picked a platform, Finance scheduled the rollout, and somewhere in the process this got labeled “our approach.” Tax wasn’t in the room for most of it. Nobody sat down and decided this on purpose — it accumulated, deadline by deadline.

That’s worth saying plainly, because it’s not really anyone’s fault. E-invoicing has its roots in EDI, structured data exchange between trading partners, which was IT and Finance territory long before tax authorities took an interest. So, when governments started demanding real-time visibility into transactions, the people already running those systems made the calls — usually against a deadline, rarely with time to ask if it was the right call.  

Get compliant first, figure out if it’s good later.  

Except “later” tends not to arrive on its own.

Two Kinds of Control, Colliding

The reason this is worth revisiting now: the whole model of how tax authorities enforce compliance has shifted underneath it.

Governments have a few different tools for this — e-invoicing, e-reporting, certified billing systems, and more, with different countries mixing and matching. They’re all pointed the same way, though: closer to the individual transaction, further from the aggregated total. For simplicity, we’ll group them under one label here — Digital Transaction Controls.

Compare that to how enforcement used to work. Periodic Transaction Controls check compliance after the fact — a VAT return filed monthly or quarterly, built from totals, audited selectively and after the event.

Digital Transaction Controls work differently. Authorities validate at or near the moment of the transaction itself, whether through real-time clearance, continuous reporting, or certified billing. Every invoice, not a summary of invoices. The control point has moved from the return to the invoice.

That’s the real reason e-invoicing stopped being an IT problem and became a tax problem. Once the invoice is where compliance gets checked, someone accountable for VAT needs to actually understand what’s moving through that system — and in a lot of companies, whoever built the pipeline wasn’t thinking about VAT when they built it.

When to Leave It Alone — and When Not To

This isn’t a case for redesigning everything on principle. If your setup works — mandates are met, data moves, nobody scrambles — leave it. There’s no prize for fixing something that isn’t broken.

But if it doesn’t work, if there’s constant friction, manual workarounds holding things together, or tax finding out about problems after they’ve already happened, that’s worth raising. And the useful way to raise it isn’t to argue about it in the abstract. It’s to describe, concretely, what path the organization is actually on. That’s what the next two sections are for: a way to name the approach you’re running and be honest about its trade-offs, so the conversation starts from something specific instead of a vague feeling that things aren’t quite right.

Seven Questions That Reveal Your Real Strategy

To see what strategy an organization is actually running — not what someone would claim if you asked them — look at how it answers these:

• Geographic scope: global, regional, or handled country by country?

• Systems architecture: one provider, or several?

• Timeline: planned ahead, or reactive to whatever’s next?

• AR/AP: is this pushing accounts receivable and payable to modernize, or just adding weight to existing processes?

• VAT: does it make compliance simpler, or create a second reporting stream tax has to reconcile separately?

• Org structure: centralized, or run locally with no shared logic?

• Functional ownership: IT, finance, tax, or joint arrangement?

Most leaders have never actually mapped their company against these seven. That’s really the whole problem — not that nothing’s happening, but that nobody’s looked closely enough to see what all the activity has actually produced.

Four Archetypes, Each Trading Something for Something Else

Apply those seven questions across enough companies and four recognizable patterns to show up.

Global. One provider, planned rollout, IT-led. The upside is simplicity — one data model, one system to govern. The downside is rigidity: the platform sets the terms, and when it can’t handle something local, the fix tends to be a manual Excel workaround sitting quietly outside the system. Which defeats the point of the mandate in the first place.

Global-Hybrid. A global backbone, with local providers brought in wherever the main platform’s coverage or economics don’t hold up. Spend gets calibrated to actual risk instead of applied everywhere at the same premium. The cost is complexity — more vendors, more integration points, and a real risk of “hybrid drift” if nobody writes down the rules for when to deviate.

Regional. Built around the shared service center footprint, so it matches how finance already operates. Easier to roll out, since it follows an existing structure. But reporting fragments across regions, a group-level VAT view gets harder to assemble, and negotiating leverage disappears when nobody’s coordinating across borders.

Ad-hoc. No unifying logic — each mandate handled as its own project. Fastest and cheapest up front. Also, the one most likely to turn into vendor sprawl, inconsistent data, and real audit exposure down the line.

None of these four is a mistake by default. Each makes sense under the right conditions. What actually matters is knowing which one you’re on and being honest about what it costs. A company running Ad-hoc isn’t necessarily doing anything wrong — but it may not have registered what it’s giving up by staying there. Same with a Global setup that assumes it’s the “safe” choice without accounting for the rigidity that comes with it. The point isn’t to crown a winner. It’s to make sure the trade-off was actually seen before it was accepted.

Checkbox or Catalyst — a Separate Question Entirely

Here’s something that tends to catch people off guard: the archetype doesn’t decide the outcome. A Global rollout can sit there as pure compliance overhead — data passes through, nobody checks it against the VAT return; tax has no real visibility — or it can become the thing that actually pushes AP/AR and VAT reporting forward. Same architecture, very different result, depending on what gets asked of it.

Three Moves, If the Conversation Needs Starting

If the strategy your organization ended up with by accident isn’t serving you, here’s a reasonable way to start fixing it — without trying to take the whole thing over:

1. Educate. Figure out which archetype you’re actually running and say so out loud, even if you weren’t part of the original decision.

2. Close the gaps. If the current strategy doesn’t cover every entity, write down the second-tier approach on purpose instead of letting it sit as an undocumented exception. Bring the evidence — the manual patches, the compliance holes.

3. Move from checkbox to catalyst. Figure out what it would actually take to get business value out of e-invoicing. Reconciliation is often the natural first step, but the real goal is turning compliance spend into something that pays for itself.

None of this is about seizing control overnight. It’s about building enough expertise to earn a genuine seat at the table — one where the people accountable for VAT actually understand, and can help shape, the system the data runs through.

The mandates keep coming, and getting compliant was never the finish line.  

Every company already has an e-invoicing strategy.  

The only real question is whether anyone chose it on purpose.

‍

If your e-invoicing strategy has grown mandate by mandate rather than by design, it may be time to take a fresh look. Join Loek for a virtual coffee to discuss where you are today, what’s creating friction, and what a more deliberate approach could look like. He’ll also share fresh insights on the latest e-invoicing developments and go deeper into the topics explored in his articles.