Restaurant Delivery Aggregator Reconciliation: Match Orders, Fees, Refunds and Payouts

Third-party delivery platforms often deposit a net amount that looks nothing like the sales the restaurant remembers.

Gross orders are reduced by commissions or commercial fees, promotions, refunds, adjustments, taxes handled under the platform arrangement, delivery-related charges, chargebacks or other statement lines. Payout timing can also cross accounting periods.

Delivery aggregator reconciliation explains the bridge from customer order to platform statement to bank deposit.

Define the reconciliation chain

For each platform and settlement period, connect four records: platform order report, restaurant POS/order record, platform financial statement and bank deposit.

If one link is missing, management can see money moved but cannot explain why.

Use gross order value as the starting point

Start from the platform’s reported restaurant sales/order amounts for the defined period before fees and deductions.

Do not use the bank payout as ‘delivery sales.’ A net deposit hides the channel’s fees and adjustments.

Match orders to POS

Where the POS integrates with the platform, compare order count and gross sales. Where orders are entered manually, use platform order IDs or another controlled reference to test completeness.

Look for missing orders, duplicates, cancelled orders that remained in POS, and POS tickets without a matching platform order.

Build the payout bridge

Line	Question
Gross platform orders	What did customers order under the platform statement?
Restaurant-funded promotions	What discount cost belongs to the restaurant?
Platform-funded promotions	Is any support/credit shown separately?
Commissions/fees	What commercial charges were deducted?
Refunds/cancellations	Which orders were reduced or reversed?
Other adjustments	What does each statement line represent?
Net payout	What should reach the bank for this settlement?

Use actual platform contract/report fields

Do not apply a generic commission percentage. Platform economics vary by agreement, market, service and promotional arrangement.

The reconciliation should use the line items actually shown on the restaurant’s statement.

Separate taxes according to actual treatment

Tax collection/remittance can vary by jurisdiction and marketplace rules. The restaurant’s accounting treatment should follow the real platform statement and qualified accounting guidance.

Do not use an article to assume who remits which tax.

Separate restaurant-funded promotions

A platform promotion can increase orders while reducing restaurant contribution. Identify which discount amount is funded by the restaurant versus the platform.

Restaurant Promotion Profitability: Measure Discounts, Traffic and Contribution Before Repeating an Offer.

Track refunds by cause

Refunds can come from missing items, quality issues, delivery failure, cancellation, platform decision or other reasons.

Where data support it, group refunds by controllability: kitchen/order accuracy, packaging, handoff, courier/platform, customer dispute or unclear.

Investigate missing-item refunds

A missing-item refund may mean the kitchen omitted product, packer missed it, driver left without part of the order, or platform workflow split the order.

Use order/pack/handoff evidence before assigning blame.

Reconcile payout timing

One bank deposit may cover orders from several days. A month-end order may settle next month.

Use settlement IDs and payout dates so timing differences are not mistaken for missing revenue.

Match bank deposits

Net expected payout from the platform statement should match the bank deposit, allowing for clearly documented grouped payouts or timing.

Restaurant Bank Reconciliation for Operators: Match Deposits, Cards and Cash to the Books.

Track adjustments that are hard to classify

Create a short unresolved-adjustment queue. Each unusual debit/credit needs an owner, explanation and final classification.

Do not leave recurring ‘other adjustment’ amounts in one misc account without understanding them.

Calculate channel effective fee load

A management metric can express restaurant-funded platform fees/promotions and other selected direct channel costs as a percentage of gross platform sales.

Define the numerator clearly and use the same definition over time. It is an internal trend, not a universal benchmark.

Compare contribution by channel

If the restaurant has reliable food cost, packaging and platform cost data, compare order contribution between dine-in/direct order/platform.

Avoid false precision if labor or shared overhead cannot be allocated credibly.

Watch price synchronization

A price change that reaches POS but not the platform can create margin leakage or guest inconsistency.

Audit menu availability and modifiers

A platform may continue selling an unavailable item or outdated modifier. Reconciliation should flag unusual refund spikes that might trace to menu-sync failures.

Create a weekly reconciliation cadence

1. Download platform order and settlement reports.

2. Match order count and gross sales to POS/order records.

3. Review cancellations/refunds and restaurant-funded promotions.

4. Classify fees and adjustments.

5. Calculate expected net payout.

6. Match settlement to bank deposit.

7. Open unresolved exceptions.

8. Record effective channel cost and material variance.

9. Assign operational fixes for repeat refund causes.

Use a platform exception log

Exception	Owner	Evidence	Resolution
Missing payout	finance/manager	settlement ID + bank	follow-up
Duplicate POS ticket	ops	order ID + POS	correct process
Refund disputed	manager	order/pack record	platform case
Unknown adjustment	finance	statement line	classify

Example: sales look low because payout is net

The restaurant’s platform gross orders are $20,000 for a period but the bank receives $13,900. Without reconciliation, management may record $13,900 as sales.

The platform statement explains the difference through contract fees, restaurant-funded promotions, refunds and other documented adjustments. Sales and channel costs can then be recorded/analyzed correctly under the restaurant’s accounting method.

Example: payout matches but operations still has a problem

The financial reconciliation is perfect, but missing-item refunds doubled. The problem is not finance. The exception data sends operations to packaging/handoff control.

Manager monthly review

Gross orders and order count by platform.
Net payout and effective channel-cost trend.
Refunds/cancellations by cause.
Restaurant-funded promotion cost.
Unexplained adjustments.
POS/platform mismatches.
Price/menu sync issues.
Bank deposits not matched to settlement.
Operational actions from repeat exceptions.

Common reconciliation mistakes

Recording net payout as sales

Channel fees and deductions disappear from visibility.

Using a generic commission rate

Actual statement economics can differ.

Reconciling only the bank

The deposit can match while missing/refunded orders remain operational problems.

Ignoring settlement timing

Month-end differences are mistaken for missing money.

No owner for unknown adjustments

Small unexplained lines accumulate.

Frequently asked questions

How often should delivery payouts be reconciled?

Use a cadence frequent enough to catch exceptions while records are fresh—often weekly or per settlement depending on volume and staffing.

What commission rate should a restaurant expect?

Use the restaurant’s actual platform agreement and statement. Do not rely on a generic percentage.

Should delivery sales equal bank deposits?

No. Deposits are often net of fees, refunds, promotions or adjustments. Reconcile the bridge.

How should refunds be treated?

Follow the platform statement and the restaurant’s accounting policy, while separately analyzing operational causes.

Next action

Take one recent platform settlement. Starting with gross order sales, list every deduction/credit until you reach the payout amount, then match it to the bank. Any line you cannot explain becomes an exception with an owner—not a miscellaneous mystery.

Related guides: