Restaurant POS Reconciliation Guide: Toast, Square, Delivery Apps, Tips, and Bank Deposits

Restaurant reconciliation looks simple until you run more than one location.

The POS says one number. The bank deposit says another. DoorDash, Uber Eats, and Grubhub each settle on their own schedule. Tips move through payroll. Gift cards create deferred revenue. Refunds, comps, discounts, chargebacks, cash deposits, merchant fees, and delivery commissions all land in different places.

By the time the bookkeeper gets the exports, the clean sales number is buried under timing differences and platform quirks.

If you wait until month-end to fix it, you are already behind.

Restaurant POS reconciliation should be a daily workflow, not a monthly archaeology project.

What You Are Actually Reconciling

Most restaurant teams say “POS reconciliation” as if it is one task. It is several tasks stacked together.

You are reconciling:

POS gross sales
Discounts, comps, voids, refunds, and house accounts
Sales tax
Tips and service charges
Cash expected vs cash deposited
Card batches and merchant deposits
Third-party delivery sales and payouts
Gift card sales and redemptions
Online ordering deposits
Catering deposits and final payments
Bank deposits
Accounting entries by location, department, and revenue category

The hard part is not that any one line item is complicated. The hard part is that every system describes the same day differently.

The POS thinks in sales day. The bank thinks in deposit date. Delivery apps think in settlement cycles. Accounting thinks in periods, classes, locations, and chart-of-account mappings.

Your reconciliation process has to translate between all of them.

Start With the Daily Sales Packet

Every location should produce a daily sales packet. It does not have to be a literal PDF, but it needs to exist as a structured set of data.

At minimum, capture:

Business date
Location
POS gross sales
Net sales
Sales tax
Discounts and comps
Refunds and voids
Cash sales
Expected cash deposit
Card sales by processor batch
Tips paid or owed
Gift card sales and redemptions
Delivery marketplace sales
Online ordering sales
Catering sales or deposits
Any manager notes explaining exceptions

The point is to create one daily source of truth before the money hits the bank.

If every location closes the day differently, finance spends the rest of the week normalizing messy data. That is where small variances become permanent noise.

Reconcile Sales Day to Deposit Day

Restaurant operators often get tripped up because sales do not always deposit on the same day.

Friday night card sales may settle Monday. Delivery app payouts may include orders from multiple dates. A bank holiday may push deposits into the next week. A catering deposit may be collected today for an event next month.

If you try to match every sales day directly to one bank deposit, you will create false exceptions.

A cleaner workflow separates the process:

Reconcile the POS sales day internally.
Map each payment stream to expected deposit timing.
Match bank deposits to expected batches and settlement reports.
Investigate only the true variances.

This is especially important for multi-location groups. The bank feed may show deposits by processor, location, merchant ID, or batch. If the mapping is inconsistent, finance ends up manually guessing which deposit belongs to which store.

That guessing should be designed out of the process.

Treat Delivery Apps as Their Own Reconciliation Stream

Third-party delivery is not just another sales channel. It has its own economics and its own reconciliation problems.

For each marketplace, track:

Gross marketplace sales
Promotions and discounts
Marketplace commissions
Delivery fees
Adjustments
Refunds
Chargebacks
Tips
Net payout
Settlement date
Related bank deposit

Do not just book the deposit as sales.

If you do, your revenue, fees, taxes, and margins will all be wrong. The deposit is net of deductions. Accounting needs the gross sales and the expense lines, not just the cash that arrived.

Delivery app reconciliation also catches operational issues. A spike in refunds, missing menu items, abnormal discounts, or unexplained payout adjustments can point to store-level problems before they show up in the P&L.

Tips Need Their Own Controls

Tips create another layer of reconciliation because they move between the guest, processor, payroll, and employees.

Your process should answer:

How much tip revenue was collected?
Which tips were paid out in cash?
Which tips are owed through payroll?
Were service charges treated differently from tips?
Did tip payouts exceed expected amounts?
Are credit card tips reconciled against processor deposits?

Tip errors are not just accounting annoyances. They create employee trust issues fast.

For multi-location groups, tip reconciliation should be standardized across every store. Managers should not be inventing local workarounds because the finance process is unclear.

Gift Cards Are Not Normal Sales

Gift cards are easy to mishandle.

When a guest buys a gift card, that is usually a liability, not immediate revenue. When the guest redeems it, the liability goes down and revenue is recognized. Depending on your accounting setup and jurisdiction, abandoned balances may need separate handling.

Your reconciliation should track:

Gift card sales
Gift card redemptions
Outstanding liability
Breakage assumptions or policy
Third-party gift card platform activity
Location-level redemption patterns

If gift cards are mixed into normal sales without a clean liability workflow, month-end cleanup gets ugly.

Build an Exception Queue

The goal of reconciliation is not to make a human review every transaction. The goal is to surface the exceptions that need judgment.

Create thresholds:

Cash deposit variance above a set dollar amount
Missing deposit after expected settlement window
Delivery payout variance above tolerance
Refund spike by location
Unusual comp percentage
Gift card liability mismatch
Missing manager closeout
POS batch not found in bank feed
Bank deposit that does not match any expected batch

Everything inside tolerance can flow through. Everything outside tolerance becomes an exception with an owner, reason code, and due date.

This is where automation helps the most. Not by replacing accounting judgment, but by doing the matching, flagging, routing, and follow-up that consumes hours every week.

The Multi-Location Problem

One restaurant can brute-force reconciliation. Five locations cannot. Twenty locations definitely cannot.

Multi-location operators need consistency:

Same chart of accounts
Same location/class mapping
Same closeout fields
Same exception thresholds
Same delivery app settlement mapping
Same cash deposit workflow
Same manager notes format
Same month-end cutoff rules

Without this, every location becomes its own mini accounting project.

The controller should not need to remember that Store 3 books catering deposits differently, Store 7 uses a different DoorDash merchant ID, and Store 12 still sends cash deposit slips by text.

That is not a process. That is institutional memory.

What to Automate First

Do not start by trying to automate every accounting entry.

Start with the repeatable matching work:

Pull POS closeout data by location and date.
Pull delivery marketplace settlement reports.
Pull bank deposits and processor batches.
Match expected deposits to actual deposits.
Flag unmatched or out-of-tolerance items.
Draft accounting entries for review.
Post daily exception summaries to the finance team.

Once that works, expand into vendor invoice matching, catering deposit tracking, loyalty adjustments, and store-level operational alerts.

The best automation gives finance a clean review queue instead of a pile of exports.

The Bottom Line

Restaurant POS reconciliation is not just bookkeeping. It is an operating control.

If sales, deposits, delivery payouts, tips, gift cards, and refunds are not reconciled daily, your P&L becomes a lagging cleanup document instead of a management tool.

For growing restaurant groups, the answer is not more spreadsheets. It is a tighter daily workflow, standardized location rules, and automation that catches exceptions before month-end.

If you are building out the broader operating model, see how OpsRev supports restaurants and hospitality groups.

OpsRev builds digital teammates for operations-heavy industries. If your finance team is buried in restaurant exports, payout reports, and deposit matching, let’s talk.