Executive summary

Key findings

Connected compliance means running VAT reporting and eInvoicing for every jurisdiction on one platform and one data layer, instead of a separate tool per country. In G2's October 2026 study of 102 tax, finance and IT leaders at multinationals, 72% are either consolidating onto a connected platform or already run one, and 77% say fragmented, country-by-country compliance creates material manual effort, cost or control risk. Continuous Transaction Control (CTC) mandates and the EU's VAT in the Digital Age (ViDA) package, which makes digital reporting of intra-EU B2B transactions mandatory from July 2030, are turning that cost into a decision.

What do multinational tax and finance leaders weigh when they move to connected compliance?

Most of the multinationals in this study are already moving. Nearly three in four are consolidating VAT and eInvoicing onto one connected platform or run one today, and what pushes them is the cost of the hybrid estate they run in the meantime: reconciliation done by hand, deadlines missed when a connector fails, audit findings when the same process runs differently in two countries. A regulatory deadline is usually the event that turns that cost into a funded project. Once the budget exists, what they weigh is evidence. They want a provider with real depth in the countries where their exposure sits before they care about the length of its country list, they treat direct ERP integration as a requirement rather than a feature, and because their last implementation slipped on data and integration, they now test providers on their own transactions before they sign.

How much of VAT compliance will they let software run alone?

Invoice generation, transmission, validation and matching are work most respondents will hand to the system today. The final filing, the payment and the exception stay with a person, because accountability sits with the company, not the software, and auditors agree. What moves that line is a parallel run on the buyer's own transactions over several filing cycles, supported by a track record through an audit and rules that trace back to the statute. The business case that funds all of it pairs total cost of ownership with compliance risk; savings alone rarely get it through.

Themes shaping the market

Six findings connect the chapters, from how far the shift has gone to the proof that decides which platform wins.

The shift

Consolidation is a project most are already running

72% are moving to one platform or already there. The hybrid estate is the starting point, not the destination.

Cost of fragmentation

Reconciliation is where fragmentation bills first

77% feel the cost of separate country tools, and reconciling VAT returns to eInvoices is becoming a live control rather than a month-end task.

Triggers and the case

A mandate opens the decision; cost plus risk closes it

A regulatory deadline moves 30%. The business case that passes pairs total cost of ownership with compliance risk (49%); savings alone rarely carry it.

Expertise and ERP fit

Depth in key countries and the ERP come before coverage

64% rank local regulatory expertise above breadth, and 69% call direct ERP integration with VAT-field mapping essential.

Implementation

Buyers test providers because they have been burned

44% hit data and integration problems last time; 30% now run their own countries and transactions through a provider before contracting.

Automation and proof

Automate the routine, keep the signature, prove it side by side

People keep sign-off on filings and exceptions (32%), and 36% want a parallel run on their own data before they step back.

Eunice Buhler, General Counsel, G2

“The promise of connected compliance isn’t simply that technology can make regulatory obligations easier to manage. Instead, it’s that businesses can move from reacting to compliance risks to anticipating and preventing them. Importantly, however, automation doesn’t transfer accountability. The companies that will benefit most are those that demand transparency, test the technology against their own operational realities, and build systems they can genuinely trust. Done right, compliance becomes a source of operational strength and competitive advantage.”

Eunice Buhler — General Counsel, G2
Chapter 1

How far along are multinationals in moving to connected compliance?

Nearly three in four are consolidating VAT and eInvoicing onto one platform or already run one. The hybrid estate they run in the meantime is the starting point for everything that follows.

“Our core transactions originate in our global ERP system, but over time we've ended with a fragmented setup. For certain mandatory continuous transaction control countries, like Italy with SDI or our preparations for the French mandate. We've had to deploy specialized local middleware and connectors. Meanwhile, for standard periodic VAT filings, we rely partly on central automated reporting and partly on outside local tax advisors to handle local filings and audits.”

— Tax technology and invoicing compliance, multinationalG2 AI Custom Research, 2026

Listen
The shift

What does the estate look like today?

Of the 101 leaders who placed their organisation on a scale from fully separate country-by-country tools to one connected platform, 46% said they are actively in the middle of consolidating and 27% said they already run one across most or all markets. Only 22% still run fully separate tools. Connected compliance is the project most of this group is running now, not a future state they are weighing.

71% of the 100 who described their setup run a hybrid: a central ERP or compliance platform for the core, with local middleware, government portals or outside advisers covering the countries that run their own clearance regimes. A tax technology lead at a multinational described "a mix of both" as "one of our biggest ongoing challenges": core transactions start in the global ERP, but "for certain mandatory continuous transaction control countries, like Italy with SDI or our preparations for the French mandate" the team had to deploy local middleware and connectors, while periodic filings lean partly on outside advisers. A digital lead in Poland called the national clearance system "huge change here in Poland" and said the rest of the group runs "separate solution in line with the local requirements" in each country. Consolidation means bringing those pieces onto the central layer one jurisdiction at a time.

Key takeaways
1
Hybrid estates are the starting point: 71% combine central systems with local tools, advisers or government portals; 14% already run a centrally managed platform and 12% rely on fragmented country-level tools (base: 100). The hybrid is rarely by design. A global controller at a US software company described one tax engine attached to the ERP for North America, an accounting firm for the UK and local firms everywhere else, each inherited with an acquisition. Respondents describe the central core as the thing they trust and the local pieces as the thing they manage.
2
The ERP is the anchor, not the whole answer: Of the 84 who named their setup, 29% run an SAP-led stack, 21% a named non-SAP platform or adviser, and 21% a mix of local providers, portals and regional tools. Even the SAP-led group rarely runs SAP alone: a head of finance and tax for EMEA and the Americas described extracting from SAP to hand to external providers who prepare the returns, while a new eInvoicing platform is "in the implementation phase". The ERP holds the transactions; something else has to turn them into compliant filings in each country.
3
Consolidation runs country by country: Respondents describe one platform for the biggest markets with legacy tools migrated as eInvoicing mandates arrive. A global purchasing lead said the group is "already benefiting from a unified platform across all European markets" but is "still in the process of running in parallel the country by country solutions" elsewhere, and a head of group controlling expects to "complete the project" in one or two years. A single global cut-over was the exception, and parallel running was the norm.
What this means for tax leaders

Plan the transition, not a rip-and-replace. Most of your peers are mid-consolidation and running a hybrid estate, so judge a platform on how it absorbs local tools, portals and advisers one jurisdiction at a time, with parallel running built in. Ask for the roadmap from hybrid to connected and the milestones along it, because that is the project you are already running.

Verbatim proof
“We are not operating on one connected platform. But most functions, they are already consolidated. I think in one or two years we will complete the project.”
Head of Group Controlling, multinationalon the consolidation programmeG2 AI Custom Research, 2026

What the hybrid estate costs. Most of this market is mid-migration. The next chapter puts a price on the estate they run in the meantime, and on the reconciliation work that price shows up in first.

Operating model stage
72%

are consolidating toward a connected platform or already run one. Fewer than a quarter still run fully separate tools.

Stacked bar chart: 72% of multinationals are consolidating VAT and eInvoicing onto one platform or already run one (base: 101) — G2 Research 202646%27%22%
Actively consolidating toward a connected platform46%
Connected platform across most or all markets27%
Fragmented country-by-country tools22%
Other5%

Source: G2 AI Custom Research, The Future of Connected Compliance, 2026. Based on 101 respondents who addressed the question; percentages of that base, rounded.

72% are on the path to one platform. Based on 101 respondents.
CategoryShare
Actively consolidating toward a connected platform46%
Connected platform across most or all markets27%
Fragmented country-by-country tools22%
Other5%
Chapter 2

What does fragmented, country-by-country VAT compliance actually cost?

