A restaurant month end checklist that actually closes a month doesn’t run on a heroic weekend. It runs on a sequence. Daily sales captured fresh, reconciliations done weekly, accruals booked before sign-off. Two weeks, not two days.
Why most hospitality close processes feel worse than they should
Most cafe month end close processes collapse into the same pattern: week one of the new month goes by with nothing closed from the old one, weeks two and three see a frantic catch-up, and the numbers get signed off in the last two days against a deadline that was set weeks earlier.
The output still arrives. It just arrives in a shape nobody can trust.
This guide is the opposite pattern. A restaurant month end checklist that treats close as a sequence of small jobs spread across the first two weeks of the following month, not one big job at the end. By day 14, the books are closed, reviewed, and signed off, with genuine confidence in the numbers.
Almost every operator we’ve onboarded had the same close problem when they arrived: heroic weekend, plausible numbers, no real sign-off. The fix is almost never more effort. It’s earlier effort.
The same structure works for cafes, dine-in restaurants, cloud kitchens, and small groups. At multi-location scale, the sequence stretches but the logic is identical.
The principle: close is a rhythm, not an event
A calm monthly close restaurant operators actually finish on time is built on one idea. The close of month N doesn’t start on day 1 of month N+1. It started on day 1 of month N, with daily sales captured and weekly reconciliations kept current.
If the daily and weekly rhythm held through the month, day-14 close is a review. If it didn’t, day-14 close is a reconstruction, and the checklist below is mostly catch-up work rather than real closing.
The checklist assumes the daily and weekly hygiene held. If it didn’t, run the delayed-bookkeeping catch-up process first, then come back here for the ongoing rhythm.
Days 1-7: lock the operational data
The first week after month-close is about making sure every transaction in the old month is captured, before any cross-checking begins.
Day 1-2: daily sales
- Every day’s POS sales summary for the prior month is captured in the books with channel split (dine-in, takeaway, each delivery platform, catering, retail)
- Discounts, voids, and comps recorded correctly (discount as reduction, comp as cost)
- Service charge recorded as VAT / GST-applicable revenue (when applicable)
- Tips segregated from revenue, held in tips-payable or tips-received, not in sales
Day 2-3: bank and card reconciliations
- Primary operating bank reconciled through the last day of the prior month
- Card merchant statements reconciled, fees separated from gross takings
- Any “mystery” bank entries investigated, not just accepted
Day 3-5: delivery platform reconciliations
- Each platform’s prior-month statements pulled and booked (gross revenue + commission + fees + tips + adjustments)
- Platform receivable cleared against payout; outstanding receivables match the last unpaid statements only
- Input VAT / GST on platform commission captured separately
Day 5-7: supplier invoices and accounts payable
- Every supplier invoice dated in the prior month is captured (not just those paid)
- Supplier statements reconciled against the ledger for the three or four largest vendors
- AP aging report reviewed, anything over 60 days flagged for follow-up
Days 8-10: accruals, payroll, cut-off
The second week is where the close gets honest. Cut-off discipline (making sure transactions land in the right period) is the difference between a clean close and a plausible close.
Payroll
- Full month’s payroll posted (gross wages, withholdings, super / WPS / mandatory benefits, payroll tax where applicable)
- Payroll accrual for the partial-week bridging into the new month (if the pay cycle doesn’t align to month-end)
- Tips payout matched to tips-collected account
Accruals for invoices not yet received
- Utilities for the prior month (estimate if bill not yet received)
- Rent for the prior month (if not already on a scheduled journal)
- Credit card processing fees (often billed on a lag)
- Software subscriptions paid on a month-of-service cycle
- Any other known expenses incurred in the prior month but not yet invoiced
Prepayments and unearned income
- Rent paid in advance, amortized to the right month
- Insurance premiums spread across their coverage period
- Catering / event deposits received but not yet earned, held as liability, not recognized as revenue
Inventory
- Closing inventory count taken (weekly or monthly, depending on process)
- COGS adjusted from the difference between opening + purchases − closing
- Wastage captured where the process supports it
Days 11-14: review and sign-off
The third week is review, variance analysis, and sign-off. No new entries unless something is genuinely wrong.
Variance review
- Revenue vs prior month and vs same month last year
- Food cost % vs target (any 3+ point deviation investigated)
- Labour % vs target (any 2+ point deviation investigated)
- Other operating expenses vs prior month (anything new or spiked?)
- Gross margin vs prior month
- Cash position vs P&L profit (the two should reconcile via working capital movement)
Tax-readiness
- VAT / GST / BAS totals pulled; sanity-check vs expected
- Output tax, input tax, and net position documented
- Any adjustments needed for prior-period corrections noted
Sign-off
- Owner / CFO review meeting (30 minutes, not three hours; that’s what the rest of the process is for)
- Any questions resolved before the period is locked
- Books locked for the closed period in the accounting system
The 30-minute close target
A hospitality bookkeeping close that runs on this rhythm takes roughly two weeks of small, spread-out time. Not one heroic push. The final review meeting is 30 minutes, not a multi-day reconstruction.
That’s the standard to aim for. If the current close feels materially worse than that, the issue is almost never the checklist. It’s that the daily and weekly rhythm upstream isn’t holding. Fix that first.
Common failure modes
- Starting the close on day 8 of the new month. By then the data is stale, memory is faded, and week-1 tasks compete with week-2 tasks. Day 1 is the start.
- Booking daily sales from the bank feed. Bank shows net deposits, not gross sales. Use the POS daily summary and reconcile the deposit separately.
- Not accruing expenses that haven’t been invoiced. A restaurant with a 30-day supplier payment cycle will systematically understate COGS in each month’s books if accruals are skipped.
- Skipping the variance review. A close that balances is not the same as a close that’s correct. Variances catch the difference.
- Making the close a one-person bottleneck. Separate the “capture” work (can be delegated) from the “review and sign-off” (owner / CFO responsibility). Same person doing both means nothing ships on time.
Related resources
- How to reconcile Talabat revenue in your books: the specific mechanics for step 3 if you operate in the UAE
- How to reconcile Deliveroo and Uber Eats statements: same for operators using those platforms
- How to clean up delayed bookkeeping without starting over: if the close is months behind, catch up first
Next step
If your monthly close currently feels like a last-week scramble rather than a day-14 review, the free books health check is the practical first step. We look at where the rhythm breaks down and what a two-week close would require for your specific setup.
Last updated: April 2026.