ONESOURCE exemption automation does not establish certificate validity

Separate certificate capture from certificate validity

Thomson Reuters' official record says ONESOURCE Determination can track and apply exemption certificates. The direct answer is that this capability can make an approved certificate available to a calculation, but the resulting exempt treatment remains only as reliable as the evidence and policy behind it. A document in the repository may be expired, unsigned, issued to a different legal entity, limited to a product class, invalid in the destination jurisdiction, or unrelated to the transaction being billed.

Tax owners should define a certificate acceptance record before automation. That record should preserve seller and purchaser legal identities, registration or certificate number, issuing jurisdiction, exemption reason, covered products or services, issue and expiration dates, signature or attestation where required, source document, reviewer, review date, and the policy that connects the evidence to transaction treatment. Missing or contradictory fields should create a visible exception instead of being converted into a default exempt code.

Make application rules effective-dated and transaction-specific

One customer can hold several certificates with different geographic, entity, product, or use restrictions. A valid certificate for resale in one state may say nothing about a different state, a direct-use purchase, a bundled service, or a transaction after an organizational change. The calculation therefore needs more than a customer-level exempt flag. It needs a reproducible match among the certificate, the buyer, the seller, the ship-to or use location, the item classification, the transaction date, and any quantity or purpose limitation.

A governed rule should state which evidence fields must match, which date controls, how renewals and revocations take effect, whether grace periods are permitted, who can override a mismatch, and what happens to transactions during review. Test cases should cover multiple ship-to locations, merged customers, changed registrations, partial exemptions, mixed invoices, backdated certificates, expired evidence, credits, rebills, and reopened periods. Qualified tax and legal owners set the rule; the platform should retain the version it applied.

Reconcile exempt treatment through filing and audit records

Certificate governance does not end when an invoice calculates zero tax. The retained chain should connect the source document, extracted fields, review decision, effective-dated policy, customer and product mappings, calculation request, invoice line, exemption amount, return treatment, ledger entry, renewal event, and any later adjustment. A reviewer should be able to identify which certificate supported each exempt line without reconstructing the answer from a customer master flag.

Operations should reconcile exempt sales by entity, jurisdiction, certificate status, reason code, product class, and filing period. Useful controls include aging reports, upcoming-expiration queues, unmatched certificate alerts, duplicate-document review, override reporting, evidence sampling, and post-revocation correction. Reconciliation should preserve disagreements rather than overwriting history: the original treatment, changed evidence, approver, correction date, amended return, customer communication, and financial impact all remain distinct records.

Keep ONESOURCE claims inside the official record

The registered Thomson Reuters page establishes current provider positioning for an integrated indirect-tax platform and specifically describes certificate tracking and application within determination. It also describes e-invoicing, reconciliation, reporting, and filing capabilities. It does not establish that a particular certificate is valid, that configuration reflects every jurisdiction's requirements, that a calculated exemption will be accepted by an authority, or that a customer's document-retention process is sufficient.

Indirect Tax Monitor reviewed the registered source on August 18, 2026 and did not operate a customer deployment. Buyers should verify current certificate workflows, supported document types, extraction behavior, validation fields, jurisdiction and product mappings, effective-date logic, overrides, renewal controls, transaction traceability, filing connections, audit exports, corrections, and service dependencies with representative evidence and qualified tax and legal review.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Indirect Tax Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.