The sales figure shown in a GoFood, GrabFood, or other marketplace dashboard may differ from the amount deposited into a restaurant’s bank account. Commissions, merchant-funded promotions, refunds, platform fees, adjustments, and payout timing can all explain the difference.
Reconciliation does not mean forcing every figure to match. It means tracing each order through the marketplace report, the settlement calculation, and the bank receipt. This guide provides a practical workflow for restaurant finance and operations teams.
Understand Gross Order Value, Net Sales, and Settlement
Gross order value (GOV) is the gross value of orders included in the reporting scope before specified deductions. First confirm whether the marketplace includes canceled orders, taxes, or delivery charges in that figure: column definitions vary by platform.
Net sales represent sales after relevant merchant-funded discounts, refunds, and sales adjustments under the restaurant’s accounting policy. Net sales are not the same as cash received. Commissions and service fees may reduce the payout even if they are recognized separately from revenue.
Settlement is the net amount the platform determines is payable to the merchant after applicable deductions, subsidies, taxes or fees, and adjustments. A bank receipt is the transfer actually credited to the restaurant’s account. One payout may cover several orders and arrive on a later date.
Important: use consistent definitions and do not deduct the same discount or refund twice. If net sales already reflect those items, do not subtract them again when calculating the expected settlement.
Identify All Components Affecting the Payout
• Marketplace commission: the deduction agreed between the platform and the merchant; no single fee rate applies to every merchant.
• Promotions and subsidies: separate merchant-funded discounts from subsidies actually reimbursed by the platform; avoid counting a subsidy twice.
• Refunds and cancellations: full or partial reimbursements that may appear in a different period from the original order.
• Adjustments: corrections, compensation, withheld payments, or releases associated with previous payout batches.
• Taxes and fees: service, administration, transaction, or tax components that apply under the platform statement and merchant agreement.
Check who funded each promotion, the refund date, and the basis of every charge. Use the merchant’s actual settlement report. The figures in the example below are illustrative, not published marketplace fee benchmarks.
Collect Four Essential Data Sources
• Order report: order ID, outlet, sales channel, transaction date, order status, gross value, discounts, refunds, and the merchant-entitled amount.
• Settlement report: payout ID, included orders, commissions, charges, subsidies, adjustments, net payout, and scheduled transfer date.
• POS sales report: marketplace order ID mapped to the POS transaction, cancellations or refunds, channel sales, and outlet identifier.
• Bank receipt: credit date, amount, payment reference, receiving account, and payer details.
Make sure the reporting time zone, cut-off period, currency, and merchant/outlet ID align. Use order IDs to reconcile individual orders; use settlement IDs or payout batches to match bank transfers because one transfer may cover multiple orders.
Read also: Order Management System (OMS): Definition, How It Works, Benefits, and Management Tips
Step-by-Step Workflow: Order → Marketplace → Settlement → Bank
1. Align reporting periods and match orders with POS records
Define the outlet, platform, order period, and settlement period. Export the order and POS sales reports, then match order IDs. Flag missing, duplicated, canceled, and unsynchronized transactions.
2. Review merchant entitlements and deductions
For each payable order, verify the original amount, merchant-funded discount, refund, reimbursable platform subsidy, commission, fees, taxes, and adjustments. Match the figures against the applicable contract and transaction details.
3. Calculate the expected settlement by payout batch
Group orders by settlement ID. Start from a consistent merchant-entitlement amount, subtract settlement deductions, and add separately payable subsidies or valid adjustments. Do not mix payouts that are not yet due with settled batches.
4. Compare the expected amount with the platform settlement
Calculate platform variance = expected settlement − reported settlement. Investigate differences in commissions, promotions, refunds, fees, or adjustment entries.
5. Match due payouts to bank credits
Match settlement ID, destination account, transfer reference, amount, and receipt date. Calculate bank variance = settlement amount already due − matched bank credits. A payout that is not yet due should remain pending, not be classified as missing money.
6. Document exceptions and follow-up actions
Apply statuses such as matched, pending, discrepancy, and escalated. Keep supporting statements, bank records, an investigation owner, dates, and findings. Never alter sales values merely to force a match.
Simulation: IDR 10 Million in Sales but a Smaller Payout
This simulation treats IDR 10,000,000 as the gross value of completed orders in one period. A platform subsidy of IDR 300,000 is paid separately to the merchant and is not already included in the gross or net sales figures. No other tax or adjustment is assumed.
| Component | Amount |
| Gross order value (completed orders) | IDR 10,000,000 |
| Merchant-funded discounts | −IDR 500,000 |
| Merchant-borne refunds | −IDR 200,000 |
| Net sales (illustrative) | IDR 9,300,000 |
| Marketplace commission | −IDR 1,000,000 |
| Merchant service fee | −IDR 50,000 |
| Separately payable platform subsidy | +IDR 300,000 |
| Expected settlement | IDR 8,550,000 |
Calculation: IDR 10,000,000 − 500,000 − 200,000 − 1,000,000 − 50,000 + 300,000 = IDR 8,550,000. Every amount is hypothetical and is not a GoFood, GrabFood, or industry-standard rate.
If the settlement report shows IDR 8,550,000, the platform variance is zero. If the bank has credited only IDR 8,300,000, there is a bank-receipt difference of IDR 250,000. Check whether the balance is scheduled for another payout, withheld, or recorded under another reference before classifying it as a discrepancy.
Handle Payouts Recorded in Different Periods
An order may be placed on October 30, included in a November 1 settlement batch, and credited to the bank on November 2. Comparing October sales directly with October bank credits would therefore produce a misleading difference.
• Order date: when the sale occurred for sales reporting.
• Settlement or payout date: when the marketplace determines or schedules the merchant payment.
• Bank receipt date: when the cash is actually credited to the bank account.
Maintain an outstanding-settlement register by payout ID, expected transfer date, and status. A payment not yet due is not a final variance. At month-end, the accounting team should consider any receivable or clearing-account treatment required by its accounting policy.
Investigate Missing, Canceled, Refunded, or Duplicate Orders
• Missing orders: present on the marketplace but absent from the POS, or vice versa. Check order mapping, connection logs, time zones, and synchronization status.
• Canceled orders: confirm they are not still treated as completed sales; check whether any cancellation fee remains payable.
• Refunded orders: match amount, responsible party, original order ID, refund date, and the settlement batch where the deduction appears.
• Duplicate orders: identify any order ID recorded more than once in the POS or consolidated report, which can inflate gross sales.
Retain status-change logs, customer complaint evidence, and refund references. Investigating individual order IDs is more effective than comparing only monthly totals.
Build a Reconciliation Sheet: Expected vs Actual vs Variance
The reconciliation sheet should track two separate checks: the marketplace calculation and the bank transfer. These are the minimum suggested fields.
| Field | Purpose |
| Merchant / outlet / channel | Separate bank accounts and outlets |
| Order ID and status | Trace source orders and cancellations |
| Order date | Determine the sales period |
| Settlement / payout ID | Match the marketplace transfer |
| Settlement period / due date | Determine whether payment is overdue |
| Gross order value / net sales | Identify the value and merchant entitlement |
| Merchant discount / refund | Avoid double-counting deductions |
| Commission / fee / tax | Track relevant marketplace charges |
| Subsidy / adjustment | Supported additions and corrections |
| Expected settlement | Calculated merchant amount |
| Reported settlement | Payout shown in the platform report |
| Platform variance | Expected minus reported settlement |
| Bank receipt / date / reference | Evidence of credited funds |
| Bank variance | Reported payout due minus matched bank credit |
| Status / owner / evidence | Matched, pending, discrepancy, escalated; follow-up |
A zero platform variance means the merchant calculation matches the marketplace report. The bank check is matched only when the due funds are actually received. One transfer may settle several payout batches, so use references and batch-level details rather than a simple date total.
When Should a Variance Be Escalated?
Not every difference warrants an immediate complaint. Separate normal payout timing from supported discrepancies and set escalation thresholds according to the restaurant’s internal policies.
• Normal pending: the payout is not yet due or the bank transfer is still within the platform’s published schedule.
• Internal investigation: missing POS orders, duplicates, incorrectly mapped promotions, or refunds not linked to original orders.
• External escalation: an overdue payout, unsupported deductions, or a mismatch between the reported payout and bank receipt.
• High-priority escalation: a material or recurring variance across outlets, repeated refunds, or suspected duplicate charges.
Attach the order ID, settlement ID, dates, amounts, fee breakdown, bank transfer reference, and internal findings. Assign an owner and due date and review the case again at the next reconciliation cycle.
Read also: How to Read Financial Statements for Culinary Entrepreneurs
Frequently Asked Questions
1. Why are marketplace sales different from bank deposits?
Sales value and net payout serve different purposes. Merchant discounts, commissions, refunds, fees, adjustments, and payout dates can create legitimate differences.
2. Can the settlement amount be recorded directly as sales revenue?
Not automatically. Settlement is the net cash received, whereas revenue, marketplace charges, refunds, and taxes should be recorded according to the restaurant’s accounting policy.
3. How often should reconciliation be performed?
Daily checks are helpful for high transaction volumes. At a minimum, reconcile each published payout and review outstanding items according to the marketplace cycle.
4. What if the settlement report matches but no money has arrived?
Check the due date, payout reference, destination account, and bank status. Escalate an overdue transfer with the settlement ID and supporting evidence.
5. Can reconciliation be automated?
Matching can be partly automated if the system has access to order, settlement, POS, and bank data. Refunds, adjustments, and exceptions still require validation rules and finance oversight.
Conclusion
Accurate marketplace reconciliation links order IDs, merchant-entitled sales, settlement deductions, and actual bank credits. The objective is not to equate gross sales with bank receipts, but to maintain a traceable explanation for every variance and correction.
As order volume and outlet count increase, disconnected spreadsheets become difficult to maintain. Restaurants need connected transaction and finance records, payout identifiers, outstanding statuses, and clear controls for refunds and adjustments.
For more structured financial operations, ESB Core provides financial reports, automated journal entries, and bank reconciliation. Confirm supported marketplace integrations and payout-matching workflows with the ESB team before relying on automated settlement checks.
