Closing the register at the end of the day: how to count the drawer without fighting

A familiar scene: eighty-seven shekels are missing from the drawer at the end of a busy Friday evening. The owner counted twice and called the employee who closed the shift, and in the end it became clear what happened: a customer complained about two cappuccinos and got the money back in cash, but the employee did not record it as a refund. She canceled a different order that was still open on the register. The cancellation removed from the expected amount a sale that had not been completed anyway, and the real refund on the cappuccinos was not recorded anywhere. The money actually left the drawer, but no record took it off the amount the system expected to find at the end. Nobody stole anything. Someone just pressed the wrong button during a rush. That is exactly the problem with closing the register at the end of the day: the gap is real, but the explanation is almost always boring, and you only find it if you check that same evening and not a week later.

Why count the drawer every evening at all

You do not count because you suspect an employee. You count because a drawer that is not counted every day builds up small gaps that nobody remembers to explain. Ten shekels on Monday, eight on Tuesday, never enough to set off a red light, but that is nine shekels a day on average, and over about twenty-six trading days a month it is already two hundred and thirty-four shekels with no explanation. A daily count turns every gap into a small, fresh event you can reconstruct because the shift is still remembered. A monthly count turns it into a mystery.

There is another side to this: a regular count protects the employee no less than it protects the till. An employee who closes by the same method every evening, and always with someone else present, is not left alone facing a question of "why is money missing" a week later when nobody remembers what happened.

What a proper close includes: the method in practice

A proper close first answers one question: how much money should be in the drawer according to the system, and how much is actually there. To answer it without guessing, you need five written numbers, not ones from memory:

• The opening float (the cash placed in the drawer at the start of the shift), written down in the morning, not estimated in the evening.
• Total cash sales according to the register's daily report.
• Total cash refunds made during the shift.
• Total cash taken out of the drawer during the shift: money that went to a courier, to buy change or to a deposit in the safe.
• The amount actually counted in the drawer, with notes and coins counted separately.

The equation is simple: the opening float plus cash sales according to the report, minus cash refunds, minus cash taken out of the drawer, should equal what was actually counted.

Every cash-out from the drawer in the middle of the day, for a courier, to buy change, for a deposit in the safe, needs a small note in the drawer at that moment: how much, why and to whom. Without the note, the cash-out looks like a shortage at closing, even though the money simply left for a legitimate purpose.

Always close with two people, even if it is the business owner closing with the last shift. One counts out loud, the other writes it down. It is not a matter of trust. It is a matter of two pairs of eyes on the same amount, so that nobody has to remember alone what exactly happened at half past six. This principle does not change at a market stall or a fair: keeping cash in order at a stall and at the market starts with the same count with two pairs of eyes, even without a fixed register and without a counter.

Every gap, even the smallest one solved within a minute, is worth a line in a regular log: the date, the amount and what was found as the explanation. A log like this does not need to be complicated. A notebook next to the register or a line in a spreadsheet is enough. Without it, the same small gaps from the example above are completely forgotten, and in a month you cannot tell whether it happened once or happens every week.

How to close the register at the end of the day when there is a gap

You close the register at the end of the day in three fixed steps. First, count the drawer by note and coin and write down the amount before you look at the system report, so the count is not bent by what you expect to find. Then compare it with the cash sales report for the same shift. If there is a gap, check it in a fixed order before concluding anything: first change given by mistake, then a discount or a freebie that was not recorded, then a refund recorded as a cancellation, and only at the end assume a counting mistake or an actual shortage.

This order matters because you can check the first three options within minutes, while the shift is fresh and the employee remembers exactly what happened. The same check a week later already costs much more. A gap that is discovered only at the end of the month, when both the seller and the customer have already forgotten the transaction, always stays in the last category.

Four things that create gaps in the till

These are the first four suspects, in the order worth checking them:

Wrong change. A seller who gave change for 200 when the customer paid 100, because of a rush or a calculation done too fast. It happens at busy times, at the register on a Saturday night or a holiday eve, when the queue gets longer and the second check is skipped, especially when the change is given in coins and not as a single note, which is easier to count.