Three in four say it costs real money, time and audit exposure. Reconciliation between VAT return data and eInvoice data is where the bill lands first.

“During a routine tax authority review, the discrepancy was flagged as an inconsistency which delayed our input VAT recovery and forced our team to spend weeks manually reconciling individual transaction logs to prove compliance.”

— Tax compliance and VAT lead, multinationalG2 AI Custom Research, 2026

Listen
Cost of fragmentation

Is reconciliation becoming a bigger priority?

77% of the 97 leaders who addressed the question say running compliance through separate country tools creates material manual effort, headcount, tool or adviser cost, and control risk. Only 7% report no material cost or audit problem. The examples are concrete: a chief risk officer at a financial services group described a VAT reconciliation "performed differently in different geographies" that internal audit flagged "as a major finding", and an operations lead said pulling data from several systems turns "a quick automated process" into "hours of work per reporting cycle".

Of the 95 asked whether reconciling VAT return data against eInvoice data is becoming a bigger priority as compliance goes digital, 41% said yes because of regulatory scrutiny and penalty exposure and 36% said yes because fragmented data and manual work make it hard. A tax compliance director at a pharmaceutical group put the change plainly: "reconciliation is no longer just a month end accounting activity", because discrepancies become visible to tax authorities much sooner. A tax technology lead explained why: under continuous transaction controls the authority already holds the transactional eInvoice data before the periodic return is filed, so a summary that does not match the invoices "triggers immediate red flags". Only 14% described reconciliation as a settled priority their current automation already handles.

Key takeaways
1
Reconciliation is becoming a control, not a chore: 77% say reconciling VAT return data against eInvoice data is a growing priority: 41% because of regulatory scrutiny and penalties, 36% because of fragmented data and manual work (base: 95). A global controller described the two speeds inside one company: where the tax engine syncs to the ERP, "it does a reconciliation automatically"; for the smaller locations that do not sync, "we have to do a manual reconciliation" every quarter and again for the audit.
2
Regulation is raising the bar: 57% say regulatory change, alone or with internal change, has recently made transaction-level reporting more of a priority; 13% see no increase (base: 95). The triggers respondents named are specific: continuous transaction controls, ViDA, the French mandate, Poland's clearance system, HMRC's Making Tax Digital. A retail CFO's trigger was an error: "in one country, Germany in particular, we were out of compliance. We had our percentages wrong", which forced an update to the central platform.
3
Local controls contain it for a few: 10% say local expertise and controls keep the coordination cost manageable, and 7% report no material cost or audit problem (base: 97). This group tends to be smaller or more vertically integrated; a healthcare-adjacent group with 11 territories on one accounting suite said digital, real-time reporting has made things "slightly more straightforward" rather than harder. For everyone else the cost is in time: a director of group transformation at a financial services group estimated that "about 20%" of the group's year-on-year investment goes on managing compliance, country by country.
What this means for tax leaders

Put a number on fragmentation before you go to the CFO. Count the manual reconciliation hours, exception volumes, missed deadlines and audit findings by jurisdiction; that figure is the opening line of the business case. Then ask any provider to show VAT-return-to-eInvoice reconciliation running inside the filing workflow rather than as a separate report. That is the control layer continuous reporting demands, and a better test than a generic automation demo.

Verbatim proofListen
“One example we had last year was around a VAT compliance reconciliation which was performed differently in different geographies, which was identified by our internal audit and flagged as a major finding. So we had to spend a lot of time to realign, fix, make sure that different processes are fit for purposes and generate a similar outcome.”
Chief Risk Officer, financial services multinationalon an audit finding caused by fragmentationG2 AI Custom Research, 2026

What turns the cost into a decision. A cost that is felt every month still needs an event to become a project. The next chapter is about which events do that, and why a fifth of organisations no longer wait for one.

Impact of fragmented compliance
77%

report material manual effort, cost and control risk. Just 7% say the status quo is cost-free.

Waffle chart: 77% say fragmented, country-by-country VAT compliance creates material manual effort, cost or control risk (base: 97) — G2 Research 2026
Material manual effort, headcount, tool or adviser cost and control risk77%
Manageable coordination cost, contained by local expertise and controls10%
No material cost or audit problem reported7%
Other6%

Source: G2 AI Custom Research, The Future of Connected Compliance, 2026. Based on 97 respondents who addressed the question; percentages of that base, rounded.

77% feel the cost of fragmented compliance. Based on 97 respondents.
CategoryShare
Material manual effort, headcount, tool or adviser cost and control risk77%
Manageable coordination cost, contained by local expertise and controls10%
No material cost or audit problem reported7%
Other6%
Lisa Dowling, Chief Tax & Client Enablement Officer, Fintua

“Managing VAT compliance across multiple systems, data sources and country-specific processes often requires time-consuming manual reconciliation. Centralising VAT compliance and eInvoicing, with automated reconciliation built into the workflow, helps businesses identify discrepancies before submission, improve accuracy and efficiency, and systematically address underlying master data issues.”

Lisa Dowling — Chief Tax & Client Enablement Officer, Fintua
Chapter 3

What triggers organisations to consolidate their eInvoicing and VAT compliance providers?

A regulatory deadline is the clearest trigger, named by 30%. A fifth are already moving without one, and a hard core will not move until something breaks.

“It would take new incoming regulatory mandates such as expanded e-invoicing laws in key operating markets that our current patch of local tools simply can't handle efficiently. So when legacy software creates a genuine risk of non-compliance or business disruption, securing executive buy-in for a single global solution becomes straightforward.”

— Tax compliance and VAT lead, multinationalG2 AI Custom Research, 2026

Listen
Consolidation triggers

Why do the rest stay put?

Asked what would move consolidation to the top of the list, 30% of the 97 who answered named a regulatory deadline, compliance exposure or an audit failure. A tax compliance lead described "new incoming regulatory mandates such as expanded e-invoicing laws in key operating markets that our current patch of local tools simply can't handle efficiently"; when legacy software creates "a genuine risk of non-compliance or business disruption", executive buy-in for a single platform "becomes straightforward". A further 20% said consolidation is already a strategic priority and needs no trigger.

13% say their current tools are adequate, so only a major failure or capability gap would make them move. A retail CFO said it would take "a significant error or a significant audit risk", because "our tools are in place and they are humming along" with outside auditors checking the work. A healthcare-adjacent finance leader was blunter: the platform is "much too deeply ingrained and embedded within the business. It's working." For this group the cost of change is visible and the cost of staying is not. A quantified ROI case would move 15%, and 8% are waiting on leadership sponsorship, budget or the timing of a wider transformation; one IT officer said the review simply happens "at each contract renewal", when the organisation runs "a formal RFP".

Key takeaways
1
Mandates convert cost into urgency: 30% say regulatory deadlines, compliance exposure or audit failures would push consolidation to the top of the agenda (base: 97). The mandates respondents cite are the ones with clearance built in: a senior accountant at a UK university said a firm deadline from the UAE or the next phase of Making Tax Digital "moves it from nice to have to a must to do", and the tax technology lead whose invoices were rejected "at the tax platform clearance level" after a minor field-mapping error now treats every schema update as a risk event.
2
For one in five, the decision is made: 20% say consolidation is already a strategic priority, with budget and programmes in motion. These are the organisations in the previous chapter's 46%: a head of group controlling with most functions consolidated and a two-year horizon, a tax technology lead "working to bring those disconnected local solutions into a unified, centralized compliance architecture". For them the trigger was a pattern of local failures rather than one deadline.
3
Adequate tools breed inertia: 13% say their tools are adequate, so change would need a major failure or capability gap. 15% would move on a quantified ROI case and 8% on sponsorship, budget or transformation timing. A finance manager at an IT services firm described the gap between the two: the company "suddenly grew in the last three to four years", outgrew "proprietary old pattern tools", and now needs top management to "do one time investment" before anything changes.
What this means for tax leaders

