72% Are Moving to Connected Compliance. Only Proof Gets Them There

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.

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.

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".

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.

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.

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".

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".

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".

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".

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.