Foodpanda Payout Reconciliation for Restaurants
A weekly control for proving that accepted orders, statement deductions and bank deposits agree.
Last verified: 2026-08-28
Foodpanda payout reconciliation means matching five records for the same settlement period: accepted orders, POS channel sales, the partner statement, fee or tax invoices and the bank deposit. If the dates and order IDs do not align, revenue can look correct while cash and margin are wrong.
Reconcile every week and at month-end. foodpanda directs partners to its portal for performance information and support; download the relevant records from the account rather than rebuilding deductions from memory.
The five-way match
| Record | What it proves | Main check |
|---|---|---|
| Marketplace orders | Accepted and completed sales | Order ID and status |
| Restaurant POS | Kitchen and channel record | No missing or duplicate entry |
| Settlement statement | Deductions and net amount | Period and adjustment lines |
| Invoice | Fee and tax evidence | Amount and reference |
| Bank statement | Cash received | Value date and net deposit |
Expected payout formula
Start with the gross value defined by the statement, then subtract commission, taxes on fees where invoiced, restaurant-funded promotion, refunds or cancellations, advertising and other contract adjustments. Add or subtract corrections exactly as labelled. The result should match the stated net settlement before any bank-side charge.
Do not invent a standard list of deductions. Packages and campaigns vary. Use the current agreement and raise unclear lines through official partner support.
A weekly reconciliation routine
- Lock one settlement date range
- Export accepted and completed order IDs
- Compare each ID with the POS channel record
- Group cancellation and refund reasons
- Tie every deduction to a statement or invoice line
- Match the net amount to the bank
- Save evidence and unresolved differences
Common differences and fixes
Date cut-off is the most common false difference: an order can be placed in one period and settled in another. Other causes include duplicate manual entry, cancelled items recorded as sales, campaign funding misunderstood, an adjustment carried from an earlier period or a payout split across deposits.
Never force the difference into sales. Keep it in an unresolved reconciliation account with order references until the portal statement, support reply or next settlement explains it.
Month-end accounting pack
Keep the order export, settlement statement, invoice, bank proof, issue log and the final reconciliation summary together. This makes management review and VAT or accounting work easier and preserves the reason behind corrections.
Access should be controlled. One staff member prepares the reconciliation and another reviews the bank match and large adjustments. Separation catches both mistakes and unauthorised changes.
Using POS channel data
Channel tagging in Rosuii helps confirm whether every marketplace order reached the kitchen and sales report. It does not replace the official marketplace statement or bank evidence.
Use one naming rule for Foodpanda across every branch, close duplicate orders promptly and compare the POS channel total with the accepted-order export before analysing profit.
Build three linked datasets
Keep restaurant orders, foodpanda order or transaction report, and payout or statement records separately, joined by stable platform and internal order IDs. Do not reconcile only a bank deposit to gross sales; the net can contain several order periods, refunds, promotions, taxes or adjustments.
Use the current partner agreement and statement definitions. This article does not assume one commission or payout period.
Reconciliation fields
Keep unconfirmed lines unresolved. Do not force a match by changing restaurant sales or combining unrelated adjustments.
| Field | Source | Check |
|---|---|---|
| Order ID | Platform report | Unique mapped order |
| Order state | Current report definition | Completed/cancelled/refunded |
| Gross item value | Statement/order report | Same tax basis |
| Discount | Funding attribution | Restaurant/platform/customer |
| Fees | Agreement and statement | Type and basis |
| Refund/adjustment | Case and statement | Reason/order link |
| Payout | Statement and bank | Reference/date/amount |
Order-to-statement matching
Normalize identifiers and amounts without discarding original fields. Match exact IDs first, then investigate outlet mapping, period boundary, refund timing, duplicate export and manual order. A date-only or amount-only match can connect the wrong order.
Record unmatched, duplicated and changed-state cases with owner and due date. Preserve the downloaded source and extraction time.
Payout-to-bank close
A statement can be internally reconciled but not yet received. Keep payout expected, initiated, received and disputed as different states.
- Statement net amount
- Payout identifier
- Initiated and received dates
- Bank account and reference
- Partial or combined payout
- Withheld or carried adjustment
- Currency/tax basis
- Unreceived amount
- Reviewer and close status
Dispute pack and recurring review
Prepare the platform order ID, statement period, exact disputed line, restaurant evidence, prior support reference and requested resolution. Redact unrelated customer and payment data. Submit through the official partner route and record response.
At close, lock the period and carry later corrections as visible adjustments. Review repeated cancellation, promotion and mapping causes, but do not publish private commercial rates or performance without approval.
Maintain a reconciliation control sheet showing source filenames, report period, extraction time, row counts, calculated expected payout, statement net, bank received, open difference and reviewer. Preserve formulas and mappings as versioned logic. When report columns change, stop automated import, compare the new definition and rerun a sample before posting. Restrict bank and contract data to finance roles, and give operations only the order exceptions they need to resolve.
A payout is trusted only after the order list, deductions and bank cash agree. A short weekly routine prevents small unexplained differences from accumulating into an unreliable month-end number.
Related guides
- Foodpanda Commission Rate in Bangladesh
- Restaurant Daily Accounting
- Manage Delivery Marketplace Orders
- Compare restaurant management software
See this workflow in Rosuii: Review Rosuii order and reporting workflows
Sources checked
Updated:
Frequently asked questions
What is Foodpanda payout reconciliation?
How often should a restaurant reconcile?
Why does the order total not match the bank deposit?
What should I do with an unexplained deduction?
Can a POS replace the Foodpanda statement?
How do restaurants reconcile foodpanda payouts?
Why does the bank deposit not equal gross foodpanda sales?
Should unmatched items be edited away?
How should a payout reconciliation be reviewed?
Run your restaurant on Rosuii
POS, menu, inventory, payroll and more — built for Bangladeshi restaurants.
Start free
