Day-close at midnight: fifteen minutes that decide whether your numbers are real

The last table pays at 11:35. The kitchen is already washing down. The cashier counts the drawer, finds it short by four hundred rupees, shrugs, tops it up from his own pocket or writes nothing at all, and goes home. Three tables are still showing as open in the billing machine because nobody closed them. Two bills were cancelled during the rush and reprinted. And the card machine's own settlement will land tomorrow afternoon, at a figure nobody will ever compare to anything.

By Friday, none of that is recoverable. The owner asks why Sunday's collection looks light, the manager says it was a slow night, and the conversation ends because there is no artefact to argue with. This is the most expensive fifteen minutes an Indian restaurant does not spend.

A day-close is not paperwork. It is the moment your numbers stop being a claim and become a record. Everything downstream depends on it: your food cost, your staff trust, your GST filing, and your own ability to tell whether a bad week was demand or leakage.

What a day-close actually is

A day-close is a declaration, made once, by a named person, that the day is finished and the numbers are these. Four things have to be true before that declaration can be made honestly.

• Every order that was opened today has been settled, cancelled with a reason, or explicitly carried forward.
• Cash counted physically equals cash the system says was collected, or the difference is recorded with a name against it.
• Every non-cash mode has a figure that can be checked against an external statement later: card, UPI, wallet, aggregator, credit.
• Every discount, void and complimentary item has an approver attached to it.

That is it. It is not a tally sheet, and it is not the manager sending a WhatsApp message saying today was 84,000. A number without those four supports is an opinion.

Settled versus unsettled: the board that has to be empty

The single most useful screen in a restaurant is a settled versus unsettled board, and the rule attached to it is simple: at day-close, the unsettled column is empty or every line in it has a written reason. Nothing else in this article matters if orders can quietly stay open.

Open orders at midnight are almost never fraud. They are a table that paid the steward directly and walked out, a takeaway parcel handed over on trust to a regular, an order punched twice during a rush and abandoned, or a delivery that was cancelled by the customer after the KOT fired. Each has a different accounting answer and all of them look identical if you find them a week later.

• Paid but not marked: settle it now, with the mode, before the steward goes home and the memory goes with him.
• Genuinely unpaid, going on credit: record it as credit against a named party, not as a settled cash bill that leaves your drawer short.
• Duplicate punch: cancel it with the reason, so the KOT that fired against it can be reconciled against wastage.
• Customer cancelled after the kitchen started: cancel with reason and record the food as wastage, because the ingredients left the store either way.
• Aggregator or delivery order stuck mid-flow: park it explicitly as carried forward, so tomorrow's opening board shows it instead of hiding it.

Once the board is empty, your day's sales figure is a fact. Until then, every other number in the close is being computed on sand.

Counting the cash drawer against cash sales

The drawer count is where most closes go wrong, because it is done as a single number instead of a comparison. Count the physical cash, subtract the opening float you put in at the start of the shift, and compare what remains against the system's cash-mode total. Not the day's total sales. Only cash.

The gap between those two figures is the only number worth arguing about, and the discipline is to record it every single night, including the nights it is zero. A short of sixty rupees written down is worth more than a perfect drawer that nobody documented, because a running record of shorts tells you within a fortnight whether you have a counting problem, a change problem, or a person problem.

• Fix the opening float and never let it float. A drawer that starts at a different number each day cannot be reconciled by anyone.
• Count in front of a second person, or at minimum have the count entered by someone who is not the person who handled the drawer.
• Record the difference, in either direction. An over is as much a signal as a short: it usually means a bill went unrecorded.
• Log cash removals during the shift. Money sent for vegetables at 6pm is not a shortage, but it becomes one if nobody writes it down.
• Never let a cashier settle a difference from his own pocket. It hides the pattern you are trying to see, and it makes an honest cashier pay for a process failure.

Cards, UPI and the settlement that lands tomorrow

Cash is the mode everybody watches and the smallest source of unnoticed loss in most urban outlets. The real gaps hide in the modes nobody counts, because the money is not physically present at midnight.

Your card terminal has its own batch total. Your UPI collections land in the bank with a delay and a reference. Aggregator orders settle on their own cycle with their commission and charges already deducted. None of those figures reconcile themselves, and the discrepancies are usually small enough that nobody notices for months.

• Capture the terminal batch total at close and put it against the system's card total for the same day. A mismatch means a swipe was taken against the wrong bill or a bill was settled to the wrong mode.
• Record the UPI total separately from card. Merging them into one digital bucket makes the next day's bank reconciliation impossible.
• Treat aggregator sales as their own mode, at gross value, with deductions reconciled when the payout arrives rather than assumed.
• Keep partial and split settlements explicit. Half cash, half UPI is two lines, not a rounded guess.
• Reconcile bank credits against day-close figures weekly, not at year end. A missing settlement found in seven days can be raised with the acquirer; one found in seven months cannot.

