Fake Receipts: How Staff Print Them, and How to Make It Impossible

Ask an owner how they know a sale happened and most will point at the receipt. That is the assumption the fraud is built on.

A receipt printed on your own printer, with your own logo, using your own paper, proves only that someone had access to your printer. If that is your control, you do not have one.

The four methods

Print and void

A sale is rung up properly. The customer takes the goods and the receipt and leaves happy. Minutes later the transaction is voided in the system. The goods are gone, the money is in a pocket, and the day's record shows nothing sold.

The duplicate

One genuine sale, two printed receipts. The second goes with goods that were never paid for. Anyone checking the gate sees a valid-looking receipt and waves it through.

The hand-written "temporary"

"The printer is not working." A written slip goes out with the goods, and the sale is entered later — or not. This is common precisely because printer problems are genuine, so nobody questions it.

The altered quantity

The receipt says two cartons. Four leave. The customer is in on it, or is not paying attention. The value taken is the difference, and the transaction looks entirely normal in your reports.

Why the usual fixes do not hold

Owners reach for stamps, signatures, and a second person at the gate. Each helps a little and each fails the same way: they authenticate the paper, and paper can be copied, stamped again, or signed by the person doing the stealing.

Voids are the other blind spot. Most systems allow them because genuine mistakes happen. If a void leaves no trace and needs no approval, it is an open door with a sign on it.

What actually closes it

Make the receipt verifiable, not just printed. If every receipt carries a unique code tied to that one transaction, and the gate can check that code against the system before goods leave, a duplicate is worthless. The second copy carries a code that has already been used, or one that does not exist.

Make voids expensive to hide. A void after the goods have left should require approval and stay in the record permanently. You are not trying to prevent voids — you are trying to make sure every one of them has a name attached.

Remove the reason for hand-written slips. This is why a till that keeps working when the power or the network goes matters more than it sounds. If staff can always ring a proper sale, "the system was down" stops being an explanation that gets accepted.

Reconcile daily, not monthly. Cash counted against sales recorded, every evening. A gap found the same day is a conversation. A gap found in March about January is an argument nobody wins.

The uncomfortable part

Most receipt fraud is not committed by career criminals. It is committed by ordinary staff who found a gap and took it, usually starting small. Systems that make the gap visible protect honest staff too — because when something does go missing, the record shows who was on the till, and everyone else is cleared.

Frequently asked questions

Will my staff be offended by receipt verification? In practice, the opposite. Staff who are not stealing are the ones most exposed when goods go missing and there is no way to prove where. A clear record is a defence.

Does this work for a business with one till? Yes, and arguably it matters more, because with one till there is nobody to cross-check against.

What if the network is down at the gate? Verification should work from the device itself, not depend on a live connection. If it needs the internet to check a code, it will fail exactly when you need it.