If third-party delivery payouts ever feel like a “trust me” number, you’re not alone. I’ve seen busy operators run great service all week, then lose margin in the quietest place possible: the settlement report.
A solid delivery reconciliation checklist turns that fog into a simple routine. You’ll catch missing items, wrong prices, surprise fees, and refunds that never hit your books, before they pile up.
Set your ground rules before you reconcile (so the math stays honest)
Reconciliation works best when you decide, upfront, what “done” looks like. For most restaurants, I recommend a quick daily check, a deeper weekly tie-out, and a monthly close that matches your accounting period.
Here are the data sources I always pull, in this order:
- Platform order detail (per-order line items, modifiers, promos, taxes, tips).
- Platform payout or settlement report (the fee breakdown and net paid).
- Restaurant POS sales detail (tickets, voids, discounts, taxes).
- Bank deposits (actual cash received by deposit date).
- Refund and adjustment logs (both platform-side and POS-side).
Third-party delivery is its own ecosystem, and it pays to set expectations for how you’ll treat common items:
- Tips: usually pass-through, often not part of restaurant revenue (confirm your setup).
- Promotions: sometimes shared, sometimes funded by you, treat the funding source consistently.
- Taxes: may be collected and remitted by the platform in some locations; your accounting needs to reflect that reality.
If you want a helpful high-level view of operational best practices around third-party delivery, I like this overview of third-party delivery best practices. It’s a good reminder that reconciliation is not just accounting, it’s operations.
The delivery reconciliation checklist I use to find issues fast
I run this checklist like a line check. Same steps, same order, no improvising. That’s how you catch small leaks before they become a weekly flood.
Step 1: Confirm you’re reconciling the right time window
Use the platform “order date” window, then separately confirm the payout date. Those rarely match, and that mismatch causes most false alarms.
Quick test: the sum of “net payout” for all settlements in a week should match your bank deposits for that week, plus or minus timing.
Step 2: Tie out gross sales, before fees
For each platform, total these fields for the period:
- Item subtotal (including modifiers)
- Taxes
- Customer delivery/service fees (often not yours)
- Tips (usually not yours)
Then compare platform item subtotal to POS ticket sales attributed to that platform. If your POS and platform aren’t integrated, you’ll do this by export and match.
If gross doesn’t match, stop and fix that first. Fee math won’t matter if the base is wrong.
Step 3: Scan for the “usual suspects” (and fix them in minutes)
This is where I save the most time. I look for patterns, not one-off oddities.
-
Missing items or modifiers
Where to look: platform order detail vs POS ticket, and kitchen chit if you have it.
Proof to attach: POS receipt, kitchen ticket, and a photo of the packed bag label if you use them.
Fast fix: file an adjustment request with the order ID and highlight the missing line.
Prevention: POS menu sync and modifier mapping. A mismapped “Add bacon” is a slow bleed. -
Wrong prices (menu drift)
Where to look: platform menu price vs POS price list.
Proof to attach: screenshot of current POS price, plus the platform menu page showing the wrong price.
Fast fix: update prices, then dispute the specific orders with clear before/after evidence.
Prevention: set a weekly “menu drift” check, especially after seasonal menu changes. -
Unexpected fees and fee changes
Where to look: settlement report fee lines (commission, marketing, service, processing, “other”).
Proof to attach: settlement excerpt with the fee line and the contract term (or email) describing the agreed structure.
Fast fix: dispute with the fee line item, not a generic complaint.
For a plain-English breakdown of how fee lines often show up, see decoding delivery fees and reconciliation. It helps your team speak the same language when reviewing statements. -
Refunds, cancellations, and chargebacks
Where to look: platform adjustments report plus POS void/refund report.
Proof to attach: order timeline, customer message thread (if available), and “order accepted” timestamp.
Fast fix: confirm whether the refund was customer-funded, restaurant-funded, or platform-funded, then book it correctly.
Prevention: require manager approval above a set threshold (I like $25 or 2 items, whichever is higher).
Step 4: Close the loop with one clean variance number
At the end of each period, you should have:
- Expected payout (what the platform should pay)
- Actual payout (what hit the bank)
- Variance (difference, explained and documented)
No explanation means no closure. Variances that sit open tend to repeat.
A reconciliation template (columns + formulas) that ties to the bank
I like a spreadsheet that can work two ways: per order (best for disputes) and per payout batch (best for accounting). Here’s a payout-batch version that stays simple but catches most problems.
Suggested spreadsheet columns (payout batch level)
| Column | What I enter | Notes |
|---|---|---|
| A: Platform | DoorDash, Uber Eats, Grubhub, etc. | Keep naming consistent |
| B: Settlement ID | From payout report | Critical for audit trail |
| C: Period Start | Date | Use platform reporting window |
| D: Period End | Date | |
| E: Gross Item Sales | $ | Items + modifiers before tax |
| F: Platform-Collected Tax | $ | If applicable |
| G: Restaurant-Funded Promos | $ | Only the portion you fund |
| H: Commission & Fees | $ | Combine if you want fewer columns |
| I: Refunds/Chargebacks | $ | Negative impact to payout |
| J: Adjustments | $ | Misc credits or debits |
| K: Expected Payout | Formula | Your “should pay” number |
| L: Actual Bank Deposit | $ | Match by deposit date |
| M: Variance | Formula | Must explain if not zero |
| N: Notes/Proof | Text | “Screenshot saved,” “ticket attached” |
Formulas (Excel or Google Sheets)
- K2 (Expected Payout):
=E2 - G2 - H2 - I2 + J2 - M2 (Variance):
=L2 - K2
If you want to get more granular, split H into commission, marketing, processing, and “other,” but only if someone will actually review those lines.
For teams that want automated reconciliation across many locations, it’s worth understanding what dedicated tools do well. This overview of delivery reporting and reconciliation gives a sense of how data normalization can reduce manual matching.
Internal controls that keep reconciliation from turning into blame
I keep controls practical, not heavy:
- Separation of duties: one person prepares the recon, another approves disputes and write-offs.
- Approval thresholds: manager sign-off for refunds, comp items, and menu edits above set limits.
- Single source of truth: store proofs in one place (shared folder) with a naming standard: Platform, Date, Order ID.
This is also where tech discipline matters. When I act as a Business Technology Partner, I treat reconciliation as part of the stack: Small Business IT hygiene, Cloud Infrastructure visibility, and Cloud Management for the files and logs. If you’re moving reports and approvals into Microsoft tools, an Office 365 Migration done right helps. I also see better results when restaurants invest in Restaurant POS Support, Kitchen Technology Solutions, and Infrastructure Optimization, because clean data starts at the order source.
And don’t ignore security. Cybersecurity Services, Endpoint Security, and Device Hardening reduce the risk of compromised accounts, fake refund activity, or “mystery admin” changes. For many operators, that fits under Managed IT for Small Business, IT Strategy for SMBs, and Business Continuity & Security, anchored by Secure Cloud Architecture, Data Center Technology standards, and practical Technology Consulting. It’s not flashy, but it protects revenue.
FAQ: quick answers busy teams need
How often should I reconcile third-party delivery?
I do a light daily check, then a weekly tie-out to bank deposits. Monthly is for clean accounting close.
Should I reconcile by order or by payout?
Both, but start with payout batches to stop cash surprises. Use per-order recon when you’re filing disputes.
What’s the fastest proof package for a dispute?
Order ID, platform receipt, POS ticket, fee line screenshot, and one sentence explaining the variance. Keep it tight.
Why do POS and platform totals disagree even when prices are correct?
Modifiers, promo funding, tax handling, and timing differences are the top causes.
Conclusion
Third-party delivery payouts don’t have to feel mysterious. With a repeatable delivery reconciliation checklist, a simple template tied to the bank, and tight proof habits, I can usually surface the real issues in one pass. If your variances keep repeating, it’s a signal to fix the source, menu sync, modifier mapping, packaging checks, and the controls around who can change what. The money is already yours, reconciliation is how you go get it.
Discover more from Guide to Technology
Subscribe to get the latest posts sent to your email.