You ask about features. You ask about integrations. You ask about pricing and support. You get a demo with a very smooth presenter who uses the words “agentic,” “real-time,” and “compliance-native” in every other sentence.

You do not ask, “How does your system decide which model handles my request?”

And the vendor — relieved you didn’t ask — moves on.

This is the infrastructure gap in TaxTech AI. And it is costing enterprises a lot more than they think.

What Actually Happens When You Hit Send

Let me walk you through what happens the moment you submit a prompt to an AI-powered compliance tool. Somewhere, a server rack with an AI chip receives your request. Your text gets converted into tokens — numerical representations of words and concepts. A model gets allocated GPU compute to process those tokens. The response streams back. Your account gets charged.

Simple, right?

Here is the part nobody talks about: in most TaxTech deployments today, the same model handles every single request. Whether you’re asking it to validate a VAT registration number (200 tokens, done in milliseconds) or reconcile 400,000 transaction lines against twelve EU continuous transaction control regimes (tens of thousands of tokens, multiple tool calls, minutes of compute) — it all goes to the same place.

No routing. No tier selection. No “this task is simple, use the cheaper model.” No “this task is complex, escalate.”

One model to rule them all. You pay for all of it.

Now let me tell you what this looks like at Uber scale, because I tested it.

I Asked for One Line. I Got a Redesign.

Earlier this year I ran a test with Anthropic’s Fable 5 — their highest-capability model at the time, since restricted for enterprise use outside the United States.

The task was simple. Embarrassingly simple. Recalculate a single line in a compliance spreadsheet based on updated input parameters.

What Fable 5 did instead: redesigned the entire spreadsheet architecture.

It reformatted the structure. Added conditional logic across twelve new columns. Restructured the formula dependencies. Generated explanatory commentary for every change. Produced a masterpiece of spreadsheet engineering that absolutely nobody asked for.

The model wasn’t broken. It was doing exactly what frontier models do — applying maximum capability to every request regardless of whether that capability is needed. Maximum intelligence. Maximum tokens. Maximum compute.

At Uber’s transaction volumes — millions of tax determination events per day, across dozens of jurisdictions — a task mismatch like this isn’t a funny anecdote. It’s a Token Effectiveness Ratio disaster that compounds quietly until it detonates your quarterly compute budget.

The fix isn’t a smarter model. The fix is a routing layer that catches the mismatch before it happens.

Do TaxTech vendors not have one?

What AWS Figured Out Fifteen Years Ago

AWS didn’t launch EC2 in 2006 and say “good luck figuring out the routing.”

They spent the next decade building the layer that makes the hard part invisible:

1️⃣ Load balancing. Incoming requests get distributed across multiple compute instances. The month-end close traffic spike doesn’t bring the system down. Someone already solved that.

2️⃣ Auto-scaling. Capacity expands during a VAT filing deadline and contracts at 3am on a Tuesday. You pay for what you use. Someone already solved that, too.

3️⃣ Instance tier routing. A background batch job doesn’t get the same resources as a real-time checkout event. AWS routes intelligently. The user doesn’t choose the rack, and he shouldn’t have to.

4️⃣ Availability zone failover. If one data center degrades, traffic reroutes automatically. Your 99.99% SLA is enforced at the infrastructure layer. Not the application layer. The infrastructure layer.

5️⃣ Spot vs. on-demand pricing. Non-urgent workloads run on spare capacity at a fraction of the cost. Latency-sensitive operations get premium compute. The decision is automatic.

6️⃣ Request-level observability. You can audit exactly which requests ran, on what instance type, for how long, and at what cost. Every dollar is traceable.

7️⃣ Agentic governance. At the AWS New York Summit in 2026, AWS introduced release management capabilities for its DevOps agent specifically because parallel AI coding creates a compounding risk of failure. As David Yanacek, AWS Senior Principal Engineer for Agentic AI, put it: “Coding agents are getting a ton done in parallel. The more that you’re doing in parallel, the higher the probability that the resulting train will not be able to leave the station because one of these things has a bug in it.” AWS also introduced Continuum, a cybersecurity tool designed to detect vulnerabilities in AI models before they reach production. The result: a task that took eight minutes in January takes three minutes in May — not because the agents got smarter, but because the governance layer got better.

Now. Imagine asking an enterprise buyer to choose which physical rack handles their AWS request. They would look at you like you’d lost your mind. That’s not a user decision. That’s an infrastructure decision. One that AWS made for you, automatically, fifteen years ago.

In 2026, asking a CTO to “select the LLM model” for their TaxTech AI prompt — without any of the above abstraction — is the exact same thing.

They will be lost. They are right to be lost.

The TaxTech AI Gap

In 2026, none of the major TaxTech AI deployments publish anything equivalent to what AWS documents on day one.

Go ahead and try.

Ask Avalara how their ALFA framework decides whether your request goes to a large or small language model. Ask Thomson Reuters what ONESOURCE+’s failover logic looks like during a provider outage. Ask Sovos what model tier handles a simple tax code lookup versus a complex cross-border VAT determination. Ask Anrok what happens to your in-flight compliance request if their primary LLM provider has a brownout at the month-end close.

You won’t get an architecture document.

You’ll get a product brochure.

And to be fair — the product surface area is genuinely impressive. As I mapped in The 2026 AI TaxTech Map, Avalara’s ALFA framework combines large and small language models across 1,400+ application integrations. Thomson Reuters launched ONESOURCE+ as an “Intelligent Compliance Network.” Sovos shipped Sovi AI. Anrok built Atlas with Big 4-verified outputs. The teams building these products are getting there.

But “combines large and small language models” is not a routing architecture. It’s a marketing line.

What governs the routing decision? What’s the threshold? What happens on failover? What’s the uptime SLA for the AI layer specifically — not the underlying AWS or Azure layer the vendor is running on, but the AI orchestration layer?

Nobody discloses this. Probably nobody asks for it either.

That’s the gap.

A Brief, Painful Look at Vendor Reality

Let’s be specific, because specificity is the point.

Avalara deserves credit for the ALFA framework — and their MCP server integration signals genuine infrastructure thinking. But there is no published routing logic. No compute tier disclosure. No AI-specific SLA. What exactly triggers the “use the small model” decision? Unknown.

Thomson Reuters ONESOURCE+ — “Intelligent Compliance Network.” What does the intelligence routing look like? What’s the failover path during a provider degradation? Not disclosed.

Sovos Sovi AI and Anrok Atlas both lead with the output story. Anrok’s combination of AI and human tax experts is smart, accuracy risk management. It is a quality control layer, not an infrastructure layer. Those are different problems.

Xero and Intuit build AI through partnerships — including Xero’s deep integration with Anthropic, which I covered here. Partnership architecture creates a second question: when Xero routes your request through Anthropic’s API, which model tier handles it? Which region? What’s the fallback? Those answers live inside the partnership agreement. They are not visible to you, the user.

Pattern: strong on what the AI does. Silent on how it’s governed.

Caps Are Not Architecture. They’re Surrender.

The enterprise response to AI budget overruns in 2026 has been impressively uniform.

Uber burned its entire AI budget by April — Uber’s CTO confirmed it publicly. Amazon capped it. Microsoft capped it. Meta capped it. The industry response to “AI is costing us a fortune” was: put a ceiling on it.

Respectable as a short-term move. Completely missing the point.

A cap is a circuit breaker. It stops the bleeding when you hit the limit. But it does nothing about what happened before the limit. If your AI compliance stack is routing 40,000-token tasks to frontier models when 2,000-token tasks to a smaller model would have produced the exact same compliance outcome, you will hit your cap faster. And you will hit it on waste, not on value.

The agentic dimension makes this worse, not better. Agentic TaxTech workflows — multiple AI agents running reconciliation in parallel, cross-referencing jurisdictions, and calling external APIs simultaneously — amplify the risk of compounding failures. AWS’s own David Yanacek flagged this exact problem at the 2026 NY Summit: the more you run in parallel, the higher the probability that one agent’s bug stops the entire output from clearing. In TaxTech terms: one misfiring reconciliation agent doesn’t just produce a bad output. It can hold up the entire compliance filing.

Are TaxTech vendors addressing this?

As I detailed in The Future Cost of TaxTech, the unit economics of AI compliance are brutal at scale. A usage cap doesn’t fix unit economics. It just tells you when you’ve run out.

The AWS analogy again: imagine AWS gave you a monthly compute budget and no load balancer. You’d burn the budget on poorly routed requests, hit the ceiling, and call it a month. Nobody would accept that from a cloud provider.

A cap is not a substitute for architecture. It is an admission that architecture is missing.

(That sentence. Read it again. That’s the one to send your ELTs.)

Five Questions. Before You Sign Anything.

If you are evaluating or renewing a TaxTech AI contract in the next twelve months, your vendor should be able to answer all five of these. No exceptions. No “we’ll get back to you on that.”

If they stall, escalate to the product team. If the product team stalls, you have your answer.

1️⃣ How does your system determine which model tier handles a given request?

A mature answer: routing logic based on task complexity, instruction length, and domain. A weak answer: one model handles everything, or worse — “the user selects the model.” (Yes, this happens. No, it’s not acceptable.)

2️⃣ What is your AI-specific uptime SLA, and what is your failover path when a primary LLM provider degrades?

A mature answer: named failover path, detection latency, recovery time objective. A weak answer: “we rely on our provider’s SLA.” That is not your SLA. That is their SLA, applied to them, not to you.

3️⃣ Do you implement semantic caching for repeated compliance queries?

A mature answer: yes, with a description of how near-identical queries are matched. A weak answer: no mention of caching. (Semantic caching alone can cut compute costs by 40–60% for structured compliance workloads. If your vendor isn’t doing it, you are paying for redundant compute every single day.)

4️⃣ How do you prevent runaway token consumption in agentic workflows?

A mature answer: circuit breakers, per-task token budgets, human escalation triggers. A weak answer: usage caps at the contract level. See the previous section on why that’s not the same thing.

5️⃣ Can you provide task-level compute telemetry — model tier used, token consumption, latency, and cost — per request?

A mature answer: yes, available in account reporting. A weak answer: aggregate spend data only. (If you can’t see task-level telemetry, you cannot manage your Token Effectiveness Ratio. You’re flying blind with a very expensive instrument panel.)

Your cloud provider answered all five of these before you signed. Your TaxTech AI vendor should too.

If they can’t — you’re not buying managed AI infrastructure. You’re buying model access with a compliance-themed UI on top. The infrastructure risk sits on your P&L. Not theirs.

The companies that asked the right cloud infrastructure questions in 2012 built the most resilient platforms of the 2010s.

The ones signing enterprise AI contracts in 2026 without asking the infrastructure questions are building the most expensive compliance technical debt of the 2030s. And they’ll call it “AI transformation” right up until the end.