A discount or a freebie that was not recorded. "On me" for a friend, a cup of coffee added free for a waiting customer, a discount agreed verbally without being entered on the register. There are two different situations here, and it is worth telling them apart. If the sale was recorded at full price but less was actually charged, for example a hundred shekels was entered and the customer paid eighty in cash, the drawer is short by exactly the amount of the discount, because the report expects a hundred. If the product was not entered on the register at all, the coffee given free without any record, there is no cash gap, because the report did not expect money that was not supposed to come in. There is a stock gap, because a product left the shelf without being sold, and the same logic about stock gaps applies even when the cause is generosity and not theft. Both situations are legitimate as a business decision, but only if they are recorded the moment they happen and not after the fact.

A refund that was not recorded as a refund. The difference between canceling a transaction and a cash refund matters more than it seems. The gap is created when money leaves the drawer with no record that takes it off the expected amount: for example, money handed back to a customer without opening any action on the register, or a refund paid in cash while a different, separate transaction is canceled on the register. A cancellation is recorded separately, and the original transaction stays in the log. But canceling a different transaction does not explain where the money that actually went out on the refund went. A short five-minute training for a new employee, with one example of each case, reduces this confusion.

An opening float that was not counted in the morning. If the shift starts with change that someone only estimated and did not actually count, the whole gap for that day may really be an opening mistake and not a closing mistake. That is why the opening count matters exactly as much as the closing count, no less.

How big a gap is normal, and how big is not

There is no single threshold that suits every shop, but there is a way to think about it that needs no research. If the shop makes eighty transactions a day on average and a gap of fifteen shekels repeats almost every day, that is less than 19 agorot per transaction on average, a number so small it is easy to explain with one random change mistake, if it had happened once. The problem is not the size but the repetition: a small gap that repeats in the same amount and in the same direction almost every day points to a procedure that is not working at exactly that point, like a refund button nobody learns to use properly, and not to coincidence. On the other hand, a one-off gap of twenty shekels on a busy evening, which does not repeat in the following days, is exactly what a daily count is supposed to catch and close that same evening. It is not a sign of an ongoing problem.

Asking without blaming: the conversation with the team

Once there is a gap, the first question to ask is not "who took it" but "what happened on this shift". The difference between the two questions decides whether the next employee reports a mistake right away or prefers to hide it. An employee who knows that reporting a mistake is met with interest and not blame will report it at that moment. An employee who has been through an interrogation over every shekel will learn not to tell.

It is better to open with a fact, "there was a gap of eighteen shekels, let's go through the transactions on your shift together", and not with a conclusion. You can find the answer within two minutes in the register report itself: a transaction with a refund, a cancellation that was not completed, or a discount recorded in the wrong category. If your register records every action with the name of the seller who did it, you can check who was at the register at the minute the gap was created instead of investigating the whole shift.

Once the explanation is found, it is worth going back to the employee that same day and saying briefly what turned out, even if it was their mistake. That is the difference between a process that teaches and a process that punishes, and in the long run it is what makes employees report a mistake themselves before anyone asks.

What to check if the gap keeps coming back

A one-off gap is an event. A gap that comes back every week with the same employee or on the same shift is a pattern, and needs to be handled differently. Two things worth checking before concluding anything about a specific person: whether this shift is unusually busy, so the employee simply does not manage to record every action in real time, and whether there is clear training on the difference between a cancellation and a refund, because that is exactly the mistake described above and nobody is born knowing it.

If after two weeks of checking the gap still comes back, and both the shift and the training were checked and explained nothing, the next step is to change the procedure and not just look for someone to blame: add a regular second counter to that shift even if it is not the procedure on other days, move to writing down every exception the moment it happens instead of summing up at the end of the shift, and if that does not help either, swap who closes that shift for a two-week trial period and check whether the gap disappears along with the person. This is not punishment. It is a way to check whether the problem is in the process or the person, before deciding something you cannot take back.

A report by shift and by seller (in KupaLi it is a custom report) shows within a week whether the problem is concentrated around a busy shift or around one person, and then you can deal with the root cause instead of guessing.

No closing method gets rid of gaps completely. People work at the register, and people press the wrong button during a rush. What changes with a fixed method is the time it takes to find the explanation: two minutes on the evening the gap was created, not half an hour a week later when nobody remembers anymore.

Everything written here is an operating procedure for closing the register, not bookkeeping advice.