Void abuse: when the register is the leak
A void cancels a transaction at the register before it settles. It is a normal, necessary function — cashiers make mistakes, customers change their minds, terminals misfire. It is also the cleanest way to steal a cash sale: ring the item, take the money, void the sale, keep the cash. The drawer balances because the sale never officially happened.
That makes voids one of the few numbers in a small store worth watching specifically, rather than as part of a general sense of how things are going.
How does the theft actually work?
The sequence is simple, which is why it is common. The customer pays cash and leaves, usually without a receipt. The cashier voids the completed sale. The money in the drawer now exceeds what the register expects, and the cashier removes the difference. The count comes out right.
Nothing about this is visible in a daily sales total or a drawer count. It is visible only in the void report and in inventory that does not match sales over time.
What does the report need to show?
Four fields: the transaction, the amount, the reason, and who performed it. Without the cashier identity the report cannot separate a busy register from a person, and without a reason field every void looks the same.
Most point-of-sale systems can produce this and many stores have never opened it. If yours cannot attribute a void to an individual, that is a configuration problem worth fixing before anything else here matters.
How do you read it?
By comparing, not by counting. A single cashier's void rate against the store's rate. This month against last month. Voids by hour against traffic by hour. A busy Friday evening produces voids; a quiet Tuesday morning producing more of them is the thing to look at.
Direction matters too. Genuine mistakes scatter across amounts and times. Abuse tends to cluster — similar amounts, similar hours, often when one person is alone.
What controls are worth having?
Three, in order of value. Require a reason on every void. Require a second person above a threshold amount. And review the report weekly, by somebody who is not the person doing most of the voiding.
Receipts help more than they sound. A store where every customer is handed a receipt makes the ring-and-void pattern awkward, because the customer holds evidence the sale occurred. That is a cheap control and it looks like good service.
What should you do when the numbers move?
Pull the whole store's data first, then like-for-like shifts, then the mundane explanations — a new hire, a menu change, a misconfigured button that makes a mistake likely. Only then look at video and the register journal for specific transactions.
The order is the point. An owner who starts from a suspicion will find something, because in a busy store there is always something. Starting from the numbers protects the people who did nothing wrong as much as it identifies anyone who did.
What are the legal cliffs?
Everything after "I think this person is stealing" is governed by law rather than by your judgment: accusing someone, withholding pay, searching a bag, detaining a person, involving the police. Wage deduction rules in particular vary by state and locality, and getting them wrong creates a second problem on top of the first.
Do not decide this from what another owner did. That is the point at which a call to an employment lawyer costs less than the alternative.
Frequently asked questions
Is a void the same as a refund?
No. A void cancels a transaction before settlement, so no money moves. A refund returns money after settlement. The customer experience differs too — a void drops a pending authorization, while a refund takes days to appear.
Should I block voids entirely?
No. Cashiers need to correct mistakes, and removing the function pushes errors into worse workarounds. Control it with a reason field and a threshold rather than removing it.
What void rate is normal?
There is no universal number, and be sceptical of anyone offering one, because it depends on your ticket size, your product mix and how your buttons are laid out. Your own trend is the useful baseline.
Can a customer tell a void happened?
If they have a receipt, yes, and their card may briefly show a pending authorization that drops off. Cash customers who left without a receipt have no way of knowing, which is exactly why receipts matter as a control.
Do voids affect my processing fees?
Usually there is little or no fee on a voided card transaction since it never settles, which is part of why a void is preferable to a refund when the batch is still open.
What if the same cashier has a high rate but a good explanation?
Then you have learned something useful and no harm was done. Training problems scatter and are fixed with a procedure; a directional pattern is a different conversation. Check the explanation against the data rather than accepting or dismissing it.
Should I tell staff the report exists?
Yes. A control that is known works better than one that is secret, because most of its value is deterrence. Telling people you review voids weekly is not an accusation; it is a description of how the store runs.