Don’t be that company. Ask the questions.

What answers have you gotten from your TaxTech AI vendors? I’m genuinely curious. Drop them in the comments.

Frequently Asked Questions

What is an AI orchestration layer, and why does it matter for enterprise tax compliance? An AI orchestration layer sits between your application and LLM providers, routing each request to the appropriate model tier based on task complexity, cost, and latency. Without it, every request — from a simple tax code lookup to a complex cross-border determination — hits the same model at the same cost. At enterprise transaction volumes, that’s not a technical inconvenience. It’s a structural margin problem.

How should I evaluate AI infrastructure when selecting a TaxTech vendor? Ask five questions before signing: How is model tier selection governed? What is the AI-specific uptime SLA and failover path? Is semantic caching implemented? How are runaway agentic workflows stopped before they exhaust compute budgets? Is task-level token telemetry available in account reporting? A vendor who cannot answer all five is selling model access, not managed AI infrastructure.

What is the difference between an AI gateway and a usage cap on LLM consumption? A usage cap stops spending when a threshold is hit. An AI gateway optimises spending before it happens — routing simple tasks to cheaper models, caching repeated queries, preventing runaway loops. A cap is a circuit breaker. A gateway is the circuit design. You need both, in that order.

Why does model selection matter for automated tax calculations? Different compliance tasks have wildly different complexity profiles. Recalculating a single tax line requires a fraction of the compute needed to reconcile multi-jurisdictional indirect tax exposure across 90 countries. Without intelligent routing, both tasks hit the same frontier model. At scale, that’s millions of dollars in unnecessary compute spend per year.

What are the infrastructure risks of single-vendor LLM lock-in in TaxTech? If your TaxTech vendor integrates deeply with one LLM provider, your compliance infrastructure inherits that provider’s pricing volatility, uptime performance, and geographic access restrictions. A vendor with multi-model routing can arbitrage across providers during outages or price spikes. A single-provider vendor cannot — and when that provider has a bad quarter, so does your compliance stack.

References & Further Reading

1. Hybrid SLM + LLM Orchestration: The 2026 Strategy for Cost-Effective Enterprise AI — Medium/GenAI Protos — Accessed June 2026

2. LLM Orchestration in 2026: Frameworks + Best Practices — orq.ai — Accessed June 2026

3. 5 Enterprise AI Gateways for LLM Cost Control in 2026 — Maxim AI — Accessed June 2026

4. Routing, Load Balancing, and Failover in LLM Systems — DEV Community — Accessed June 2026

5. Avalara Agentic Tax & Compliance — Avalara — Accessed June 2026

6. AI Prices Are Going Up, Up, Up — Josh Bersin — May 2026

7. Gartner: LLM Inference Cost to Drop 90% by 2030 — Gartner — March 2026

8. Anrok Raises $55M Series C — Business Wire — October 2025

9. Agentic AI Cost Management: Stopping Margin Erosion — Kong Inc. — Accessed June 2026

10. The Future Cost of TaxTech: Managing the New Unit Economics of Compliance — dmihaylov.com — April 2026

11. Intelligent LLM Routing: How Multi-Model AI Cuts Costs by 85% — Swfte AI — Accessed June 2026

12. Failover Routing Strategies for LLMs in Enterprise AI Applications — Maxim AI — Accessed June 2026

13. AWS Introduces New Cybersecurity, Coding Tools at NY Summit — The Information (Catherine Perloff) — June 2026

You’ve probably been in the room when your Tax SaaS vendor claimed to have an excellent tax filing audit trail. It lives on their infrastructure. It’s queryable through a UI. You can easily generate and download it. But there’s a catch. It may take 6-8 weeks or more to do it. For one jurisdiction.

I’ve learned this while working on TaxTech infrastructure at Uber. We operate in 70+ countries. Every jurisdiction has different VAT rules, entity registration requirements, and filing cadences. When you’re processing millions of trips, deliveries, and partner transactions per day, the gap between what your transaction system records and what your compliance tool reports can span days, entities, and undocumented transformation steps. Reconstructing how you got there is a different problem entirely — and it’s one the Tax SaaS was never designed to solve. Or at least I have not seen a tool remotely capable of doing this yet.

So, when the IRS, HRMC, or an EU tax authority flags your entity structure or a discrepancy between real-time e-invoicing and VAT reporting, and the inquiry lands, you’ll be facing this very problem. And it’s an issue you’ll face very often because of the sheer efficiency with which tax authority systems can now deploy AI to find even minor inconsistencies in your data.

Last week, I wrote about how three tax authorities deployed AI in 2026 that queries your data rather than your return. The IRS runs Palantir’s SNAP (Selection and Analytic Platform) across 100+ fragmented legacy databases, surfacing entity relationships no human auditor could trace manually. Through a contract with the HMRC, Quantexa is building a Unique Customer Record: a single, consistent view of every taxable entity in the UK, resolved from fragmented public and private sources. The EU AI Act’s high-risk AI enforcement comes into force on 2 August 2026.

The question I left open: how do you prepare for this?

The Readiness Gap, By the Numbers

On 19 May 2026, Vertex published a global study of 1,050 senior IT, Finance, and Tax leaders across the US, UK, and Europe:

94% expect stronger collaboration between IT, Tax, and Finance. Only 12% have achieved full integration. Tax teams are consulted on technology decisions 37% of the time. Only 37% report high confidence in their tax-ready data.

I recognize that 12% gap from the inside. At Uber, the product team making decisions about trip pricing, partner fee structures, and payment flows is not the same team filing VAT returns. The decisions upstream create tax obligations downstream — and the pipeline connecting those two realities is something you build intentionally, or you discover under pressure. Most enterprises are discovering it under pressure.

Why Your Vendor Cannot Close This Gap

So, data readiness seems to be the most pertinent compliance risk. The natural move is to buy a tool. I’ve seen it happen repeatedly, and it’s the right call for many problems. But it is the wrong call for this one — for three specific reasons.

1. Your vendor’s audit trail is not your audit trail

When your compliance data lineage lives on a vendor’s infrastructure, you are paying for access to your own operational data. If an inquiry requires you to reconstruct a tax position independently — outside the vendor’s interface, without an active support contract — you discover that the lineage exists only within their system.

At Uber scale, this matters profoundly. What I’ve found is that no single vendor has access to all of our data. Let’s take Portugal as a good example. A trip there touches a local operating entity, a Tax SaaS, a payment processor — each potentially in a different jurisdiction with a different data system. The compliance tool shows the output of that structure, not granular views of the local entity’s ERP, the SaaS vendor’s software, or the payment processor’s dashboard. However, the Tax Authority’s system has a unified view of all data and uses AI to detect discrepancies to the finest detail. So, if you can only explain the output, you’ve already lost the first exchange.

2. The compliance logic lives in a vendor’s black box

In many cases, your vendor provides the tax determination logic—configurable via toggles and rule dropdowns. After all, that’s their bread and butter. But it’s something you don’t actively monitor for correctness, and you cannot explain on demand. A human auditor might accept “it’s a system configuration”. The IRS SNAP and HMRC Quantexa do not. They generate conclusions before the inquiry even arrives. By the time a human asks, the model has already formed a view.

You need to be able to say: here is the rule, here is the source, here is the transformation, here is the timestamp. If the only honest answer is “our vendor configured it,” you’re in trouble.

3. Entity resolution has to reflect your specific corporate structure — not a vendor template.

Vendor entity models are built for the median enterprise. They support a parent holding company, a handful of subsidiaries, and standard related-party taxonomies. They were designed to handle what most companies look like — not what your company actually is.

At Uber, a single trip can touch four legal entities before it produces a VAT-reportable output: the local operating entity that contracts with the driver, the technology licensor that licenses the platform, the payment processor that clears the funds, and the entity that reports the consolidated revenue. Each entity has a different registration, a different role in the intercompany chain, and potentially a different identifier across our data systems. No off-the-shelf entity template maps that structure correctly out of the box. You configure it, you maintain it, and when the structure changes — a new country entity, a restructuring, a merger — you own the update.

HMRC’s Quantexa does not work from your vendor’s entity template. It resolves your structure from Companies House filings, PAYE records, MTD transaction feeds, and cross-referenced VAT registration data — sources your vendor never touches. The result is a Unique Customer Record that HMRC builds from the outside in, using data you submitted to other government systems, not data your vendor configured on your behalf. If that externally resolved view of your entity graph surfaces a parent-subsidiary relationship that your ERP has inconsistently classified across jurisdictions, the algorithm flags it. Your vendor’s template cannot explain the inconsistency because the template was never aware of it.

You own that template, which means it has to be built and maintained by people who understand your corporate structure, not inherited from a vendor taxonomy that was never designed for it.

The Nine-Step Enterprise Readiness Guide

These nine steps follow a five-phase arc: Diagnose → Measure → Build → Test → Own. They’re sequenced so each phase builds on the output of the previous one.

1️⃣ Map your tax data pipeline. Find every source feeding a compliance output. Find where the inconsistencies live before the algorithm does.

2️⃣ Establish column-level lineage. For any material tax position: which transaction, which rule, which source, which transformation. If it takes more than an hour to answer, you don’t have defensible lineage.

3️⃣ Run a cross-jurisdiction entity audit. The same entity shouldn’t have different identifiers in your US, UK, and EU systems. HMRC’s Quantexa will find that mismatch. Run it yourself first.

4️⃣ Benchmark your data freshness SLA. HMRC queries real-time patterns against your quarterly filing. If your data is 90 days stale, that gap is your exposure — not your return. Here’s why compliance latency matters.

5️⃣ Audit your vendor’s output format. An ML model cannot query a PDF. If your audit trail is a PDF, it is not an audit trail for an algorithmic adversary.

6️⃣ Decouple your compliance logic from your vendor’s UI. If your vendor is acquired tomorrow, can your engineers independently reproduce the determination logic? If not, version-control it until they can.

7️⃣ Build the Tax × Engineering × Data bridge. Not a committee. A standing function with a charter, a meeting cadence, and a CPO/CTO reporting line.

8️⃣ Red-team your own entity graph. Run the analysis SNAP and Quantexa would run. The IRS AI targets “allocations that don’t match economic reality.” Find those internally before the model does.

9️⃣ Name an owner for AI audit readiness. Not the tax team. Not IT. One cross-functional role, one mandate, one reporting line to the CPO or CTO. If nobody owns it, nobody fixes it.

📥 The full operational guide — with step-by-step instructions, the questions to ask your team, and the tools to use at each phase — is available as a free PDF.

Download

Download: The Nine-Step Tax Data Readiness Guide →

The Tax Data Readiness Guide

17.3KB ∙ PDF file

