Bank Reconciliation and Payment Controls: The CFO’s Anti-Fraud Routine
Use daily cash visibility, independent reconciliation and beneficiary controls to reduce treasury fraud and reporting error.
A bank reconciliation is often treated as a month-end accounting task. In reality it is one of the cheapest anti-fraud controls available. It detects duplicate payments, unauthorised debits, missing receipts, bank charges, stale instruments and manipulation of the cash balance.
The preparer of payments should not be the sole reconciler.
High-volume accounts need daily or near-daily reconciliation.
New or changed bank details deserve a stronger control than routine payments.
Old reconciling items require investigation, not perpetual roll-forward.
1. The operating framework
| Control | Frequency | Escalation trigger |
|---|---|---|
| Cash-position report | Daily | Unexplained movement, negative balance or covenant buffer breach. |
| Bank reconciliation | Daily/weekly for operating accounts; monthly minimum for low activity. | Unidentified debit/credit, old item or unreconciled difference. |
| Beneficiary master review | On creation/change plus periodic review. | Name mismatch, personal account, offshore account or email-only request. |
| Payment release | Transaction level | Override, split payment, weekend/holiday release or new beneficiary. |
| User-access review | Quarterly and on role change/exit. | Dormant user, shared credential or incompatible maker/checker role. |
| Bank confirmation | At reporting dates and audit | Account omitted from ledger or confirmation difference. |
2. CFO playbook
- Maintain a complete bank-account register including dormant, escrow, deposit and payment-gateway accounts.
- Import bank statements directly where possible; restrict manual statement upload and editing.
- Require independent preparation/review or compensating CFO review with evidence.
- Age every reconciling item and set automatic escalation at 7, 30 and 60 days.
- Verify beneficiary additions and changes through an independent channel.
- Use payment batches, dual authorisation and bank limits aligned with the delegation matrix.
- Review bank users, tokens, mandates and authorised signatories immediately on employee/director exit.
3. Practical example
A ₹9.8 lakh payment appears in the bank but not the ERP. The reconciling accountant should not post it automatically to “vendor advances.” The payment file, bank user log, beneficiary details and approval trail must be inspected first; the difference may be a duplicate or unauthorised payment.
4. Common failure points
- Reconciling only the closing balance without reviewing transactions.
- Leaving payment-gateway and collection accounts outside the bank register.
- Allowing shared banking credentials.
- Posting unidentified receipts to revenue.
- Carrying stale cheques and transfers indefinitely.
5. Evidence folder
- Bank-account register
- Daily cash report
- Signed reconciliations
- Reconciling-item ageing
- Beneficiary verification log
- Payment approval and bank log
- Quarterly access/mandate review
6. Finin2min takeaway
Design the evidence before the transaction.
Reliable compliance is the result of clear ownership, timely action, reconciled records and a documented escalation route—not a last-minute filing exercise.