Finance
In DevelopmentKnow what every location actually earned, not what the platform says it paid.
Between POS totals, marketplace payouts, commissions, and fees, the numbers rarely match on their own. Finding out where they don't is usually a spreadsheet exercise that happens too late to act on.
- Matches payouts against POS and order-level detail
- Surfaces fee and commission discrepancies by location
- Closes the books without a manual spreadsheet reconciliation
The problem
Reconciliation that happens after the money's already gone
Most finance teams reconcile delivery and marketplace revenue in arrears, once a month, by hand. By the time a fee miscalculation or a missing payout turns up, the dispute window for correcting it is often already closed.
- Discrepancies surface weeks after the transaction, not days
- Every location adds another payout feed to manually tie out
- Finance time goes to matching numbers instead of acting on them
How it works
Reconciliation that runs continuously
The goal is a close that's already done by the time someone needs to look at it.
- 01
Every payout is tied to its source orders
Marketplace and POS data are matched at the order level, so a payout isn't just a lump sum — it's traceable back to what was actually sold and what was actually deducted.
- 02
Discrepancies are flagged, not buried in a total
A fee that doesn't match the agreed rate, or a payout that's short, is surfaced as its own line item instead of disappearing into a rounding difference.
- 03
Location-level statements are ready on demand
Finance gets a clean reconciliation per location, per period, without rebuilding it from five different exports every time someone asks.
Why it's built this way
Built for finance teams covering many locations, not one
A reconciliation process that works for three stores breaks at thirty. This is built for the scale past that.
One ledger across every channel
Dine-in, pickup, and every delivery marketplace reconcile into the same view, so finance isn't stitching together separate processes per channel.
Audit-ready by default
Every number traces back to the order and payout it came from, so a question about a discrepancy has an answer instead of a shrug.
Common misconceptions
What finance teams usually get wrong about this
Misconception
If the payout total looks roughly right, it's fine.
Reality
A total can look right while individual fees, commissions, or adjustments inside it are wrong in both directions. Only order-level matching catches that.
Misconception
This is a once-a-month finance problem.
Reality
The later a discrepancy is caught, the more likely the window to correct it with the platform has already closed. Continuous matching is what keeps that option open.
Questions, answered
FAQ
- Does this replace our accounting system?
- No. It reconciles the revenue and fee data that feeds into it, so what lands in your books is already matched.
- How far back can discrepancies be caught?
- Reconciliation runs on an ongoing basis as payouts land, so issues are caught close to when they happen rather than at a later audit.
- Does this work across multiple brands under one group?
- Yes — reconciliation is organized by location and can be rolled up by brand or by group, depending on how your operation is structured.
Close the books on numbers you've actually verified.
Talk to us about reconciliation configured for your locations and your channels.