Restaurant finance guide · Singapore
How to Reconcile Restaurant Delivery Payouts in Singapore (Step-by-Step)
To reconcile a restaurant delivery payout, total the batch’s gross sales, then subtract refunds, merchant-funded promotions and fees to calculate the expected payout. Match that amount to the relevant bank deposit, calculate the difference, and investigate any mismatch against the platform and bank records. This guide gives Singapore restaurant operators a copyable spreadsheet layout, a fictional S$ worked example, and a repeatable process for each outlet and payout batch. The key is to record every component once and check timing before treating an unmatched amount as a shortfall.
Head of AI Finance Operations team from ccMonet
Experienced leader in AI-powered accounting services with 5+ years experience and AI-powered accounting services enthusiast. This guide focuses on traceable records, careful payout matching and exception review for restaurant finance workflows.
What Is Restaurant Delivery Payout Reconciliation? (Quick Definition)
Restaurant delivery payout reconciliation is the process of comparing a delivery platform’s sales and adjustment records with the payout it says it owes, then matching the expected amount to the bank deposit. It helps restaurant operators check that sales, refunds, merchant-funded promotions and fees have been accounted for consistently. Restaurants can use it batch by batch and outlet by outlet to identify records that need further checking.
What to Track in Each Payout Batch
Open the worksheet in Excel or Google Sheets. Replace the fictional example, then copy the formula cells down for new payout batches.
Foodpanda merchant settlement example
Start with the exact Foodpanda settlement period and batch reference. Match the batch to the bank deposit, then identify commission, refunds or merchant-funded promotions already deducted in the statement before entering any adjustment. If a refund or correction falls in the next payout cycle, log it as an open exception and clear it against the next statement. Use your merchant statement and agreement to confirm which deductions apply.
See the GrabFood and Foodpanda commission reconciliation guide.
Identify the outlet and batch
Record the outlet, platform and order or batch ID. Those identifiers make it easier to trace a spreadsheet line back to the relevant source records.
Separate sales and deductions
Keep gross sales, refunds, merchant-funded promotions and fees in separate fields. This makes the expected payout calculation visible and helps guard against subtracting a component twice.
Match the deposit, not just the platform total
Compare the expected payout with the corresponding bank transaction. Payout and deposit dates can differ, so check the source dates and subsequent bank activity before concluding that a mismatch is unexplained.
Use matching details to investigate
Compare transaction amounts, dates and descriptions when checking records. Keep source-to-ledger evidence together with your restaurant bookkeeping records.
Illustration: compare amount, date and description while reviewing transaction matches.
Quick Answer (Do This First)
For each payout batch, use one spreadsheet row at the same level of detail and apply the same calculation:
- Gather platform sales, payout and adjustment records, plus the matching bank transaction record.
- Label the row with the outlet, delivery platform and order or batch ID.
- Enter gross sales, refunds, merchant-funded promotions and fees from their supporting records.
- Calculate expected payout: gross sales − refunds − merchant-funded promotions − fees.
- Subtract expected payout from the actual bank deposit to find the difference.
- Check dates and subsequent bank activity if the deposit does not appear to match the batch.
- Record what you checked and mark the item matched, pending or requiring follow-up.
Copyable template: the table below uses one row per payout batch. Select and copy it into your spreadsheet, then add a separate row for each batch.
Prerequisites (What You Need)
- A spreadsheet with one row per payout batch.
- Delivery-platform sales, payout and adjustment records for the period.
- The restaurant’s bank statement or transaction record for the same period.
- Outlet, platform and order or batch identifiers from the source records.
- Access to the records needed to confirm sales, deductions and deposits.
Step-by-Step: Reconcile Restaurant Delivery Payouts
Restaurant delivery payout reconciliation template
One row per payout batch · amounts in S$
| Outlet | Platform | Order or batch ID | Gross sales (S$) | Refunds (S$) | Merchant-funded promotions (S$) | Fees (S$) | Expected payout (S$) | Actual bank deposit (S$) | Difference (S$) | Status / notes |
|---|---|---|---|---|---|---|---|---|---|---|
Expected payout = gross sales − refunds − merchant-funded promotions − fees
Difference = actual bank deposit − expected payout
Worked example: fictional Singapore restaurant
The figures below are fictional and illustrate the formula for a single delivery payout batch.
| Gross sales | S$1,000 |
|---|---|
| Fees | (S$200) |
| Refunds | (S$50) |
| Merchant-funded discounts | (S$30) |
| Expected payout | S$720 |
| Actual bank deposit | S$700 |
| Difference: actual − expected | (S$20) |
The expected payout is S$1,000 − S$50 − S$30 − S$200 = S$720. The difference is S$700 − S$720 = −S$20, meaning S$20 remains to investigate. Check the platform payout or transaction statement and the bank record before deciding how to record it.
-
Step 1: Gather the supporting records
What to do: Export the platform’s relevant sales, payout and adjustment records. Obtain the restaurant bank statement or transaction record for the same period.
Success looks like: You have the platform and bank records needed to check the same payout period.
Common mistake to avoid: Comparing a platform batch with bank activity from an unrelated period.
-
Step 2: Identify the outlet and payout batch
What to do: Add the outlet, delivery platform and order or batch ID to the spreadsheet row before entering amounts.
Success looks like: The row can be traced to a particular outlet, platform and source-record batch.
Common mistake to avoid: Combining outlets or payout batches in one row without a clear source reference.
-
Step 3: Enter each component once
What to do: Record gross sales, refunds, merchant-funded promotions and fees separately, using their supporting records. If an export already shows a net figure, check its contents before entering deductions.
Success looks like: Each component in the calculation has a source and is included once.
Common mistake to avoid: Subtracting fees or refunds again when the starting figure is already net of that item.
-
Step 4: Calculate the expected payout
What to do: Apply the formula: gross sales − refunds − merchant-funded promotions − fees. Keep the formula consistent for every batch.
Success looks like: The expected amount can be recalculated from the four component fields.
Common mistake to avoid: Mixing batch totals with order-level totals, which can count the same activity twice.
-
Step 5: Compare the expected payout with the bank deposit
What to do: Find the corresponding bank deposit and calculate actual bank deposit − expected payout. Use the actual amount shown in the bank record.
Success looks like: The spreadsheet shows a zero difference for a matching deposit or a clearly recorded amount to investigate.
Common mistake to avoid: Treating a non-zero difference as proof of an error before checking deposit timing and source records.
-
Step 6: Investigate and document the outcome
What to do: Check for a payout that has not arrived yet, a deposit recorded in a different period, an incorrect outlet or batch match, or missing or duplicated transactions. Note the source checked and whether the item is matched, pending or needs follow-up.
Success looks like: Each difference has a documented status and a clear next step, where needed.
Common mistake to avoid: Recording a conclusion without checking the platform statement and bank record.
Validation Checklist (Make Sure It Worked)
- ☐ Each spreadsheet row represents one payout batch, not a mixture of batch and order totals.
- ☐ Each row identifies an outlet, delivery platform and order or batch ID.
- ☐ Gross sales, refunds, merchant-funded promotions and fees are recorded separately.
- ☐ Each deduction is included once and can be traced to a supporting record.
- ☐ Expected payout follows the stated formula.
- ☐ Actual deposit is taken from the relevant bank transaction record.
- ☐ Difference is calculated as actual deposit minus expected payout.
- ☐ Deposit timing and subsequent bank activity have been checked for unmatched items.
- ☐ The status or notes field records what was checked and what happens next.
Common Issues & Fixes
| Problem | Cause to check | Fix |
|---|---|---|
| Expected payout is higher than the deposit | The payout may not have arrived yet, may be recorded in a different period, or a component may be missing or duplicated. | Compare the platform payout statement with the bank record, check subsequent bank activity, and verify each component once. |
| One batch does not match the bank transaction | The outlet or batch may be matched incorrectly, or the deposit date may differ from the platform date. | Recheck the outlet and batch ID against both source records, then review the relevant dates and subsequent bank activity. |
| The difference appears too large | A net platform figure may have been used as gross sales, or the same fee or refund may have been subtracted twice. | Inspect how the platform export presents the starting figure and recalculate using only supported components. |
| Rows cannot be traced back to their sources | The spreadsheet is missing an outlet, platform or order or batch identifier. | Add those identifiers and retain a note of the source record checked for each reconciliation item. |
Best Practices (Do It Right Long-Term)
- Use one row per payout batch — it keeps the level of detail consistent and helps prevent duplicate totals.
- Keep sales and each deduction in separate columns — it makes the payout calculation easier to review.
- Record outlet, platform and batch IDs — those details make source checks more traceable.
- Capture dates from the source records — payout and bank deposit dates may differ.
- Check whether figures are gross or net before calculating — it helps avoid subtracting a deduction twice.
- Document the source and resolution for each exception — another reviewer can see what has been checked.
- Use a consistent approach across outlets — it makes batch-to-batch review clearer.
If you maintain reconciliation procedures alongside broader bank reconciliation checks and multi-outlet bookkeeping, make sure each process identifies the source records it relies on.
Recommended Tool (Optional): ccMonet
For teams considering a supported reconciliation workflow, ccMonet describes a process that can propose transaction matches and flag exceptions for review. Connectivity and professional review depend on setup and scope; the spreadsheet method above can also be used on its own.
- Transaction matches can be proposed for review rather than relying only on manual comparison.
- Exceptions can be flagged for follow-up against source and bank records.
- Reviewers can use a structured workflow to check unmatched items and document outcomes.
Learn about ccMonet bank reconciliation, or see its F&B information.
Use a tool when you want a supported workflow for transaction matching and exception review; do not rely on it instead of checking the underlying platform and bank records.
FAQs
What is restaurant delivery payout reconciliation?
Restaurant delivery payout reconciliation compares platform sales and adjustment records with the payout expected for a batch, then checks that amount against the bank deposit. The calculation accounts for gross sales, refunds, merchant-funded promotions and fees. It helps a restaurant identify items that need checking and document whether a payout is matched, pending or requires follow-up.
What is the formula for expected delivery payout?
Expected payout equals gross sales minus refunds, merchant-funded promotions and fees. Keep each component separate so the calculation can be checked against supporting records. First confirm whether the platform’s starting figure is gross or already net of deductions.
What does a negative difference mean?
With the formula in this guide, difference equals actual bank deposit minus expected payout. A negative result means the bank deposit recorded is lower than the expected payout for that row. It is a prompt to investigate, not by itself proof of an error or an unexplained shortfall.
Should I reconcile delivery payouts by order or by batch?
The template here uses one row per payout batch. Keep the same level of detail throughout and do not add order-level totals again to batch totals. If you use a different level of detail, make sure the figures are not counted twice.
What if the platform payout and bank deposit have different dates?
Record the dates shown in the platform and bank source records rather than assuming they must be identical. Check subsequent bank activity before treating an unmatched payout as an unexplained difference. Note what you checked and whether the item remains pending or needs follow-up.
Conclusion
A repeatable delivery payout reconciliation comes down to four things: identify the batch, record each sales and deduction component once, calculate the expected payout, and compare it with the bank deposit. When amounts differ, check the platform and bank records, including dates and subsequent activity, before deciding what the difference means. Use the copyable template as a starting point, and explore restaurant payout reconciliation guidance when refining your process.