Restaurant Reporting: Delivery App Payout Reconciliation

Restaurant reporting helps Saudi operators reconcile delivery-app order records with platform settlement reports and actual bank deposits. Compare completed orders, commissions, refunds, promotions, and other adjustments using shared order and payout identifiers. Separate order dates from settlement dates, investigate missing or duplicate entries, and measure payout variance before monthly close. A consistent reconciliation workflow strengthens branch controls, supports finance teams, and reveals channel profitability without mistaking payouts for sales revenue.

Which Restaurant Reports Support Reconciliation?

Restaurant reporting requires matching operational orders with platform financial statements and actual bank deposits. Order totals alone cannot explain settlement differences because platforms may deduct commissions, refunds, and other charges.

A reliable reconciliation process uses the following records:

Order Reports: Show order IDs, branches, amounts, transaction dates, and completion or cancellation statuses.
POS Records: Provide the restaurant's recorded sales, taxes, discounts, and order references.
Settlement Reports: Detail platform payouts, commissions, refunds, adjustments, and other applicable deductions.
Bank Statements: Confirm the actual amount received and the date funds reached the restaurant's account.
Refund Reports: Identify customer reimbursements and the portion charged to the restaurant.
Commission Agreements: Establish the contractual rates and fee rules used to verify marketplace deductions.

These records should use consistent branch, channel, and transaction identifiers to support accurate order reconciliation.

The LYNNC restaurant operations platform provides centralized visibility into supported delivery-app orders and branch performance, forming an operational basis for reconciliation.

Orders vs Platform Payout Records

Order reports show customer transactions, while payout records explain how much the delivery platform owes or transfers to the restaurant after applicable adjustments.

A completed order does not necessarily generate an equivalent bank deposit. The difference becomes clearer when the records are separated into three stages.

1. Operational Order Records

Order Identification: Record the platform order ID, branch, channel, and transaction timestamp.
Order Status: Distinguish completed sales from canceled, rejected, or pending transactions.

2. Platform Settlement Records

Financial Adjustments: Identify commissions, restaurant-funded discounts, refunds, and additional charges.
Payout Reference: Link eligible transactions and adjustments to the platform's settlement statement.

3. Bank Deposit Records

Transferred Amount: Match the settlement total with the amount actually received.
Transfer Timing: Verify the deposit date and reference before classifying a payment as missing.

Workflow and Operational Acceptance Criteria

Before using restaurant reporting for financial reconciliation, operators should test the complete transaction-matching process.

Order Matching: Confirm that completed platform orders can be associated with their settlement entries.
Amount Verification: Compare recorded sales with the relevant payout components using consistent tax and discount definitions.
Refund Tracking: Verify that adjustments remain linked to the original transactions, even when processed later.
Branch Accuracy: Ensure that every settlement item belongs to the correct restaurant location.
Deposit Matching: Confirm that final settlement totals can be matched to actual bank deposits.
Exception Reporting: Identify unmatched transactions without incorrectly treating every timing difference as a loss.

Commission, Refunds and Adjustments

Restaurant delivery commissions reduce the amount transferred to restaurants, but they are only one component of marketplace deductions.

Accurate settlement reporting should separate each adjustment according to its commercial and accounting treatment.

1. Marketplace Commissions

Commission Rate: Verify deductions against the contract and the correct commissionable sales amount.
Additional Charges: Record applicable service fees and taxes on fees separately where required.

2. Refunds and Cancellations

Customer Refunds: Identify amounts charged to the restaurant rather than assuming every refund is merchant-funded.
Late Adjustments: Match refunds appearing in later settlement periods to their original orders.

3. Promotions and Other Adjustments

Restaurant-Funded Discounts: Record promotional costs borne by the restaurant without deducting them twice.
Platform-Funded Credits: Identify reimbursements or incentives added to the restaurant's settlement.
Other Deductions: Review disputed charges, corrections, and contractual adjustments individually.

Example: Calculating an Expected Platform Payout

Consider a hypothetical Saudi restaurant settlement with the following amounts:

Settlement Component	Amount
Merchant-entitled order proceeds before listed adjustments	SAR 10,000
Marketplace commissions	−SAR 1,500
Restaurant-funded promotions	−SAR 200
Refunds charged to the restaurant	−SAR 300
Other applicable deductions	−SAR 100
Platform adjustment credit	+SAR 50
Expected Net Payout	SAR 7,950
Net payout shown by platform	SAR 7,900
Unexplained Payout Variance	SAR 50

