How to Reconcile Delivery App Sales With Your POS Payouts

The order said $48.20. The payout said $31.6-something. You didn't check, because it was Tuesday and there were forty other things on fire.

Multiply that across every delivery platform, every order, every payout cycle — and somewhere in there is real money you're never getting back, because you never noticed it left.

This is the quiet tax on F&B businesses that sell through GrabFood, Foodpanda, Deliveroo, and ShopeeFood. The platforms bring volume. They also bring commission deductions, ad fees, promo co-funding, adjustment line items, refunds you didn't approve, and payout cycles that don't line up with anything. Learning to reconcile delivery app sales against what actually lands in your bank account is one of the highest-ROI back-office habits an operator can build. It's also one of the most neglected.

Here's how to do it without hiring someone full-time to stare at spreadsheets.

---

Why the numbers never match on their own

A delivery order passes through three different versions of the truth before it becomes cash:

1. Your POS records the gross order — what the customer paid for the food.
2. The platform's settlement report records gross sales minus commission, minus fees, minus promo funding, plus or minus adjustments and refunds.
3. Your bank records a single lump payout, batched across dozens or hundreds of orders, landing days later on the platform's schedule.

None of these three numbers is meant to match the others directly. That's the trap. Operators glance at the bank deposit, see money arrived, and assume it's correct. But the payout is a net figure with a dozen deductions baked in — and any one of them can be wrong.

The discrepancies aren't theoretical. The common ones:

• Commission overcharges — you're billed 30% when your contract says 28%, on every order, silently.
• Missing orders — an order shows in your POS and never appears in the settlement report at all.
• Refunds you didn't authorise — a customer complains, the platform refunds them, and you absorb the full order value with no say.
• Promo co-funding errors — a discount the platform was supposed to split 50/50 gets charged to you at 100%.
• Fee creep — service fees, processing fees, and "campaign" fees that appear without explanation.

Each one is small. None is worth a Tuesday-night argument on its own. Together, across a quarter, they're a line item you'd notice if it had a name.

---

The five-point match: the only check that matters

You don't need to verify every cent of every order by hand. You need a repeatable check that catches the patterns. For each platform, each payout cycle, match on five points:

1. Order count — does the number of orders in the settlement report equal the number in your POS for that period? A gap here means orders went missing in one system or the other.
2. Gross sales — does total gross sales on the report match total delivery gross in your POS?
3. Commission percentage — back out the commission from the report and check the rate. Is it the rate in your contract? On every order, or just most of them?
4. Adjustments and refunds — list every refund and adjustment. Do you recognise each one? Were you notified?
5. Net payout received — does the report's net figure actually equal what hit your bank?

When a line fails, you don't need to fix it on the spot. You need to log it — order ID, platform, expected vs actual, date — and raise the dispute within the same payout cycle. Platforms almost universally have a dispute window. Miss it, and a legitimate claim becomes a write-off.

The operators who recover this money aren't smarter. They're just the ones who check inside the window, every cycle, without fail.

---

Build the cadence before you build the system

Before anyone reaches for software, the discipline has to exist. A weekly reconciliation cadence beats a perfect tool used sporadically.

The minimum viable version is a daily log: gross delivery sales by platform, pulled from your POS, recorded the next morning. Then, each payout cycle, you sit the settlement report next to the bank deposit and your daily log, and you run the five-point match. Anything that fails goes into a disputes tracker with the order ID and the date you raised it.

This is tedious. It is also exactly the kind of tedious that compounds. A 2% commission error you catch in week one is 2% you stop bleeding for the rest of the year.

If you're doing this for one outlet and one platform, a spreadsheet is genuinely fine. The problem is what happens next.

---

Where the spreadsheet breaks

The manual approach holds up until you have three outlets and four platforms. Then you're reconciling twelve report-to-payout combinations, each on its own schedule, each with its own export format, each landing in your bank as a batched lump you have to unbundle by hand.

This is the point where most F&B finance functions quietly give up on real reconciliation and switch to a glance-and-hope model: money came in, close enough, move on. The losses don't stop. They just stop being visible.

The structural problem is that the data lives in incompatible places. POS exports in one format. Each platform's settlement report in another. Bank statements in a third. The reconciliation only works if something pulls all three together, normalises them, and flags the mismatches automatically — so a human only ever looks at the exceptions, not the thousands of orders that matched cleanly.

That's a systems problem, not a spreadsheet problem. And it's squarely the kind of thing a custom ops layer is built to solve: ingest the POS feed, ingest each platform's settlement data, match against bank payouts, and surface only the orders where the five-point check fails. The finance person's job shifts from re-keying numbers to resolving the handful of disputes that actually need a human.

If your team is spending hours a week unbundling payouts by hand — or worse, not checking at all — that's the inflection point where Hippo Labs tends to get the call. We build the connective tissue between your POS, your delivery platforms, and your bank, so reconciliation runs in the background and you only see what's broken. Worth a conversation if delivery is a real share of your revenue and nobody's fully sure the payouts are right.

---

The short version

Three systems hold three different versions of every delivery order, and none of them is built to match the others. Run the five-point check — order count, gross sales, commission rate, adjustments, net payout — every cycle, and dispute the gaps inside the window. Do it in a spreadsheet while you can. Move it into a system before the spreadsheet quietly stops being checked.

The money you're losing to delivery reconciliation isn't dramatic. It's a slow leak. But you can't plug a leak you've never measured.