Move before the mandate moves you. Map the clearance and reporting deadlines in your key markets and run a jurisdiction-by-jurisdiction readiness assessment with a quantified exposure scenario; that is what turns connected compliance into the risk-control investment executives approve. If your tools are humming along, benchmark the current-state gaps anyway, so a latent risk is visible before a mandate failure forces a reactive replacement.

Verbatim proofListen
“I think you would have to have a positive ROI or a direct linkage to cost takeout. I think it could stem from the organization itself. However, a regulatory deadline or an external factor would likely speed it up.”
Head of Global Business Services for Finance Operations, spirits multinationalon internal versus external triggersG2 AI Custom Research, 2026

Writing the case. Whether a deadline or a programme opens the door, the investment still has to clear the CFO and CIO. The next chapter is about what the business case has to contain to get through.

What would trigger consolidation
30%

would move on a regulatory deadline, compliance exposure or an audit failure, the single largest trigger named.

Regulatory deadlines, compliance exposure or audit failures
30%
Already a strategic priority
20%
A quantified efficiency, cost-saving or ROI case
15%
Current tools are adequate; only a major failure or capability gap
13%
Leadership sponsorship, budget, IT capacity or transformation timing
8%
Other
14%

Source: G2 AI Custom Research, The Future of Connected Compliance, 2026. Based on 97 respondents who addressed the question; percentages of that base, rounded.

A deadline moves 30%; a fifth are already moving. Based on 97 respondents.
CategoryShare
Regulatory deadlines, compliance exposure or audit failures30%
Already a strategic priority20%
A quantified efficiency, cost-saving or ROI case15%
Current tools are adequate; only a major failure or capability gap13%
Leadership sponsorship, budget, IT capacity or transformation timing8%
Other14%
Chapter 4

How do tax teams build the business case for a connected compliance platform?

Half frame it as economics plus risk. Savings alone rarely carry it, and the people who approve it are the CFO and CIO.

“What matters most to our approvers is a clear ROI model backed by tangible operational risk reduction, proving that doing nothing carries far higher recurring costs and business disruption than the implementation itself.”

— Tax technology and invoicing compliance, multinationalG2 AI Custom Research, 2026

Listen
The business case

Do hard numbers get it approved on their own?

Half of the 85 leaders who discussed the investment decision (49%) frame it as a combined economic and risk case: total cost of ownership and implementation effort on one side, exposure to penalties, audit failures and disruption on the other. A tax technology lead framed the case for the CFO and CIO around "the direct cost takeout, the working capital and revenue protection, and head count and audit exposure reduction", proving "that doing nothing carries far higher recurring costs and business disruption than the implementation itself".

21% lead with quantified time, headcount or ROI savings, and 13% lead with compliance, audit and penalty-risk reduction. The savings-first camp is real: a business development manager said "at the end a business case is it's just about money", and would simply "put the hours or the mistakes that we've done" into currency. But most respondents in both camps said the other half is needed to close. An operations lead leans toward "risk reduction and strategic position and then we support that with numbers", because hard savings "on their own" are "not usually enough to push it through". A product manager at a consultancy described the formal paper every group-wide investment needs: "why, what, how, when", a measured return and benefits realised at the end.

Key takeaways
1
Economics plus risk is the winning frame: 49% set total cost of ownership and implementation effort against compliance and operational risk, more than twice the share leading with savings alone (base: 85). The TCO line is specific: a corporate finance lead at a conglomerate benchmarks "statutory non-compliance fines against the one time implementation and recurring platform subscription costs" and shows "the elimination of expensive local point solutions and redundant IT maintenance overhead".
2
Savings alone rarely carry it: 21% lead with quantified time, headcount, cost or ROI savings and 13% with risk reduction. Both groups said the other half of the argument is needed to get approval. A digital lead in Poland said the organisation talks "mostly" about cost savings, but on regulation the decision is forced: "we have to implement something new because we are missing some of the parameters".
3
Strategic cases are a minority: 9% say approval rests on scalability, a mandatory requirement, provider proof or an executive sponsor rather than a quantified case. Where the mandate does the arguing, as with the French reform for an e-commerce finance project manager, the case writes itself: regulatory requirements "pushed us to move faster", and the efficiency and fraud-control benefits followed.
What this means for tax leaders

Write both columns of the business case. Pair a total-cost-of-ownership model that retires local point solutions, adviser spend and manual reconciliation with a costed view of avoided penalties, audit findings and filing disruption. Write it for the CFO and CIO, who are the approvers your peers named, and treat a provider's ROI calculator as the start of the conversation rather than the whole of it.

Verbatim proofListen
“If I had to lean one way, it's more about risk reduction and strategic position and then we support that with numbers. Hard numbers like time savings or cost reduction definitely help justify the investment, especially for finance teams, but on their own they are not usually enough to push it through.”
Operations lead, multinationalon risk versus savingsG2 AI Custom Research, 2026

Which platform earns the money. With the budget approved, the question becomes which platform deserves it. The next three chapters are the proofs buyers ask for, starting with the one they rank first: expertise in the countries that matter.

How the business case is framed
49%

pair total cost of ownership and implementation effort with compliance risk. Savings alone lead for 21%.

Donut chart: 49% build the business case for connected compliance on cost plus risk (base: 85) — G2 Research 2026
49%
Combined economic and risk case, including TCO and implementation effort49%
Led by quantified time, headcount, cost and ROI savings21%
Led by compliance, audit, penalty and operational-risk reduction13%
Strategic scalability, mandatory compliance, provider proof or executive sponsorship9%
Other8%

Source: G2 AI Custom Research, The Future of Connected Compliance, 2026. Based on 85 respondents who addressed the question; percentages of that base, rounded.

49% build the case on cost plus risk. Based on 85 respondents.
CategoryShare
Combined economic and risk case, including TCO and implementation effort49%
Led by quantified time, headcount, cost and ROI savings21%
Led by compliance, audit, penalty and operational-risk reduction13%
Strategic scalability, mandatory compliance, provider proof or executive sponsorship9%
Other8%
Diagram: connected compliance runs on proof, from fragmented systems to trusted decisions. Left: fragmented systems, ERP data, local tools and country portals, with manual reconciliation of disconnected data and repeated checks. Middle: a connected data flow where transactions move through one controlled workflow, with three checkpoints: parallel testing against human review, an audit trail tracing each decision to data and rules, and validated results over several filing cycles. Right: connected compliance with shared data, rules and controls, and human sign-off on filings and exceptions.
Left: the hybrid estate most respondents run today, ERP data plus local tools and country portals, reconciled by hand. Middle: parallel testing against human review, an audit trail from each decision to its data and rules, and results proven over several filing cycles. Right: one controlled workflow with shared data, rules and controls, and a person still approving filings and exceptions.

The left side is where 71% of respondents start: a central ERP with local middleware, portals and advisers bolted on, and the reconciliation between VAT return data and eInvoice data done by hand. 77% say that estate costs them real time, headcount and audit exposure.

The checkpoints in the middle are the part of the story buyers care about most. 64% want proof of local expertise before a long country list, 69% call ERP integration essential, and 36% will only step back from manual checks after a parallel run on their own data. The right side keeps a person on the signature: 32% retain final sign-off on filings.

Chapter 5

Should a multinational choose one global eInvoicing provider or local specialists?

Buyers answer a different question first: can the provider prove depth in the countries where the exposure sits? 64% rank that above the length of the country list.

“Depth in key countries usually matters more than just broad coverage. We'd rather have a provider that is really solid and reliable in our core markets, even if their global coverage is slightly more limited.”

— Operations lead, multinationalG2 AI Custom Research, 2026