Illustrative settlement amounts only. The starting proceeds must include only amounts owed to the merchant before the listed deductions. Taxes, discounts, and adjustments must follow the platform's actual settlement definitions.

Expected Payout = Merchant-Entitled Proceeds + Settlement Credits − Commissions − Merchant-Funded Promotions − Merchant-Borne Refunds − Other Deductions

Payout Variance = Expected Payout − Reported Platform Net Payout

The SAR 50 difference requires investigation before the settlement can be marked fully reconciled.

This variance does not automatically mean the restaurant has lost SAR 50; the cause may be an unrecorded fee, credit, or timing adjustment.

Matching Orders to Settlement Periods

A transaction's order date may differ from its settlement date and bank deposit date. Restaurant reporting must preserve these differences to prevent false discrepancies.

A consistent matching process follows four steps.

Step 1: Identify the Order Date

Record when the customer placed the order and when the transaction became eligible for settlement.

Step 2: Confirm the Platform Settlement Period

Use the reporting period defined by the platform rather than assuming all orders settle at month-end.

Step 3: Match Settlement References

Connect order-level payment entries to the relevant payout batch using available platform references.

Step 4: Verify Bank Deposit Timing

Match the finalized payout to the bank transaction, accounting for processing delays and non-banking days.

For example, an order completed on March 31 may appear in an April settlement. It should remain traceable without being counted twice.

Platform reporting data may also receive later refunds or corrections, so financial teams should distinguish provisional results from finalized settlement information.

Handling Missing and Duplicate Records

Missing transactions and duplicate entries can distort both payout variance and reported channel profitability.

Instead of adjusting totals manually, finance teams should classify each exception and verify its source.

Reporting Exception	Possible Cause	Recommended Action
Order missing from settlement	Order is pending or outside the payout period.	Check status and settlement eligibility.
Order appears twice	Duplicate import or repeated transaction reference.	Compare unique identifiers and retain valid records.
Settlement item lacks an order	Fee, refund, or late adjustment.	Trace its source and original reference.
Incorrect commission	Wrong rate, base, or contractual adjustment.	Compare the statement with agreed terms.
Unexpected refund	Customer dispute or post-order correction.	Review the refund reason and merchant responsibility.
Branch mismatch	Incorrect location or account mapping.	Verify branch and merchant account identifiers.
Missing bank deposit	Pending transfer or settlement issue.	Review payout status and bank records.
Unexplained payout variance	Missing fee, credit, or transaction.	Investigate the unmatched components.

Controls to Prevent Recurring Errors

Unique Transaction Keys: Match records using stable order and payout identifiers rather than amounts alone.
Duplicate Detection: Flag repeated records before calculating financial totals.
Import Validation: Check missing fields, invalid values, and inconsistent statement formats.
Exception Ownership: Assign unresolved discrepancies to a finance or operations representative.
Correction History: Preserve original entries and maintain a traceable record of approved adjustments.

These controls reduce reconciliation errors while preserving the information required for later financial review.

Comparison: Automated vs Manual Reconciliation

Both methods can support accurate reconciliation, but they differ in data handling, scalability, and implementation requirements.

Comparison Factor	Manual Reconciliation	Automated Reconciliation
Data Collection	Staff download and organize reports.	Supported reports are imported through configured connections.
Order Matching	Employees compare transactions manually.	Matching rules associate eligible records.
Commission Review	Fees are checked using spreadsheets.	Configured fee rules identify expected deductions.
Duplicate Detection	Depends on manual checks and filters.	Rules can identify duplicate transaction keys.
Settlement Timing	Staff investigate different reporting periods.	Date and payout mapping can help separate periods.
Variance Detection	Differences are calculated manually.	The system can calculate and flag exceptions.
Error Investigation	Requires reviewing source files individually.	Linked records can support faster investigation.
Audit Trail	Depends on file storage and documentation.	Can maintain traceable imports and adjustment history.
Implementation Cost	Lower initial technology requirements.	May require software, integrations, and maintenance.
Main Limitation	Greater manual effort as order volume grows.	Depends on data access, integration quality, and configured rules.
Best Fit	Smaller operations with limited transaction volume.	Multi-branch restaurants with frequent settlement activity.

Automation does not eliminate the need for financial review. Unmatched records and unexpected adjustments still require authorized investigation.

Variance Dashboard and Monthly Close Checklist

A reconciliation dashboard should show unsettled orders, payout differences, overdue deposits, and unresolved deductions by branch and platform.

