Lavu POS Sales Not Matching Your DoorDash & Uber Eats Payouts

Your Lavu End of Day report says you did $1,180 in DoorDash, Uber Eats, and Grubhub orders today. Almost none of that arrives via Lavu’s processor. The delivery platforms collect the customer’s payment and pay you separately, days later, after taking a 15–30% commission — so a $48 order that shows as $48 in Lavu nets roughly $34 on DoorDash and $36 on Uber Eats. Your Lavu total will never match your bank, because the iPad POS and the delivery platforms are measuring two different things on two different timelines. This is the structural reason behind the “Lavu POS bank statement doesn’t balance” complaint that surfaces all over operator forums.

One Lavu operator described their reports as “wrong on a daily basis — not due to human error.” Another flagged the issue more specifically: “items duplicate on the receipt and cause end-of-day differences,” compounded by Lavu’s default of recording credit card tips as cash. Layer in delivery commission deductions and refund clawbacks that nobody is matching back to the original tickets, and the daily cash up turns into a guessing game.

The gap is explainable once you separate what your Lavu processor handled (in-house card sales) from what the delivery platforms owe you. This guide covers exactly why your Lavu POS bank statement doesn’t balance against DoorDash, Uber Eats, and Grubhub payouts, the discrepancies hiding in those payouts, and a step-by-step process to reconcile every dollar. For the broader cross-platform picture, see our guide to reconciling delivery platform payouts and our general POS deposits don’t match bank walkthrough.

Why your Lavu sales don’t match your delivery payouts

Lavu restaurants running delivery through multiple platforms face a reconciliation problem that neither Lavu nor the delivery platforms are designed to solve — and Lavu’s modifier-heavy ticket engine, credit-card-tip-as-cash default, and the Cash Discount Program all add layers that make it harder to see.

Several payment timelines, one End of Day. Your Lavu End of Day report includes in-house card sales (deposited in 1–2 days via your Lavu Pay or third-party processor), DoorDash orders (paid weekly by DoorDash), Uber Eats orders (paid weekly by Uber Eats), and Grubhub orders (paid on Grubhub’s schedule). Several separate payment timelines feed one POS total. On any given day your bank deposit only reflects the in-house card volume — the delivery money is still in transit through the platforms.

Commission variability. DoorDash charges 15–30% depending on plan. Uber Eats charges 15–30%. Grubhub charges 15–25% plus marketing fees. Each platform also deducts refunds, customer promotions, and delivery fees before paying you. A $48 order might net $34 on DoorDash and $36 on Uber Eats for what looks like the same ticket in your Lavu POS. There is no way to track this from Lavu reports alone.

The modifier-duplication problem. Lavu’s flexible modifier engine is one of its strengths, but operators routinely report that items duplicate on the printed receipt when servers reopen a check, swap a modifier, or split a check across guests. That duplicate inflates the POS total but doesn’t exist on the platform’s side — so when you compare the Lavu daily total to a DoorDash payout, a portion of the “missing” money is actually phantom revenue from a duplicated line item. Until you rule that out, you cannot tell what’s a duplicate vs. what’s an actual platform short-pay.

Credit card tips as cash. By default, Lavu’s End of Day report treats credit card tips as cash in the till until they’re paid out. That means the iPad shows a cash overage that isn’t real cash — the tips are still sitting in the processor and will be deposited net of fees on a later batch. Operators who don’t adjust the report logic see a daily cash up that never reconciles to the actual drawer.

Refund black holes. When a delivery customer gets a refund from the platform, the platform deducts it from your next payout — but the original order still sits in your Lavu POS as a closed ticket. A restaurant doing 175 delivery orders per week with a 3–5% refund rate has 6–9 phantom orders per week inflating POS totals. By month end that’s $450–$1,800 in revenue your POS reports but your bank never received.

