Picture this: your business had a great month. The bank account is fatter than it has been all year, and you are tempted to look at that balance as money you earned. But if you collect sales tax from customers, a chunk of that cash was never yours. It belongs to your state, and you are simply holding it until you hand it over.
This single misunderstanding—treating collected sales tax as revenue instead of a liability—is one of the most common bookkeeping mistakes small business owners make. It inflates your reported income, distorts your profit margins, and can leave you scrambling for cash when the remittance deadline arrives. Worse, it is exactly the kind of sloppy record-keeping that turns a routine state audit into an expensive one.
Here is how to record sales tax correctly, why it never touches your income statement, and how to reconcile the liability so it zeroes out cleanly every filing period.
You Are a Tax Collector, Not a Taxpayer
When you sell a taxable product or service, the sales tax is not a cost to your business. It is a cost to your customer. You are merely the middleman the state has deputized to collect it.
Think of it like a tip jar that belongs to someone else. A customer hands you $107 for a $100 item in a 7% tax state. You earned $100. The other $7 is money you are holding in trust for the state. It passes through your bank account, but it is never income, and remitting it later is never an expense.
This is why sales tax payable belongs on your balance sheet as a current liability—not on your income statement as revenue or as a deduction. The moment you collect it, you owe it. The accounting has to reflect that obligation from the very first transaction.
If you lump that $7 into your sales figure, three things go wrong at once:
- Your revenue is overstated, which makes your business look more profitable than it is.
- Your gross margin and profitability ratios are distorted, so any decision based on them—pricing, hiring, borrowing—rests on bad numbers.
- Your income tax could be overstated, because you may end up paying income tax on money that was never yours to keep.
The Journal Entry: Splitting the Sale From the Tax
Recording sales tax correctly comes down to one habit: every taxable sale gets split into two credits, not one.
Suppose you make a $1,000 sale at a 7% sales tax rate, and the customer pays in cash. The entry looks like this:
Debit Cash $1,070
Credit Sales Revenue $1,000
Credit Sales Tax Payable $70The debit and credits balance at $1,070, but notice what each line does. Cash reflects the full amount that hit your bank account. Sales Revenue captures only what you actually earned. Sales Tax Payable records the obligation you now owe the state.
If the sale is on credit instead of cash, the only thing that changes is the debit:
Debit Accounts Receivable $1,070
Credit Sales Revenue $1,000
Credit Sales Tax Payable $70The principle is identical. The customer owes you the whole $1,070, you earned $1,000, and $70 is destined for the state regardless of the payment method.
When You Remit the Tax
When the filing deadline arrives and you send the money to the state, you are simply discharging the liability you have been accumulating. The entry reverses the payable:
Debit Sales Tax Payable $70
Credit Cash $70Notice that this entry never touches Sales Revenue or any expense account. It moves cash off your books and erases the liability—nothing more. If your Sales Tax Payable account is doing its job, it should drop to zero (or close to it) right after you remit.
Use One Liability Account Per Jurisdiction
If you only ever collect tax for a single state with a single rate, one Sales Tax Payable account is enough. But the moment you sell into multiple states—or multiple local jurisdictions with different rates—a single bucket becomes a reconciliation nightmare.
The cleaner approach is to maintain a separate liability sub-account for each state where you have a filing obligation: Sales Tax Payable – California, Sales Tax Payable – Texas, and so on. This does two things. First, it makes filing each state's return a matter of reading one account balance instead of disentangling a blended total. Second, if an auditor ever asks how you arrived at a number, you can point to a clean, jurisdiction-specific trail rather than reverse-engineering it.
This is the kind of structure plain-text accounting handles gracefully. Because tools like Beancount.io let you define an account hierarchy that is just text, you can create Liabilities:SalesTax:CA and Liabilities:SalesTax:TX in seconds, and every transaction posts to the right place automatically. See the documentation for how account trees work.
Do You Even Owe Tax in That State? The Nexus Question
Before you can record sales tax for a state, you have to know whether you are required to collect it there at all. That requirement is called nexus—a connection significant enough that the state can compel you to collect.
There are two main flavors:
- Physical nexus: an office, a warehouse, inventory stored in a fulfillment center, or employees in the state.
- Economic nexus: enough sales into the state to cross a dollar or transaction threshold, even with no physical presence. Most states set this around $100,000 in sales or 200 transactions per year, though the exact numbers vary and several states have been adjusting them.
The single most expensive nexus mistake is assuming you do not have it in a state where you actually do. An e-commerce seller can quietly cross an economic nexus threshold in three new states in a busy quarter and not realize it until a state sends a notice—at which point the back taxes, penalties, and interest are all retroactive.
Review your sales by state at least quarterly. The point of the review is not the accounting entry; it is catching a new filing obligation before the state catches it for you.
Reconciling Sales Tax Payable at Filing Time
Reconciliation is where good bookkeeping pays off. The goal is simple: the sales tax you collected in your books should match the sales tax you report and remit on the state return. When those two numbers diverge, you have either underpaid (a future assessment waiting to happen) or overpaid (your own money handed to the state for no reason).
Here is a practical reconciliation routine for each filing period:
- Pull the period's Sales Tax Payable activity. Start with the opening balance, add everything collected during the period, and you have what you should owe before remittance.
- Separate taxable from non-taxable sales. Exempt sales, resale transactions, and shipping to states where you have no nexus should not be generating a tax liability. Confirm they were excluded correctly.
- Break the total down by jurisdiction. Each state return needs its own figure. If you used per-state accounts, this step is already done.
- Compare your books to your point-of-sale or e-commerce platform. This is the step most businesses skip—and the one auditors love. If your sales platform calculated $4,200 of tax but your books show $4,050, something is mis-mapped. Find the gap before you file, not during an audit.
- File, remit, and clear the account. Once paid, your Sales Tax Payable balance for that jurisdiction and period should return to zero.
Run a lighter version of steps 3 and 4 weekly rather than waiting for the filing deadline. A small integration error caught after seven days is a five-minute fix. The same error caught after ninety days is a reconciliation project.
Common Mistakes That Trigger Trouble
A handful of recurring errors account for most sales tax pain. Watch for these:
Recording tax as revenue. The headline mistake. It inflates income and can cause you to overpay income tax on money you never earned.
Treating remittance as an expense. Paying the state is not a business expense—it is settling a liability. Booking it as an expense double-counts and understates your profit.
Missing or expired exemption certificates. If you make a tax-free sale to a reseller or exempt buyer, you need a valid exemption certificate on file. No certificate means the auditor assumes the sale was taxable and assesses you for tax you never collected. Certificates also expire—keep them current.
Ignoring use tax. Sales tax's quieter sibling. If you buy supplies or equipment from an out-of-state vendor who did not charge you sales tax, you generally owe use tax on it directly to your state. Many small businesses never record use tax at all, and it is a frequent audit finding.
Letting the liability balance drift. If Sales Tax Payable never returns to (or near) zero after you remit, something is wrong—an entry was missed, a rate was off, or a remittance was misposted. A liability that only grows is a red flag you should investigate immediately.
Overlooking a filing-frequency change. States move businesses between monthly, quarterly, and annual filing as sales volume changes. Miss the notice and you miss a deadline.
A Quiet Bonus: Vendor Discounts for Filing on Time
One upside worth knowing: a number of states let you keep a small slice of the tax you collect as compensation for collecting it—if you file and pay on time. Florida, Missouri, and New York, among others, still offer some form of this "vendor discount" or timely-filing allowance.
The amounts are modest and capped, and the trend is mixed—some states have trimmed or suspended their discounts recently, so do not build a budget around them. But when you do earn one, record it properly: the retained amount is other income to your business, because it is genuinely yours to keep. It is the rare case where part of a sales tax transaction legitimately does become revenue.
Keep Your Finances Organized From Day One
Sales tax done right is mostly discipline: split every taxable sale into earned revenue and held-in-trust liability, keep a clean account per jurisdiction, and reconcile before you file rather than during an audit. The mechanics are not hard—the danger is letting them slide until the numbers no longer agree.
Maintaining clear, auditable financial records is exactly where a transparent system earns its keep. Beancount.io provides plain-text accounting that gives you complete visibility and control over every liability account—no black boxes, no vendor lock-in, and a full version-controlled history an auditor can follow line by line. Get started for free and see why developers and finance professionals are switching to plain-text accounting.