The indirect tax lifecycle for omnichannel retailers

Consider what this looks like in practice for a retailer running BOPIS operations across physical and e-commerce channels during a peak trading period. A customer purchases a bundled product online. It is a tablet with a separately priced accessories kit. The tax engine applies a blended rate to the bundle rather than disaggregating the components and applying the correct rate to each.

The error is small. At the transaction level, it is invisible. But the invoice is generated from the incorrect tax calculation, and in a clearance-model jurisdiction, the invoice fails real-time validation before the transaction completes. The sale does not go through. During Black Friday trading, when the retailer is processing thousands of transactions per hour, that failure does not surface as a compliance alert. It surfaces as lost revenue.

The transaction is reprocessed manually. The invoice clears. But the corrected invoice data does not reconcile cleanly against the ERP record, which still carries the original bundled rate. The discrepancy is logged but not resolved before the return period closes. When the pre-filled VAT return arrives from the tax authority, it does not match internal records. A member of the compliance team spends two days tracing the discrepancy back through the invoice, the ERP entry, and the original transaction data. The team assembles evidence manually from three separate systems.

The original error was a single incorrect rate applied to a single transaction type. By the time it reaches the compliance team, it has touched four systems, generated a failed transaction during peak trading, created a reconciliation gap, and consumed two days of professional time that was not budgeted for exception handling. This is not an edge case. It is what fragmented architecture does at scale. The failure compounds because the systems were never designed to catch it early.

Where retail tax compliance actually breaks down

Each of these failure points is predictable and recurring. They do not get better as transaction volumes grow or as mandate coverage expands. They get worse. A fragmented architecture scales its own weaknesses. The conventional response is to add more resources, more manual review steps, and more reconciliation work at each handoff. That addresses the symptom rather than the structure. It also consumes the capacity that tax professionals need for the work their function was designed to do.

The connected indirect tax lifecycle: Five stages, one workflow

When the indirect tax lifecycle runs on a connected platform, the failure points that fragmented architectures create simply do not exist. Data flows consistently from determination through e-invoicing validation, reconciliation, and compliance filing. Each stage receives clean, structured input from the one before it. Errors are caught at the point of origin, not discovered at the point of filing.

The lifecycle has four sequential stages. Each depends on the accuracy of the one before it. Each is addressable with purpose-built technology. They each carry a different kind of risk when it operates in isolation.

At the determination stage, the question is whether tax is calculated correctly at the point of transaction. It must be correct before the invoice is issued and before the data enters any downstream system. Thomson Reuters ONESOURCE Determination applies the right rate and rule across more than 19,000 U.S. jurisdictions and 205+ countries and territories, covering the full complexity of retail taxability — SNAP eligibility, food and beverage distinctions, tax holidays, bag fees, delivery fees, and the promotional mechanics that rules-based systems cannot reliably handle at scale.

At the e-invoicing stage, the question is whether invoices meet the validation requirements of each jurisdiction before transmission. In real time, this must happen before the transaction completes in clearance-model markets. ONESOURCE Pagero connects to tax authorities and trading partners in more than 140 countries, handling format conversion, validation, and transmission so that invoice compliance is built into the transaction rather than bolted on afterward.

At the reconciliation stage, the question is whether the data flowing into the compliance filing stage is consistent across all its source systems. ONESOURCE Reconciliations compares e-invoice data, ERP data, and VAT return data at the line-item level, detects and classifies discrepancies before they reach filing, and validates pre-filled VAT returns from tax authorities against internal records. Reconciliation time that previously consumed days moves to minutes. The filing team receives clean, confirmed data rather than a set of questions. At the compliance filing stage, the question is whether returns can be prepared and delivered to the tax professional in a review-ready state. That must happen without manual intervention at each step of the cycle. ONESOURCE Sales and Use Tax AI powered by CoCounsel delivers touchless compliance across more than 19,000 U.S. jurisdictions, covering 1,200+ signature-ready returns and electronic filing in 33 states, with early customers reporting up to 65% reduction in routine reporting time.

ONESOURCE Indirect Compliance AI powered by CoCounsel extends the same model globally, automating VAT return preparation, SAF-T, and digital filings across 60+ countries. A connected lifecycle does not just reduce errors. It changes where they are caught. Determination errors surface before the invoice is issued. Reconciliation discrepancies surface before the return is filed. Audit exposure is addressed before an auditor asks the question.

What changes when the lifecycle is connected

The operational difference between a fragmented architecture and a connected one is not incremental. It is categorical. The failure modes that fragmentation creates are structural features of point-solution architectures. These include recurring reconciliation gaps, manual exception queues, pre-filled return mismatches, and audit trails that must be assembled after the fact. They do not get better through effort. They disappear when the architecture changes. A reported 58% of corporate tax departments describe themselves as under-resourced. This is up from 51% the prior year.

For U.S. retailers, that structural change means a compliance cycle that runs from data ingestion through to signature-ready returns without a manual queue at each stage. Exceptions are resolved by AI rather than parked for human intervention. Returns arrive at the tax professional's desk in a review-ready state. Every data import is reconciled, every exception is logged with its rationale, and every jurisdiction-specific requirement is applied. The professional reviews, approves, and files. The audit trail is built into the return, not reconstructed from separate systems when an auditor asks for it.

For retailers with international operations, it means that the compliance infrastructure handling U.S. complexity is the same infrastructure absorbing international mandate requirements as they go live. France's B2B e-invoicing mandate takes effect in September 2026. Germany follows in 2027. The EU's ViDA framework requires e-invoicing for cross-border B2B transactions by 2030. A connected platform that already handles determination, e-invoicing, reconciliation, and compliance filing does not need to be rebuilt for each new mandate. It is configured, not replaced.

For the tax team itself, the most significant change is where professional expertise is applied. When AI and automation handle the execution stages of the compliance lifecycle, tax professionals have the capacity for the work their function was designed to do — analyzing the tax implications of entering a new market, modeling the impact of promotional strategies, contributing to commercial decisions, and building the relationship with finance leadership that a team buried in reconciliation work rarely has time for.

The window to act is narrowing

Seventy-seven percent of tax professionals expect agentic AI to be central to their compliance workflow by 2030, according to the 2026 AI in Professional Services Report. The omnichannel retailers best positioned when that expectation becomes standard practice are not the ones rebuilding their infrastructure reactively as each new mandate arrives. They are the ones whose compliance lifecycle is already connected.

The ONESOURCE platform covers every stage of that lifecycle. It is built on the same data model, designed to work together, and governed by the Fiduciary-Grade AI™ standard that makes AI-produced compliance outputs auditable, traceable, and defensible.

Each product in the ONESOURCE indirect tax suite addresses a specific stage of the compliance lifecycle. Together, they eliminate the handoff failures that fragmented architectures compound over time and across jurisdictions. The result is a compliance model that is built for the complexity omnichannel retailers are managing now. It is also built for the mandate requirements arriving over the next four years.

Assess your indirect tax lifecycle. The handoff failures in this paper provide a practical lens for evaluating whether your current compliance architecture is generating compounding risk or absorbing it. To see what a connected indirect tax lifecycle looks like in practice across determination, e-invoicing, reconciliation, and compliance filing, speak with a Thomson Reuters ONESOURCE specialist.