Download

Based on my experience at Uber

Download

(Free. No paywall. If you find it useful, please share it.)

🔮 Prepare for What’s Coming

By 2028, “tax data observability” will be a defined engineering discipline at S&P 500 companies — with dedicated tooling, named ownership, and SLAs sitting inside Product and Engineering, not the tax function. The CPOs and CTOs who build this infrastructure in 2026 will spend 2028 explaining their methodology to auditors from a position of control. The ones who don’t will spend 2028 reconstructing pipelines under inquiry timelines they don’t control. The gap between those two outcomes is the nine steps above.

Frequently Asked Questions

What data does the IRS AI actually query during a tax enforcement action?

The IRS uses its Selection and Analytic Platform (SNAP), built with Palantir, to query structured transaction data, entity relationships, intercompany flows, and basis records across its fragmented legacy databases. The system compares these against sector benchmarks and historical patterns to flag statistical anomalies — without reviewing a return in the traditional sense. Source: GAO-26-107522, March 2026; Capitol Technology University, 2026; FindLaw.

What is entity resolution, and why does it matter for enterprise tax compliance?

Entity resolution is the process of linking records that refer to the same individual, company, or transaction across multiple databases — even when those records use different identifiers, formats, or naming conventions. HMRC's Quantexa contract is built precisely on this capability. If your enterprise's entity model is inconsistent across jurisdictions, enforcement systems will surface the inconsistency before you can explain it. Source: Quantexa press release; Global Government Finance; The Next Web, May 2026.

How do I make my enterprise tax data audit-defensible?

Audit defensibility requires column-level data lineage: the ability to trace any filed tax position back to its source transaction, through every transformation, with timestamps and ownership records — producible on demand, independently of your compliance vendor, in under one hour for material positions. Manual reconstruction via spreadsheets, email chains, or vendor support tickets does not meet the standard an algorithmic inquiry implies. Source: OvalEdge; JMCO, 2026.

Who should own tax data infrastructure — the tax team, IT, or engineering?

None of them independently. The gap between these three functions is precisely where enterprise tax exposure lives in the agentic enforcement era. A cross-functional role spanning Tax, Product, and Engineering — with a mandate, a budget, and a reporting line to the CPO or CTO — is the correct ownership structure. This is distinct from the tax team, which owns determination logic, and from IT, which owns system availability. Source: Vertex Inc. global research, May 2026.

Should enterprises build or buy their tax compliance technology stack?

Both — but the boundary matters. Vendor tools remain appropriate for commodity compliance tasks: return preparation, statutory filing, and routine determination. Tax data infrastructure — lineage, entity resolution, pipeline architecture, independent audit trail ownership — must be a core internal engineering competency. A vendor can be a layer on top. The pipeline, the lineage, and the ability to reconstruct your position independently cannot be outsourced. Source: Fortune, April 2026; Vertex Inc., May 2026.

REFERENCES & FURTHER READING

1. Vertex Inc. — “New Vertex Research Highlights Rising Revenue Risk from IT, Tax, and Finance Misalignment” — https://www.vertexinc.com/company/news/latest-news/new-vertex-research-highlights-rising-revenue-risk-it-tax-and-finance-misalignment — Accessed May 2026

2. Global Government Finance — “HMRC inks £175m deal to boost data, analytics and AI firepower” — https://www.globalgovernmentfinance.com/hmrc-quantexa-entity-resolution-service-data-analytics-ai/ — Accessed May 2026

3. The Next Web — “HMRC awards £175 million AI contract to British firm Quantexa” — https://thenextweb.com/news/quantexa-hmrc-ai-tax-fraud-sovereignty — Accessed May 2026

4. Quantexa — “Quantexa Selected by HMRC for Landmark £175M Sovereign Data and AI Transformation” — https://www.quantexa.com/press/quantexa-selected-by-hmrc-for-landmark-pound175m-sovereign-data-and-ai-transformation/ — Accessed May 2026

5. U.S. GAO — “Artificial Intelligence: IRS Actions Needed to Address Skills Gaps, Information Quality, and Strategic Management” — https://www.gao.gov/products/gao-26-107522 — Accessed May 2026

6. FindLaw — “IRS Seeking Increased Use of Palantir’s AI and Data Tools to Help Decide Who to Audit” — https://www.findlaw.com/legalblogs/law-and-life/irs-seeking-increased-use-of-palantirs-ai-and-data-tools-to-help-decide-who-to-audit/ — Accessed May 2026

7. OvalEdge — “Data Lineage Best Practices for 2026: Ensure Accuracy & Compliance” — https://www.ovaledge.com/blog/data-lineage-best-practices — Accessed May 2026

8. JMCO — “Data Lineage and Audit Trails: What Finance Teams Must Get Right in 2026” — https://www.jmco.com/articles/daniel-shorstein/data-lineage-and-audit-trails-what-finance-teams-must-get-right-in-2026/ — Accessed May 2026

9. Fortune — “Why your data infrastructure — not your AI model — will determine whether Agentic AI scales” — https://fortune.com/2026/04/30/agentic-ai-data-infrastructure-readiness-scale/ — Accessed April 2026

10. GoCardless — “Making Tax Digital explained: Your guide to the 2026 Income Tax changes” — https://gocardless.com/blog/mtd-itsa-income-tax-changes-2026-guide/ — Accessed May 2026

11. Deloitte TaxScape — “Making Tax Digital for Income Tax” — https://taxscape.deloitte.com/article/making-tax-digital-for-income-tax.aspx — Accessed May 2026

12. PwC — “The next era of tax compliance: real-time and data-driven” — https://www.pwc.com/gx/en/services/tax/connected-tax-compliance/tax-authorities-ai-compliance.html — Accessed May 2026

13. Capitol Technology University — “Audited by an Algorithm: How the IRS Is Using AI in 2026” — https://www.captechu.edu/blog/audited-algorithm-how-irs-using-ai-2026 — Accessed May 2026

Tax enforcement went agentic. Your tax compliance didn’t.

That sentence likely lands somewhere between “interesting” and “uncomfortable” for many TaxTech leaders. The assumption that has governed enterprise tax strategy for the last decade — buy/build a compliance tool, let the tax team run it, move on — has quietly broken.

And the people who need to fix it must start asking the right questions.

The New Watchdog Doesn’t Read Returns

The IRS now runs 126 active AI applications targeting audit selection, fraud detection, and pattern matching — up from 10 in 2022. HMRC just awarded a £175M, ten-year contract to Quantexa — a platform originally built for financial crime detection at banks — to cross-reference every UK business entity against a unified data infrastructure it’s building from scratch. The EU AI Act’s full high-risk AI enforcement lands on 2 August 2026 — fines for prohibited AI practices are already active at up to €35M or 7% of global turnover; high-risk non-compliance from August carries a further exposure of up to €15M or 3%.

These systems don’t review returns the way a revenue agent does. They query structured (and probably unstructured) data. They resolve entities across fragmented datasets. They build graph models of your corporate structure, intercompany flows, and VAT reclaim ratios — and compare them against sector benchmarks, peer groups, and expected configurations at scale. The IRS AI has already selected 3,600+ large partnerships for examination. It didn’t do that by only reading PDFs.

The return is the structured output of your data pipeline. If the pipeline is fragmented, entity resolution is inconsistent across jurisdictions, or your intercompany flows don’t reconcile cleanly, the algorithm finds the gap. This is when you also start blipping on the tax authority’s radar.

What HMRC Just Revealed About Your Stack

The Quantexa contract is worth studying in detail because what HMRC is building on the enforcement side mirrors what most enterprise tax teams haven’t built on the compliance side.

Quantexa’s platform was built for entity resolution at scale — connecting fragmented data from multiple sources, resolving identities across datasets, and using graph analytics to surface patterns that no human team could find manually. HMRC’s stated goal is a single, trusted, connected view of every taxable entity in the UK, built from data currently stored across multiple legacy systems that don’t communicate with each other.

Read that again from the other side of the table: HMRC is solving the data fragmentation problem on the enforcement side. Most enterprise tax teams haven’t solved it on the compliance side. The authority will soon have a cleaner, more connected view of your entity structure than your ERP does.

Three Questions to Run Internally This Quarter

1. Can you reconstruct the lineage of any tax position in your stack?
   Not the final number — the lineage. Which transaction triggered it, which rule applied, which data source it came from, and which engineer last touched the pipeline that produced it? If the answer takes more than a day to produce, your lineage is not audit-defensible against an algorithmic adversary.
   

2. Is your entity model consistent across jurisdictions?
   If the same legal entity appears differently in your US ERP instance, your UK instance, and your EU reporting layer, an AI enforcement system will notice. A human auditor might accept an explanation. The algorithm flags the inconsistency and moves on. Run the cross-jurisdiction entity reconciliation before Quantexa does.
   

3. What is the data freshness SLA for your compliance outputs?
   HMRC’s Making Tax Digital has been feeding continuous transaction data into Quantexa’s platform since April 2026. If your compliance tool produces a quarterly filing from data that’s already 90 days stale, and the enforcement system queries real-time transaction patterns against that filing, the mismatch is your exposure, not your return.

When an AI enforcement inquiry arrives — and it will arrive not as a letter but as a model’s conclusions, already formed before the inquiry is even sent — the tax team will need to answer data questions that you can only address if you have planned for it. This gap is where enterprise exposure lies in 2026.

The adversary is now a data system. The only defensible response to a data system is better data.

References & Further Reading

1. U.S. GAO — “Artificial Intelligence: IRS Actions Needed to Address Skills Gaps, Information Quality, and Strategic Management” — https://www.gao.gov/products/gao-26-107522 — Accessed May 2026

2. The Next Web — “HMRC awards £175 million AI contract to British firm Quantexa to close £46.8 billion tax gap” — https://thenextweb.com/news/quantexa-hmrc-ai-tax-fraud-sovereignty — Accessed May 2026

3. FinTech Futures — “Quantexa lands £175m HMRC contract for data infrastructure overhaul” — https://www.fintechfutures.com/partnerships/quantexa-lands-175m-hmrc-contract-for-data-infrastructure-overhaul — Accessed May 2026

4. Capitol Technology University — “Audited by an Algorithm: How the IRS Is Using AI in 2026” — https://www.captechu.edu/blog/audited-algorithm-how-irs-using-ai-2026 — Accessed May 2026

5. U.S. GAO — “Inside the IRS’s Use of Artificial Intelligence” — https://www.gao.gov/blog/inside-irs-use-artificial-intelligence — Accessed May 2026

6. Thomson Reuters — “Tax firm AI platform vs. point solution: 2026 buyer’s guide” — https://tax.thomsonreuters.com/blog/tax-firm-ai-platform-vs-point-solution-2026-buyers-guide/ — Accessed May 2026

