Exception rate
Exception lines per hundred tickets by cashier, terminal and store, against the store and the chain.
Every ticket line of the week, aggregated to store, day, terminal, cashier and exception, so the loss prevention manager sees who is outside the pattern and why before the next weekend. Built on the sales audit fact, not on a separate feed.

Exception lines per hundred tickets by cashier, terminal and store, against the store and the chain.
Returns and voids rung before opening or after close, with the hour and the ticket.
No-sale opens per hundred tickets by terminal, with the reason entered.
Cash-out variances by store and terminal, net and gross, recounts flagged.
Override value by cashier and the average per line; tightening the permission where it is high.
The reason codes that carry most of the dollars, by cashier and store.
Lines rung by one person and attributed to another, combined with any other flag.
Web order sites in the totals, out of the rankings, because they carry no ticket count.
The audit fact loads with the ETL; the week-scoped dataset resolves the last complete Sunday to Saturday week.
The exceptions page is generated: chain scorecard, store table, cashier watch list, day by day, seven finding lists with an action each.
Review CCTV for the tickets, recount the drawer, coach the cashier, tighten the override permission, or no action, recorded against the finding.
Same brief, next week, so a coached cashier's rate is visible against the prior week.
The sales audit fact carries every line with its audit type: regular, price override, discount, return, void, no-sale, over/short. Exceptions are flags on the fact, so the loss prevention view, the sales audit view and the finance journal read the same rows.