Revenue leakage is the most expensive thing a small business runs blind to. Money that should have arrived and didn't; money that arrived and was misallocated; money that disappeared at the seams between systems. Each leak is usually small. The cumulative effect over a quarter — particularly in F&B and retail with dozens of payment flows — can be material.
Here are the seven leakage patterns we walk into most often when inheriting a Singapore F&B or retail set of books, and the dashboard signals that surface each one early.
1. Delivery platform payout shortfalls
The expected payout from a delivery platform is knowable: gross orders × (1 - commission rate) - refunds. The actual payout from the platform sometimes doesn't match. Causes include promotional adjustments the operator forgot they signed up for, chargebacks netted off, fee changes the platform implemented without clear notification, and occasional reconciliation issues on the platform side.
Dashboard signal: weekly platform payout vs expected. Variance above tolerance flagged for investigation. Our Outlier agent watches this for clients.
2. Card terminal settlement gaps
Daily POS card sales should reconcile to the next day's bank settlement deposit. When they don't, the cause is usually one of: a terminal that didn't close its batch properly, a settlement that was held by the acquirer, a refund processed against the wrong terminal, or a merchant fee netted off without clear breakdown.
Dashboard signal: daily card sales per terminal vs settlement deposit. Reconciliation age — “deposits 3 days behind expected” — flagged immediately.
3. Cash drawer shortages
Till counts that consistently come in short of POS cash sales. Each individual variance might be small (rounding, change errors, an honest miscount), but persistent shortage points to either operational discipline issues or, in worse cases, theft.
Dashboard signal: cumulative cash variance per outlet per week. A single outlet consistently running variance above 0.5% of cash sales is a flag.
4. Voids and refunds without supervisor approval
POS systems usually allow voids and refunds with a manager PIN. When voids exceed normal patterns or are processed by the same staff repeatedly, the difference between recorded revenue and actual cash collected widens.
Dashboard signal: voids and refunds as a percentage of sales, per outlet, per shift. Anomalies surfaced in the exception feed.
5. Receivables that quietly age out
For F&B with catering or wholesale, and for retail with B2B or marketplace components, receivables can slip past payment terms. Customers stop responding to chasers; the bookkeeper writes them off as bad debt; the operator never knew the revenue was at risk.
Dashboard signal: AR aging with customers past 60 days called out; total value at risk; trend over time.
6. Wholesale or catering invoices not raised
A catering job is delivered; the manager confirms the customer is happy; everyone moves on; the invoice never gets raised. Three months later someone notices the customer was never billed. By then, raising the invoice belatedly is awkward and sometimes the customer claims confusion.
Dashboard signal: jobs scheduled but no invoice raised within 7 days. A simple workflow check.
7. Promotional discounts absorbed when they shouldn't be
Delivery platforms often run promotions where the operator and the platform share the discount cost. If the platform's reporting collapses operator-absorbed and platform-absorbed promos into a single line, the operator can end up paying for discounts that were supposed to be platform-funded — or claiming back less than they're entitled to.
Dashboard signal: promotional cost per platform vs revenue. Reconciled against platform statements to confirm the split.
The structural fix: build leakage detection into the dashboard
The pattern across all seven: the leak is detectable if you're looking, invisible if you're not. A working dashboard doesn't leave the operator to spot anomalies manually — the exception feed surfaces them automatically.
For Acuitas clients, the Outlier agent watches the common leakage patterns and surfaces deviations to the dashboard's exception feed. The human review confirms or dismisses; persistent flags trigger operational review with the operations lead.
What “normal” tolerance looks like
Rough rules of thumb we use (adjust to your operation):
- Card settlement reconciliation: variance under 0.1% of card sales
- Platform payout reconciliation: variance under 0.5% of platform revenue
- Cash drawer variance: under 0.5% of cash sales per outlet
- Voids / refunds: under 2-3% of sales (varies by concept)
- AR aging past 60 days: under 5% of total receivables
Above these, investigation. Persistent breach, structural review.
Common questions about revenue leakage
How much revenue do most operators leak before catching it?
Varies enormously by operation. We've seen individual issues (a single platform's payout systematically short for months) cost multiple percentage points of revenue before being caught. Cumulative leakage in poorly-monitored multi-channel operations can be 2-5% of revenue — material for any business running on tight margins.
How do I know if I have leakage today?
Run the seven checks above against your current data. If reconciliation isn't happening at all, you don't know — start there. If it's happening but variance is persistent, the leakage is detectable but isn't being addressed.
What's the difference between leakage and normal business loss?
Normal loss is expected — small cash variances, occasional voids, some bad debt. Leakage is loss that should have been prevented or recovered. Tolerance bands above help separate the two; what falls within tolerance is normal, what exceeds it is leakage.
Should I tell staff I'm monitoring for leakage?
Yes, generally. Transparency about controls is healthy and the monitoring itself is a deterrent. The dashboard exception feed is usually visible to outlet managers; structural issues are addressed with the operations lead.
What if I find systematic leakage — what's the recovery process?
Depends on the source. Platform payout shortfalls: raise with the platform's merchant support, usually recoverable for current period and recent history. Card settlement issues: raise with acquirer. Cash shortages: operational review with the outlet team. The point of catching leakage early is making recovery viable; caught late, recovery options narrow.
Revenue leakage is the cheapest thing to fix because every dollar caught is a dollar back. The dashboard discipline is what turns “wish we'd known” into “caught it Monday morning and recovered it Tuesday”.
— The Acuitas team