How to Audit Delivery Platform Fees

Every restaurant operating on DoorDash, Uber Eats, or Grubhub should periodically audit its delivery platform fees. The gap between contracted commission rates and actual effective rates — driven by layered fees, refund deductions, and processing charges — means most restaurants are paying more than they realize. Without regular auditing, these discrepancies compound silently, draining revenue month after month.

This guide provides a practical, step-by-step audit workflow that any restaurant operator or bookkeeper can follow to verify delivery platform charges against actual order data and bank deposits. Whether you’re dealing with Uber Eats fees, DoorDash fees, or Grubhub fees, the same principles apply.

Why Restaurants Should Audit Delivery Platforms

The case for regular auditing is straightforward: delivery platform fee structures are complex enough that errors are statistically inevitable, and the only way to detect errors is to verify the math.

Consider the scale of the problem. A restaurant processing 1,200 delivery orders per month across two platforms has 2,400 individual transactions, each with its own commission calculation, potential refund adjustments, processing fees, and promotional deductions. Even a 1% error rate on these transactions produces 24 incorrectly charged orders per month — small enough to be invisible without systematic checking, but large enough to cost hundreds of dollars annually.

Based on industry data, restaurants that perform their first delivery fee audit typically discover discrepancies totaling 2–5% of gross delivery revenue. For a restaurant generating $35,000 per month in delivery orders, that’s $700 to $1,750 in monthly discrepancies — $8,400 to $21,000 annually. Understanding the types of overcharges that commonly appear is covered in our analysis of whether delivery platforms are overcharging restaurants.

Data Needed for Reconciliation

A complete delivery fee audit requires data from three sources:

1. Delivery Platform Payout Statements

Download the detailed, transaction-level payout data (not just the summary) from each platform for the audit period. This data should include individual order IDs, order amounts, commission deductions, fees, refund adjustments, and the net payout amount per order. For guidance on navigating DoorDash statements specifically, see our complete DoorDash statement guide.

2. POS Delivery Order Reports

Export your POS system’s delivery order data for the same period. This provides your record of what was ordered, when, and the expected revenue — the “source of truth” for order details.

3. Bank Deposit Records

Obtain your bank statement or transaction records showing the actual deposits received from each delivery platform during the audit period. This is the final verification layer — confirming that the net payout reported by the platform actually arrived in your account.

4. Merchant Agreement

Have your merchant agreement accessible to reference contracted commission rates, fee terms, and promotional program details. This is your contractual baseline for what you should be paying. For a refresher on how commission structures work, see our guide on how delivery platform commissions actually work.

Matching Orders to Statements

The first reconciliation step matches individual orders from your POS to the delivery platform statement:

1. Align the time period. Ensure the POS export and platform statement cover the same dates. Note that platform statements often batch orders from multiple days, so the edges of the period may not align perfectly.
2. Match by order ID. Most POS systems record the delivery platform order ID. Use this to create a one-to-one mapping between POS orders and statement line items.
3. Compare order amounts. For each matched order, verify that the order subtotal reported by the platform matches your POS record. Discrepancies here indicate potential issues with how the order was recorded.
4. Identify unmatched orders. Orders on the platform statement that don’t appear in your POS (or vice versa) require investigation. These may be cancelled orders, test orders, or data entry errors.

For DoorDash specifically, our dedicated DoorDash reconciliation guide walks through matching orders to statements and bank deposits with a detailed worked example.

Matching Payouts to Bank Deposits

The second reconciliation layer verifies that platform payouts actually arrive in your bank account:

1. Identify platform deposits in your bank statement. Each platform deposits on a regular schedule (typically weekly), and these deposits should match the net payout amount on the corresponding platform statement.
2. Account for timing differences. Bank deposits may post 1–3 business days after the platform processes the payout. Align dates accordingly.
3. Match amounts. The bank deposit should equal the net payout on the platform statement. If they differ, investigate whether processing fees, holdbacks, or other deductions were applied between the statement and the deposit.
4. Track cumulative variance. Small per-deposit variances can indicate systematic issues even when individual differences seem negligible.

Identifying Discrepancies

With orders matched and payouts verified, you can now identify specific discrepancies. The most common categories are:

Manual Audit Workflow

Here is a step-by-step workflow for conducting a manual delivery fee audit:

1. Select the audit period. Start with one month. Choose a recent month with complete data.
2. Download all three data sources (platform statements, POS data, bank records) for the selected period.
3. Create a master spreadsheet with columns for: order ID, order date, platform, POS amount, statement amount, commission charged, commission rate, refund deductions, processing fees, other fees, net payout.
4. Match orders between POS and statements. For each matched order, populate all columns.
5. Calculate the effective commission rate per order (commission ÷ order subtotal).
6. Flag discrepancies: Orders where the effective rate differs from contracted rate by more than 0.5%, refund deductions without matching POS data, and any unmatched orders.
7. Calculate total variance: Sum all flagged discrepancies to determine the total dollar amount of potential overcharges.
8. Verify bank deposits match statement net payouts for the period.
9. Document findings with specific order IDs, amounts, and discrepancy types.
10. File disputes for material discrepancies through the platform’s merchant support process.

Why Manual Audits Fail

While the manual workflow above is effective, most restaurants cannot sustain it for several reasons:

Volume. A restaurant with 1,500 monthly delivery orders across three platforms faces 4,500 transactions to reconcile. At 2 minutes per order (optimistic), that’s 150 hours of work per month — nearly a full-time position.

Format inconsistency. Each platform exports data in different formats with different column names, date formats, and order ID structures. Normalizing data across platforms requires technical skill.

Time constraints. Restaurant managers and owners are operational personnel. Reconciliation work competes directly with running the restaurant, and reconciliation almost always loses.

Diminishing returns per order. The discrepancy per individual order is small ($0.50–$5.00 typically), making it feel uneconomical to verify each one. The cumulative impact is significant, but the per-order economics discourage manual review. For a focused walkthrough of matching DoorDash orders specifically, see our guide on how to reconcile DoorDash payouts.

Expertise gap. Many restaurants lack accounting staff with the skills to perform multi-source financial reconciliation, especially across platforms with non-standard reporting.

Automating Delivery Reconciliation

The limitations of manual auditing make a strong case for automated reconciliation tools. Effective automation addresses the core challenges:

• Automated data ingestion: Pulling payout data from delivery platforms, POS data from the restaurant’s system, and deposit data from bank accounts without manual exports.
• Cross-source matching: Automatically matching orders across all three data sources using order IDs, timestamps, and amounts.
• Discrepancy flagging: Identifying orders where commission rates, refund amounts, or processing fees deviate from expected values.
• Trend analysis: Tracking effective commission rates over time to detect gradual increases and new fee categories.
• Dispute documentation: Generating evidence packages for specific discrepancies that can be submitted to platform support.

The delivery reconciliation calculator can help you estimate the potential value of automated reconciliation for your restaurant based on your delivery revenue and order volume. For restaurants generating significant delivery revenue, the return on investment for reconciliation tools often exceeds the cost within the first month.