Watch every payment, loan and fee, not a sample of them.
Banks, lenders, insurers and fintechs run millions of transactions a day. We test all of them against your rules and the regulator’s, so problems surface in days, not at the next audit.
01Where money leaks in financial services
Payments and vendor spend
Duplicate payments, bank-detail changes and payments outside the normal runs.
Loans and credit
Loans approved outside policy, restructured to hide arrears or paid out to linked parties.
Fees and charges
Fees waived without approval, or never charged at all.
Claims and commissions
Insurance claims and agent commissions that don’t match the policy.
Twelve use cases across lending, payments, insurance and compliance
- Disbursement checksLoan files, approvals, bank accounts
- Evergreening and restructuringRepayment history, restructures
- Collateral and valuation gapsCollateral register, valuations
- Payment anomaliesPayment files, vendor master, logs
- Dormant account activityAccount master, transactions
- Treasury limit breachesDeal records, limits
- Claims anomaliesClaims, policies, repair invoices
- Agent and broker commissionCommission rules, policies sold
- Mis-selling signalsSales, cancellations, complaints
- KYC and screening gapsCustomer master, sanctions lists
- Fee waivers by userFee rules, waivers, user IDs
- Access used outside roleRoles joined to transactions
Each use case names the data it needs. Core banking, card and claims systems usually sit outside the ERP.
One case: from a quarterly sample to a daily test
Payments: the controls existed. Nobody saw them fail.
- Situation
- A lender tested its payment controls each quarter, on a sample of a few hundred transactions.
- What a sample misses
- A bank-detail change and a payment the next day each look approved. Together they are the warning.
- Data and technique
- Every payment joined to the vendor master change log and user IDs; rules run each night, with risk scores by vendor and approver.
- Typical findings
- Payments to accounts changed within 48 hours; approvals by the person who raised the request; payments outside the normal runs.
- Control fix
- A call-back before any payment to a changed account; same-user approval blocked; exceptions sent to owners each morning.
A control tested once a quarter can fail for 89 days before anyone knows.
Illustrative composite case, read-only access.
A lender moves its payment controls from quarterly to daily →
Lending, payments and claims: 12 tests to run first
| Lending and payments | Insurance and fees |
|---|---|
| Loans paid out before every approval | Claims filed soon after the policy started |
| Repeated restructuring of the same loan | Repair invoices from one garage across many claims |
| Disbursements to accounts linked to staff | Commission paid on cancelled policies |
| Payments to recently changed bank accounts | Fees waived by the same user, again and again |
| Dormant accounts that suddenly move money | Charges below the published tariff |
| Treasury deals outside limits or hours | Customers onboarded with incomplete KYC |
Thresholds follow your policy and the regulator’s rules, and are tuned on the results.
05Earn $ and Save $ in financial services
A lender moved 40 payment controls from a quarterly sample to a nightly test of every transaction, and stopped USD 600K of payments to changed accounts in six months.
Where is your money hiding?
06Other industries
Where is your money hiding?
Three minutes to an estimate. Thirty minutes to a plan. Six weeks to valued findings on your own data.