Bookkeeping for restaurants in QuickBooks
How does restaurant bookkeeping in QuickBooks work with POS and delivery apps?
Restaurant books break down when POS deposits get recorded as one lump sum instead of split into sales, tax, tips, and fees, and when delivery payouts land net of commission with no record of the original ticket. A clean setup posts 4 separate feeds, being POS, delivery apps, payroll and the operating account, into distinct accounts every day.
Common for restaurants
- POS deposits hit the bank as one number and nobody can tell how much was tips versus sales
- Sales tax liability in QuickBooks doesn't match what the state return says is owed
- Third-party delivery payouts show up net of fees with no record of the gross ticket total
- Food cost percentage can't be calculated because purchases aren't mapped to Cost of Goods Sold
- Tip payouts to staff aren't separated from wages, so payroll reports come out wrong
In detail
Why restaurant books are harder than most small businesses
A retail business or a consultant usually has one or two money-in feeds. A restaurant has at least four running at once, each on a different schedule and each netting out different things before the money ever reaches the operating account: the point-of-sale system (Toast, Square, Clover), one or more third-party delivery apps (DoorDash, Uber Eats, Grubhub), payroll for an hourly staff with tip income, and the vendor side: food, beverage and paper purchases that need to map to Cost of Goods Sold instead of a generic expense account if the food cost percentage is going to mean anything.
Every one of those feeds nets something out before it lands in the bank. A POS batch deposit is sales minus the processor’s fee. A delivery app payout is the ticket total minus a commission that can run 15–30%, minus a marketing fee, sometimes minus a chargeback from a prior period, all bundled into one number with no breakdown unless someone pulls the app’s own settlement report. Recording any of these payouts as a single deposit to Sales is the single most common mistake in restaurant books, and it is invisible until someone tries to reconcile sales tax or calculate a real margin.
Splitting the POS deposit correctly
A POS batch deposit needs to be entered as a Bank Deposit with multiple lines, not one line categorized to Sales. At minimum: gross sales (income), sales tax collected (a liability rather than income, and the account that has to tie to the state return), credit card processing fees (an expense), and tips collected through the card (a liability owed to staff, not revenue). A restaurant running one line for the whole batch deposit is, by definition, overstating revenue by the tax and tip amounts and understating expenses by the processing fee, every single day that pattern repeats.
Reconciling delivery app payouts to the actual ticket total
Each delivery app issues its own settlement report showing gross sales, commission, marketing spend, and any adjustments, batched into the lump sum that actually deposits. Without pulling that report and entering the components separately, QuickBooks Online only sees the net payout, so commission and marketing spend for that channel disappear from the books entirely, which understates true sales and true marketing expense by the same amount and makes it impossible to tell whether a delivery channel is actually profitable once its real commission rate is accounted for.
Tip liability is a payroll problem hiding in the bank feed
Tips collected through the POS on a card are the restaurant’s money for exactly as long as it takes to pay them out to staff. They are a liability from the moment they’re collected, not income, and they should never touch a Sales account. When tip payouts run through payroll, the liability created by the POS deposit and the payout recorded in payroll both need to tie to the same number for the same pay period. When they run through cash or a separate tip pool distribution, that liability account still needs to zero out on a predictable schedule. If it doesn’t, either tips are being underpaid or a chunk of them are sitting unrecorded as an overstated liability that never clears.
Food cost only means something if purchases are mapped correctly
Food cost percentage, the number that tells an owner whether a menu is priced correctly, only works if vendor purchases post to Cost of Goods Sold, split at minimum between food and beverage, instead of a single generic “Supplies” or “Cost of Goods” line. A produce delivery, a beverage distributor invoice, and a paper goods order are three different cost categories with three different margins riding on them; lumped together, the food cost percentage on the profit and loss statement is not wrong exactly, but it’s not useful for pricing a menu either.
Prime cost is the number that actually runs the business
Food cost alone tells an owner about the menu. Prime cost, meaning food and beverage cost plus total labor cost including tips paid through payroll, is the number that tells an owner whether the restaurant itself is viable, and it depends on both halves being accurate at the same time. A restaurant with clean food cost tracking but labor lumped into one undifferentiated wage account still can’t calculate it, because hourly wages, tipped wages, and employer payroll tax need to be visible separately before they can be summed correctly against revenue for the same period.
Multi-location complicates every one of these problems
A restaurant group running more than one location needs each of these same splits, so POS deposits and delivery payouts and tip liability and food cost, tracked by location, not just in aggregate, or none of the per-store numbers an owner actually needs (which location is profitable, which one’s food cost is out of line) can be pulled from the file at all. QuickBooks Online’s class or location tracking handles this, but only if every transaction across every one of those four daily feeds gets tagged consistently at the time it’s entered. A single missed class assignment on a delivery payout is enough to throw off that location’s numbers for the month.
What restaurant cleanup and monthly close actually cover
Fixing a restaurant file usually means rebuilding several months of POS and delivery deposits line by line against each app’s settlement reports. That’s a cleanup engagement, scoped to the number of months affected.
$199 per month of backlogOnce the accounts are split correctly, a monthly close keeps POS, delivery, payroll, and vendor feeds reconciled against each app’s own reports every month, closed by the 5th business day. Full pricing for both is on the pricing page.
Updated August 10, 2026 · Omkar Moraye