Exception-Based Reporting: The LP Tool You’re Probably Underusing

Your POS data already knows who’s stealing. EBR just makes it speak up.

Every point-of-sale system in your stores is quietly recording the raw material of internal investigations: every void, refund, discount, no-sale drawer open, and price override, stamped with a time, a register, and an employee ID. Exception-based reporting (EBR) is simply the discipline of mining that data for patterns that don’t look right — and it remains one of the highest-ROI tools in loss prevention.

Here’s how it works in practice. Instead of reviewing transactions at random or waiting for a tip, you define “exceptions”: the transaction types most associated with employee theft and error. The classic list includes:

• Excessive voids and refunds, especially post-transaction voids processed after the customer leaves
• Discount abuse — employee discounts applied to non-employees, or discounts clustered around one associate
• No-sale drawer opens with no corresponding transaction
• Price overrides concentrated on high-value items or with a single cashier
• Refunds without a receipt or with repeated “customer” names

The software flags transactions that exceed thresholds you set, and your investigators review the exceptions rather than the entire transaction universe. A 200-store chain might generate millions of transactions a month; EBR narrows the review pool to a few hundred genuinely suspicious ones.

Three best practices separate programs that work from ones that just generate noise:

1. Tune your thresholds to your business, not the vendor default. Out-of-the-box settings are built for an average retailer that doesn’t exist. Start with vendor baselines, then adjust based on your first 90 days of data. Too sensitive and your team drowns in false positives; too loose and real theft sails through.

2. Pair data with video. An exception tells you what happened; synchronized POS video tells you how. The strongest programs link the two, so an investigator clicks a flagged refund and immediately watches the transaction. Without video confirmation, you’re building cases on data alone — and data alone rarely sustains a termination or prosecution.

3. Close the loop with operations. EBR findings should feed back into training, not just investigations. If one store’s cashiers generate triple the voids of comparable stores, that’s often a training problem before it’s a theft problem. Share anonymized trends with store leadership and watch the numbers move.

One caution: EBR is a detection tool, not a conviction machine. Exceptions are starting points for investigation, not proof of wrongdoing. Build your process around verification — review, corroborate, interview — and document every step. The programs that get in trouble are the ones that treat a report as a verdict.

If you’re not running EBR today, you’re leaving your best internal-theft detection capability on the table. And if you are running it but haven’t tuned it in a year, it’s probably crying wolf more than catching thieves.

Want a second set of eyes on your EBR program? Robert John Bonus Consulting assesses exception-reporting setups, tunes thresholds to your operation, and trains your team to work exceptions effectively. Contact us.