New CereTax SmartResearch. AI tax research. Cited answers. SmartResearch. Cited answers. SmartResearch. Learn more
Your accounts payable team approves thousands of dollars in purchases every month. Equipment arrives from an out-of-state supplier. An employee renews a software subscription using a corporate card. Procurement negotiates a new vendor contract. AP processes the invoices, matches them to purchase orders, and closes the books.
Everything looks routine. But one question may have gone unanswered: Was the correct sales tax paid on every taxable purchase?
That question matters because when a seller does not collect the required sales tax, the responsibility may shift to the buyer. The resulting use tax liability can sit unnoticed in purchase records until an audit brings it to light.
For businesses operating across multiple states, the problem becomes harder. Different jurisdictions apply different taxability rules, rates, sourcing requirements, and exemptions. A vendor's failure to charge tax does not automatically make a purchase exempt, and an invoice showing zero tax is not proof that no tax is due.
Use tax is therefore not just a tax team's problem. It is an accounts payable, procurement, finance, and systems problem. And the data needed to catch it is often already sitting inside your AP workflow.
Use tax is generally the counterpart to sales tax. It applies when a business purchases taxable property for use, storage, or consumption in a state, but the seller does not collect the required sales tax.
For example, imagine your company buys $20,000 worth of taxable equipment from an out-of-state vendor. The equipment is delivered to your facility, but the vendor does not charge sales tax. If the purchase is taxable in the state where the equipment is used and no exemption applies, your business may owe use tax directly to that state.
The Indiana Department of Revenue explains that use tax is due on property acquired for use, storage, or consumption in Indiana when Indiana sales tax has not been paid to the seller. It also identifies purchases from vendors not registered to collect Indiana tax as a common source of liability.
The principle is straightforward: if a taxable purchase escapes sales tax at checkout, it may still create a tax obligation for the purchaser.
The challenge is identifying those purchases before they become an audit finding.
Use tax problems rarely arrive as a clearly labeled exception. They are buried in ordinary purchasing activity, spread across systems and departments that may not be designed to evaluate tax liability.
A vendor may not be registered to collect tax in the state where your business uses the purchased item. Or the vendor may simply fail to apply the correct tax.
Neither situation automatically removes your obligation.
California's Department of Tax and Fee Administration (CDTFA), for example, instructs businesses to examine invoices from out-of-state retailers and verify whether California use tax was collected. Its Publication 123 also recommends reviewing general ledger asset accounts and federal income tax depreciation schedules to identify purchases that may be subject to use tax.
That is an important point for finance teams: reviewing only the invoices that already contain a tax line can leave a significant blind spot. The purchases with no tax charged may deserve just as much attention.
Corporate purchasing cards make it easy for employees to buy supplies, equipment, subscriptions, and other business necessities. They also create a potential gap in sales and use tax controls.
A purchase made through a P-card may never follow the same purchase-order and invoice approval process as a conventional vendor transaction. A receipt may be uploaded late, contain limited product details, or simply show that no tax was charged.
The payment method does not determine whether a purchase is taxable. The underlying transaction does. But when P-card activity is not reviewed alongside other purchasing data, the business can miss taxable purchases that should have been evaluated for use tax.
A useful control is to bring card transactions into the same tax review process as AP invoices, rather than treating them as a separate expense category.
Software subscriptions deserve particular attention because businesses frequently purchase them through centralized procurement, individual department budgets, or corporate cards.
But do not assume that every software subscription is taxable, or that none of them are. State rules can differ significantly depending on whether the transaction involves downloaded software, remotely accessed software, data processing, hosted services, or a combination of products and services.
Consider the contrast between two state approaches. California generally does not tax electronically transferred software when no tangible storage media is provided under its established rules. Texas, meanwhile, treats certain data processing services as taxable and identifies software-as-a-service providers as data processing service providers.
That difference makes a generic AP classification such as "software expense" insufficient for determining taxability.
Your team needs to understand what the vendor is actually providing, how the service is delivered, where it is used, and how the relevant state treats that transaction.
Even when a vendor charges sales tax, the transaction may not be fully correct.
The vendor could apply the wrong rate, use an incorrect jurisdiction, or tax only part of a purchase that should be treated differently. A business may also pay tax to another state at a lower rate than the rate applicable where the property is used.
Indiana's guidance illustrates this last point: when the sales tax paid to another state is below Indiana's 7% rate, the purchaser may owe the difference in use tax, subject to applicable rules and exemptions.
In other words, checking whether an invoice contains a tax amount is not enough. Your business needs to determine whether the amount charged satisfies the obligation.
Consider a hypothetical business purchasing $50,000 in taxable equipment for use in a jurisdiction with an applicable 8% rate. If the vendor collects no tax and no exemption applies, the potential use tax liability is $4,000.
That is from one purchase. Now consider multiple locations, recurring purchases, decentralized card spending, and several reporting periods.
The exposure can accumulate quietly, particularly when the business has no process for identifying untaxed purchases or reconciling them to its sales and use tax returns.
The risk is not limited to the tax itself. Unreported liabilities can lead to interest, penalties, audit adjustments, and time-consuming reviews of historical purchasing records. Indiana, for example, states that businesses that self-report use tax owe the tax, while waiting for the department to assess it can also result in a 10% penalty plus interest.
The answer is not to ask AP to become a tax department. It is to give AP, procurement, finance, and tax teams a shared process for identifying transactions that need tax review.
Start by bringing together the records that reveal what the business purchased, where it was used, what the vendor charged, and how the transaction was recorded.
The review should also account for timing. In California, businesses holding a seller's permit generally report use tax due on business purchases through their sales and use tax return for the period in which the item is first used, stored, or consumed in the state. Other states have their own reporting requirements.
A repeatable review process is far more effective than trying to reconstruct purchasing activity when an auditor requests supporting records.
AP systems are designed to manage purchasing and payments. They are not necessarily equipped to make every jurisdiction-specific tax determination a business needs.
That is where the connection between purchasing data, ERP systems, and tax technology becomes important.
A reliable sales tax process should help your business evaluate transaction details, apply the appropriate tax rules, identify missing or inconsistent information, and make the resulting liability visible to the teams responsible for reporting.
This matters even more as purchasing becomes decentralized. More vendors, more software subscriptions, more locations, and more employee card transactions mean more opportunities for tax decisions to fall between departments.
The goal is not simply to find invoices with zero tax. It is to build a process that can distinguish a genuinely exempt purchase from a taxable purchase where the vendor failed to collect the required tax.
Use tax should not be an afterthought in your monthly close. It should be part of the broader sales and use tax control environment, supported by accurate purchasing data, clear ownership, and consistent review.
Your AP records already contain many of the clues needed to identify use tax exposure. The challenge is connecting those records to the right tax rules and making sure potential liabilities do not disappear between procurement, purchasing, finance, and tax.
CereTax helps businesses manage complex sales tax requirements with configurable tax logic, jurisdiction-level precision, and integrations designed to support high-volume transaction environments. When tax determination is connected to the systems running your business, teams have a stronger foundation for consistent tax decisions and better visibility into compliance risk.
Don't wait for an audit to discover what your AP data could have told you months ago. Explore CereTax Sales Tax Solutions or talk to a CereTax expert about building a more reliable sales and use tax process.
Complex tax. Calculated correctly.