7. PwC — “Navigating the shift to an AI-powered tax operating model” — https://www.pwc.com/us/en/services/tax/library/tax-operating-model-ai-shift.html — Accessed May 2026

8. Axis Intelligence — “EU AI Act News 2026: Compliance Requirements & Deadlines” — https://axis-intelligence.com/eu-ai-act-news-2026/ — Accessed May 2026

In the boardrooms of the S&P 500 and high-growth scale-ups, the “common wisdom” is that AI is primarily a productivity booster within specific workflows—a narrative fueled by marketing promises of an “era of builders” where everyone can create at scale. This is not wrong. But there is a twist. In 2026, we have transitioned from highly predictable, established SaaS pricing models to a “tokenized economy,” in which data is the input and output, and compute is the fuel, metered like a utility—a shift that makes real-time AI infrastructure stability as critical to the P&L as the tax logic being executed.

But here is the catch. You cannot manage a 2026 cost structure with a 2016 KPI dashboard. Here is the ground truth for the new KPI framework needed to navigate the tokenized economy today.

I. Latest Trends in AI Tech: The Tokenization of the S&P 500 Cost Structure

1. Enterprise Pricing: The Metered Reality

A look at the pricing models of the top 4 AI platform providers reveals that the era of the “flat-fee seat” is dead. We have entered the era of “utility AI”, in which compute is metered like electricity1:

It’s clear that for the S&P 500—companies managing 100 million to more than 1 billion transactions per year—AI costs are a direct hit to the margins. This is also what Uber’s CTO, Praveen Neppalli Naga, recently confirmed. In this interview, he revealed that the company exhausted its entire 2026 Claude budget by April due to deep agentic integration. Uber's R&D expenses rose 9% to $3.4 billion in 2025, and the company expects that figure to keep climbing—suggesting AI may be as much a cost driver as a productivity lever.

2. The Stability Layer: Reliability Tracking

At the S&P 500 scale, downtime isn’t an inconvenience—it’s a breach of compliance. The gold standard is “four nines” (99.99%), which allows for only 52 minutes of downtime annually. Let’s look at how the AI platform providers are doing in 2026:

None of the major LLM providers currently guarantees 99.99% uptime during peak global cycles. So, any taxtech architecture must have a failover logic to hot-swap providers in milliseconds when a “brownout” occurs.

3. Ownership Disruptions: Related Parties and Consolidation

In 2026, the AI world is one of related parties and imminent consolidation. Here are only the recent signals:

• The SpaceX-Cursor Vertical Integration: SpaceX has secured a $60 billion option to acquire Cursor to fill xAI’s infrastructure gap.

  This signals that the infrastructure used to build AI is as valuable as, if not more valuable than, the models themselves. If your infrastructure is tied to a platform that gets acquired, the impact may not be convenient.

• The OpenAI-Microsoft “Risk Factor”: In recent draft IPO filings, Sam Altman officially labeled Microsoft a “risk factor” due to OpenAI’s deep dependence on their compute.

  When such partnerships signal strategic friction, you must prepare for a change in compute infrastructure that could spike your costs overnight.

• The Anthropic-Amazon “compute debt”: Anthropic and Amazon have committed $100 billion to AWS custom Trainium chips.

  This creates a new vendor lock-in. If you are integrated with Claude, you are now effectively an AWS-dependent entity, regardless of your primary cloud strategy.

In summary, the shifting landscape introduces risks such as:

In other words, if your tax data is latent or your vendor stack is fragile, your AI becomes an expensive way to generate errors at the speed of light—transforming a potential efficiency engine into a high-frequency audit liability.

So, what’s the right course of action to mitigate those risks?

To mitigate these risks, the traditional fintech/taxtech KPI dashboard is no longer sufficient. We are moving toward dynamic, metered infrastructure with significant cost implications — a shift that requires a new set of KPIs to protect the bottom line. Here is how I would stay ahead:

1. No Infinite Spending Loops: Agentic AI can enter recursive loops that burn $100,000 in tokens before you finish your morning coffee. You need hard “circuit breakers” at the API level to stop runaway costs.
   

2. Get a Grasp of ROI: Stop using AI to only write memos or summarize meeting notes. Use it to automate the 4,000 manual monthly reconciliations that keep your accounting team up at night. The highest returns are found in escaping the manual loop, not executive dashboards or piles of memos.
   

3. Own Your Logic Library: If you bake your proprietary tax logic into a specific vendor’s prompt, as Xero did, you are a hostage to their uptime and pricing. Build for model agnosticism so you can migrate from OpenAI to Gemini in under 24 hours.
   

4. Audit for Infrastructure, Not Just Model Performance: With SpaceX securing a $60 billion option to acquire Cursor, the infrastructure that builds the code is now as valuable as the AI itself. Ensure your vendors are built on hyperscale foundations (Google/AWS/Azure) that can actually handle your transaction volume.

II. The S&P 500 TaxTech Dashboard

For the Chief Tax Officer or VP of Engineering, the greatest risk in 2026 isn’t a single audit; it’s invisible inefficiency. At the S&P 500 scale, you cannot manage what you do not measure. Therefore, we need KPIs that move beyond “monitoring” to “ROI orchestration,” i.e., actively managing the unit economics of compliance. Your dashboard should be more than a status report—it should be a decision engine that incorporates AI efficiency.

Here's my proposal for a scalable TaxTech Dashboard at the S&P 500 level:

Along with the traditional metrics such as Effective Tax Rate, Compliance Spend, and % of Manual Journal Entries, TaxTech leadership must follow some new KPIs:

1. AI Pricing Drift (Delta %)

With the end of the “flat-fee era,” the AI costs are now as volatile as energy prices. This KPI tracks the per-token spend variance. For example, if weekly drift exceeds 5%, the dashboard triggers an automated “model swap,” routing low-complexity tasks to more cost-effective tiers.

2. AI Decision Accuracy (%)

In 2026, manual troubleshooting is the silent killer of scale. This KPI tracks the percentage of tax triages handled by AI without human intervention. If it dips below 98%, for example, the dashboard should automatically increase the “human-in-the-loop” sampling rate to prevent systemic audit risks.

3. Token Effectiveness Ratio (TER / 1M tokens)

This KPI identifies exactly how many tokens are converted into defensible compliance outcomes versus the compute waste generated by recursive loops like API validation ping-pong (endless retries against failing portals), consensus conflict (agents arguing over logic until quotas are exhausted), or hallucination spirals (expensive internal reasoning used to resolve contradictory data). By tracking TER, budget owners can detect these “inference leaks” before they decimate quarterly results, ensuring the system maintains a defensible 1:1 ratio rather than slipping into the 1:1000 efficiency abyss that defines unmanaged infrastructure.

4. AI Latency & Uptime

In the fintech world, 5 seconds is an eternity. This metric tracks the milliseconds between a transaction and its tax-defensible status. Any dip below 99.99% reliability triggers a failover to a secondary sovereign cloud instance.

5. CAPEX Token Allocation

In the tokenized economy of 2026, CAPEX Token Allocation (ASU 2025-06) is extremely important. Following the 2025 FASB update regarding AI software capitalization, organizations must now surgically differentiate between tokens consumed for “creation”—the R&D and asset-building phases that qualify as capitalizable investments—and those used for “maintenance”, which hit the books as immediate operational spend. By monitoring this metric through real-time financial telemetry, budget owners can meet specific asset capitalization targets, thereby demonstrating to auditors that their AI spend is building a long-term intangible asset rather than merely subsidizing an expensive, ongoing maintenance loop.

Strategic Forecast

Over the next 24 months, the most successful FinTax leaders will shed their traditional “Head of Tax” skins and re-emerge as VPs of Compliance Infrastructure. In this new reality, the silo between the tax department and the platform engineering team will vanish entirely, replaced by a shared mandate: the real-time management of compliance telemetry. The standard for success will shift from “getting it done” to algorithmic efficiency. Expect to see:

• The Rise of the TER Audit: The Token Effectiveness Ratio (TER) will shift from a niche DevOps metric to a primary audited financial disclosure. The market will begin to value AI-enabled firms by their compute-to-compliance efficiency, with a ratio approaching $TER = 1:1$ (one successful outcome per unit of spent compute) representing a competitive moat, while anything higher signals an unmanaged inference leak.

• Drift-Triggered Rerouting: Pricing drift will become the new “interest rate risk.” Companies will deploy automated arbitrage bots that “hot-swap” compliance logic across LLMs (OpenAI, Anthropic, or Gemini) in milliseconds, based on real-time price-per-token volatility and latency performance.

• The End of the Monthly Close: As AI decision accuracy stabilizes above 99%, the concept of a monthly close will become a legacy term. We are moving toward “continuous compliance”, where tax filings are an automated, real-time byproduct of a data stream, and audit readiness is a constant state rather than a quarterly fire drill.

If you aren’t metering your way to ROI today, you aren’t just falling behind—you are accruing massive technical and fiscal debt that no amount of human “productivity” will be able to pay off.

FAQs: The 2026 Tokenized Economy

What is the “Tokenized Economy” in 2026?

The tokenized economy represents a shift from flat-fee SaaS pricing to a metered “utility AI” model. In this framework, data acts as the input/output, while compute is treated like electricity—metered and billed based on consumption. This makes real-time infrastructure stability a critical factor in a company’s P&L.

Why is the “flat-fee seat” model dying for enterprise AI?

As companies like Uber integrate deep agentic workflows, the volume of transactions (often exceeding 1 billion annually) makes per-user pricing unsustainable for providers. Utility AI allows providers to bill for the actual compute consumed, ensuring margins are protected as agentic complexity scales.

What is the Token Effectiveness Ratio (TER)?

The Token Effectiveness Ratio (TER) is a KPI that measures the ratio of AI tokens converted into defensible outcomes to the amount of waste. A 1:1 ratio is the gold standard, while higher ratios indicate “inference leaks” caused by recursive loops, hallucinations, or redundant API validation.

How does ASU 2025-06 affect AI spending?

Under the ASU 2025-06 FASB update, organizations must surgically differentiate between tokens used for “creation” (capitalizable R&D) and “maintenance” (operational spend). CAPEX Token Allocation allows companies to build long-term intangible assets on their balance sheets rather than just incurring ongoing expenses.

What are the main risks of AI infrastructure fragility?

The primary risks include pricing drift (volatility in token costs), infrastructure fragility (service outages during peak periods), and model latency. In 2026, a 5-second delay in AI processing can lead to blocked checkouts or failures in real-time tax compliance reporting.

How can companies achieve “model agnosticism”?

