How to close out the restaurant pos at end of night on Starch
Closing out the POS at end of night means verifying that what the register says happened actually matches what the cash drawer holds, what the card processor settled, and what the day's receipts show. It sounds like a ten-minute job. In practice, it's the task that exposes every gap — the voided transaction that wasn't documented, the tip adjustment that didn't post, the drawer that's $14 short with no obvious explanation. What this looks like in detail depends on your setup: a single-location restaurant on Toast runs a different close than a multi-unit operation reconciling Square across four terminals, or a bar tracking cash-heavy tabs against end-of-night credit settlements. The steps share the same shape; the failure points are different. On Starch, the end result is a close-out checklist that runs itself and a daily summary that lands where your team already works — a Slack message, a task that closes automatically when the numbers match, or a dashboard showing today's POS actuals against your running weekly total. You describe what you want to see and when you want to see it, and Starch builds the surface. No spreadsheet to pull manually, no close checklist printed and left on the counter.
Why it matters
A sloppy POS close compounds. A $30 drawer variance left unresolved tonight is a $900 mystery by the end of the month. Card settlements that don't match sales reports create accounting entries that are wrong from the start — and wrong entries in your books mean your food cost percentages, your labor ratios, and your actual margin are all off. Operators who close clean every night catch theft, processor errors, and tip fraud early, when there's still a paper trail to follow.
Common pitfalls
First, reconciling the drawer to the POS total without also checking card processor settlements separately — the POS can show a balanced drawer while a batch fails to settle overnight. Second, treating the close as a single step rather than a sequence: cash count, then POS Z-report, then processor batch, then comparison. Skipping the order makes it impossible to isolate where a discrepancy started. Third, running the close report but not logging the variance — if no one writes down that the drawer was $12 short on Tuesday, there's nothing to pattern-match against when it happens again Thursday.
Starch apps used
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
Choose your operator
A version of this guide tailored to your role — same recipe, different starting context.
Related workflows in Ops & Supply
Inventory shrinkage is the gap between what your records say you have and what's actually on the shelf, in the warehouse, or at your co-packer.
Read guide →Contractor job costing is the practice of tracking what a job actually costs — labor, materials, subcontractors, equipment — against what you estimated, and updating that number as work progresses and change orders land.
Read guide →Retailer deductions and distributor chargebacks are line items that show up on your remittance as money already taken — a short-pay for a late delivery, a promotional allowance you never agreed to, a compliance fee for a label that met spec.
Read guide →Demand forecasting is the work of turning what you know — past sales, upcoming promotions, seasonal patterns, retailer commitments — into a defensible number for how much product you need, and when.
Read guide →