# Food Delivery App Payout Reconciliation for Restaurants

- Author: PreciseBankFlow (https://precisebankflow.com)
- Published: 2026-10-17
- Category: Payment and deposit reconciliations
- Canonical: https://precisebankflow.com/blog/food-delivery-app-payout-reconciliation

> Food delivery app payout reconciliation for restaurants: order reports, commissions, promotions, adjustments and tying weekly payouts to the bank.
Food delivery app payout reconciliation ties each payout a restaurant receives from a delivery app back to the orders it covers and forward to the bank deposit. Start from order subtotals and tax, subtract commissions, marketing costs, error charges and adjustments, and the result should equal the net payout that reached the bank on the payout date.

## What is in a food delivery app payout?

A food delivery app payout is the net of everything that happened to the restaurant's orders on that app during one payout period. It starts with the menu value of the orders, adds tax passed through, and subtracts the app's commission, the restaurant's share of promotions and any charges for problem orders. The bank receives only the final figure.

DoorDash's merchant guide to [understanding the payout and the monthly statement](https://merchants.doordash.com/en-us/learning-center/payout-and-monthly-statement) is a useful example of the parts. It lists the payout date, payout ID, status, sales, commission and fees, marketing spend, amendments and net payout. It defines the order subtotal as the price before taxes, commissions, fees, error charges and tips, and describes error charges as charges that cover reimbursements to customers for missing or incorrect items.

Other apps use their own labels, but the same groups usually appear:

- **Order subtotals:** the menu value of the food sold.
- **Tax:** collected from the customer and either passed to the restaurant or remitted by the app, depending on the location.
- **Commission and fees:** the app's charge per order, sometimes at different rates for delivery and pickup.
- **Marketing:** discounts, free-delivery offers and paid promotions the restaurant agreed to fund.
- **Error charges:** deductions for customer refunds on missing or wrong items.
- **Adjustments:** corrections and additions, including money returned after a disputed error charge.
- **Tips:** usually paid to the courier, not to the restaurant, so they often do not appear in the payout at all.

## Food delivery app commissions and promotions in the books

Food delivery app commissions and promotions should be booked as expenses, with sales recorded at the order subtotal. Recording the payout as sales would understate revenue by the commission and the promotions, and the owner would never see what the app costs. Each payout becomes one entry: gross sales and tax in, costs out, net to a clearing account.

A simple account structure for each app:

| Payout part | Example account |
| --- | --- |
| Order subtotals | Sales: delivery app (one per app if the owner wants to compare) |
| Tax passed to the restaurant | Sales tax payable |
| Commission and fees | Delivery app commission expense |
| Marketing and promotions | Delivery app marketing expense |
| Error charges | Delivery app refunds, a contra-sales account |
| Adjustments | Reverse the account the original charge went to |
| Net payout | Delivery app clearing account |

Promotions deserve a careful read. A discount the restaurant funded reduces what it receives, so it is a real cost. A discount the app funded on its own should not reduce the payout at all. If the payout report shows a promotion the owner does not remember agreeing to, check the app's marketing settings before booking it.

Commission rates can differ by order type and by plan. If commission as a share of subtotal moves from one payout to the next, the order mix or the plan changed, and the owner should know which.

## Error charges and adjustments in a delivery app payout

Error charges and adjustments are the parts of a delivery app payout that change after the orders are complete. An error charge takes back money for a refund the app gave a customer. An adjustment adds or corrects an amount, sometimes for an earlier period's order. Both make a payout differ from the orders delivered in that period.

Error charges are the line restaurants most often dispute. Each one names an order, a reason and an amount. Keep a log with the order number, the reason the app gave, whether the kitchen agrees, and whether a dispute was raised. When a dispute succeeds, the money usually returns as an adjustment in a later payout. The log lets you match the adjustment to the original charge instead of treating it as new revenue.

Watch the pattern as well as the amounts. A run of error charges on one item points to a kitchen or packaging problem. A run of claims from one customer, or for high-value orders only, can point to refund abuse. [How fraudulent refunds work and how to spot them](/blog/fraudulent-refunds) covers the patterns a reviewer should look for.

Adjustments for orders outside the payout period break the simple rule that a payout equals its own orders. Note each such adjustment in the tie-out with the order date it relates to, so the period it belongs to is clear.

## Tying each delivery app payout to the restaurant bank deposit

Each delivery app payout should appear once on the bank statement, for the net payout amount, within a few business days of the payout date. Match them one to one by amount and date. A restaurant on several apps sees several payout streams, so keep one clearing account per app.

Steps for one month:

1. Export the list of payouts from each app, with payout ID, date and net amount.
2. Tick each payout against a bank credit of the same amount.
3. Note the bank's description for each app's credits; it is usually consistent and helps the next month.
4. Move each matched payout from the app's clearing account to the bank.
5. At month end, the clearing account should hold only payouts dated in the month that reached the bank in the next one.

Payouts arrive by ACH, so they appear as single credits from the app's bank, sometimes alongside other ACH credits on the same day. [ACH batch deposit reconciliation](/blog/ach-batch-deposit-reconciliation) covers splitting and matching batch credits when a summary statement merges them. For the broader method of tying processor reports to the ledger and the bank, see [payment reconciliation across processor, ledger and bank](/blog/payment-reconciliation).

If a payout status in the app shows as paid but no bank credit arrives, check that the bank account on file in the app is the one you are reconciling. Restaurants that change banks sometimes leave an old account in one app.

## Worked example: one delivery app payout tied to orders and the bank

The table below is an invented example for an illustrative restaurant. It covers one payout period on one app and walks from the order subtotal to the bank credit. The figures are made up to show the arithmetic, not to suggest real rates.

| Line (example) | Amount |
| --- | ---: |
| Order subtotals, 142 orders | 4,860.00 |
| Tax passed to restaurant | 388.80 |
| Commission and fees | (1,069.20) |
| Marketing: restaurant-funded discount | (215.00) |
| Error charges, 3 orders | (46.75) |
| Adjustment: error charge reversed from prior period | 18.50 |
| Net payout | 3,936.35 |
| Bank credit, three business days after the payout date | 3,936.35 |

Check the arithmetic: 4,860.00 plus 388.80, less 1,069.20, 215.00 and 46.75, plus 18.50, equals 3,936.35. The bank credit agrees. The entry records sales of 4,860.00, tax payable of 388.80, commission expense of 1,069.20, marketing expense of 215.00, refunds of 46.75, a refund reversal of 18.50, and 3,936.35 to the clearing account, cleared when the bank credit posts.

Two extra checks finish the example. First, the 142 orders in the app should agree with the delivery app orders in the restaurant's own records for the same dates. Second, the commission works out to 22% of subtotal in this example; if that figure jumps next period, find out why.

## Why does the delivery app monthly statement differ from the payouts?

A delivery app monthly statement differs from the payouts because the statement covers orders by calendar month while payouts cover payout periods that often cross month end. The payouts dated in a month include orders from the end of the previous month and leave out the last days of the current one.

DoorDash's guide says monthly statements are available by the 5th day of each month and that the monthly statement differs from the sum of payouts in the month because payout dates are not the same as transaction dates. To see every transaction in a calendar month rather than payouts, it points restaurants to the Transactions view filtered by month.

A practical approach is to use both reports for different jobs. Use the payouts to tie to the bank, because each payout is one bank credit. Use the monthly statement, or the transaction report for the month, to record sales and costs in the right period. The difference between the two is the clearing account balance: orders completed in the month whose payout lands in the next.

## Mistake: counting delivery app orders twice in point-of-sale sales

Counting delivery app orders twice in point-of-sale sales happens when the app sends its orders into the restaurant's POS, and the bookkeeper records both the POS sales total and the app payout as revenue. Sales are then overstated by the app's whole order value. The mistake is easy to miss because both figures look like real money.

Many restaurants connect delivery apps to their POS so that the kitchen sees every order in one place. In that setup, the POS daily sales report already includes the app orders, usually as a separate tender or order type. If the bookkeeper records POS sales from that report and then records each app payout as sales too, the app orders are counted twice.

The fix is to choose one source for delivery app revenue:

- **Record from the POS:** take the app orders from the POS report, posted to the app's clearing account rather than to cash or card, and record the payout only as a transfer from clearing to bank, with costs.
- **Record from the app:** exclude the app tender from the POS sales posting, and record sales from the app's payout or monthly report.

Either works, as long as the clearing account empties as payouts arrive. A clearing account that grows month after month is the sign that orders are being recorded twice or a payout was missed.

PreciseBankFlow reads the restaurant's bank statements, checks that each one foots, and matches every credit to the ledger, so a payout with no matching entry or a deposit booked twice shows on the exception report. The [PreciseBankFlow homepage](/) describes how it works.