To avoid vendor lock-in and mitigate downtime, firms must build a proprietary logic library independent of any single LLM. This allows them to “hot-swap” between providers such as OpenAI, Gemini, or Anthropic in under 24 hours, based on real-time pricing and performance telemetry.

What is “Continuous Compliance”?

Continuous compliance is the 2026 standard, where tax filings are a real-time byproduct of automated data streams rather than a monthly manual “close.” As AI decision accuracy stabilizes above 98%, audit readiness becomes a constant state, eliminating the need for traditional quarterly fire drills.

References & Sources

• Anthropic Pricing: Anthropic Shifts Enterprise Billing to Per-Token Pricing (Implicator.ai, April 14, 2026).

• Uber AI Budget: Uber CTO Shows Claude Code Can Blow AI Budgets (The Information, April 10, 2026).

• SpaceX-Cursor M&A: SpaceX Secures Right to Acquire Cursor for USD 60 Billion (LatestLy, March 28, 2026).

• OpenAI: Official API Pricing Guide (Accessed April 22, 2026).

• Google Gemini: Vertex AI Pricing Overview (Accessed April 22, 2026).

• Vertex Resource Library: AI and Indirect Tax Trends (Accessed April 22, 2026).

• PwC Tax Tech: Unlocking Value in Tax Technology (Accessed April 22, 2026).

• Platform M&A & Infrastructure: Musk’s SpaceX bets $60 billion on Cursor to fix xAI’s coding gap (The Decoder, April 2026).

• Accounting Standards (ASU 2025-06): Accounting Best Practices for AI Use in Software Development (Broadcom/Clarity, April 2026).

• Unit Economics & Pricing: Anthropic Shifts Enterprise Billing to Per-Token Pricing (Implicator.ai, April 14, 2026).

• Performance & ROI: Want ROI from AI? Go for growth (PwC Global, April 2026).

• System Reliability Benchmarks: Real-Time Availability & Status Monitor (OpenAI, April 2026) and Anthropic System Status (Anthropic, April 2026).

• Sovereign AI & Compliance Risk: The Sovereign AI Boom and Trillion-Dollar Predictions (Motley Fool, April 2026) and Legal Analysis of AI Compliance Risks (Northman & Sterling, March 2026).

Some S&P 500 CFOs and Chief Tax Officers may take the obvious path, treating AI as a procurement exercise: buy the license, schedule mandatory training, set KPIs for usage, and wait for ROI. After all, this approach worked for other challenges, such as e-invoicing or the adoption of last year’s new accounting/tax software.

It won’t come. At Uber, I’ve seen that you cannot bridge the 2026 “fluency gap” with a three-month seminar. Nor with mandatory usage metrics.

The Market Mandate for AI-Native Fin/TaxTech Talent

The industry standard has shifted. My analysis of more than 100 current openings across the S&P 500, high-growth scale-ups such as OpenAI, Anthropic, and Lovable, the Big Four, and traditional SaaS vendors such as Xero, Intuit, and Brex reveals that leading firms are bypassing the “training phase” and hiring for AI fluency as a day-one prerequisite.

We are seeing a structural shift in the “Tax/FinTech Lead” role. In other words, there are new capabilities and requirements being sought for high-stakes transformations:

• OpenAI is recruiting a Tax Technology Lead to design tax as a “Production System,” integrating compliance directly into core product infrastructure.

• PwC has shifted from “upskilling” to hiring AI-Native Engineering Leads who must demonstrate daily proficiency with AI coding assistants.

• Intuit is aggressively hiring for AI Workforce Transformation to lead the shift toward AI-first developer velocity.

• Anthropic and Lovable are seeking AI-native operators who use agentic workflows to handle real-time Finance & BI decision velocity.

• EY and Grant Thornton are targeting Tax Automation & AI Managers to build “AI-enabled solutions” for global VAT and indirect tax reporting.

So, what do you need to do?

The FinTax AI Fluency & Hiring Rubric

To move your organization from “pro forma” adoption to “front-line” efficiency, you need to update your hiring rubric. Here is Zapier’s hiring rubric, designed to bring AI-native talent in-house with every hiring decision. It’s a good example.

Here is what a Fin/TaxTech hiring rubric may look like, along with examples of the expected behavior, potential gain, and hiring filter questions to ask:

• Stage 1: The Consumer (Passive Use)

  • Behavior: Using public LLMs to summarize tax memos.

  • Potential Gain: 5-10% productivity lift on administrative tasks and gross time savings of ~5 hours per week.

  • Hiring Filter: Ask: "Explain the difference between an LLM and a database." If they view AI as a "search engine" rather than an "execution engine," they are liable for hallucinations.

• Stage 2: The Auditor (Problem Decomposition)

  • Behavior: Reviewing AI-generated reconciliations. They understand the “why” behind the logic.

  • Potential Gain: 20-30% reduction in manual review time and a 15-25% reduction in manual errors.

  • Hiring Filter: Ask them to decompose a complex tax problem into prompts. If they can’t break down the workflow, they can’t create working AI flows.

• Stage 3: The Orchestrator (Agentic Design)

  • Behavior: Designing workflows where AI agents handle the “first mile” (data ingestion) and “last mile” (filing).

  • Potential Gain: Teams hiring orchestrators see a 3.5x higher ROI than those stuck in “training mode.”

  • Hiring Filter: Ask: "Walk me through a multi-agent workflow you've designed to automate a high-volume tax workstream. How did you structure the 'human-in-the-loop' intervention points?"

• Stage 4: The Architect (Tax Product Lead)

  • Behavior: Building a reusable logic library for 100+ jurisdictions.

  • Potential Gain: 40-60% cycle-time reduction on global filings and the ability to launch in new markets in days, not months.

  • Hiring Filter: Ask: "How would you structure a global tax engine to ensure compliance logic is a 'production system' integrated into the product roadmap, rather than a stand-alone 'to-do' list for the tax team?"

Summary

To scale a FinTech or TaxTech function in 2026, you must stop treating AI as a procurement project and start treating it as a hiring mandate.

References & Comprehensive Job Analysis (100+ Openings)

• Deloitte, “The State of AI in the Enterprise 2026: Strategy for the S&P 500”, April 2026. deloitte.com/state-of-ai-2026

• DualEntry, "AI in Accounting: The Complete 2026 Guide", April 2026.

• Market Growth Reports, "Artificial Intelligence in Accounting Market Size and Trends Research [2035]", February 2026.

• Thomson Reuters, “2026 Corporate Tax Technology Report: The Rise of Agentic Tax Tech”, March 2026. tax.thomsonreuters.com/corporate-tax-technology-2026

• Zapier, “Raising the AI Fluency Bar in Hiring”, March 2026. zapier.com/blog/raising-ai-fluency-bar-in-hiring

• PwC, “From Compliance to Intelligence: The 2026 Global Tax Outlook”, February 2026. pwc.com/global-tax-outlook-2026

• Microsoft Official Blog: New IDC study shows AI’s real-world ROI (November 1, 2023)

• Direct Link to the IDC InfoBrief: The Business Opportunity of AI

• OpenAI Careers, Tax Technology Lead, April 2026. openai.com/careers/tax-technology-lead

• PwC Careers, AI-Native Engineering Lead, April 2026. jobs.us.pwc.com/ai-native-lead

• Intuit Careers, AI Workforce Transformation, March 2026. jobs.intuit.com/ai-workforce

• Lovable Careers, Finance & BizOps Strategic Partnerships, April 2026. lovable.dev/careers/finance-bizops

• Anthropic Careers, Finance Analytics & BI, April 2026. pitchmeai.com/anthropic-finance

• EY Careers, Tax Technology and Operations, February 2026. ey.com/tax-tech-jobs

• KPMG Careers, Tax Transformation Specialist, 2026. kpmg.com/tax-transformation

I have been watching the rapid rollout of AI assistants across the tax/accounting/finance tech stack—from Brex Assist and Xero’s JAX to Intuit Assist. These tools are incredible at turning fragmented, manual processes into centralized, automated engines.

But amidst these rapid developments, I've been asking the same question: if your AI “hallucinates” a €10M tax deduction based on a misinterpretation of a cross-border VAT treaty, who signs the penalty check?

So, I decided to analyse the consequences focusing on two aspects:

1. What are the current guidances on using AI for tax reporting from Tax Authorities around the world? (note: of course, my research is not tax advice and is based on publicly available sources. Consult tax professionals for further guidance.)

2. How should product manager, engineers, and tax managers approach incorporating these guidances when integrating AI into critical systems?

Global Research Summary: AI Liability & Tax Compliance (2026)

To answer the first question, I dove into publicly available, country-specific guidances. Here are some observations from across the globe based on publicly available articles.

1. The UK & EU: The “Liability Hammer”

• United Kingdom: The FRC’s March 2026 guidance is the global gold standard—audit partners and directors are 100% accountable for AI outputs. The precedent set in Gary Elden v HMRC (2026) proves that “unchecked AI use” is now legally categorized as professional incompetence. As the regulator says: “You can’t blame it on the box.”

• European Union: As of August 2026, the EU AI Act is fully enforceable. Penalties for “high-risk” financial AI errors can hit €35M or 7% of global turnover.

• France & Poland: France’s 2026 e-invoicing mandate and Poland’s KSeF system have removed the buffer. Taxpayers—not their software providers—remain solely liable for every data point transmitted.

2. APAC: Governance of “Agentic” AI

• Singapore: Budget 2026 introduces a 400% tax deduction for AI expenditure, but with strings attached. Singapore has launched the world’s first Model Governance Framework for Agentic AI, emphasizing that “meaningful human accountability” must remain central to deployment.

• Japan: The 2026 Tax Reform incentivizes AI R&D but tightens intra-group transaction documentation. The NTA is moving toward Tax Administration 2.0, using AI to automatically match NTA data to identify taxpayer errors.

• New Zealand: Inland Revenue (IRD) has confirmed that “human in the loop” oversight is mandatory for all AI workflows.

• Australia: The ATO now requires an AI Transparency Statement from all entities that use AI in tax-affecting decisions.

3. LATAM: Transparency & “Risk-Based” Compliance

• Brazil: The new Taxpayer Protection Code (TPC) introduces the “habitual tax debtor” status. If your AI creates unjustified non-payment, you lose tax benefits.

• Mexico: The 2026 Master Plan targets improper deductions identified by SAT’s AI. If your system cannot prove the “materiality” of a transaction, the deduction is denied.

• Argentina: Law No. 11,089 mandates that any AI used for tax settlement must be subject to external, independent audits.

4. North America: The Enforcement Surge

• USA (IRS): The IRS has expanded its AI use cases to 126, with a focus on large partnerships. They use AI to catch the “hallucinations” in your filings. Without contemporaneous support, your AI-driven deduction is a red flag.

• Canada: The CRA 2026-27 Plan treats AI errors the same as manual ones.

