Segregation of Duties (SoD)
Segregation of Duties (SoD) is the control principle of dividing a transaction's key tasks — authorising, recording, and holding the related asset — among different people, so no one individual controls it end to end. It is built into how roles and system access are assigned. It matters because concentrating those tasks in one person is the single biggest opening for fraud and undetected error in a finance function.
What Is Segregation of Duties (SoD)?
Segregation of Duties splits the incompatible parts of a transaction so that carrying out a fraud or hiding an error would need two or more people to collude. The classic separation is between authorising a transaction, recording it in the books, and having custody of the asset involved. If the person who approves a payment cannot also enter it and release the funds, a fabricated payment becomes far harder to push through.
An Indian business meets SoD as a core internal control that auditors look for when assessing internal financial controls. It is expressly recognised as a control activity in the ICAI's Standards on Auditing (SA 315) and the Guidance Note on internal financial controls. The challenge is sharpest in small teams, where one accountant may naturally do everything — which is exactly where compensating controls and owner review become essential.
Key terms
- Month-End Close Checklist — A close routine where SoD over review and posting applies.
- Ind AS 102 Share-based Payment — Complex accounting needing controlled, separated review.
- Vesting Period Graded Amortization — An ESOP calculation that benefits from independent review.
Why Segregation of Duties (SoD) Matters
Concentrating duties in one person is where most internal frauds begin:
- Undetected fraud — One person who can approve, record and pay can create and conceal a fictitious payment with nobody to catch it.
- Errors with no second check — A mistake made and recorded by the same person passes straight into the accounts unreviewed.
- Control weakness in the audit — Auditors treat missing segregation as a control deficiency, which can affect the internal financial controls report.
- Asset misappropriation — Custody of cash or stock combined with recording lets shortages be hidden by adjusting the books.
- Key-person risk — A single person controlling a whole cycle makes the business hostage to their honesty and their availability.
How Segregation of Duties (SoD) Works - Step by Step
SoD is applied by mapping and splitting the incompatible tasks in each cycle:
- 1Map the transaction cycle
The key tasks — authorise, record, custody, reconcile — are identified for each process such as procure-to-pay.
- 2Identify incompatible combinations
Tasks that must not sit with one person, like approving and paying, are flagged — the SoD matrix.
- 3Assign tasks to different roles
Duties are distributed across staff so no single role spans an incompatible combination.
- 4Enforce through system access
Accounting-software roles and approval limits are set so the split is enforced technically, not just on paper.
- 5Add compensating controls where needed
In small teams, owner review, bank-statement scrutiny or maker-checker steps compensate for unavoidable overlaps.
Segregation of Duties (SoD): A Practical Example
| Particulars | Amount (INR) | Treatment |
|---|---|---|
| Purchase invoice entered by Accountant A | 3,20,000 | Recording duty |
| Payment approved by Finance Manager | 3,20,000 | Authorisation duty (separate person) |
| Funds released by Accountant B | 3,20,000 | Custody/execution duty (third person) |
| Bank reconciliation by Accountant A | - | Reviewed independently by Finance Manager |
A Pune manufacturing firm splits a ₹3,20,000 supplier payment across three people: Accountant A records the invoice, the Finance Manager approves it, and Accountant B releases the funds. No single person can both create and pay a bill. When A prepares the bank reconciliation, the Finance Manager reviews it — a compensating check that keeps segregation intact even in a lean team.
One person owning the whole cycle: Letting an accountant approve, record and pay concentrates fraud risk → split at least authorisation from execution and recording.
Common Mistakes With Segregation of Duties (SoD)
SoD breaks down quietly, usually as teams grow or shrink:
- One person owning the whole cycle — Letting an accountant approve, record and pay concentrates fraud risk → split at least authorisation from execution and recording.
- Segregation on paper only — Roles look separate but shared logins let one person do everything → enforce the split through individual system access.
- No compensating control in small teams — Accepting overlap in a lean team without any review leaves the gap open → add owner review or maker-checker steps.
- Ignoring access creep — Access rights accumulate as people change roles, quietly recombining duties → review system roles periodically.
Segregation of Duties (SoD) is the control principle of dividing a transaction's key tasks — authorising, recording, and holding the related asset — among different people, so no one individual controls it end to end. It is built into how roles and system access are assigned. It matters because concentrating those tasks in one person is the single biggest opening for fraud and undetected error in a finance function.
Need help with Segregation of Duties (SoD)?
Segregation of Duties (SoD) sits inside your day-to-day books. Patron's CA-led team keeps them accurate, compliant and audit-ready.
Applicable framework: ICAI Standards on Auditing (SA 315) and Guidance Note on Internal Financial Controls; Companies Act 2013 (IFC). For general information only, not professional advice. Verify the current position for your entity before acting.