Restaurant end-of-day close checklist for POS, batches, tips, cash drawer, and next-day prep

Closing a restaurant isn’t just “run a report and lock the door.” It’s more like landing a plane: you can’t skip steps because you’re tired, and small misses add up fast.

My restaurant closing checklist focuses on what actually protects your money, your team, and your guest data: POS end-of-day close, card batches, tips, cash drawer controls, manager approvals, and the setup that makes tomorrow’s shift feel easier.

POS end-of-day close: shifts, batches, and offline transactions

I start by treating the POS close like a financial handoff. The goal is simple: no open checks, no loose ends, and totals that match across reports and payment batches.

POS EOD and shift close steps (vendor-neutral)

1. Freeze the floor: Confirm all orders are sent, all checks are closed, and no tabs are hanging open (bar tabs are the usual culprit).
2. Close each server shift: Require each staff member to review sales, tips, and cash due before they clock out.
3. Run core reports (save or print):
   • Sales summary by revenue center
   • Tender summary (cash, card, gift, house account)
   • Tip report (credit tips, cash tips declared, tip adjustments)
   • Voids/comps/refunds report (for manager review)
4. Check for weird items: Zero-dollar checks, split tenders left “pending,” or duplicate refunds.

If your POS has a guided close, follow it consistently. Square’s overview of close-of-day reporting is a helpful reference for what a “close” typically includes, even if you’re on a different platform: close of day report steps.

Batch settlement verification (don’t assume it ran)

Before I settle, I confirm:

• All tip adjustments are finalized (if you adjust tips after the shift, the batch total changes).
• All captured payments are in the batch (no “authorized only” stragglers).
• Batch total matches POS card tenders within your normal tolerance (rounding and timing can cause small differences, but large gaps need a stop-and-fix).

Handling offline mode (store-and-forward): If the internet dropped, some card sales may be queued. I print or export the offline transaction list and verify it clears after connectivity returns. If an offline payment later declines, I document it immediately and follow your house policy for collecting the balance (never “hide” it in cash variance).

Declines at close: If a payment is declined after the guest leaves, don’t patch it with a refund-and-recharge guess. I log it, attach details, and escalate to management so it’s handled consistently.

Sample end-of-day reconciliation template (fill this nightly)

Category	POS Total	External Reference	Actual Count	Variance	Notes
Gross sales	0.00	Sales summary
Net sales (after discounts)	0.00	Sales summary
Card sales (captured)	0.00	Batch total			Tip adj timing?
Cash sales expected	0.00	POS cash due
Gift card sold/redeemed	0.00	POS tender report
Refunds (by tender)	0.00	Processor + POS			Receipt attached
Credit tips	0.00	Tip report
Cash tips declared	0.00	Tip declaration
Cash in drawer (ending)			0.00
Less starting bank			(0.00)
Cash to deposit (calc)			0.00

I like this template because it forces one question: “What should be true?” then proves it with reports and counts.

For a reconciliation-focused walkthrough you can adapt, see this end-of-day sales reconciliation checklist.

Tips closeout that’s fair to staff and clean on paper

Tips are where small process gaps turn into big arguments. I keep tip handling predictable, documented, and consistent across managers.

Credit tips vs cash tips (and where mistakes happen)

Credit tips live inside the POS and processor flow. My checklist:

• Verify tip adjustments are complete before settling the batch.
• Confirm tip totals by employee match shift reports.
• Flag unusual items (large tips, zero tips, negative tips, edits without a reason code).

Cash tips are different. If staff declare cash tips in the POS, I require it at shift close, not later, and I keep the record with the daily packet. This supports payroll accuracy and tax reporting. (This is not legal or tax advice; I tell owners to confirm their approach with their accountant or payroll provider.)

Tip-out, tip pool, and payout method

Tip-out can be clean or chaotic, depending on the rule clarity.

• Tip-out rules: Written percentages or points, and which roles qualify.
• Timing: Calculated from net sales, gross sales, or tips (pick one and stick to it).
• Payout method: Cash at close, next-day cash, or paid via payroll.

If you pay out credit tips in cash nightly, I confirm the cash impact is reflected in the drawer math. If you pay via payroll, I confirm the POS exports match payroll inputs.

Documentation I keep every night

I staple or export:

• Shift summary per employee
• Tip detail report
• Tip-out worksheet (who paid who, and how much)
• Manager sign-off if anything was edited

When someone asks, “Why is my tip different?” I don’t want vibes. I want receipts.

For more general closing process ideas you can compare against your own, this is a solid reference: restaurant closing checklist routine.

Cash drawer, manager approvals, PCI reminders, and next-day prep

This is the part that prevents “mystery losses” and protects the business when staff changes happen.

Cash drawer count procedure (with dual control)

My cash close is boring on purpose:

1. Count in a quiet spot away from guests.
2. Count by denomination, then recount totals.
3. Separate the starting bank from the deposit.
4. Compare cash expected (POS) to cash actual (drawer).
5. Record variance in an over/short log with a reason if known.
6. Perform safe drop and prep deposit (tamper-evident bag, date, amount).
7. Use dual-control for the final number (two people verify, one deposits).

I also keep a clean audit trail: who counted, when, and which drawer.

Review voids, comps, and refunds (manager approval only)

Every close, I review exceptions like I’m scanning for leaks:

• Voids: Was it a true mistake, or a re-ring?
• Comps/discounts: Were they policy-based, and did a manager approve?
• Refunds: Match POS records to processor activity, attach the receipt, and log the reason.

If your POS allows it, I require unique logins and permissions so approvals are attributable to a specific manager.

PCI and security reminders (quick, practical)

I stick to a few non-negotiables:

• Don’t store full card numbers anywhere, including notes.
• Lock down receipts and disable unneeded reprint access.
• Keep POS devices updated, and change default passwords.

This is where restaurant ops intersects with real Cybersecurity Services. When I support clients, I treat the close as part Small Business IT hygiene: strong Endpoint Security, consistent Device Hardening, and role-based access. If your POS and back office tie into Cloud Infrastructure, I want Secure Cloud Architecture and reliable Cloud Management, so updates and logs don’t get skipped. I also see restaurants benefit from Office 365 Migration for shared close packets and permissions, plus Business Continuity & Security planning for internet outages and offline payments. The mix of Restaurant POS Support and Kitchen Technology Solutions should feel like one system, not five vendors pointing fingers. That’s where a true Business Technology Partner helps, with Technology Consulting, IT Strategy for SMBs, Managed IT for Small Business, and practical Infrastructure Optimization using proven Data Center Technology standards. Done right, it’s Digital Transformation that actually reduces nightly stress, with Tailored Technology Services and Innovative IT Solutions that fit how your staff works.

Next-day prep (5 minutes that saves an hour)

Before I leave, I set tomorrow up:

• Check par levels and 86 list notes
• Confirm reservations and large-party prep
• Restock printer paper, label rolls, and receipt tape
• Charge handhelds and check one test print per station
• Write pre-shift notes (menu changes, comps policy reminders, staffing gaps)
• Schedule POS updates after hours, never mid-service

Common closing mistakes and quick fixes

• Batch doesn’t match POS card total: Look for unsettled tips, duplicate refunds, or offline transactions still pending.
• Cash is short but sales look right: Recount, confirm starting bank, then verify paid-outs and tip payouts were recorded.
• Tips look inflated: Check tip adjustments, forced entries, and whether gratuity is being counted twice.
• Too many voids: Require reason codes and manager approval, then coach on re-ring steps.

Closing well is a habit, not a hero moment. If you run this restaurant closing checklist the same way every night, you’ll catch problems early, protect cash flow, and walk into the next day already ahead.