Based on this research, here is a summary of where global authorities sit on the “AI Sentiment Spectrum”:

Guide to the Spectrum:

• Zone 1: Innovation-First

  • Core Philosophy: AI is viewed as a national competitive advantage. Regulators prioritize adoption and “safe harbor” provisions for early movers.

  • Examples: In Singapore, Budget 2026 offers massive tax deductions (up to 400%) for AI implementation, provided companies follow the Model Governance Framework for Agentic AI.

  • The Trade-off: High transparency is expected, but the focus is on “Cooperative Compliance” rather than punitive measures.

• Zone 2: Balanced Scrutiny

  • Core Philosophy: “Trust, but verify.” These authorities use AI aggressively for their own enforcement (e.g., the IRS’s 126 use cases) and expect taxpayers to maintain a high bar of documentation.

  • Examples: Australia (ATO) and the USA have effectively mandated “Contemporaneous Support.” If an AI picks a deduction, you must be able to surface the underlying data trail immediately.

  • The Trade-off: No special penalties for AI errors yet, but standard penalties are applied strictly with a lower tolerance for “clerical error” excuses.

• Zone 3: Liability-First

  • Core Philosophy: “The AI black box is no defense”. Algorithmic mistakes are treated as human professional negligence.

  • Examples: The EU AI Act (enforced Aug 2026) imposes fines up to 7% of global turnover. In the UK, the FRC’s stance is that a hallucination is proof of a lack of professional skepticism.

  • The Trade-off: Speed is secondary to Auditability. In these regions, a “Black Box” AI system is essentially a ticking legal time bomb for a CFO.

So, what do we do to prepare for this seismic shift? In the upcoming sections, I am giving some thoughts on how to prepare.

1️⃣ The Tech Maturity Gap: Breaking the “Tech Stack Prison”

In my experience building at S&P 500 scale, the biggest risk isn’t the AI itself—it’s the Maturity Gap. According to the Thomson Reuters 2026 Corporate Tax Department Technology Report, the term describes the relative advancement of a company’s tech stack through the different stages of technological maturity, which refers to the typical steps that a corporate tax department travels through on its technological journey toward a more proactive approach to tax work:

According to the report, 55% of the surveyed companies are stuck in Phase 2: Reactive. This stage includes:

• Using tax department databases, some 3rd party software, with some auto mated feeds, but not connected to enterprise data or departments across the company.

• Tech budget shared with multiple departments

• Hired a tech consultant or outsourced tech resources

• No technology training provided

• Needs investment in process automation/tech solutions for most time-consuming activities (tax data management, transfer pricing, FATCA/CRS/AEOI )

• More robust metrics needed to measure succes

In essence, these companies have an outdated tech stack which makes any scalable AI usage impossible. To escape this “tech stack prison,” they must move up the Technological Maturity Curve to get to Optimized & Predictive (Stages 4-5). In those, the tax logic is a standalone platform capability. This is the only way to scale sustainably.

2️⃣ The Audit Trap: Defining “Reasonable Care” in a Neural Network

How do you prove “reasonable care” when your tax logic is buried in a neural network?

In a traditional audit, you show your work via spreadsheets or law citations. In an AI world, regulators are shifting the definition of “care” from what you filed to how you governed the system that filed it.

As the ACCA’s 2026 Topical Guidance notes: “Members should avoid overstating the accuracy of the data output... Undertaking appropriate due diligence on the output provided by an AI tool can help safeguard against the risks.”

The “A.C.E.S.” Framework for Defensible AI

To get a step closer to complying with the updated reasonable care definition, I suggest the A.C.E.S. Framework—a four-pillar approach to ensuring any AI is audit-ready and legally defensible:

3️⃣ The Penalty Reality: Moving to “Rules as Code”

If you are sourcing a system today, move beyond the “AI” hype. Tax requirements shouldn’t be a one-off ticket; they need to be a reusable logic library.

As organizations like the OECD and OPSI have championed in their Rules as Code (RaC) frameworks, the goal is to transform legislation into machine-consumable code. To incorporate this at your enterprise, I suggest the you consider the following:

1. Rule Atomization: Decouple tax logic from your ERP. Store rules in a modular “Source of Truth” (using engines like OpenFisca or Drools).

2. API-First Consumption: Expose these rules via a Tax Service Layer. Any system—whether it’s a checkout page or a GenAI assistant—must call this central library for a deterministic check.

3. Governance Wrappers: Wrap AI probabilistic insights within human-defined, deterministic rules to ensure an immutable audit trail.

In case you source your tax reporting software from a 3rd party, make sure those are in place before signing a contract.

🎯 The Bottom Line: Strategic Mandates for Defensible Tax Reporting Using AI

The era of “black box” tax automation is officially over. To reach the next level of global digital transformation and mitigate the €35M risk, senior leadership must adopt the following three mandates:

I. Accountability: Human-Centric Liability

“You cannot blame it on the box.” Regulatory mandates in the UK (FRC) and the EU (AI Act) have made it clear: liability for AI hallucinations sits squarely with human partners and company directors. Neither the software vendor nor the AI model can hold the burden of proof. Organizations must move from passive consumption of AI outputs to active, documented oversight.

II. Architecture: Transitioning to the “Predictive” Stage

The “Tech Stack Prison” is one of the greatest barrier to AI-driven efficiency. Companies stuck in Stage 2 (Reactive) lack the data integration required to validate AI insights. To scale sustainably, the tax logic must be decoupled from the ERP and implemented as a standalone platformcapability. This shift allows for the validation of probabilistic AI guesses against hard-coded legal rules in real-time.

III. Defense: Re-Defining “Reasonable Care”

In a traditional audit, care is shown through spreadsheets. In an AI-native world, auditors will inspect your governance. Institutionalizing AI governance through a framework such as A.C.E.S. or another is the only way to satisfy the “Reasonable Care” requirements of modern tax authorities. Without a framework that allows you to “replay” the logic of a 2024 transaction in a 2026 audit window, your AI-driven deductions will be treated as red flags.

References & Sources

• OECD OPSI: Rules as Code: A Case Study in Public Sector Innovation (2024-2026)

• Thomson Reuters Institute: 2026 Corporate Tax Department Technology Report (March 2026)

• Financial Reporting Council (UK): Guidance on AI Accountability (March 2026)

• Ross Martin Tax: Gary Elden v HMRC (2026) Case Summary (Jan 2026)

• K&L Gates: Singapore’s New Model AI Governance Framework for Agentic AI (Feb 2026)

• Alvarez & Marsal: Singapore Budget 2026 Spotlight (Feb 2026)

• EY Japan: 2026 Japan Tax Reform Highlights (Feb 2026)

• IMF/NTA Japan: Tax Administration 2.0 Digital Transformation (2026)

• Inland Revenue NZ: OIA: Use of AI at IR (Jan 2026)

• ATO Australia: AI Transparency Statement (2026)

• BDO Global: Brazil Taxpayer Protection Code 2026 (March 2026)

• Olshan Law: IRS AI Use in Tax Enforcement (March 2026)

• Baker McKenzie: EU AI Act Compliance Radar (Accessed April 2026)

• OECD: Due Diligence Guidance for Responsible AI (Feb 2026)

• ACCA Global: Application of PCRT to AI Ethics (Jan 2026)

Imagine that a Tax, Accounting, and Finance team consists of 100 people. 80 of them are doing work a script could do in 4 seconds. Why?

Because that team is trapped in what I would call a “Tech Stack Prison.” According to the newly released March 2026 study by Thomson Reuters, tax teams are trapped extracting data from fragmented ERPs, shared drives, and disparate CRMs. Tax teams that eliminate these structural, manual bottlenecks reduce preparation time by 50%—reclaiming more than 10,000 hours annually. The report also highlights that human error at scale is the silent killer of enterprise agility. A single decimal-point error, multiplied across millions of global transactions, doesn’t just result in an overpayment; it also triggers audits and blocks new market expansion. A single decimal-point error, multiplied by a quarter, creates massive financial liability.

If you lead Finance or Tax at an S&P 500 company or a hyper-growth scale-up like Anthropic or OpenAI, your team already knows the law. They understand the regulations natively. What they probably lack is the technical architecture to execute that knowledge at scale.

This is where the “Compliance Brain” needs the “Product Heart.”

To prevent compliance from blocking top-line growth, Finance and Tax leaders must stop thinking like back-office administrators and start operating like Product Managers. Here are five architectural strategies to break your team out of the tech stack prison:

1️⃣ Escape the Manual Loop via Automated Pipelines

Don’t drown your top talent in arduous reconciliations. The modern standard is to partner with your product and engineering teams to replace fragmented ERP data extraction with automated API pipelines. By feeding a centralized data warehouse, you establish a single source of truth. You turn a chaotic, manual data-gathering exercise into a centralized, automated engine that provides auditability in days, not months.

2️⃣ Eradicate the Spreadsheet Version Nightmare

A comprehensive Bloomberg Tax survey found that 92% of corporate tax professionals view their workpapers as critical. Yet, most rely on legacy spreadsheets that lack cell-level tracking and robust access controls. Moving out of the tech stack prison means adopting systems with embedded native controls. You need automated roll-forwards, version control, and cell-level audit trails so that “version_final_v4.xlsx” never compromises your compliance posture again.

3️⃣ Data Workings at S&P 500 Scale

What I learned while scaling global operations at Uber is that compliance isn’t just about calculating the tax rate; it’s about the data trail. Today, AI can identify anomalies in millions of transactions and generate reporting at a massive scale. But modern tax and finance tech shouldn’t just flag an error; it should simulate the fix upstream.

Shift your system from reactive error-catching to proactive, systemic resolution.

4️⃣ Move from Historical Reporting to Predictive Exposure

As outlined in EY’s Global Tax and e-Invoicing strategies, governments are shifting to near real-time compliance (like the EU’s ViDA or LATAM’s continuous transaction controls). They want your data before the transaction is finalized. Your tech stack must evolve from historical reporting to predictive analytics. AI should be leveraged to identify tax exposure and nexus risks before they materialize, allowing you to build compliance roadmaps that accelerate—rather than delay—business expansion.

5️⃣ Tax as a Product, Not a Project

Tax requirements shouldn’t be a one-off IT ticket every time a regulation changes. You need to build a reusable logic library. When your company decides to expand into its next market, you shouldn’t have to rebuild your tech stack from scratch. A modular, product-led architecture allows you to enter 100+ jurisdictions seamlessly because the foundational logic is already centralized and adaptable.

For modern enterprises, compliance is merely the baseline. Efficiency, real-time insight, defensible data trails, and enabling business outcomes are the true prizes.

Take a hard look at your current infrastructure: Is your tax logic a standalone “to-do” list, or is it baked directly into your core product roadmap?

