Till, refund and discount abuse
Voids, refunds and manual discounts are tracked by cashier, hour and store, flagging behaviour that stands apart from peers.
Overview
Rules (“alert on refunds above 3,000 TL”) only catch what you already imagined; anyone who knows the threshold stays under it, and when volumes change the rule drowns you in false alarms. Anomaly detection instead learns a profile of normal behaviour from history — by branch, hour, product and season — then scores meaningful deviations from it. New abuse patterns nobody predicted get caught, while seasonal swings stop generating noise.
How it works
Scope
Each transaction or event is scored 0–100 so the team works down from the riskiest.
Each alert shows which signals triggered it — “why did this fire?” always has an answer.
Critical anomalies reach the responsible manager instantly by e-mail, SMS or WhatsApp.
Team feedback and seasonality modelling steadily reduce unnecessary alerts.
Your existing business rules stay in place; the model adds the patterns they cannot catch.
Every alert opens as a case, recording who reviewed it and what was decided.
Industry Use Cases
“Abnormal” means something different in every industry — a till shortfall here, a vibrating bearing there. The setups we build most often:
Voids, refunds and manual discounts are tracked by cashier, hour and store, flagging behaviour that stands apart from peers.
Combinations of amount, time, device and location that deviate from a customer’s usual profile are scored instantly.
Machine sensors and quality measurements are monitored to catch pre-failure drift and rising scrap rates early.
Fuel use, distance, load and route data are compared per vehicle, flagging consumption that cannot be explained.
Electricity, water and gas use is monitored per building and floor, reporting deviations such as consumption rising in an empty building overnight.
Access at unusual hours or from unusual locations and abnormal data-download volumes are detected.
Typical Gains
Figures show typical ranges from comparable projects; actual results depend on your data quality and processes.
Integration
FAQ
A short analysis on your historical data shows what the system would catch — before any deployment.