Expertise over coverage

Who puts coverage first, and why?

Asked to weigh breadth of country coverage against depth of regulatory expertise, 64% of the 95 who answered put expertise in their key jurisdictions first. The logic is risk-weighted. A tax compliance lead said a provider "can cover 100 countries, but if their coverage in our key revenue drivers is superficial or it is relying on unstable local workarounds, the risk of audit penalties increases". In clearance countries, as a tax technology lead put it, errors "cause real time invoice rejections that stop shipments, delay cash collections and trigger statutory penalties".

15% prioritise broad global coverage and supplement it with in-house or local specialists, usually because they are committed to a single provider across every territory. A healthcare-adjacent finance leader with 11 countries said the group would choose the provider that covers all of them even if its depth in one is weaker, because "we can buy in depth of expertise from a person if we need to", whereas missing functionality in a territory "we can't plug that on to a software solution". Another 16% refuse the trade-off and want both from one provider. A director of group transformation at a financial services group said it is "not an either or, it's both", and the strategy and finance lead at an insurer said the weight on coverage "is increasing" as the group standardises tools, even though depth still decides.

Key takeaways
1
Expertise is the hardest thing to compromise on: Asked which requirement they would find hardest to give up, 37% of 94 said regulatory expertise and compliance reliability, ahead of ERP fit and data quality (31%) and coverage (13%); 9% said several are jointly non-negotiable. A financial controller at a technology consultancy explained the ranking: with expertise "you could explain the information" to a regulator even on a manual process, whereas without it "there's no point having a fancy system or coverage because everything will just be wrong".
2
A sizeable minority refuse the trade-off: 16% want broad coverage and strong local expertise from one provider, and they check that depth market by market rather than take it on trust. A gear manufacturer's compliance lead warned that broad coverage with expertise that is "a kind of a shallow thing" creates a risk of clearance failures and local audit penalties, while deep expertise in only a few countries leaves "a fragmented vendor track".
3
Coverage-first buyers back it with people: 15% prioritise broad coverage and supplement it with in-house or local specialists; for them a territory the software cannot support is the harder gap. An IT lead in chemical logistics said the group tends to go for "the big well-known global brands" and still relies "more heavily on internal in-house knowledge", which "can be quite costly".
What this means for tax leaders

Test depth in your biggest markets before you read the country list. Lead evaluations with jurisdiction-specific scenarios: who maintains the rules for your key markets, how quickly a change reaches you, and the track record of keeping them current. Then treat global coverage as the layer that lets you expand without adding another vendor. Coverage without demonstrated depth is the claim your peers discount most.

Verbatim proof
“It would probably be expertise. Because you can make the ERP fit work. But the expertise is hard won. And that's sort of the premium that we are paying for that solution or provider.”
Director of Group Transformation Office, financial services multinationalon the hardest compromiseG2 AI Custom Research, 2026

The second proof is technical. Local depth gets a provider onto the shortlist. The next chapter is the proof that keeps it there, and it sits inside the buyer's ERP.

Coverage versus regulatory expertise
64%

prioritise regulatory expertise in their key jurisdictions. 16% want both; 15% put coverage first.

Bubble chart: 64% prioritise depth of regulatory expertise over breadth of country coverage (base: 95) — G2 Research 202664%16%15%5%
Regulatory expertise in key jurisdictions over breadth of coverage64%
Broad coverage and strong local expertise, both required16%
Broad global coverage, supplemented by internal or local specialists15%
Other5%

Source: G2 AI Custom Research, The Future of Connected Compliance, 2026. Based on 95 respondents who addressed the question; percentages of that base, rounded.

64% choose depth over breadth. Based on 95 respondents.
CategoryShare
Regulatory expertise in key jurisdictions over breadth of coverage64%
Broad coverage and strong local expertise, both required16%
Broad global coverage, supplemented by internal or local specialists15%
Other5%
Chapter 6

How important is ERP integration in an eInvoicing and VAT compliance platform?

Close to a universal requirement. 69% call direct integration with VAT-field mapping essential, and the 1% who call it secondary are the exception that proves it.

“The direct ERP integration is essential, it's a non-negotiable requirement for us. When source data doesn't map directly to VAT return fields, the entire process breaks down into manual extraction and messy offline spreadsheets. Our tax team has to spend days manually reconciling line items, tax codes, and credit notes before submission.”

— Tax technology and invoicing compliance, multinationalG2 AI Custom Research, 2026

Listen
ERP integration

What happens when the mapping is missing?

69% of the 98 leaders who addressed the question say direct ERP integration, including mapping source data to VAT return fields, is essential for automation and compliance; only 1% treat it as a secondary requirement. A tax technology lead called it "a non-negotiable requirement": when source data does not map to return fields, "the entire process breaks down into manual extraction and messy offline spreadsheets" and the tax team spends days reconciling line items, tax codes and credit notes before submission.

The failure mode is the same in every account. A tax compliance lead described exporting reports to Excel, transforming schemas with "custom macros or lookup formulas" and re-uploading files, "a slower process that often has the risk of human error and audit risk". A manager in local government said the team manually extracts, manipulates and presents the data, and "the error checking is all manual or flagged by Excel, so it cannot be trusted"; a platform that integrated with the ERP "would be the dream". A senior accountant at a UK university said that without integration "we're back to spreadsheets" and scattered evidence, and that integration is "what gives us the time savings and the accurate reconciliation".

Key takeaways
1
Essential for seven in ten: 69% say direct ERP integration and source-to-VAT-field mapping are essential. With the 28% who call it important, 97% rate integration as essential or important (base: 98). A sales director at an IT services company tied it to the regime itself: in "a continuous clearance environment", compliance "is no longer a periodic report exercise. It's a live cooperation".
2
Workarounds are tolerated, not preferred: 28% accept APIs, custom builds or manual workarounds, but describe them as a phase to get through. A staff software engineer described adapters sitting between SAP and the compliance layer that work but add a hop; several linked a past workaround to the clean-up and audit exposure they now want to remove.
3
The audit trail is the point: Those who called integration essential described the benefit as a clean trail from transaction to return: no re-keying, no reformatting, and reconciliation that works because both sides share a source. The senior accountant summed it up: pull the data "straight from our ERP", map it "to the VAT returns field automatically", and "we get a clean audit trail" from each transaction to the return.
What this means for tax leaders

Make ERP-native connectivity a gate, not a line on the requirements list. Ask for prebuilt connectors for your ERP, jurisdiction-specific mapping templates and auditable data lineage from source transaction to VAT return, and see them running on your own data. Accept API-led or managed workarounds only as a phased migration path while you are still on fragmented tools. Any data, any system is a claim to test in your own ERP.

Verbatim proofListen
“If the platform pulls data straight from our ERP and maps it to the VAT return fields automatically, we cut out the manual extract process, the reformatting process, the keying process, and we get a clean audit trail from such transaction to the return, which makes the reconciliation against invoice data far easier.”
Senior accountant, higher education institutionon the audit trailG2 AI Custom Research, 2026

When integration is taken on trust. Integration is the requirement most buyers test least, and the one that slips most often. The next chapter is what happened the last time they took it on trust, and what they check now.

Importance of direct ERP integration
97%

rate integration as essential or important. Only 1% call it a secondary requirement.

Dot grid chart: 69% say direct ERP integration with VAT-field mapping is essential (base: 98) — G2 Research 2026
Essential for automation and compliance69%
Important, but APIs, custom builds or manual workarounds are acceptable28%
A secondary requirement or not a current priority1%
Other2%

Source: G2 AI Custom Research, The Future of Connected Compliance, 2026. Based on 98 respondents who addressed the question; percentages of that base, rounded.