Sources

For those looking to dive deeper into the architectural shifts and data driving this transformation, I highly recommend reviewing the foundational research:

• Thomson Reuters: 2026 Corporate Tax Department Technology Report (Primary data source on AI integration timelines and the 10,000-hour reclamation metric).

• EY (Ernst & Young): Global Tax e-Invoicing & Digital Reporting Solutions (Context on the shift toward near real-time, predictive tax authority interactions).

• Bloomberg Tax: Corporate Tax Department Benchmark Report (Data regarding the 92% reliance on legacy workpapers and spreadsheet vulnerabilities).

It looks like in a world governed by binary tax code and rigid regulatory frameworks, we are still burning through thousands of human hours on manual reconciliations.

The Structural Collapse of the Pyramid

For decades, Tax departments were built as pyramids: a massive base of junior staff handling the “routine banality” of data entry. That model is dead.

As PwC recently highlighted, we are shifting to a diamond-shaped talent structure. The base of manual preparation is shrinking. What is expanding is the center: a core of Financial AI Agent Orchestrators. In this new model, the "middle" expands with skilled professionals who don't prepare tax returns but orchestrate the AI agents that do.

The Shift: From “Worker” to “Orchestrator”

In a deterministic world, the “What” (the law) is fixed. The “How” (the implementation) is where the S&P 500s lose millions in efficiency. Here is how the high-growth tax team must evolve:

• From Data Entry to Logic Design: Instead of fixing errors in a spreadsheet, the Orchestrator designs the logic gates that prevent the error from ever hitting the ERP.

• From Reporting to “AI Ops”: We don’t need people to generate reports. We need professionals who can troubleshoot the automated engine, ensuring AI agents don’t hallucinate jurisdictional logic.

• From Analysts to “Product Managers for Tax”: The most valuable hires won’t be tax specialists; they will be “multidisciplinary units” who can translate a regulatory update into a technical roadmap.

The 2026 Mandate for Tax Leaders

If your team is still spending 80% of their time on work that a script could do in 4 seconds, you are building a massive “human-heavy debt”. The world is moving to Continuous Transaction Controls. You cannot “human” your way through a 5-second API validation window.

Better start planning your tech stack and team skills now. The alternative is a “Compliance Brain” that eventually chokes your “Business Heart.”

Sources:

• Thomson Reuters: 2026 Corporate Tax Technology Report

• Deloitte: Tax Insights and Perspectives

• PwC: Tax Technology Transformation

• EY: Tax Technology & Data Strategy

According to the Thomson Reuters Institute’s 2026 Corporate Tax Department Technology Report, 61% of tax departments surveyed are ignoring the only metric that actually matters to the C-suite: business outcomes. Instead, they are still measuring themselves by “Tax Internal” yardsticks. The survey shows they prioritize time savings (66%) and accuracy (55%):

To avoid basing my conclusions on a single report, I had a quick look at what the “Big Four” think about this. The consensus is that measuring “adoption” or “accuracy” alone is no longer sufficient; tax departments must now prove their impact on the enterprise P&L and growth speed.

Main Conclusions:

• PwC (AI-Driven Value): Predicts a shift from “ground-up” crowdsourced AI to “top-down” enterprise strategies. Metrics are moving toward “proof points” that link AI-driven tax workflows to market differentiation and P&L impact.

• KPMG (Value Driver Trees): Recommends identifying “functional levers” that impact the broader organization, such as optimizing indirect tax cash flow and minimizing irrecoverable taxes to boost working capital.

• EY (Controversy & Policy): Focuses on “Tax Risk & Controversy” as a business metric. They suggest that “Time to Resolution” and “Data Readiness for Pillar Two” are critical KPIs to prevent tax from becoming a bottleneck during global expansion.

• Deloitte (Resource Mix): Suggests that the “Optimal Resource Mix” (balancing AI, outsourcing, and in-house talent) should be measured by its ability to free up the tax team for “high-value, strategic activities” rather than just cost reduction.

Don’t get me wrong—accuracy is a baseline requirement. It’s the “Compliance Brain” doing its job. But if your tax tech stack only solves for accuracy, you aren’t a strategic partner; you’re an insurance policy.

To move from being a cost center to a value driver, we need the “Product Heart.”

The “Tech Stack Prison” of Internal Metrics

At the S&P 500 scale, “efficiency” is a generic goal. If you save 1,000 hours but your tax logic blocks a new market launch for three months, the net value to the business is negative.

When tax tech is built as a standalone “to-do” list rather than being baked into the product roadmap, it becomes a blocker. We focus on the data trail for the audit we might have in three years, while the business prioritises the checkout completion rate today.

The Pivot: Adopting “Business-First” OKRs

Without a doubt, Tax Departments must bridge the gap between “tax internal” metrics and “business outcomes.” But what can those be?

To align with the “Product Heart” philosophy, these OKRs are categorized by Compliance Hygiene (Efficiency) and Strategic Enablement (Business Outcomes).

Category 1: Business Enablement & Speed (The “Product Heart”)

• Objective: Accelerate global expansion and product agility through tax automation.

  • KR 1: Reduce “Tax-to-Market” Latency (the time to configure tax logic for a new jurisdiction) from X weeks to < 48 hours.

  • KR 2: Achieve a 0% Tax Latency impact on checkout completion rates by moving tax calculation logic to the “edge” or a real-time engine.

  • KR 3: Increase the “Tax Incentive Capture Rate” (e.g., R&D credits, OB3 Act benefits) by 15% through automated data extraction.

Category 2: Cash Flow & Financial Performance

• Objective: Maximize free cash flow and EBITDA through strategic tax optimization.

  • KR 4: Increase Free Cash Flow by $X million through real-time VAT/GST recovery automation.

  • KR 5: Maintain an Effective Tax Rate (ETR) variance of < 1% between forecast and actuals, enabling more predictable capital allocation.

  • KR 6: Reduce Irrecoverable Tax as a percentage of total spend by X% via improved vendor onboarding logic.

Category 3: Compliance Hygiene & AI Maturity (The “Compliance Brain”)

• Objective: Transition to an “agentic” tax operating model to eliminate manual loops.

  • KR 7: Automate 95% of standard tax reconciliations using AI agents, reducing manual FTE hours by X%.

  • KR 8: Achieve Audit-Ready Status within 24 hours for any jurisdiction via a centralized “Tax Data Lake.”

  • KR 9: Maintain a 0% Audit Penalty rate on all “real-time reporting” mandates (e.g., EU e-invoicing).

If you want a seat at the table where the CEO decides on the next $1B investment, your tax tech needs to speak the language of the business.

Sources:

• 2026 Corporate Tax Department Technology Report | Thomson Reuters

• Tax changes: A strategic look ahead to 2026 | Thomson Reuters Institute

• Tax KPIs & Benchmarks | KPI Depot

• PwC 2026 AI Business Predictions: Delivering Measurable Outcomes

• KPMG: Key Performance Indicators Driving Indirect Tax Value

• EY 2026 Global Tax Policy and Controversy Outlook

• Deloitte Tax Transformation Trends 2025: Rising to Meet the Moment

• PwC Value Creation: Linking Tax Operations to Enterprise Growth

In the world of S&P 500 scale and high-growth scale-ups, the line between “Tax Compliance” and “Revenue Operations” has officially vanished.

We’ve entered the era of Continuous Transaction Controls (CTC). In this world, tax determination isn’t a monthly reconciliation task; it is a live dependency baked into your checkout flow.

The Hidden Risk: Compliance as a Single Point of Failure

The stakes in 2026 are binary. If the API to a tax authority hangs for 5 seconds, your checkout hangs for 5 seconds. In the mobility world, 5 seconds is an eternity—it is the difference between a completed ride and a frustrated user switching to a competitor.

If your data is flawed or your integration is “brittle,” your transactions won’t just be misreported; they will fail to complete entirely. You haven’t just added a compliance step; you’ve added a single point of failure to your revenue stream.

Based on my experience at Uber, here is how you move to a resilient, product-led tax infrastructure:

1️⃣ Robust, Real-Time Calculation: Your tax engine must handle complex logic—location-based rules, exemptions, and thresholds—in milliseconds. If your calculation can’t keep pace with a high-concurrency order service, your architecture is already broken.

2️⃣ Asynchronous Orchestration: Does the transaction move forward while the tax validation runs in a prioritized queue? Or is the user staring at a loading spinner? Build your user flows with contingency in mind. At Uber, we prioritize the user experience while ensuring the tax logic catches up in parallel.

3️⃣ Continuous Data Quality (DQ) Checks: Don’t wait for an audit to find a schema drift. Schedule automated DQ checks to catch mapping errors before the data ever hits a tax authority. At Uber, data points are checked continuously against external databases to ensure success before the API call.

4️⃣ The “Offline Mode” Fallback: What happens when a government server goes dark? You need fallback logic that preserves data integrity without killing the UX. Invest in smart retry mechanisms. At Uber, we invest a lot in smart retry mechanisms. Nothing else will scale in this case.

5️⃣ Agentic Troubleshooting: Manual troubleshooting is the silent killer of the S&P 500. When a document fails, you need an AI Agent that can trace the error, suggest the fix, and re-trigger the submission. This is a deterministic task—perfect for AI agents, not for your high-priced tax team.

The Takeaway for Leaders: Your goal is to build tax technology that never blocks business operations. Is your tax logic a standalone project, or is it baked into your product roadmap?

Stop treating Tax as a project. Start treating it as a Product.

Sources:

• OECD Guidance: Digital Continuous Transactional Reporting (DCTR) for VAT

• Fonoa Blog: Real-Time Reporting and the Shift to CTC

• Deloitte Insights: Strategic Moves: Navigating the Age of Agentic AI

• Vertex Resources: Overcoming SAP S/4HANA & E-Invoicing Challenges

• VATupdate: Daily Global VAT & CTC News

If you are leading tax or accounting technology for an organization in the Xero ecosystem, the mandate has shifted from “How do we record this?” to “How do we verify what the AI just did?”

The Prize: Compressing the Financial Cycle

The immediate upside of integrating Claude’s reasoning via Just Ask Xero (JAX) is the elimination of the “Manual Reconciliation Loop.” By moving from a “System of Record” to a “System of Action,” we are seeing the realization of what Xero calls Accountable Intelligence:

• Near-Instant Monthly Close: AI categorizing transactions with high confidence, allowing teams to put small business finances directly inside Claude for rapid analysis.

• Generative Forecasting: Moving from static spreadsheets to asking: “If our VAT liability in the UK increases by 2%, how does our Q4 cash flow look?”

• Real-Time Insights: Moving beyond the dashboard into “Headless Finance,” where Claude is linked directly to the accounting platform to surface anomalies in real-time.