The point is not that your acquirer is cheating you. It is that a restaurant with no daily mode-wise record has no basis for a conversation with anybody: not the bank, not the aggregator, not the cashier.

Voids, discounts and comps: approvals, not erasures

A cancelled bill should never be a bill that disappeared. Your tax invoice series has to run unbroken and every number in it must be accountable, which means a cancellation is a recorded event with a reason and a person, not a gap. If your billing lets someone delete a printed bill and reuse the number, you do not have a control problem, you have an evidence problem.

Discounts and complimentary items deserve the same treatment for a different reason. They are legitimate, they are useful, and they are the easiest thing in a restaurant to abuse precisely because nobody wants to look mean by questioning them.

• Every void carries a reason from a fixed list and the name of whoever approved it. Free text reasons become blank within a week.
• Discounts above a threshold you set need a second name. Below it, they still get recorded against the person who applied them.
• Complimentary items are tied to the bill and to the approver, and they roll into the day-close as their own line, not as a reduced sale.
• The KOT that fired against a cancelled order gets reconciled to wastage, because the kitchen consumed the ingredients whatever the bill says.
• Review void and discount counts by person monthly. The pattern is visible long before the amount becomes serious.

A bill that vanished is not a smaller sale. It is a hole in the only record you have, and it will be found by an auditor before it is found by you.

The tables still open at 11:40 pm

There is a specific, recurring failure worth naming on its own. The floor is laid out in sections, guests are seated, and a running order builds against each table. On a heavy night, a table pays at the counter directly, walks out, and the table is never released. It sits open, holding an order, showing as occupied to the next shift.

The cost is not just the reconciliation. It is that your live table status becomes untrustworthy, so the floor stops looking at the screen and goes back to shouting across the room, which is the exact habit the system was bought to remove. A day-close that forces every table back to free is what keeps the floor view believable on Saturday at nine, when it actually matters.

Handing the shift over without a verbal summary

In outlets running two shifts, most disputes are not about theft. They are about the boundary. The evening cashier inherits a drawer, a set of open tables and a set of unrecorded promises, and by the time anything is questioned, both people can describe the handover differently and honestly.

• Close the shift, not just the day: drawer counted, float handed over as a stated number, difference recorded before the next person touches it.
• Open orders at handover are listed and acknowledged by the incoming person, so a table that has been running for four hours is somebody's problem before it becomes nobody's.
• Cash taken out for purchases during the shift goes into the handover, with the amount and the reason.
• Anything promised to a guest, such as a settled complaint or a comp for a delayed order, is written down rather than passed on verbally.

The day-close pack you should be able to send the owner

Here is the test for whether your close is real. At 12:15, without opening a laptop, could the manager send the owner one summary that answers every question the owner would ask? Not a sales figure. This.

• Total sales, split dine-in, takeaway and delivery, with order counts against each.
• Mode-wise collection: cash, card, UPI, aggregator, credit, with the drawer difference stated even when it is zero.
• Bill number range used today, with cancellations listed by number and reason.
• Discounts and complimentary items, total value, with approvers.
• Open orders carried forward, if any, and why.
• Top-selling items and the covers count, because that is the line the owner reads first.
• Wastage recorded, so the kitchen number and the billing number are closed on the same night.

A manager who can send that in one message every night is running an outlet. A manager who sends a single sales figure is reporting a feeling.

How the workspace closes the day

BizRevolt's restaurant workspace is built around this close rather than around the printer. Billing produces gap-free numbered bills with the CGST and SGST split, discounts and rounding handled on the bill itself, and a settled versus unsettled board that makes the empty-column rule enforceable rather than aspirational. Sections and tables carry live status with a running order against each, so the tables still open at 11:40 are visible instead of assumed. Dine-in, takeaway and delivery run on one menu and consolidate into one order, so mode-wise and channel-wise totals fall out of the day rather than being assembled from three places.

One-tap KOT ties each item from fired to served, which is what lets a cancelled bill be reconciled against what the kitchen actually cooked. The live dashboard carries today's sales, order count, open orders, active tables, top-selling items and unsettled bills, which is most of the day-close pack already written. Day-end and item-wise reports export to CSV when the accountant wants them.

None of this makes the fifteen minutes disappear. It makes them possible to do the same way every night, by whoever is on shift, so that a question asked on Friday about Sunday has an answer instead of an argument.