69% say direct ERP integration is essential. Based on 98 respondents.
CategoryShare
Essential for automation and compliance69%
Important, but APIs, custom builds or manual workarounds are acceptable28%
A secondary requirement or not a current priority1%
Other2%
Karl Nolan, Chief Strategy Officer, Fintua

“Connected compliance doesn’t start with a mandate. It starts with your ERP data. When eInvoicing and VAT compliance draw on the same source of truth, each new mandate becomes an extension of what you already do, not another project to staff and fund. And tax teams are right to ask for proof. We’d rather customers test us alongside their existing process, using their own data, than simply take our word for it.”

Karl Nolan — Chief Strategy Officer, Fintua
Chapter 7

What goes wrong when implementing an eInvoicing and VAT compliance provider?

Data and integration, for 44%. The technology was rarely the surprise; the effort to get clean data into it was, and buyers now test providers on their own scenarios before they sign.

“We ask the provider to demonstrate actual scenarios that will be relevant to our company rather than just give us a generic demo. We look to see how they handle key countries, transaction types and VAT treatments end to end. And secondly, we specifically ask them to test the integration within our own ERP and the quality of the data flow.”

— Tax Manager, multinationalG2 AI Custom Research, 2026

Listen
Implementation lessons

What do buyers check now that they did not check then?

Asked what went differently than expected the last time they implemented or switched a compliance provider, 44% of the 87 who answered pointed to integration, data quality, master-data mapping or country-specific edge cases. A senior accountant said the consistent surprise is that "the technology is the easy part": legacy ERP data looked clean until it was mapped to return fields. A tax technology lead found master data that "passed our internal ERP validation just fine" but "failed government's validation engines instantly", and clean-up "tied up our IT and operational teams for longer than the vendor's optimistic timeline suggested".

The challenge isn’t simply connecting to the ERP. It’s getting the source data into a form that can reliably support compliant outcomes.

30% of the 83 who drew a lesson now validate ERP integration, data quality and real scenarios through testing before contracting, and another 30% screen providers harder on expertise, support, track record, contractual commitments and references. The lessons are specific. One tax technology lead said "the biggest mistake was trusting vendor sales demos that claimed out of the box ERP integrations": the connectors "handled standard clean domestic invoices well" but "fell apart on real world business scenarios like triangular cross-border trade, partial credit notes, and multi-currency down payments". A tax compliance lead would now "insist on a live proof of concept using our actual ERP data and custom fields before signing a contract". A product manager at a consultancy warned that a sales demo can be "configured at a high level, just to show off", and that technical people need to be in the room to ask the difficult questions. A gear manufacturer's lead found that "80% of the custom configuration time is spent on 5% of the complex transaction scenarios".

Key takeaways
1
Data and integration are the usual surprise: 44% hit integration, data quality, master-data mapping or country-specific edge cases. 11% found provider capability or sales claims fell short; 18% underestimated effort, timelines or change management (base: 87). One finance executive expected tax-code mapping to take a week; "it took 3 weeks", and "60% of the time was spent cleaning master data" such as missing tax IDs and incomplete addresses.
2
Testing on real scenarios is now standard: 30% would validate ERP integration, data quality and real scenarios through testing before choosing, and 30% would screen expertise, support, track record and references harder (base: 83). A tax manager asks providers to demonstrate "actual scenarios that will be relevant to our company rather than just give us a generic demo", and to test the integration within the company's own ERP; a compliance lead checks track record, uptime and whether there is "a 24 by 7 support team".
3
No regret usually means diligence was done: 20% report no material regret, and describe long vendor analysis, reference calls and proof on their own data before committing. A head of IT and procurement at an investment bank said the team does "a lot of analysis" of vendors and only chooses "once we're comfortable that it is the right platform", because "there's a big cost for that". A global purchasing lead was satisfied with the provider and the implementation; the only regret was that the provider could not extend the same service beyond Europe.
What this means for tax leaders

Make the provider prove implementation before you sign. Ask for scenario-based evaluations on your own countries, transaction types and ERP data instead of a generic demo, and get data transformation, mapping and parallel running written into the contract as a defined onboarding workstream with named support and uptime commitments. The peers with no regrets are the ones who tested first.

Verbatim proofListen
“Whenever we select a provider, we make sure that they have a proper track record and what is their uptime? Is there any downtime also? And if there are any problems or any hiccups during the implementation, how do they handle it? Do they have a 24 by 7 support team to handle that? So these are the things that we check.”
Compliance Lead, technology companyon provider screeningG2 AI Custom Research, 2026

How far automation is allowed to go. Buyers test before they trust a platform with their data. The same instinct governs how much of the work they let it do alone, which is the next chapter.

Lessons buyers now apply
44%

hit integration, data-quality, master-data or country edge-case problems in their last implementation (base: 87).

Column chart: two implementation lessons tie at 30%, testing on your own data before contracting and screening providers harder (base: 83) — G2 Research 202630%30%20%13%7%
Validate ERP integration, data quality and real scenarios through testing30%
Screen expertise, support, track record, contracts and references more rigorously30%
No material provider-selection or implementation regret20%
Improve planning, timelines, documentation, change management and training13%
Other7%

Source: G2 AI Custom Research, The Future of Connected Compliance, 2026. Based on 83 respondents who addressed the question; percentages of that base, rounded.

Two lessons tie at 30%: test it, and screen harder. Based on 83 respondents.
CategoryShare
Validate ERP integration, data quality and real scenarios through testing30%
Screen expertise, support, track record, contracts and references more rigorously30%
No material provider-selection or implementation regret20%
Improve planning, timelines, documentation, change management and training13%
Other7%
Chapter 8

Which VAT compliance tasks can be automated, and where is human review still required?

Routine work goes first: invoice generation, transmission, validation and matching. People keep the final filing and the exceptions, because someone has to be able to explain what went out.

“I'd be comfortable letting the system compare the VAT transaction data to the GL, calculate the expected VAT position and identify discrepancies without someone manually checking every transaction.”

— Tax Manager, multinationalG2 AI Custom Research, 2026

Listen
Automation and sign-off

Where do people stay, and why?

Organisations are clear about where software can run on its own. 32% of the 91 who answered are comfortable automating invoice generation, transmission and standard tax calculations without a person checking each one, and 24% extend that to rule-based extraction, validation, matching and reconciliation. A compliance lead at a gear manufacturer described the split inside one company: outbound eInvoice transmission and VAT determination are "100% automated", inbound reconciliation is "70 to 80% automated", and returns are "draft automated and submission is manual".

Of the 92 asked where they still want a person to review, approve or explain, 32% keep the final filing, payment or external release with a person and another 32% reserve human review for exceptions, unusual transactions, high-value items and regulatory judgement. The reason is accountability rather than distrust. A senior accountant said that even if the platform calculates everything correctly a person "should review and approve before it's filed", because "accountability sits with us and not the software". A finance team member added that "in the audits they still don't approve if we have this 100% being done by AI". An e-commerce finance project manager wants the tool to "detect and flag anomalies" but "I want a person to retain that decision" when the situation is ambiguous or the tax risk is significant. A key account manager in food production described the destination most respondents share: human checks at the start, and once they are sure, "everything from A to Z, I want to be automatic".

Key takeaways
1
Routine work goes first: 32% automate invoice generation, transmission and standard calculations and 24% rule-based extraction, validation, matching and reconciliation; 16% describe broad straight-through processing (base: 91). The tasks named are the same across companies: VAT number validation, schema checks, format conversion, transmission to the tax portal, and a reconciliation that compares the VAT data to the general ledger and "identify discrepancies" without someone checking every transaction.
2
Final release stays human: 32% want a person to approve final filings, payments or external submissions even where the software could do it, and 32% reserve review for exceptions, high-value items and regulatory judgement (base: 92). A finance manager said he is "very much sure" the tax logic is automated properly, but when it comes to "making a payment on the portals, I would expect that a human will do that thing".
3
Oversight is moving from checking to monitoring: 11% oversee mainly through sampling and audit checks, 10% keep preventive review of inputs and master data, and 1% limit people to incidents and audits. A product manager at a consultancy described the double check as "quite quick", a sanity check that the right code was selected, and the direction of travel is from checking every line to governing the process.
What this means for tax leaders