Unlike general sales dashboards, it must identify why reported marketplace earnings differ from expected and received amounts.

Essential Variance Dashboard Metrics

Metric	Formula or Measurement	Management Purpose
Expected Payout	Proceeds plus credits less applicable deductions.	Estimate the amount due from the platform.
Payout Variance	Expected Payout − Reported Net Payout	Identify differences between order and settlement records.
Bank Deposit Variance	Reported Net Payout − Matched Bank Deposits	Identify differences between platform statements and received funds.
Unmatched Orders	Number of eligible orders without a settlement match.	Locate missing financial records.
Unexplained Deductions	Total deductions without an accepted explanation.	Identify fees requiring investigation.
Outstanding Settlements	Finalized payouts not yet matched to bank deposits.	Track amounts awaiting receipt or verification.
Aged Exceptions	Unresolved discrepancies grouped by age.	Prioritize overdue reconciliation issues.

A platform payout difference and a bank deposit difference should be investigated separately.

If the platform reports SAR 7,900 and the bank receives SAR 7,900, the bank deposit variance is zero—even if the expected payout remains SAR 7,950.

Monthly Close Checklist

A structured monthly close helps finance teams confirm settlement completeness and preserve supporting records.

1. Collect Finalized Reports

Platform Statements: Gather available settlement reports and adjustments for every connected delivery account.
Operational Records: Export the corresponding order and POS records using consistent branch identifiers.

2. Reconcile Orders and Fees

Transaction Matching: Match eligible orders with settled entries and document outstanding exceptions.
Commission Verification: Check fees, refunds, promotions, and corrections against supporting records.

3. Confirm Bank Transfers

Deposit Matching: Match payout references, amounts, and dates with bank transactions.
Outstanding Amounts: Record pending or disputed transfers without treating them automatically as missing revenue.

4. Validate Financial Records

Accounting Classification: Separate sales revenue, applicable VAT, platform fees, and settlement receivables.
Document Retention: Maintain the invoices, credit notes, and supporting records required under applicable Saudi regulations.

5. Approve the Monthly Reconciliation

Exception Resolution: Document unexplained differences and assign owners with review deadlines.
Finance Approval: Sign off on reconciled settlements and carry documented outstanding items into the next period.

How Reconciliation Supports Channel Profitability

Settlement reconciliation confirms payment completeness, while channel profitability measures the financial contribution of completed orders.

The two reports should remain distinct because a bank payout is not equivalent to revenue or profit.

Channel Contribution = Net Channel Revenue − Food Cost − Packaging Cost − Marketplace Commissions − Payment Fees − Merchant-Funded Delivery Cost − Attributable Promotions − Other Variable Costs

Finance teams can use verified settlement fees alongside POS and cost records to assess channel profitability without confusing payouts with sales.

For multi-location controls, see Restaurant Branch Management.

Connect Order Visibility With LYNNC

LYNNC provides centralized delivery-app order management, operational status tracking, and reports covering orders, sales, and branch activity across supported channels.

These capabilities help establish the operational records needed for a structured reconciliation process.

Explore LYNNC restaurant order management and analytics to review supported integrations and request a demonstration.

Before implementation, confirm the availability of payout exports, fee data, settlement matching, accounting integrations, and automated exception reporting.

For broader operational KPIs and channel contribution margin, read Restaurant Analytics for Saudi Chains: Channels, Branches and Margin. This reconciliation guide focuses specifically on platform settlements and bank deposits.

Request a LYNNC demo to verify supported channel order reports, available payout data, and how your finance team would reconcile third-party settlement and bank records.

Frequently Asked Questions About Restaurant Reporting

Why Do Delivery App Payouts Differ From Order Totals?

Restaurant reporting may show differences because platforms deduct commissions, refunds, merchant-funded promotions, and other adjustments. Settlement timing can also affect comparisons.

How Are Restaurant Delivery Commissions Recorded?

Commissions should be recorded as applicable platform expenses, with their accounting and tax treatment based on the relevant invoices and agreements.

How Do Refunds Change Settlement Amounts?

Refunds charged to the restaurant reduce the amount payable or appear as adjustments in a later settlement, depending on platform rules.

Can Order Reports Support Restaurant Finance Teams?

Yes. Order reports support transaction matching and investigation, but accurate reconciliation also requires settlement statements, bank records, and financial adjustments.

Restaurant Reporting: Reconcile Delivery App Payouts and Order Records