A sales tax overpayment is exactly what it sounds like: your company paid more sales or use tax than it legally owed, either because a vendor charged tax it should not have or because your team self-assessed tax on an exempt purchase. It happens at nearly every large company, quietly. Most tax teams prepare rigorously for a state sales tax audit but rarely apply the same scrutiny in the other direction, toward the tax they overpaid.
That gap is expensive. Overpaid sales tax is recoverable, but only within each state’s statute of limitations, and most finance organizations have no process that would surface it. This article walks through the most common causes, how recovery works, and how to find out what you are owed.
One distinction before we start: this article is about overpaying tax, not overpaying suppliers. Duplicate invoices and vendor billing mistakes are an accounts payable problem, covered separately in our guide to overpayment recovery for supplier payments. Here, the invoice amount was right. The tax on it was not.
Missing or expired exemption certificates
Missing or expired exemption certificates are the most common cause of sales tax overpayment. When a vendor has no valid certificate on file, it must charge tax, even on purchases that clearly qualify for exemption. Your AP team pays the invoice as billed, and the overcharge becomes permanent unless someone claims it back.
Certificates lapse for ordinary reasons. Legal entity names change after a merger or restructuring. States that require periodic renewal quietly age certificates out. New vendors get onboarded without a certificate exchange step, and decentralized purchasing opens vendor accounts the tax department never sees. Keeping certificates current across hundreds of vendors and dozens of states is a discipline of its own, which is why we cover exemption certificate management as a separate topic.
Taxability errors on manufacturing and utility purchases
Manufacturers overpay sales tax when purchases eligible for state manufacturing exemptions get taxed anyway. Most states exempt machinery, equipment, repair parts, and consumables used directly in production, and many exempt the electricity and natural gas that power the process. These exemptions are incentives states created deliberately, but they must be claimed, not assumed.
Washington, for example, exempts machinery and equipment used directly in a manufacturing operation, subject to eligibility and use tests spelled out by the Washington Department of Revenue. Texas exempts natural gas and electricity used predominantly in manufacturing, but only after a predominant use study documents that more than half of the metered usage is production, per the Texas Comptroller’s manufacturing exemption rules. Direct use tests, percentage thresholds, and documentation requirements vary by state, so buyers default to paying tax on close calls, and incentives meant to keep manufacturing competitive go unclaimed.
Paying tax twice on the same purchase
Double payment happens when a vendor charges sales tax on an invoice and your company also accrues use tax on the same purchase. Each entry looks correct in isolation. The vendor collected as required, and the accrual followed policy. Without matching the two records against each other, the duplication is invisible.
This became far more common as states expanded economic nexus rules. Vendors that never charged tax in your state register and begin collecting, while your use tax accrual logic, set at the GL account or purchase order level years earlier, keeps firing on the same transactions. It is one of the most frequent findings when purchase data finally gets reviewed line by line.
Rate and jurisdiction errors
Rate and jurisdiction errors occur when tax is calculated at the wrong local rate or sourced to the wrong taxing jurisdiction. ZIP codes do not align with jurisdiction boundaries, sourcing rules differ from state to state, and local rates change constantly, so small setup errors repeat across thousands of transactions.
Common versions include vendors charging their own location’s rate on shipped goods, misapplied origin versus destination sourcing, special purpose district taxes added where they do not apply, and local tax charged above a state’s cap. Any single instance is small. Across a year of enterprise purchasing volume, the total is not.
Automation misconfiguration and stale tax decisions
Tax engines calculate exactly what they are configured to calculate. When product taxability codes, exemption flags, or jurisdiction mappings are wrong or out of date, the software applies the same wrong answer to every transaction it touches. Automation does not eliminate sales tax overpayments; it standardizes them.
The typical failure modes are mundane: new SKUs get mapped to a default taxable code because that is the safe setting. A statutory change makes a category exempt, and the mapping never gets updated. A conservative “when in doubt, tax it” configuration made sense at go-live and was never revisited. Tax software is built to keep you compliant on filings, not to flag tax you paid but did not owe, which is why we examine what sales tax automation misses in its own article.
How sales tax overpayment recovery works
Recovering overpaid sales tax takes one of two paths: requesting a refund from the vendor that collected the tax, or filing a refund claim directly with the state. The right path depends on each state’s rules and on whether the tax was vendor-collected or self-assessed, and both paths run against a statute of limitations.
For vendor-collected tax, many states expect you to go back to the vendor, which refunds you and takes a credit on its own return; others allow direct claims, sometimes with an assignment of the refund right. Self-assessed use tax is generally recovered directly from the state. Either way, the process is documentation heavy. Texas, for instance, requires a completed claim form with supporting records such as invoices and proof of payment, allows four years from the date the tax was due, and only a complete claim stops the limitations clock, according to the Texas Comptroller’s refund requirements.
The statute is what makes timing matter. In one Revenew engagement, a leading global food manufacturing company expected a modest recovery, and the first state examined showed a high incidence of overpaid sales tax. The engagement ultimately identified nearly $34 million in refunds across eight states, and the first state’s claim was approved in full. Because filing periods were aging out of statute continuously, every month of delay cost at least $1 million in recoverable tax. That was one engagement’s outcome, not a projection for yours, but the statute math applies to everyone: unclaimed refunds expire.
How to find out what you are owed
A reverse sales tax audit is how companies quantify their overpaid sales tax. A specialist reviews purchase data, invoices, exemption certificates, and taxability decisions across every year still open under statute, identifies the overpayments, and files the refund claims. Most engagements are structured as no-risk reviews with zero upfront cost.
If the term is new to you, start with our explainer on what a reverse sales tax audit is. It complements what you already have: your team and your software are built to file accurately and on time, and a reverse audit checks the other side of that validation problem, whether the amounts paid were right to begin with. Independent sales and use tax recovery services exist because a second set of eyes, working from the refund side, finds what compliance-focused processes are not designed to look for.
About the author: Jake Deaton, Senior Consultant, Sales Tax Recovery at Revenew International. Jake has spent his career in sales and use tax consulting, with deep experience serving manufacturing, insurance, financial services, technology, and retail clients.
If any of these causes sound familiar, the next step is to find out what the numbers say. Request a No-Risk Review and Revenew’s sales tax recovery team will assess your refund potential with zero upfront cost.