At a glance
- Maker-checker: one person enters, another independently verifies and authorises.
- Dual custody: cash, keys, security stationery and valuables are held jointly by two officials.
- Audit trail: every system entry records who did what and when; user IDs must never be shared.
- Exception reports must be reviewed daily and the review evidenced.
- Concurrent and internal audits test whether controls work in practice.
You will learn
- The logic of segregation of duties
- Key branch controls with examples
- Reviewing exception reports effectively
- Responding to audit observations
- Red flags of control breakdown
01Why controls exist
Most branch frauds and losses are not sophisticated. They happen when one person can both initiate and approve, when passwords are shared, or when exception reports are signed without being read. Controls make it hard for one mistake or one dishonest act to go unnoticed.
02Core controls
| Control | How it works | What goes wrong without it |
|---|---|---|
| Maker-checker | Separate users enter and authorise transactions | Fictitious entries, wrong debits |
| Dual custody | Two keys/two officials for strong room, cash safe, security forms | Cash shortages, misuse of cheque books and DD leaves |
| User access management | Role-based access; IDs disabled on transfer; no sharing | Transactions under someone else's ID |
| Exception reports | Daily review of large cash, overdrawings, parameter changes | Unauthorised overdrafts, dormant account misuse |
| Reconciliation | Suspense, sundry and inter-branch accounts reconciled on time | Hidden frauds parked in suspense |
| Leave and rotation | Mandatory leave and job rotation for sensitive desks | Concealed long-running frauds |
03Reviewing exception reports
- 1Read every itemDo not sign in bulk.
- 2Ask whyFor each exception, check the reason and supporting document.
- 3ActRegularise, reverse or escalate.
- 4EvidenceRecord remarks and sign with date; keep the report.
04Cash and valuables
- Cash balance verified jointly at day end; surprise checks by branch head.
- Keys of strong room and safes held by different officials; key register maintained.
- Security stationery issued and returned with register entries.
- Locker operations recorded with customer signature and time.
05Working with auditors
Treat audit observations as early warnings. Rectify with evidence, not just a reply that it 'will be complied'. Track repeat observations: they show a control that is not working.
06Key terms explained
Separation of duties where one person prepares a transaction and another authorises it.
Joint control by two officials over cash, keys and valuables.
System records showing who did what and when, used to investigate errors and frauds.
Continuous audit of high-risk branches and functions, close to the time of transactions.
Risk-Based Internal Audit, which focuses audit effort on the highest-risk areas.
Case study: A shared password
An officer leaves his system logged in during lunch. A temporary staff member uses the ID to change a dormant customer's mobile number, and money is transferred out the next day.
- Audit trail shows the officer's ID made the change.
- Exception report for mobile number changes was signed without review.
- Both the access lapse and the review lapse contributed to the loss.
Lesson: Lock screens, never share IDs, and actually review exception reports. Each control covers the gap of another.
Illustrative case. Names and figures are invented for learning.
Common mistakes to avoid
- Signing exception reports without reading.
- One official holding both keys 'temporarily'.
- Leaving suspense entries unreconciled for months.
- Not disabling user IDs of transferred staff.
Exam and interview angle
- Know maker-checker, dual control, four-eyes principle and segregation of duties.
- Concurrent audit focuses on high-risk areas in large branches; internal audit (RBIA) assesses risk-based.
Frequently asked questions
What is the four-eyes principle?
At least two people must review or approve a significant transaction, the same idea as maker-checker.
What is risk-based internal audit?
An audit approach that focuses resources on the highest-risk areas and branches, as required by RBI for banks.
Test yourself
3 questions. Pick an answer to see the explanation.
Q1. Maker-checker ensures that:
It separates entry from authorisation.
Q2. A high-risk exception is:
This pattern is common in account takeover frauds.
Q3. Mandatory leave for staff in sensitive positions helps to:
Long-running frauds often surface when the person is away.
Facts used in this guide
| Fact | Source | As of |
|---|---|---|
| Control guidance | RBI guidelines on internal controls and bank policies | 9 Nov 2026 |
Rules, limits and rates change. Check the current official text before using any figure for an operational decision.
Official sources
Clerk2Officer guides are educational. They do not replace RBI directions, your bank's circulars or professional advice.