Buy controlled automation, not autonomous filing. Let the platform generate, validate, transmit and reconcile end to end, and insist that the human points are visible and configurable: approval of final submissions, exception queues, rule-change review and an audit trail that explains every decision. The goal is to move your team from checking every transaction to governing the process.

Verbatim proof
“For outbound e-invoice transmission it is 100% automated. For VAT determination or sales tax we have 100% automation. For reconciliation or inbound invoices, there is some exception. I can say 70 to 80% automated, and monthly, quarterly or tax return filing, it is draft automated and submission is manual.”
Research participant, global gear manufactureron what runs without a personG2 AI Custom Research, 2026

What moves the human line. Buyers are specific about the evidence that would let them step back from the final check. The last chapter is that evidence, in the order they rank it.

What software is allowed to handle alone
32%

automate invoice generation, transmission and standard calculations. The same share keep final sign-off with a person (base: 92).

Bar chart: routine automation comes first, and 16% describe broad straight-through processing (base: 91) — G2 Research 202632%24%19%16%9%
Invoice generation, transmission and standard tax calculations32%
Rule-based extraction, validation, matching and reconciliation24%
Only limited autonomy, or routine human pre-checks retained19%
Broad straight-through automation across VAT and eInvoicing16%
Other9%

Source: G2 AI Custom Research, The Future of Connected Compliance, 2026. Based on 91 respondents who addressed the question; percentages of that base, rounded.

Routine automation first, straight-through for 16%. Based on 91 respondents.
CategoryShare
Invoice generation, transmission and standard tax calculations32%
Rule-based extraction, validation, matching and reconciliation24%
Only limited autonomy, or routine human pre-checks retained19%
Broad straight-through automation across VAT and eInvoicing16%
Other9%
Chapter 9

What proof should buyers ask for before trusting tax automation?

A parallel run on their own data, over several filing cycles, with an audit trail of every decision. Track record and transparent rules support that proof; they do not replace it.

“We would need to run the automated logic side by side with our manual review process over several consecutive filing cycles with a near zero error rate. Once our internal tax team sees consistent precision and defensibility without surprises, we can comfortably shift our people from manual double checking to spot checking and governance.”

— Tax technology and invoicing compliance, multinationalG2 AI Custom Research, 2026

Listen
Proof for trust

What else builds confidence?

Asked what would let them rely on a provider's automated tax logic for something a person currently double-checks, 36% of the 87 who answered named demonstrated accuracy through pilots, parallel runs and testing on their own transaction data. The bar is specific. A tax technology lead would "run the automated logic side by side with our manual review process over several consecutive filing cycles with a near zero error rate"; an operations lead wants "clear practical proof over time that the system works reliably in real scenarios", and "the most convincing would be a parallel run results, side by side comparison".

Track record, customer references and local regulatory credibility come next (22%), followed by transparent, explainable tax logic with auditable transaction trails (20%). The two travel together in most accounts. The tax technology lead said the engine "cannot be a black box": it needs audit logging that "links every tax determination back to the specific statutory rule, article, and source ERP field that triggered it". A senior accountant said "trust would have to be earned over time and with evidence", starting with rules "traceable back to the legislation" and then a proper parallel run. An IT lead in chemical logistics wants case studies of similar companies running the technology "over more than one audit cycle". Contractual liability or regulatory acceptance persuades only 7%, and 8% say a human double-check stays whatever the evidence.

Key takeaways
1
Proof on their own data, over several cycles: 36% want pilots, parallel runs and testing on company data, compared against human checks across consecutive filing cycles (base: 87). An e-commerce finance project manager would start with "a pilot phase where we could compare the tool's results with human checks, then gradually expand automation if the results are satisfactory", with "complete traceability of transactions" in case of an audit.
2
Credibility and transparency support the proof: 22% cite provider track record, references and local credibility, and 20% transparent, explainable tax rules with an inspectable audit trail. Neither replaces a pilot. An operational management lead said references "would help establish credibility, but I wouldn't rely on those alone"; the convincing proof is "demonstrated accuracy using our own transaction data", not test data.
3
Guarantees persuade few on their own: 7% would rely on contractual liability or regulatory acceptance, and 8% say a human double-check stays whatever the evidence. A finance manager at an IT services firm is one of the 8%: the software may be "designed in a way that will handle everything", but "one human check is needed" before money moves.
What this means for tax leaders

Make the parallel run your gate. Ask for a structured pilot on your own transactions across two or three filing cycles, with side-by-side results against your manual review, error rates and a full audit trail of every check. Back it with references in your key jurisdictions and the right to inspect the rule logic. Your peers have described the evidence that moves them; ask for it in that order.

Verbatim proof
“I'd need a clearly successful pilot phase comparing the tool's results with human checks, with a low error rate and validation that the VAT data is consistent with the country in question. I'd also need a complete audit trail showing the invoices, the checks carried out, the decisions made, and the tests that demonstrate these cases are handled correctly.”
Finance project manager, e-commerce multinationalon pilots and audit trailsG2 AI Custom Research, 2026

What this adds up to. Proof on your own data, over several cycles, is what gets a platform from shortlist to system of record. The takeaways turn that into five questions to put to any provider.

Evidence that earns trust in automation
36%

name pilots, parallel runs and testing on company data, ahead of track record (22%) and explainable rules (20%).

Lollipop chart: 36% want proof from a pilot or parallel run on their own transaction data before trusting automation (base: 87) — G2 Research 202636%22%20%8%7%7%
Demonstrated accuracy through pilots, parallel runs and testing on company data36%
Provider track record, customer references and local regulatory credibility22%
Transparent, explainable tax logic with auditable transaction trails20%
Human double-checking remains non-negotiable8%
Contractual liability, guarantees or regulatory acceptance7%
Other7%

Source: G2 AI Custom Research, The Future of Connected Compliance, 2026. Based on 87 respondents who addressed the question; percentages of that base, rounded.

36% want the proof in their own data. Based on 87 respondents.
CategoryShare
Demonstrated accuracy through pilots, parallel runs and testing on company data36%
Provider track record, customer references and local regulatory credibility22%
Transparent, explainable tax logic with auditable transaction trails20%
Human double-checking remains non-negotiable8%
Contractual liability, guarantees or regulatory acceptance7%
Other7%
Segment analysis

The more countries a company files VAT in, the more proof it asks for before trusting automation

85 respondents told us how many countries their VAT and eInvoicing obligations cover. Grouped into three bands (1 to 4 countries, 5 to 25, and 26 or more), the main themes show one market at three stages of the same journey: 60% of those filing in 26 or more countries want a parallel run before they trust automation, against 26% of those filing in 1 to 4.

Footprint segments: nine measures by countries managed. Percentages of each band, with respondent counts and bases.
Measure1 to 4 countries (n=23)5 to 25 countries (n=35)26+ countries (n=27)
Builds the business case on cost and risk together28% (5 of 18)48% (15 of 31)67% (16 of 24)
Wants a parallel run on its own data before trusting automation26% (5 of 19)29% (8 of 28)60% (15 of 25)
Still runs fully separate country-by-country tools43% (10 of 23)14% (5 of 35)19% (5 of 26)
Keeps human review for exceptions and judgement only20% (4 of 20)26% (8 of 31)46% (12 of 26)
Is consolidating onto a connected platform, or already there52% (12 of 23)74% (26 of 35)77% (20 of 26)
Puts breadth of country coverage first5% (1 of 20)12% (4 of 34)28% (7 of 25)
Puts local regulatory expertise first70% (14 of 20)62% (21 of 34)56% (14 of 25)
Calls direct ERP integration essential71% (15 of 21)62% (21 of 34)65% (17 of 26)
Hit integration or data problems last time45% (9 of 20)41% (12 of 29)42% (10 of 24)

