You run Toast for the restaurant and QuickBooks Online for the books. Every month you sit down to reconcile the bank account in QBO, and every month the same thing happens: there’s a $1,180 DoorDash deposit sitting in the bank feed that matches no Toast invoice, no single day of sales, and no number you can find anywhere in QuickBooks. You try to force it. You create an adjustment. The reconciliation “closes” but you know it’s wrong — and next month it’s a different amount, a different day, the same problem.
One operator put it exactly: their “statements don’t match the deposits” and the numbers “did not balance to reality” no matter how many times they re-ran the reports. If you’re on Toast + QuickBooks Online and you run DoorDash, Uber Eats, or Grubhub, this is not a QuickBooks problem and it’s not a you problem. It’s structural — and once you see where the gap actually lives, it becomes reconcilable and, often, partly recoverable.
The short version: QuickBooks Online is just where you notice the problem. The money difference is created between Toast (which records orders at full menu price), the delivery platforms (which pay you net of a 15–30% commission, days later), and your bank. Reconcile the delivery payouts back to the Toast orders first — then the QBO bank reconciliation finally has something clean to match, and the recoverable overcharges surface in the process.
Why your QuickBooks Online bank reconciliation never balances with Toast + delivery
QuickBooks Online reconciliation is a matching exercise: every transaction in the bank feed should tie to a recorded sale, deposit, or expense. That works cleanly for in-house card sales. It breaks completely for delivery, and here is the exact mechanism.
Toast records gross; the platform pays net. When a $42 DoorDash order hits the Toast kitchen display, Toast books $42 in sales that day. DoorDash never sends you $42. It keeps a 15–30% commission, nets out any refunds and promotional costs, and deposits the remainder — maybe $30 — into your bank. QuickBooks sees the $42 (if you sync Toast) on one date and a $30-ish slice of a lump deposit on another. There is no transaction in QBO that equals the bank-feed line, because the bank-feed line is net of deductions Toast never knew about.
The deposit is a weekly lump, not a daily total. DoorDash, Uber Eats, and Grubhub each batch many orders into one weekly payout. That single deposit in your QBO bank feed covers dozens of orders spread across several days, minus commission, minus refunds, minus promos. You are trying to match one number against a week of Toast sales recorded a different way on different dates. The arithmetic cannot close without breaking the payout back down.
Timing pushes it across periods. Platforms pay 3–5 business days after the order. Orders near a month-end fall into the next month’s deposit. So your QBO reconciliation for March is missing money that physically arrives in April, and April’s deposit contains March’s orders. Reconciling by calendar month guarantees a mismatch.
Undeposited Funds and clearing accounts are a symptom, not a fix. Many Toast + QBO setups route delivery sales through an Undeposited Funds or a clearing account, hoping the deposit will clear it out. It never clears cleanly, because the amount deposited is smaller than the amount that went in (commission), and it arrives on a different date (timing). The balance in that account drifts upward every month. That growing, unexplained balance is the same problem wearing a different hat — it is not solved by more journal entries, it is solved by reconciling the payout to the orders.
Already staring at a delivery deposit in QBO that won’t tie to anything? Run a free scan and see exactly which orders, fees, and refunds make up the gap.
Run a Free ScanThe gap isn’t inside QuickBooks — it’s between Toast, the platforms, and your bank
This is the reframe that makes the problem solvable. QuickBooks Online is the messenger. It is faithfully reporting that the money received does not equal the sales recorded. It cannot tell you why, because the “why” lives in three places QBO never sees together:
- Commission drift. Your contracted rate is one number; the rate actually applied per order drifts higher with plan changes, promotional tiers, and order-type misclassification. Every fraction of a percent across hundreds of orders is real money.
- Refund clawbacks. Platforms deduct refunds for driver lateness, delivery issues, and customer fraud — problems your kitchen didn’t cause. Your Toast ticket shows the order was made and handed off; the platform pulled it from your payout anyway.
- Missing orders. An order that’s in Toast but never appears on any platform payout is the cleanest possible leak: you made the food and were never paid for it.
- Promotional deductions without enrollment. Marketing and promo charges sometimes hit payouts with no matching enrollment record.
- Payout timing. Not an error, but until you account for it, period-boundary orders look like missing money against your Toast totals.
None of those five are visible in QuickBooks, and none are reconciled by Toast or by a POS–QuickBooks connector. They are only visible when you put the Toast orders and the platform payout side by side. That is the work that makes the QBO bank reconciliation close — and it is exactly the work this guide, and DeliverGuard, is about. For the platform-side mechanics in isolation, see Toast sales not matching your delivery payouts; for the multi-platform version, see reconciling delivery platform payouts.
How to reconcile Toast + delivery payouts so QuickBooks finally ties out (step by step)
You need three things for the same period: your Toast sales export (to isolate delivery orders), each delivery platform’s transaction-level payout report, and your bank statement / QBO bank feed. About 30–45 minutes per platform the first time.
Step 1 — Separate delivery orders in Toast
In Toast, run the sales report for the period and filter by order source. Pull out DoorDash, Uber Eats, and Grubhub revenue from in-house card sales. The delivery total is money the platforms owe you on their own schedule — it should never be expected to land in your processor’s in-house deposit, and treating it as if it should is half of why the QBO reconciliation breaks.
Step 2 — Pull each platform’s transaction-level payout report
From each merchant dashboard (DoorDash Merchant Portal, Uber Eats Manager, Grubhub for Restaurants), export the transaction-level payout report — not the summary. You want per-order subtotal, commission, refund adjustments, promotional charges, and the net payout, plus the deposit reference and date.
Step 3 — Match payout line items to Toast orders
For each platform, match its payout line items to the Toast delivery orders by order ID (or by timestamp and amount if the IDs don’t line up). For every matched order verify three things: commission ÷ subtotal equals your contracted tier rate; every refund deduction has a matching Toast ticket; and every Toast delivery order appears somewhere on a payout. Anything that fails one of those is a flag.
Step 4 — Tie the net payout to the bank deposit and the QBO bank-feed line
Sum the reconciled net for the payout period and match it to the actual bank deposit (allow 3–5 business days of transfer time), then to the corresponding transaction in your QuickBooks Online bank feed. This reconciled net — not your gross Toast delivery sales — is the number the bank-feed line was always going to match. Once you have it per platform per payout, the QBO reconciliation has a clean target.
Step 5 — Flag and dispute the recoverable gaps
Commission charged above your contracted rate, refund clawbacks on orders your Toast tickets show were fulfilled correctly, missing orders, and promo deductions you never enrolled in are all recoverable. Record the order ID, expected amount, actual amount, and dispute through the platform’s merchant portal with the Toast ticket as evidence. Our DoorDash payout reconciliation guide walks the per-order dispute workflow in detail.
Worked example: $4,000 of Toast DoorDash sales, one $2,910 QBO deposit
A restaurant on the DoorDash Plus plan (25% commission) runs a week of delivery. Here is what each system shows:
Toast delivery sales recorded (gross, menu price): $4,000.00
QuickBooks Online bank feed — single DoorDash deposit, 4 days later: $2,910.00
Apparent “missing” money: $1,090.00
What the reconciliation against the DoorDash payout report explains:
- Marketplace commission at the contracted 25%: −$1,000.00 (expected — not a discrepancy)
- 6 orders charged at 28% instead of 25%: −$42.00 (recoverable overcharge)
- 2 refund clawbacks on orders Toast shows were handed off correctly: −$60.00 (disputable)
- 1 Toast delivery order ($30.00) that never appears on any DoorDash payout: (missing payout)
Reconciled, expected net payout: $3,000.00 · Actually deposited: $2,910.00 · Recoverable: $132.00 for one week
Now the QBO bank-feed line makes sense: the $2,910 deposit reconciles to $3,000 of true net minus $90 still owed (the $42 overcharge + the $30 missing order + a $18 timing slice that clears next week). The bank reconciliation closes against a number you can defend — and you have a $132 dispute filed instead of a forced adjustment papering over the gap.
Annualize that single week and it’s well over $6,000 of leak plus recoverable disputes that, without reconciliation, just disappear into a clearing account that never zeroes out.
See your real numbers: upload Toast, your delivery statements, and your bank deposits and get the reconciled net plus every recoverable discrepancy.
Run a Free ScanWhat this means for your books (and your bookkeeper)
Here is the clean hand-off. Once delivery payouts are reconciled, what your books actually need is two things per platform per payout period: the true net amount received (which now matches the bank), and the itemized list of deductions and recoverable discrepancies that explains the difference between gross Toast sales and that net.
With those two things, the QuickBooks Online bank reconciliation closes against a defensible number instead of a plug. How those figures are then posted — which accounts the commission, refunds, and recoverable disputes are booked to — is your bookkeeper’s or accountant’s call and outside the scope of this guide. The point of this guide is upstream of that: your bookkeeper cannot book a number nobody has reconciled, and a raw bank lump is not that number. DeliverGuard produces the reconciled net and the discrepancy list; your accounting professional books it.
This is also the line between this guide and a POS–QuickBooks integration. An integration moves Toast sales data into QBO. It does not reconcile what the platforms paid. If you’re still evaluating connectors, our breakdown of POS systems that actually sync with QuickBooks covers that — but note that no connector closes this gap, because the gap is in the payout, not the data transfer. Square has the best native QuickBooks connector of any POS and it still leaves this exact delivery gap; see Square + QuickBooks Online deposits not matching delivery payouts.
How DeliverGuard reconciles this automatically
Doing the five steps above by hand works for one week. Across hundreds of orders a month, three platforms, and a monthly close, it is the task that gets skipped — and skipped reconciliation is exactly where the leak compounds and the clearing account balloons.
DeliverGuard ingests your Toast exports, your DoorDash, Uber Eats, and Grubhub statements, and your bank deposits, then matches every order across all three. Commission overcharges, refund clawbacks, missing payouts, promo deductions, and timing shifts are categorized automatically, with the per-order evidence you need to dispute them. You get the reconciled net per platform that your QuickBooks Online bank reconciliation will finally match — in minutes instead of an afternoon. Verifying delivery commissions this way also surfaces the broader hidden delivery fees most restaurants miss.
Frequently Asked Questions
Because the numbers QuickBooks is trying to match come from three systems that never agree on a daily basis. Toast records a delivery order at full menu price the moment it hits the kitchen. DoorDash, Uber Eats, and Grubhub collect the customer’s payment and deposit you separately, days later, net of a 15–30% commission plus refund and promotional adjustments. So the bank-feed line in QBO is a net lump sum that ties to no single Toast sale and no single day. Until each platform’s payout is reconciled back to the underlying Toast orders, the QBO reconciliation has nothing clean to match against and will not close.
The deposit in your bank feed is one weekly net payout covering many orders, after the platform removed its commission, refund clawbacks, and promotional costs. Your Toast sales were recorded per order at full menu price on the day the food went out. One net lump vs. many gross daily orders on a different date is a structural mismatch, not a QuickBooks error. The deposit only makes sense once you break the platform payout back down to the orders it actually paid for.
Toast has no native QuickBooks Online integration; operators use a third-party connector. But even with a connector, what syncs is Toast sales at menu price, not the delivery platform’s net payout. The connector moves the inflated gross number into QBO, so the bank reconciliation still will not tie out, because the actual money received is net of commission and arrives on the platform’s schedule, not Toast’s. A sync moves data; it does not reconcile delivery payouts.
Separate delivery orders from in-house sales in Toast, pull each platform’s transaction-level payout report, and match the payout line items to the Toast orders for that period order-by-order. Verify the commission rate (commission divided by subtotal vs. your contracted tier), confirm every refund deduction has a matching Toast ticket, and flag any Toast delivery order missing from the payout. The reconciled net per platform is the figure the QBO bank-feed deposit will finally match.
Conceptually, the deposit that hits your bank is the platform’s net payout, not your gross delivery sales, so the books need the reconciled net plus the list of commission, refund, and fee deductions that explain the difference. Producing those reconciled figures and the recoverable-discrepancy list is the reconciliation step this guide covers. How they are then booked to specific accounts is your bookkeeper or accountant’s call and outside the scope of this guide; the point is that they need a reconciled net to book, not a raw bank lump.
A POS-QuickBooks integration moves sales data from Toast into QuickBooks. It does not reconcile what the delivery platforms actually paid you. An integration will happily sync $4,000 of menu-price DoorDash sales into QBO while only $2,910 ever reached your bank, leaving the same unexplained gap. Integration solves data entry; reconciliation solves the money difference. You need the second one to make the bank rec close.
It depends on the platform and discrepancy type. Commission-rate errors are generally disputable up to roughly 90 days back, longer with contract documentation if the error is systematic. Refund clawbacks are most easily disputed within about 30 days. Missing orders should be disputed as soon as discovered because supporting delivery logs expire. Running a reconciliation across the last 90 days of Toast orders and platform payouts typically surfaces one-time recoverable money alongside the ongoing leak.