POS Exception Reports: Catch Void, No-Sale, and Discount Abuse
Learn which POS exception reports to pull each week, how to set a baseline for voids and discounts, and how to check every flag against video first.
Photo: Pixabay
On this page 7 sections
- What POS Exception Reports Show That Sales Reports Hide
- The Five Reports to Pull Every Week
- Reading a POS Void Report: Look Past the Count
- What a No-Sale Report and Cash Refunds Reveal
- Where POS Discount Abuse Hides: Comps, Overrides and Employee Meals
- Match Each Flag to Video Before You Talk to Anyone
- Set Permissions so Loss Prevention Reports Stay Useful
Key takeaways
- A balanced drawer doesn't clear anyone. A void after a cash sale lowers expected cash by the same amount, so the count still matches.
- Compare employees by rate, such as voids per 100 transactions, against your own four-week baseline instead of raw counts.
- Exception reports catch the cover-up. Items that were never rung up only show in inventory and pour-cost checks.
- Before any conversation, confirm the camera clock matches the POS clock and review several flags on video with a second manager.
POS exception reports list every transaction that broke from a normal sale: voids and deleted items, refunds, no-sale drawer opens, and discounts or comps. Each entry carries an employee login and a timestamp. Pull five of these reports every week and measure each employee against your own baseline instead of a raw count. When someone stands out, check the camera footage before you say a word. Theft that alters a recorded sale, such as a void, refund, no-sale or discount, leaves an exception tied to a login, so the reports are where it shows up. A flag on its own proves nothing, which is why the video step comes before any conversation.
What POS Exception Reports Show That Sales Reports Hide
Your daily sales summary nets everything out. Say a bartender rings a cocktail, takes cash, then voids the ticket and pockets the money. Net sales drop by the price of that drink and expected cash drops by the same amount, so the drawer balances to the penny. Many owners miss this. A balanced drawer only shows that the cash matches what the POS says should be there, and if someone changes what the POS says, the count still comes out right. A clean end-of-shift count, like the one in our guide to balancing a cash drawer at shift change, is necessary. It can't catch this kind of theft by itself.
Exception reports pull those edits back out of the totals. Each line shows who made the change and when it happened, along with the terminal and the tender that paid for the original sale.
They have one blind spot you should know about up front. A sale that was never rung leaves no exception at all. A bottle handed over the counter, or a beer poured for a friend with no ticket, won't appear on any report. To catch that, you need inventory checks: pour cost at a bar, shrink counts in a store. Our piece on inventory management methods for small business covers how to run those counts. Exception reports catch the cover-up, and inventory catches the missing product.
The Five Reports to Pull Every Week
Report names differ by POS brand, but most modern systems can produce some version of these five, filtered by employee and date range.
| Report | What it lists | First thing to check |
|---|---|---|
| Void and delete report | Items or tickets removed before or after payment or kitchen send | Voids after a completed cash sale |
| Refund and return report | Refunds by employee and tender, and whether each is linked to an original sale | Cash refunds with no original transaction |
| No-sale report | Drawer opens with no transaction | Timing relative to the previous sale |
| Discount, comp and override report | Percentage and dollar discounts, comps and manual price changes, by reason code | Heavy use by one employee or one manager code |
| Cash over/short report | Drawer variance by shift and cashier | Drawers that are always short, or always exactly even |
Run all five for the full week on Monday morning, before older footage rolls off your recorder. Then export the same reports for the prior three weeks. Four weeks of history gives you a baseline built from your own store and your own staff, which beats any industry rule of thumb.
Two rules keep the numbers comparable. Use rates instead of counts: voids per 100 transactions, and discounts as a share of each employee's gross sales. A full-timer will always rack up more raw voids than a weekend part-timer, and that says nothing about honesty. The second rule is to compare people who work similar shifts. Friday night at a bar and Tuesday lunch produce very different exception patterns for perfectly ordinary reasons.
Reading a POS Void Report: Look Past the Count
Start with the rate, then look at what sits behind it. The table below is an illustrative week at a liquor store. It assumes four cashiers over one week and counts only voids that happened after payment. The numbers are made up to show the method and don't come from a real store.
| Cashier | Transactions | Voids after payment | Voids per 100 transactions |
|---|---|---|---|
| A | 820 | 6 | 0.73 |
| B | 790 | 5 | 0.63 |
| C | 410 | 9 | 2.20 |
| D | 760 | 7 | 0.92 |
| Team | 2,780 | 27 | 0.97 |
Leave Cashier C out and the other three have 18 voids across 2,370 transactions, or 0.76 per 100. C's rate is about 2.9 times that. This justifies a closer look and nothing more.
Open C's nine voids one by one, starting with timing. A void before tender usually means a scanning or keying mistake. A void minutes after a completed cash sale, with nothing rung in its place, is the pattern to worry about. Next, check how the original sale was paid. Void-based theft depends on cash, because voiding a card sale reverses money the employee never held. Last, look at what came right after. An honest mistake is usually followed by the correct item a few seconds later.
Suppose C's voids are all small cash sales on Sunday nights when C works alone, and none is followed by a re-ring. That's worth checking on video. If the voids are spread across tenders and each one is followed by a correction, you more likely have a new hire who needs scanner practice.
What counts as normal depends on the business, and knowing the honest reasons keeps you from chasing false alarms. Liquor stores void sales when a customer can't produce valid ID after the items are scanned. Those voids should cluster on evenings and weekends and line up with a refused-sale log if you keep one. Grocery lanes see voids when produce is weighed under the wrong code or a shopper comes up short at the end of a big order.
Restaurants should separate deletes, which remove items before the ticket reaches the kitchen, from voids made after the kitchen has it. A post-send void should carry a reason code such as "kitchen error" or "guest changed order" plus a manager approval. Bars generate voids from tab transfers and split checks, so the reason code tells you more than the raw number does.
What a No-Sale Report and Cash Refunds Reveal
A no-sale opens the cash drawer without a transaction. It has honest uses, such as making change for a customer or a manager pulling a safe drop. Count no-sales per shift, then read the timestamps.
The pattern that matters most is a no-sale seconds after a customer leaves. That can mean a cash sale was taken without being rung, and the drawer was opened so the money could go in now and come out later. A run of no-sales during a busy cash rush is another warning sign, since there's little reason to open the drawer outside a sale when every customer is paying anyway.
The subtlest version shows up on the over/short report. Honest drawers drift a little from day to day. A cashier whose drawer comes out exactly even shift after shift, while their no-sale count runs high, may be pulling the overage before the count. Our guide to safe drops, deposits and dual control covers the cash procedures that make this harder to pull off.
Cash refunds deserve the same read. The weakest ones have no linked original sale, or were processed by the same employee who rang the purchase. Check the camera at the refund timestamp too. A refund with no customer at the counter, especially one entered near closing, needs an explanation.
Card refunds can be abused as well, when the money goes back to a card that wasn't used for the original purchase. The simplest fix is a policy that every refund links to the original transaction and returns to the original tender. Enforce it in the POS if your system allows.
Where POS Discount Abuse Hides: Comps, Overrides and Employee Meals
Discounts are the quietest exception because each one looks small. Giving friends or family free or discounted items is called sweethearting. To put illustrative numbers on it, a cashier who discounts a friend's basket three times a week produces 156 discounted sales a year, every one coded as legitimate. Multiply that by your average discount and you have the cost.
Pull the discount report by employee and by reason code. Employee discounts deserve a look when they land on tickets while that employee isn't clocked in, or show up several times in one shift. Manager overrides that concentrate under one manager's code, especially on shifts that manager didn't work, usually mean a code or swipe card is being shared.
Grocery and retail stores should watch price overrides, where an item rings at a lower manual price than the shelf tag. Compare a sample of override prices against the shelf before assuming anything, since outdated tags cause honest overrides too.
At the bar, comps running above house policy are the thing to watch, particularly when they concentrate with one bartender on the nights the same regulars come in. Employee meals have their own tell: a full table's worth of food rung at the end of a shift, or more than one meal per person.
Restaurants and bars should put comp rules in writing so the report has something to compare against. The policy might allow one buyback round per regular per visit and one shift meal up to a set menu value. Without a written policy, every comp is defensible.
Match Each Flag to Video Before You Talk to Anyone
A report flag tells you where to look, and video tells you what happened. Review the footage before any conversation. Accusing someone over a pattern with an honest explanation can cost you a good employee and invite a legal claim.
- Sync the clocks. Check the camera system's clock against the POS clock and note any drift. If the camera runs four minutes slow, you'll be watching the wrong customer.
- Copy the transaction detail. For each flagged item, record the transaction number and exact time from the report, along with the terminal and the tender.
- Watch a window around each timestamp. Review a minute or two on either side. You're looking for whether a customer was actually there and where any cash went.
- Check several flags. One bad-looking clip can have an innocent explanation. Five that look the same is a pattern.
- Document as you go. Save each clip alongside its report page, and write a plain note on what the clip shows.
- Bring in a second person. Have another manager or the owner review the evidence before any conversation, and keep that person in the room when it happens.
Check your recorder's retention setting today. Many systems overwrite older footage after a set period, and a flag you find on Monday is useless if the clip is already gone. Some camera systems can link to POS data and overlay transaction text on the video, which speeds up this review considerably. Ask your camera vendor whether yours supports it.
Rules on workplace recording and audio capture vary by state, and so do rules on employee interviews and paycheck deductions. Treat this section as general information, and talk to an employment attorney before you discipline or fire anyone over suspected theft. Our article on preventing employee theft in a retail store covers the policy side.
Set Permissions so Loss Prevention Reports Stay Useful
Loss prevention reports are only as good as the logins behind them. If several people share one manager code, the discount report can't tell you who did what. These settings make every report sharper:
- Give every employee a unique login, and retire codes the day someone leaves.
- Require manager approval for post-payment voids and cash refunds.
- Cap discounts at a set percentage unless a manager approves the exception.
- Make a reason code mandatory on every void and discount, comps included.
- Tie the employee discount to the employee's own login so nobody can apply it from someone else's.
Blind drawer counts help too. The cashier counts the drawer before seeing the expected total, which removes the temptation to make the count match the screen.
If your current system can't enforce these controls, more training won't close the gap. Our POS feature checklist by business type lists what to ask about permissions and reporting. You can also compare the POS systems MannyPay offers for restaurant and bar payment setups or liquor store processing. A free quote request gets a reply from a MannyPay specialist within one business day.
Start this Monday. Export four weeks of the five reports and calculate each employee's void rate and discount share. Then confirm how many days of video your recorder keeps. With that baseline in place, next week's reports will tell you which flags are worth checking on video.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