Source: G2 AI Custom Research, The Future of Connected Compliance, 2026. Based on the 85 respondents who said how many countries their remit covers; bases vary by question because percentages reflect the respondents who addressed each one. The 1 to 4 and 26+ bands are under 30 respondents and are directional. Values are percentages of each band.

The nine chapters describe one market, but the respondents in it are not at the same point. Groups with obligations in one to four countries are the most likely to still run fully separate tools (43%), and they shop for depth: 70% put local regulatory expertise first and only 5% lead with coverage. Their proof is a track record and references, and their business case is payback. A finance director at a life sciences company was explicit that risk "has to be on hard numbers at the end of the day".

Groups in 26 or more countries have mostly made the move (77% are consolidating or connected) and their asks change shape. Two thirds argue the case on cost and risk together (67%), nearly half limit human review to exceptions and judgement (46%), and 60% will only trust automation after a parallel run on their own transactions: "an error free 3 to 6 months parallel run against our historic cross border edge cases" for one corporate finance lead, "a track record and then our own testing, heavy testing" for a PMO lead in technology consulting. Coverage starts to matter again at this scale (28%), because the long tail of countries is now theirs to run.

What does not move is the foundation. Expertise first, ERP integration essential and the share who hit integration or data problems last time sit within a few points across all three bands. The proof a provider has to show is the same everywhere; how much of it, and in what order, depends on footprint.

What this means

Know where your footprint puts you. If you file in a handful of countries, weight jurisdiction depth, references and a payback case; the parallel run is reassurance, not the gate. If you file in 26 or more, the parallel run is the gate: structure the pilot on your own cross-border edge cases, ask to see exception handling rather than sign-off screens, and build the case on total cost of ownership against compliance risk. The mid band is where most of the market sits, and it is still choosing which of those two buyers to become.

Verbatim proof
“The main thing would be building the business case around measurable cost, risk reduction and scalability rather than just a technology investment. I suppose quantify the current cost of compliance, the hours, the external advisors, different licenses that we require.”
Tax Manager, multinational26 to 99 countries, on the business caseG2 AI Custom Research, 2026
Verbatim proof
“We would look for opportunities for cost savings, reduction in manual work by employees. It would need to pay for itself in some way before we would consider doing it. Reduction of risk could be used, but we would need to quantify what that actually means in terms of dollars.”
Finance Director, life sciences company1 to 4 countries, on the business caseG2 AI Custom Research, 2026
Strategic patterns

Cross-cutting themes

Pattern 1

Consolidation is a transition 72% of buyers are already in

72% are consolidating onto a connected platform or already run one, yet 71% still describe a hybrid estate of central systems plus local tools, portals and advisers. The market is mid-migration, moving country by country as mandates arrive, not choosing between two end states.

Implication

Judge a platform on how it absorbs your local tools one jurisdiction at a time, with parallel running built in. Ask for the roadmap from hybrid to connected; that roadmap is the product you are buying.

Pattern 2

Fragmentation gets funded when its cost is made visible

77% feel the cost of separate country tools and 77% say reconciliation between VAT return and eInvoice data is a growing priority, but only a regulatory deadline (30%) or an already-committed programme (20%) reliably moves the decision. The case that passes pairs total cost of ownership with compliance risk (49%).

Implication

Put a number on your reconciliation effort, exception volumes and audit exposure by jurisdiction, ask to see reconciliation inside the filing workflow, and write both columns of the business case before you go to the CFO.

Pattern 3

Proof decides which platform wins

Buyers rank local regulatory depth (64%) and direct ERP integration (69%) above breadth of coverage, because that is where implementations slip (44% hit data and integration problems). They want automation for routine work but keep sign-off on filings (32%), and 36% will only step back after a parallel run on their own data.

Implication

Test jurisdiction-specific expertise, a live integration in your own ERP and a structured pilot across consecutive filing cycles before you weigh the country list. Coverage without demonstrated depth is the claim your peers discount.

Quick answers

Frequently asked questions

Question 1

What is the future of VAT compliance for multinational enterprises?

Continuous, transaction-level and connected. 72% of the multinationals interviewed are consolidating VAT and eInvoicing onto one platform or already run one, as Continuous Transaction Control mandates and the EU's ViDA package move reporting from periodic returns to near real-time. Reconciliation between VAT return data and eInvoice data becomes a live control rather than a month-end task: 77% say it is a growing priority.

Question 2

How far along are multinationals in moving to connected compliance?

Further than the hybrid picture suggests. 46% are actively consolidating their VAT and eInvoicing tools onto a connected platform and 27% already run one across most or all markets, so 72% are on the path. 22% still run fully separate country-by-country tools. Day to day, 71% describe a hybrid estate with a central system plus local tools, advisers or government portals, which is what consolidation is working through.

Question 3

How will ViDA affect indirect tax operating models?

It turns reconciliation into a control. ViDA makes digital reporting of intra-EU B2B transactions mandatory from July 2030, so tax authorities will hold transaction data before the periodic return is filed. Respondents already feel that shift: 57% say regulatory change has recently raised the priority of transaction-level reporting, 77% say VAT-return-to-eInvoice reconciliation is a growing priority, and 69% call direct ERP integration with VAT-field mapping essential to keep the two in step.

Question 4

How should tax teams prepare for real-time VAT reporting?

Fix the data path before the deadline. The teams in this study start with ERP integration and source-to-VAT-field mapping (essential for 69%), automate reconciliation between VAT return and eInvoice data (a growing priority for 77%), and test any provider on their own transactions and key countries before contracting (30%). Readiness assessments ahead of mandates matter because a deadline is the single largest consolidation trigger (30%).

Question 5

What triggers organisations to consolidate their eInvoicing and VAT providers?

Regulatory deadlines, compliance exposure or an audit failure, named by 30% as the event that would move consolidation to the top of the list. 20% say it is already a strategic priority, 15% would move on a quantified ROI case, and 13% say their current tools are adequate so only a major failure would prompt change.

Question 6

How do enterprise organisations consolidate eInvoicing providers?

Country by country, with parallel running. Respondents describe one platform for the biggest markets first, legacy tools and local advisers migrated as eInvoicing mandates arrive, and a central data, workflow and control layer that absorbs the local pieces one jurisdiction at a time. A single global cut-over was the exception; two-year horizons were common. 46% are in that process now.

Question 7

What is the operational cost of fragmented, country-by-country compliance?

77% say it creates material manual effort, headcount, tool or adviser cost, errors and audit risk; only 7% report no material cost. Respondents described weeks of manual reconciliation to prove compliance to a tax authority, missed deadlines when a connector failed, and internal audit findings when the same reconciliation ran differently in two geographies.

Question 8

Should a multinational use one global eInvoicing provider or several local ones?

The research tested the trade-off buyers actually make, which is expertise against coverage: 64% prioritise depth of regulatory expertise in their key jurisdictions, 16% want both from one provider, and 15% prioritise broad coverage supplemented by specialists. A single global provider wins where it can prove local depth in the buyer's biggest markets first.

Question 9

Is an ERP's built-in capability enough for multi-country compliance?

The research did not test ERP-native tools against dedicated platforms directly. It did find that 69% treat direct ERP integration with source-to-VAT-field mapping as essential in any compliance platform, 28% accept APIs or workarounds, and only 1% call integration secondary. Among those who named their setup, 29% run an SAP-led stack that is often supplemented by other providers.