The Cash Discount Program twist. If you’re enrolled in the Lavu Cash Discount Program, every card transaction has a service-charge surcharge added at the POS to offset processing fees. The surcharge shows in your Lavu sales total but is essentially a wash — it is deducted again on the processor side when fees are calculated, so the net deposit is closer to the menu price than a naive reading of the POS report would suggest. Without accounting for the program on both sides, you’ll chase a phantom shortfall every day.

Which Lavu report to reconcile against

One reason the numbers don’t match is that you’re reconciling against the wrong report. Lavu gives you several reporting surfaces — the iPad End of Day, the Lavu Control Panel sales reports, the Lavu Pay processor portal, and the QuickBooks export — and they all show different numbers. Critically, none of them include the delivery platform payouts, which arrive separately. Use the table below to confirm which report maps to which money.

Common Lavu + delivery reconciliation gaps

Knowing why the numbers don’t match is one thing. Knowing which specific discrepancies to look for in each platform’s payout is what actually lets you recover the money.

Commission charged above your contracted rate. DoorDash, Uber Eats, and Grubhub each have a contracted commission tier, but the rate actually applied per order drifts — plan changes, promotional tiers, and order-type misclassification all push it higher. Pull a sample of Lavu delivery tickets, divide the platform’s commission by the order subtotal, and compare to your DoorDash fees agreement, Uber Eats fees agreement, or Grubhub fees agreement. Anything consistently over is a recoverable overcharge.

Modifier-duplicated tickets that never appear on any payout. Lavu’s modifier engine occasionally fires a duplicate line item on the kitchen ticket. If the server doesn’t catch it before closing the check, the POS total is inflated by a phantom item that has no corresponding platform record. Treat any Lavu-side overage as a duplicate first, not a platform short-pay, until proven otherwise.

Refund clawbacks on tickets you fulfilled correctly. Platforms deduct refunds for driver errors, delivery delays, and customer fraud that aren’t the restaurant’s fault. Your Lavu ticket shows the order was made and handed off; the platform still pulled it from your payout. Those are disputable.

Missing orders. An order in your Lavu sales report that never appears on any platform payout is the clearest leak — you made the food and were never paid. These only surface when Lavu tickets are matched line-by-line against platform payouts.

Promotional adjustments without enrollment. Marketing and promo deductions sometimes appear on payouts without matching enrollment records. If you never opted into the promotion, the deduction is disputable — the platform must show enrollment evidence.

Cash-tip vs. card-tip misclassification. Because Lavu defaults to recording credit card tips as cash, an unadjusted End of Day will show a cash overage that should actually be a card-receivable. When the tip is later deposited (net of fees), the deposit appears to be short by the tip amount when in reality it was never expected as cash in the first place.

How to reconcile Lavu against your delivery payouts (step by step)

You need three data sources for the same period: your Lavu sales data (to isolate delivery orders and rule out modifier duplicates), each platform’s merchant payout report, and your bank statement (plus the Lavu Pay processor statement).

Step 1 — Separate delivery orders in Lavu

From the Lavu Control Panel, run the Sales report for the period. Break out revenue by tender type and order source so you can isolate DoorDash, Uber Eats, and Grubhub orders from in-house card volume. Adjust the credit-card-tips-as-cash classification before treating any variance as missing money. The delivery total is what the platforms owe you separately — it should not be expected in your Lavu Pay bank deposit at all.

Step 2 — Pull each platform’s payout report

Log into each delivery platform’s merchant dashboard (DoorDash Merchant Portal, Uber Eats Manager, Grubhub for Restaurants) and export the transaction-level payout report for the same period. This gives per-order commission, refund adjustments, promotional charges, and net payout.

Step 3 — Match Lavu tickets to platform payouts

For each platform, match its payout line items to the Lavu tickets by order ID (or timestamp + subtotal). Watch for duplicate items from the Lavu modifier engine that inflate the POS subtotal but never appear on any payout — those are the most common cause of false “missing” revenue. Verify commission rate (commission ÷ subtotal vs. contracted), refund deductions (every refund should have a matching Lavu ticket), and order presence (every Lavu delivery ticket should appear on a payout).

