TL;DR: Reconcile third-party delivery by matching every order to five records: the POS sale, the platform payout statement, the bank deposit, the sales tax report, and the general ledger. Advertised commissions start at 15 to 20%, but total deductions often reach 30 to 40% of order value once fees, ads, and refunds are counted. In most states, marketplace facilitator laws make the platform remit sales tax, but you still need order-level proof.
Restaurants should reconcile food delivery fees by matching each platform order to the POS sale, the payout statement, the bank deposit, the tax report, and the general ledger. That five-way match is the only way to see the real cost of commissions, ads, refunds, and promos before they eat the channel’s margin.
Third-party delivery is both a growth channel and a financial control problem. Between commissions, service fees, payment processing, promotions, refunds, chargebacks, and shifting sales tax rules, the amount a platform deposits rarely matches the order value in your POS. And with the FTC examining delivery fee practices, fee structures keep changing under operators’ feet.
This guide explains how to decode platform payout statements, who actually owes the sales tax, the accounting controls that keep delivery revenue clean, and how to use your own reconciliation data to negotiate better terms.
What Does Third-Party Delivery Really Cost?
The real cost of a delivery order is the net left after every platform deduction, not the advertised commission. Base rates start at 15 to 20%, but processing fees, ad spend, promos, refunds, and chargebacks often push the effective cost to 30 to 40% of order value.
Delivery platforms have moved from extra exposure to a primary sales channel, with a cost stack that reads like a mini P&L inside each order. Industry breakdowns show that once every platform-linked deduction is counted, restaurants can face an effective drag of roughly 30 to 40% of order value on the major marketplaces.
That’s why delivery reconciliation is a margin discipline, not a bookkeeping afterthought. The pain shows up as shrinking margins, unpredictable payouts, and timing gaps between order activity and deposit dates. Comparing DoorDash, Uber Eats, Grubhub, and direct ordering on equal footing requires a consistent net-order-economics view, including the ad spend and the admin labor it takes to audit statements.
The math for any channel is one line:
Total platform deductions ÷ gross platform sales = effective platform cost
Compare that percentage against your food cost and labor to see whether the channel actually contributes to profit margin or just adds volume.
Decoding Platform Payout Statements
Treat every payout statement as a bridge from customer spend to bank deposit. Start with gross platform sales, then tag every deduction into consistent buckets: commission, delivery and service surcharges, payment processing, marketing, refunds, chargebacks, promos, tax, and adjustments.
Each platform exposes the columns you need, in its own format. DoorDash provides statement and payout reporting with error charges and adjustments at the transaction level. Uber Eats weekly pay statements work the same way, separating sales, the Uber fee, adjustments, and net payout. Grubhub statements break out order adjustments, account adjustments, and promotion redemptions.
Two categories deserve special attention. First, advertising: DoorDash Sponsored Listings are pay-per-order ads billed when an ad-driven order completes, so ad spend scales with volume and hides inside the payout. Second, refunds: Grubhub’s policies distinguish merchant-responsible refunds (missing items, quality issues, late self-delivery) from platform-responsible ones, and that split determines whose money covers each error.
Common reconciliation breaks are operational: timing gaps between order date and payout date, duplicate refunds, mismatched menu prices, missing promo reimbursements, and unexplained negative adjustments. Tie every line to an order ID and the breaks surface themselves.
Who Handles Sales Tax on Delivery Orders?
In most states, marketplace facilitator laws require the delivery platform to collect and remit sales tax on orders it facilitates. The restaurant still needs order-level records showing who collected the tax, what was taxed, and what was refunded so platform-reported sales reconcile to the books.
Marketplace facilitator laws now exist in nearly every state with a sales tax, shifting collection and remittance to the platform for marketplace orders, and the platforms publish their own state-by-state guidance on where they collect. Direct orders through your own website remain your responsibility. That split means the same menu item can have two different tax workflows depending on how the guest ordered it.
Product taxability adds a second layer. States tax prepared food differently from grocery items, with definitions tied to heating, mixing, or whether utensils are provided. Florida, for example, taxes prepared restaurant food while exempting most groceries, so Miami delivery orders are almost always taxable. Delivery charges and service fees can be taxable in some states and exempt in others, so an order that bundles taxable and exempt items needs line-level treatment.
Work the decision tree in plain language: identify the taxing jurisdiction, determine product taxability, identify the seller of record, determine whether delivery fees sit in the taxable base, and confirm who collected and remitted. Then preserve the order-level evidence. For refunds, the tax generally reverses with the refund, and sellers claim the adjustment through credits or amended returns, so refund timing belongs in your compliance file.
If you operate across state lines or your sales tax filings don’t tie to platform reports, fix that reconciliation before an auditor asks for it.
What Accounting Controls Keep Delivery Revenue Clean?
Strong delivery controls match every order to the POS, the platform statement, the payout batch, the bank deposit, and the general ledger. Add standard fee codes, an exception queue with owners and deadlines, refund review, and tax validation, with automation carrying the volume.
Start with the account structure. Each platform’s commissions, processing fees, ad spend, and refunds should post to dedicated accounts in your restaurant chart of accounts, never netted into sales. Gross sales stay gross, deductions stay visible, and a clearing account bridges the timing gap between order and deposit.
Define the revenue recognition policy once and apply it to every platform: how you record gross sales, commissions, processing costs, ad spend, refunds, promo funding, customer tips, and platform-collected tax. Review it with your accountant, because marketplace facilitator treatment changes whether tax appears as your liability or stays outside your remittance entirely.
Then let automation carry the matching. Useful controls include platform-specific fee code maps, order ID matching, payout-to-bank matching, duplicate refund checks, promo reimbursement checks, and tax variance reports. The goal isn’t removing human review. It’s sending humans only the items that need judgment.
Keep the document trail: contracts and amendments, fee schedules, payout files, POS exports, tax reports, dispute evidence, and bank records. That file protects cash during disputes and lets an auditor trace any amount from guest order to financial statement.
Using Reconciliation Data to Negotiate Better Terms
Clean reconciliation turns delivery from a black box into a negotiable P&L line. The strongest data points are your effective commission rate, refund rate by reason, promo funding split, tax variance, and profit by store and menu item.
When you can measure fee leakage by store, daypart, and item category, you can push for tier changes, credits, or revised workflows with proof instead of frustration. Platform contracts have grown longer and more complex, so review the clauses that move money: commission tiers and plan definitions, who bears refunds and chargebacks, promotion funding, tax collection language, payout timing and holdbacks, data access, audit rights, and dispute windows.
Fee pass-through can be surgical rather than blunt: platform-specific menu pricing, delivery-only bundles, and loyalty offers that move repeat guests to direct ordering, all kept consistent with platform terms and the FTC’s tightening disclosure expectations.
A practical 90-day arc: assemble contracts, statements, tax reports, and POS exports in the first 30 days. Build the reconciliation matrix connecting orders to payouts and the ledger by day 60. By day 90, automate the high-volume matching, renegotiate the worst clauses with variance evidence in hand, and stand up channel profitability reporting.
Where FORCS Fits In
Delivery reconciliation is exactly the kind of work that separates restaurant bookkeeping built for this industry from generic bank-feed bookkeeping. We match platform payouts to POS sales and bank deposits weekly, keep every commission and fee visible in its own account, and validate that platform-collected tax ties to what the states expect.
The payoff is a delivery channel you can actually price, negotiate, and trust. If your platform deposits never quite match your POS and nobody can explain the gap, book a consultation and we’ll show you what a clean five-way match looks like on your own numbers.
Frequently Asked Questions
What is the effective commission rate restaurants actually pay on delivery orders?
The effective rate is total platform deductions divided by gross platform sales. Platforms advertise base rates of 15 to 20%, but the real number climbs once payment processing, ad spend, refunds, and chargebacks are added. Most operators land between 25 and 40% of order value when every deduction is counted.
Who is responsible for collecting and remitting sales tax on third-party delivery orders?
In most states, marketplace facilitator laws require the platform to collect and remit sales tax on orders it facilitates. Restaurants still need order-level records showing who collected the tax, what was taxed, and what was refunded so platform-reported sales reconcile to the books. Rules vary by state, so confirm each platform’s handling in your jurisdiction.
Why does the amount deposited by DoorDash or Uber Eats differ from my POS sales total?
The deposit is lower because platforms deduct commissions, processing fees, advertising charges, refunds, and sometimes tax before paying out. Timing gaps between order date and deposit date add more variance, especially on weekly pay cycles. Reconciling each payout against POS sales and the bank statement is the only way to confirm every deduction.
How often should restaurants reconcile their delivery platform statements?
Weekly at minimum, matching each payout to its order batch, bank deposit, and general ledger entry. High-volume operators benefit from daily exception reports that flag unmatched items automatically. Monthly reconciliation alone leaves too much time for disputed refunds and missing promo credits to go stale.
Can restaurants negotiate lower commission rates with delivery platforms?
Yes, and clean reconciliation data is the strongest tool you have. When you can show your effective commission rate, refund rate by reason, and ad spend return with documentation, you have specific numbers to bring to a contract conversation. Platforms have tier structures that operators with proven volume can access, but you need your own data to make the case.