Question 10

What should organisations look for in an eInvoicing and VAT compliance platform?

In the order buyers rank them: regulatory expertise in the countries that matter (hardest to compromise on for 37%, ahead of breadth for 64%), direct ERP integration with VAT-field mapping (essential for 69%), proof on real scenarios and the buyer's own data before contracting (30%), and track record, support and references (30%). Automation should run routine work with visible human sign-off on filings and exceptions.

Question 11

Which eInvoicing and VAT compliance platforms do multinationals use today?

No single platform dominates. Of the 84 respondents who named their setup, 29% run an SAP-led stack, usually supplemented by other providers, 21% a named non-SAP commercial platform or adviser, 21% a mix of local providers, government portals and regional tools, 7% an in-house or manual solution, and 20% did not disclose. The research does not rank vendors; the criteria buyers use are above. G2 lists and reviews providers in its Sales Tax and VAT Compliance Software category.

Question 12

How is AI and automation being used in eInvoicing and VAT compliance?

Today's automation is rule-based and applied to routine work: 32% automate invoice generation, transmission and standard tax calculations, 24% extend that to extraction, validation, matching and reconciliation, and 16% describe broad straight-through processing. Where respondents mentioned AI, it was as the next step for reconciliation and exception detection, under the same rule: a person keeps the final filing and the exceptions.

Question 13

Which compliance activities can be automated, and where is human review still required?

Invoice generation, transmission and standard tax calculations (32%) and rule-based extraction, validation, matching and reconciliation (24%) are the activities buyers are comfortable letting software run alone. People keep approval of final filings, payments and external releases (32%) and review of exceptions, high-value items and regulatory judgement (32%).

Question 14

What proof should buyers ask for before trusting tax automation?

A pilot or parallel run on their own transaction data across several filing cycles, compared against manual review, with a low error rate and a complete audit trail of the checks and decisions (36%). Provider track record and references (22%) and transparent, inspectable tax logic (20%) support that proof but rarely replace it.

Question 15

Will eInvoicing replace periodic VAT returns?

The study did not measure legal changes to periodic returns or make jurisdiction-specific predictions. What it shows is the operating reality behind the question: as eInvoicing and VAT reporting converge, tax authorities hold transaction data before the return is filed, so 77% now treat reconciliation between the two as a growing priority and organisations are changing their platforms, data and controls accordingly.

Before you choose

What to ask a provider before you consolidate

1
Critical

How will you absorb our estate one jurisdiction at a time?

Most of your peers are mid-consolidation and running a hybrid estate. Look for a platform that works as the central data, workflow and control layer, absorbs local tools, portals and advisers one jurisdiction at a time, and shows you a roadmap from hybrid to connected.

2
Critical

Show us reconciliation running inside the filing workflow.

77% feel the cost of separate country tools and 77% say VAT-return-to-eInvoice reconciliation is a growing priority. Size that cost jurisdiction by jurisdiction before you start, then ask to see reconciliation inside the filing process rather than as a separate report.

3
High

Prove depth in our key markets and fit in our ERP before coverage.

64% put regulatory expertise in their key markets ahead of breadth, and 69% call direct ERP integration with VAT-field mapping essential. Lead the evaluation with jurisdiction-specific scenarios and a live integration in your own ERP, then weigh the country list.

4
High

Run a parallel pilot on our data before we drop manual checks.

36% want pilots and parallel runs on their own transactions before they step back from manual checks, and a third keep final sign-off on filings. Ask for a structured pilot across consecutive filing cycles with human approval points visible, and buy governed automation rather than autonomous filing.

5
Medium

Help us write both columns of the business case.

49% get approval on total cost of ownership and implementation effort set against compliance risk; savings alone rarely carry it. Ask for a TCO model that retires point solutions and adviser spend alongside a costed view of avoided penalties and audit findings, written for the CFO and CIO.

Final thoughts

Conclusion

For most multinationals in this study, the question is no longer whether VAT and eInvoicing should become more connected, but how to get there. 72% are consolidating onto a connected platform or already run one, and the rest mostly describe a hybrid estate they expect to simplify. Continuous, transaction-level reporting is forcing the question, and fragmentation is answering it: 77% feel the cost of separate country tools in manual reconciliation, missed deadlines and audit findings.

Challenges

What stands between a hybrid estate and a connected one is proof. Insist on depth of regulatory expertise in the markets that matter before a long country list, direct ERP integration with VAT-field mapping before any promise of automation, and a parallel run on your own data before you take your hands off the controls. Implementations slip on data and integration, so the buyers with no regrets are the ones who tested first.

Looking ahead

The operating model that emerges is connected and controlled. Software generates, validates, transmits and reconciles; people approve what leaves the building and handle the exceptions. The business case that funds it pairs total cost of ownership with compliance risk. Choose the provider that shows local depth, ERP fit and a clean audit trail in your own environment; that is the one your peers are consolidating onto.

72% are moving to connected compliance. But trust has to be earned. Connect the data, prove it against real transactions and keep accountability visible.

How we did it

Research methodology

1

How was this research conducted?

This research draws on 102 in-depth interviews with tax, finance, IT and operations leaders responsible for VAT compliance and eInvoicing at multinational organisations, conducted in October 2026 as conversational, AI-led, open-ended voice interviews. Interviews ran up to 55 minutes, with an average of 23 minutes, and totalled 38.8 hours. The 18-question flow covered the current compliance operating model, the drivers of continuous reporting, reconciliation and the cost of fragmentation, consolidation triggers, provider selection and ERP integration, automation and human oversight, implementation experience, and the internal business case. Respondents answered in their own words rather than from preset options.

2

Who we interviewed

Respondents were screened to work at organisations with 500 or more employees and to hold indirect tax or eInvoicing obligations in at least one region outside the United States (the UK, EU/EEA, Middle East, Asia-Pacific or Latin America); organisations with obligations in the United States alone were excluded. Just over half of those who described their organisation reported annual revenue above €500 million. Roles spanned heads of tax, VAT and indirect tax; tax technology and compliance leads; finance directors, controllers and CFOs; IT and ERP leaders; and operations, procurement and shared-services managers. Of the 85 who said how many countries their obligations cover, 23 file in one to four countries, 35 in five to 25 and 27 in 26 or more. Company names are withheld.

3

How we analysed it

Each interview response was coded to a small set of labels per question by AI semantic analysis of the transcript, followed by validation and cross-verification, and every transcript was independently reviewed by G2's AI Custom Research team. Percentages are calculated on the respondents who addressed each question, and the base is stated with every figure. Every quotation is verbatim from the interview transcript, with light cleanup of transcription stutters and misheard product names only, and is attributed by role only. Fintua commissioned this research. Fintua provides a connected compliance platform for VAT reporting and eInvoicing. The G2 AI Custom Research team conducted it, with Anubha Garg as research analyst; respondents were recruited through independent research panels rather than from the Fintua customer base, Fintua took no part in the interviews, and all analysis, figures and conclusions belong to G2.

4

Limits

Not every leader answered every question, so each percentage is calculated only on the people who did, and that number is stated with every figure; it ranges from 83 to 101. Findings are cut by one self-reported attribute, the number of countries a respondent's obligations cover; where a band rests on fewer than 30 people, as the one to four and 26 or more bands do, the report says so and treats the figure as an indication rather than a precise measurement. Company size, industry and function were not linked to transcripts, so findings are not cut by those. All respondents hold obligations outside the United States and most are hands-on with multi-country compliance, so the findings describe these buyers rather than the whole market.

G2 Research, November 2026 · Part of the G2 Research Hub, G2's library of original research based on AI-conducted interviews with business professionals.