The Risks: Navigating the AI “Black Box”

While the efficiency gains are seductive, the stakes can also be quite high. Here are some serious risks to take into account:

1. The Hallucination Hazard

LLMs are built for conversation, not calculus. While Claude uses highly sophisticated models for reasoning, it may still struggle with complex, multi-jurisdictional tax logic. If the AI “hallucinates” a reconciliation that satisfies the software but fails an audit, the liability sits with the company, not the AI provider. An example of such a recent case is Moffatt v. Air Canada (2024). It is a significant legal precedent for AI and enterprise that happened recently. Air Canada’s chatbot “hallucinated” a bereavement fare policy that didn’t exist, promising a passenger a retroactive discount that contradicted the airline’s actual written policy.

• The Outcome: The court rejected Air Canada’s defense that the chatbot was a “separate legal entity” responsible for its own actions.

• The Lesson for Tax Tech Leads: In the eyes of the law, the tool is an extension of the company. If Claude suggests a VAT treatment in Xero that contradicts tax law, “the AI told me so” is not a defense. You are legally responsible for every action taken based on an AI suggestion.

2. The Data Privacy Moat

Xero has secured a “non-training” guarantee, meaning your company’s balance sheet won’t become part of Claude’s next public update. However, data leakage isn’t just about training; it’s about access. Tax leads must ensure that the “Just Ask Xero” (JAX) interface respects existing user permissions. There is a recent example connected to this. While not involving Xero, the 2023 Samsung case is the gold standard for data privacy risks. In that case, engineers inadvertently leaked proprietary source code and meeting notes by using ChatGPT to summarize them.

• The Material Risk: Once data is input into a public-facing LLM without enterprise-grade “Zero-Retention” or “No-Training” APIs, it becomes part of the model’s knowledge base.

• Xero Context: Even with Xero’s security guarantees, it is still worth making sure that if a junior accountant uses Claude to analyze a “sensitive payroll file” in Xero, the data stays within the secure Xero/Anthropic tunnel, and it is not cached in a way that violates internal GDPR or SOC2 protocols.

3. The Vanishing Audit Trail

In a traditional system, you can trace a journal entry to a user ID and a timestamp. In an AI-augmented system, if the AI “suggests” an entry and a human clicks “Approve” without checking the source, the audit trail becomes a game of telephone. The same can happen if the human in the loop misses some “ghost regulations” the model uses to suggest decisions. For example, in multiple jurisdictions, lawyers have been sanctioned for submitting briefs that cited completely fabricated legal cases (e.g., Mata v. Avianca). The AI created citations that looked perfectly formatted but were “ghost cases.”

• Financial Reality: This has already moved into the accounting world. Recent reports (The Logic, 2025) show that 44% of accountants now spend up to three hours a month correcting AI-generated mistakes from clients who relied on “authoritative-sounding” but incorrect tax advice.

• Material Example: An AI might suggest a “Small Business Credit” for your specific SIC code based on an outdated 2022 regulation that has since been repealed.

All in all, at least for now, I would keep in mind that

The Strategic Playbook

What I learned at Uber is that scaling isn’t just about calculating tax; it’s about the data trail and the cost of technology. To leverage this partnership without compromising your defensible tax position, I recommend applying the following restrictions to your data trail:

1. Institute Rigorous Verification Processes: Use the Accountable Intelligence framework to ensure every AI-generated entry links back to a specific, real, correctly interpreted data point. If the AI can’t “show its thinking,” don’t trust and use - verify first!

2. Audit Your Permission Logic: Ensure your internal data security protocols match the new “agentic” reality. You don’t want everyone to be able to pull executive salary information within Claude.

3. Human-in-the-Loop is Mandatory: Use AI to flag and simulate, but keep the action authorisation under human control.

When it comes to the cost of technology, before fully committing your workflows to the Xero x Anthropic integration, evaluate each use case (e.g., automated categorization, cash flow forecasting) against some metrics. Here are some that come to mind (note: of course, you must adapt these examples to your company’s context):

1. Velocity of Close: Metric: % reduction in “Hours to Close.”

   • The Goal: If JAX can handle the “manual effort” of low-risk reconciliations, your team should be shifting a % of their time from data entry to anomaly simulation and detection.

2. Error Rate & Correction Cost: Metric: Number of AI suggestions rejected vs. approved.

   • The Risk: High-volume hallucinations. If your team spends a substantial amount of time each week correcting Claude’s reasoning, the “efficiency” is a mirage. Refer to the CPA.com 2025 Report to benchmark your correction burden.

3. Regulatory Auditability: Metric: Availability of Verified Citations per AI-generated entry.

   • The Mandate: Tax requirements shouldn’t be a one-off ticket. Does the AI help you build a reusable logic library for 100+ jurisdictions, or are you rebuilding your stack every time you enter a new market?

4. API & Resource Arbitrage: Metric: Cost of Xero Developer Tiers vs. Headcount Savings.

   • The Calculation: Compare the cost of high-tier API access and “agentic” compute against the cost of manual reconciliations. If you update the VAT logic once via AI and save 4,000 manual fixes tomorrow, the ROI is defensible.

Sources:

Official Announcements & Product Overviews

• Xero Media Release: Xero and Anthropic Collaborate to Bring AI-Powered Financial Intelligence to Millions of Small Businesses

  • Key Insight: The primary announcement details the multi-year partnership and the bidirectional integration between Xero and Claude.ai.

• Xero Blog: Accountable Intelligence: The New Standard Shaping the Future of Finance

  • Key Insight: Details Xero’s “Accountable Intelligence” framework, emphasizing “verifiable AI” and human oversight.

• Xero Product Page: Just Ask Xero (JAX) - Your AI Business Companion

  • Key Insight: Technical breakdown of JAX features, including bank reconciliation automation and conversational insights.

Data Privacy & Security Frameworks

• Anthropic Privacy Center: How do you use personal data in model training?

  • Key Insight: Anthropic’s official stance on data usage for commercial API customers and their “non-training” policies.

• Xero Responsible Data Use: Responsible Data Use at Xero

  • Key Insight: Xero’s company-wide pledge to data security, SOC 2/ISO 27001 compliance, and “privacy by design.”

• Security Boulevard: OWASP Top 10 Risks for Agentic Applications

  • Key Insight: Critical security risks for “agentic” AI like JAX, including data leakage and unintended tool misuse.

Industry Analysis & External Perspectives

• The Next Web (TNW): Xero partners with Anthropic to put small business finances inside Claude

  • Key Insight: Deep dive into why the “headless” integration into Claude.ai is a strategic shift for SaaS platforms.

• ChannelLife Australia: Xero & Anthropic link Claude to the accounting platform

  • Key Insight: Analysis of the partnership’s impact on the Australian and global accounting landscape.

• FinTech Weekly: Reddit Sues Anthropic for Alleged Misuse of User Data

  • Key Insight: Context on external public concerns regarding Anthropic’s data sourcing practices.

Technical & Pricing Updates

• Xero Developer Portal: Xero Developer Pricing Tiers (March 2026 Update)

  • Key Insight: The new tiered pricing model for data egress and connections may signal future “add-on” structures for high-volume AI usage.

If you are still hiring exclusively from audit backgrounds for your tech roles, you are being outpaced by the very firms you likely hire for advice. The global hiring boards for the Big Four reveal that they have pivoted. They are no longer just accounting firms—they are software houses. They have already realized that compliance is the output of a high-performing engineering engine.

Here is what to do first. Continue reading.

The DIY Architecture Trap

Probably you or somebody you know in Tax/Accounting/Finance have been in this hell hole already: you have a mandate to modernize your global tax architecture. You secure the budget, you gather your brightest team members, and you set out to ensure a system that can handle continuous transaction controls and real-time reporting.

Twelve months later, complaints that you are blocking the business are piling up, and your team is trapped in an endless cycle of trial and error. What went wrong?

You tried to build a software product using only a “Compliance Brain.”

In the S&P 500 and hyper-growth scale-up world, building tax technology is no longer a finance project. It is a hardcore software engineering and product management discipline. If your team is composed entirely of former auditors, tax specialists (ex-Big Four), and CPAs, you are already behind.

When tax professionals are tasked with building or integrating technology, they naturally optimize for the only thing they have learned matters: rules and regulations.

They will map out the most incredibly detailed, compliant logic trees imaginable. But translating that logic into a high-concurrency architecture that handles millions of transactions in milliseconds? That is a different language entirely.

Without seasoned tech professionals at the helm, tax teams often face grave challenges. In my work with different tax teams, I have observed:

• The Single Point of Failure: Hardcoding tax logic rather than using microservices, for example.

• The Latency Killer: Designing synchronous API calls to external tax engines that block the user experience if the government server takes 5 seconds or 24 hours to respond.

• The Tech Stack Prison: Accumulating massive technical debt because “quick fixes” were implemented to hit a compliance deadline, making future expansion nearly impossible.

The Stakes: Why Trial and Error is Not an Option

In the era of continuous transaction controls (like ViDA or France 2026 E-Invoicing or Mexico 2026 Digital Reform), tax is no longer a post-transaction, end-of-month reconciliation exercise. It is a live dependency.

If you get the architecture wrong, the stakes aren’t just an audit finding three years down the line. The stakes are blocked payments or onboarding flows today. A 5-second delay in e-commerce or many other online businesses is an eternity. If your system hangs, you lose the revenue. You haven’t just added a compliance step; you’ve added a bottleneck to the core business.

You do not have the time to let a finance team “figure out” cloud infrastructure through trial and error.

The Playbook: Hire the “Product Heart”

To escape the DIY loop, you need to bring the “Product Heart” into the compliance function. Use this checklist for your next round of interviews to ensure you aren’t just hiring another “Compliance Brain”:

• The Product Test: Can the person explain a tax requirement as a “User Story”? (e.g., “As a marketplace seller, I need to see my tax breakdown in real-time so I can price my goods competitively.”)

• Architecture Fluency: Do they understand the difference between a synchronous and asynchronous API call? (If they don’t, they will break your checkout flow).

• Scalability Mindset: Ask: “How would this logic hold up if we processed 1 million transactions per hour?” A tax person will talk about the law; a tech person will talk about load balancing and latency.

• The Translation Layer: Can they sit between a Tax Director and a Lead Engineer and make both feel understood?

• Tool Proficiency: Move beyond Excel. Are they comfortable with SQL, Snowflake, Python, Claude Code or at least the logic behind CI/CD pipelines?

A beginner’s mindset supported by product experience is more valuable than blindly applying a tax playbook that worked in an analog world. Stop asking your tax experts to be software architects. Build a true cross-functional tech team.

Dark patterns came up as a hot…

Read more