Step 4 — Match each payout to the bank deposit

DoorDash and Grubhub pay weekly; Uber Eats pays weekly. Match each platform’s net payout to the corresponding bank deposit, allowing 3–5 business days of transfer timing. Account for the Lavu Cash Discount Program surcharges on both the sales and fees sides if you’re enrolled. Our DoorDash payout reconciliation guide walks the per-order process in detail.

Step 5 — Flag and dispute the gaps

Anything that doesn’t reconcile after commission, timing, modifier duplicates, and the tip-classification adjustment — over-charged commission, refund clawbacks on correctly-fulfilled tickets, missing orders, unenrolled promo deductions — is recoverable. Record the order ID, expected vs. actual amount, and dispute through the platform’s merchant portal with the Lavu ticket as evidence. This is where most Lavu operators find the largest unexplained gaps.

The secondary gap: Lavu Pay processing fees, Cash Discount Program & billing

Separately from delivery, your in-house Lavu card sales also deposit short of the POS total — a smaller, more predictable gap worth ruling out so it doesn’t get confused with delivery discrepancies.

Processor fees. Lavu Pay (or whichever processor you signed with) deducts processing of roughly 2.5–3.2% before depositing in-house card sales, daily or monthly depending on your merchant agreement. Calculate your effective rate monthly (total fees ÷ card volume); if it exceeds your contracted rate, our guide on auditing POS processing fees covers disputing the overcharge.

Cash Discount Program math. The Cash Discount Program surcharge appears in the Lavu sales total at the menu level, but it’s offset by the processor on the fees side. The two should largely cancel out — if they don’t, the surcharge configuration on the POS or the processor side is wrong and you’re either overcharging customers or absorbing fees the program is supposed to offset.

Lavu billing inaccuracy. A recurring operator complaint is that “Lavu billing is constantly inaccurate” — subscription months billed twice, modifier add-ons billed when not active, terminal-fee surprises on the monthly invoice. Audit the Lavu invoices quarterly against your contracted plan; any overcharge there compounds the deposit gap if you don’t catch it.

Lavu isn’t alone in this pattern. Clover restaurants face the same delivery reconciliation gap, and Lightspeed Restaurant operators deal with reporting quirks that distort end-of-day before deposits even arrive. The common thread: POS systems were built for the POS’s own logic, not for matching against delivery platforms that pay on a completely different timeline.

How DeliverGuard helps Lavu restaurants

DeliverGuard replaces the multi-tab spreadsheet with automated reconciliation across all your payment streams. Upload your Lavu sales data, your delivery platform statements from DoorDash, Uber Eats, and Grubhub, and your bank transaction history. The system matches every transaction across all sources and categorizes every gap.

Modifier-duplicated tickets are flagged so you don’t treat them as platform short-pays. Credit card tips are reclassified to the right tender. Cash Discount Program surcharges are netted on both sides so the math actually balances. Delivery platform commissions are matched against contracted rates to catch overcharges. Refund deductions are traced back to the original Lavu ticket so you know exactly which refunds hit your payout and whether the amount was correct. The reconciliation methodology behind Mike Reilly’s operator playbook was specifically designed for the messy multi-source matching that Lavu shops contend with.

The result: instead of guessing why your Lavu deposit was $215 short yesterday, you see a line-by-line breakdown — $110 in processing fees, $25 in a duplicated entree on a closed check, $40 in DoorDash commission variance, and $40 in a Grubhub refund deduction that doesn’t match any Lavu ticket. That $40 is the kind of discrepancy that gets lost in spreadsheets but represents real money you can dispute and recover.

For Lavu restaurants running delivery across multiple platforms, the cross-source matching is the critical piece. Each platform’s payout is reconciled against both your Lavu ticket records and your bank deposits, closing the loop that manual reconciliation leaves open.

Frequently asked questions