Sales tax should be simple. You collect it from customers, hold it in a liability account, and remit it to the state. For restaurants, it’s never that simple.
Between varying tax rates on food vs. alcohol, delivery platform remittances, catering exemptions, and the gap between what your POS collects and what QuickBooks reports, most restaurants have a sales tax problem they don’t know about — until they get an audit notice.
Why Restaurant Sales Tax Is Harder Than Other Businesses
A retail store charges one tax rate on everything. A restaurant deals with multiple rates on different items, often within the same transaction. A guest orders a burger (taxed at the food rate), a beer (taxed at the alcohol rate, sometimes higher), and takes a dessert to go (potentially tax-exempt in some states). The POS handles this at the register, but the accounting often doesn’t keep up.
Add delivery platforms into the mix — where DoorDash, Uber Eats, or Grubhub may collect and remit sales tax on your behalf for marketplace orders — and you’ve got a reconciliation challenge that most restaurant accounting setups aren’t built to handle.
The 5 Sales Tax Mistakes Restaurants Make in QuickBooks
1. Using a Single Sales Tax Rate for Everything
QuickBooks lets you set up one default sales tax rate and apply it globally. Many restaurants do exactly that — set it to the combined state + local rate and move on.
The problem: food and alcohol often have different tax rates. Some jurisdictions charge an additional alcohol excise tax. Some states exempt prepared food for takeout. If you’re applying one rate across all revenue, you’re either over-collecting (creating a refund liability) or under-collecting (creating a surprise bill when you file).
Fix: Set up separate tax rates in QuickBooks for each category your jurisdiction requires. At minimum, most restaurants need a food tax rate, an alcohol/beverage tax rate, and a to-go/takeout rate (if your state treats it differently). Map each POS category to the correct tax rate.
2. Not Reconciling POS Tax Collected vs. QuickBooks Tax Liability
Your POS (Toast, Square, Clover, Revel) tracks exactly how much sales tax it collected on every transaction. QuickBooks tracks how much sales tax liability you owe based on recorded sales. These two numbers should match. They almost never do.
Common causes of the gap: manual entry errors when posting daily sales, rounding differences between POS calculations and QuickBooks calculations, timing differences between when a sale is recorded and when the payment posts, and voided transactions in the POS that don’t get reflected in QuickBooks.
Fix: Every month, pull the Sales Tax Collected report from your POS and compare it to the Sales Tax Liability report in QuickBooks. The variance should be under $50. If it’s more, dig into the daily totals to find where the discrepancy started. This is a 20-minute monthly check that prevents quarterly surprises.
3. Ignoring Delivery Platform Tax Remittance
This is the one that catches the most restaurants off guard. In most states, marketplace facilitator laws require DoorDash, Uber Eats, and Grubhub to collect and remit sales tax directly to the state on orders placed through their platforms.
That means the tax on those orders is not your liability to pay — the platform already paid it. But if your QuickBooks records the full order total (including tax) as revenue and then calculates sales tax liability on top of that, you’re double-counting. You’ll file a return showing you owe tax that was already paid by the platform.
Fix: Record delivery platform revenue net of sales tax in QuickBooks. The tax collected by the platform should never hit your Sales Tax Liability account. Create a process to reconcile the platform’s payout statements against what’s recorded in QuickBooks. The platform’s statement shows gross sales, commission, tax collected and remitted, and net payout — use the net payout figure as your revenue entry, or break it out with a separate contra-revenue line for commissions.
4. Filing Based on QuickBooks Numbers Without Verification
QuickBooks has a built-in sales tax report that many restaurants use to file their quarterly or monthly returns. The problem is that this report is only as good as the data behind it. If your revenue categories aren’t mapped correctly, if delivery platform tax is double-counted, or if your tax rates don’t match your jurisdiction’s current rates, the report will be wrong.
Filing based on incorrect numbers leads to one of two outcomes: you overpay (and leave money on the table until you file an amended return) or you underpay (and owe penalties and interest when the state catches it).
Fix: Before filing, cross-check three numbers: total taxable sales in QuickBooks vs. total taxable sales reported by your POS, tax rate applied vs. current published rate for your jurisdiction, and delivery platform tax already remitted (subtract this from your liability). Only file after all three check out.
5. Not Tracking Tax Exemptions Properly
Restaurants that do catering often serve tax-exempt organizations — nonprofits, government agencies, schools. When a catering order is tax-exempt, the POS needs to be configured not to charge tax, and QuickBooks needs to reflect that the sale was non-taxable.
What usually happens: the team knows the order is exempt but forgets to toggle it in the POS, tax gets charged anyway, and then it either gets refunded (creating more accounting work) or it doesn’t (and the customer disputes it). In QuickBooks, the sale shows up as taxable whether or not tax was actually collected, throwing off the liability report.
Fix: Keep a master list of tax-exempt customers in QuickBooks. When a catering order comes in from an exempt org, flag it as non-taxable at the POS level and verify the customer record in QuickBooks has the correct tax-exempt status and certificate on file. This protects you in an audit — the state will want to see the exemption certificate for every non-taxable sale.
What Your QuickBooks Sales Tax Setup Should Look Like
A properly configured restaurant sales tax setup in QuickBooks includes:
Liability accounts:
2200 – Sales Tax Payable – Food
2210 – Sales Tax Payable – Alcohol
2220 – Sales Tax Payable – Other
Tax rates configured for:
State food tax rate
State + local alcohol rate (if different)
Takeout/delivery rate (if your state treats it differently)
Zero-rate for exempt sales
Monthly reconciliation process:
POS tax collected = QuickBooks tax liability (within $50 tolerance)
Delivery platform tax remitted = excluded from your liability
Exemption certificates on file for all non-taxable catering sales
The Quarterly Check That Prevents Audit Problems
Before you file each quarter (or monthly, depending on your jurisdiction), run through this checklist:
Total taxable sales: Does QuickBooks match your POS within 1%? If not, find the variance before filing.
Tax rates: Are the rates in QuickBooks current? States and localities change rates more often than you’d expect — usually January 1 and July 1.
Platform remittance: Have you subtracted the tax that DoorDash/Uber Eats/Grubhub already remitted on your behalf?
Exemptions: Do you have certificates on file for every non-taxable sale? If audited, “we know they’re exempt” isn’t enough — you need the paperwork.
Filing method: Are you filing on the correct basis — cash or accrual — consistent with how your QuickBooks is set up?
This quarterly check takes about an hour. Skipping it can cost thousands in penalties, interest, or overpayments you never recoup.
FinAcct360 handles restaurant sales tax reconciliation as part of our weekly accounting service. We match your POS tax collected to your QuickBooks liability every week — not once a quarter when it’s too late to fix problems cleanly.
If your sales tax numbers don’t reconcile or you’re not sure whether delivery platform tax is being handled correctly, book a discovery call and we’ll walk through your setup.
FinAcct360 works with restaurants on QuickBooks using Toast, Square, Clover, Revel, Aloha, and any POS platform.