Why 'Trust, But Verify' Matters for South African Businesses
Owners and buyers often treat the general ledger (GL) as gospel. But sophisticated, low‑profile frauds can hide among legitimate entries. In the South African context—where cash flow for SMMEs and mid‑market firms is tight—a few missing rands can become a business‑threatening hole. Below are 10 invisible fraud schemes that commonly hide in the GL, with real‑world examples, detection signals and practical controls you can implement today.
10 Invisible Fraud Schemes and How to Expose Them
1. Ghost Vendors and Duplicate Vendor Accounts
Scheme: Payments are made to fake suppliers or to the same supplier set up multiple times to permit duplicate payments.
- Example: A Cape Town contractor created two vendor records for "Supa Supplies" and submitted duplicate invoices to be paid twice.
- Detection: Run vendor master reports for identical bank account numbers, contact details or VAT numbers. Look for sequential invoice numbers from the same supplier.
- Control: Implement vendor onboarding verification (ID, CIPC docs, proof of banking) and require secondary approval for new vendors.
2. Fictitious Refunds and Cash Skimming
Scheme: Recorded refunds or credit notes are issued, but cash is diverted to an employee or third party.
- Example: A retail outlet in Durban recorded multiple customer refunds but the customer accounts showed no returns; cash was pocketed by a cashier.
- Detection: Match refund entries with POS return receipts and CCTV where available; investigate refunds processed outside standard hours.
- Control: Require customer signatures for returns and segregate refund processing from cash handling.
3. Payroll Padding and Ghost Employees
Scheme: Ghost employees receive salaries or managers add overtime/allowances for themselves and others.
- Example: A Johannesburg SMME found three salaries paid monthly to names not on operational rosters; the bank account belonged to a former temp.
- Detection: Reconcile payroll to HR records, check bank account changes and run headcount variance reports monthly.
- Control: Link payroll to HR approval workflows and require proof of banking and ID when adding or changing employees.
4. Manual Month‑End Journals to Hit Targets
Scheme: Unsanctioned journals are posted at month‑end to inflate revenue, deflate expenses or hide losses.
- Example: Finance in a manufacturing firm posted recurring "adjustment" journals that masked cost overruns.
- Detection: Flag high‑value or unusual journals entered after hours or by a small group of users; track recurring identical entries.
- Control: Require supporting documentation, independent approvals and an audit trail for manual journals.
5. Round‑Tripping and Fictitious Revenue
Scheme: Revenue is artificially created through circular transactions with related parties or shell entities.
- Example: A services company reported sales to a client that subcontracted the same work back—no net economic benefit.
- Detection: Investigate large, nonrecurring sales with little receivable collection activity and related‑party disclosures.
- Control: Tighten related‑party transaction reviews and require written contracts and delivery evidence.
6. Related‑Party Payments to Shell Companies
Scheme: Payments are routed to companies controlled by insiders and misclassified in the GL.
- Example: Rent classified as "consulting" went to a shell company owned by a director's associate.
- Detection: Review payments to unrecognised suppliers and cross‑reference beneficiary names with director registers (CIPC).
- Control: Mandate disclosures for related parties and enhanced due diligence for new contracts.
7. Expense Reimbursement and Petty Cash Abuse
Scheme: False expense claims, inflated mileage or multiple claims for the same expense.
- Example: A sales rep in the Western Cape submitted repeated overnight allowances without travel logs.
- Detection: Audit a sample of expense claims against receipts, travel logs and calendar entries.
- Control: Use expense management tools with receipt capture and supervisor sign‑off before payments are approved.
8. Inventory Manipulation and Phantom Stock
Scheme: Inventory counts are overstated or write‑offs are misused to divert goods or cover theft.
- Example: A Durban warehouse recorded write‑offs as "damaged goods" while stock was sold off the books.
- Detection: Reconcile stock ledger to physical counts and review write‑off approvals and reasons.
- Control: Introduce surprise counts, barcode scanning and dual sign‑off for write‑offs.
9. FX Manipulation and Cross‑Border Payments
Scheme: Foreign exchange rates or routing are manipulated to skim small margins across many transactions.
- Example: A imports firm showed consistent small FX losses routed to a beneficiary account linked to an employee.
- Detection: Compare ERP FX rates with bank rates and monitor small, frequent adjustments in clearance accounts.
- Control: Standardise FX procedures, use authorised FX providers and review exchange margins regularly.
10. Suspense and Clearing Accounts Left Unreconciled
Scheme: Funds are parked in suspense accounts and never cleared, making them a convenient hiding place.
- Example: A R20k per month item kept reappearing in a suspense account for a chemical supplier with no supporting invoices.
- Detection: Run ageing reports on suspense balances and require investigation of items older than 30 days.
- Control: Limit use of suspense accounts, mandate monthly reconciliations and assign ownership for clearing items.
Practical Next Steps
Start by running simple analytics on your GL: duplicate supplier checks, journal entry exception reports, payroll reconciliations and suspense ageing. Use your accounting system (Sage, Xero, QuickBooks or an ERP) to enforce approvals and keep an immutable audit trail. For buyers performing due diligence, insist on reconciled ledgers and evidence for significant manual adjustments.
If you suspect irregularities, engage a forensic accountant listed with a trusted directory, and preserve records and bank statements. Small improvements in segregation of duties, vendor onboarding and automated checks can prevent large losses. In short: trust your numbers, but verify them.