Glossary · Accounting & Bookkeeping
Segregation of Duties (SoD)
Definition
Segregation of duties (SoD) is an internal control that splits the key tasks in a transaction among different people. The usual split is between authorising a transaction, recording it, holding the related asset (such as cash or stock) and reconciling the balance. Because no one person controls the whole transaction, fraud or error would need two or more people to collude or would be caught by the next person.
At a glance
- Category
- Accounting & Bookkeeping
- In this entry
- What it means for Indian businesses How it works · Example
In practice
01 What it means for Indian businesses
If the person who approves a payment cannot also enter it and release the money, a fake payment is much harder to push through. SoD is one of the first controls an auditor looks for when testing internal controls, and the Standards on Auditing issued by ICAI (SA 315) list it among control activities.
For companies where internal financial controls are reported on, the statutory auditor states whether the company has adequate internal financial controls over financial reporting and whether they operated effectively. SoD is a core part of that review, so companies document an access matrix and approval limits. Exempt: private companies that are OPCs or small companies, or have turnover below ₹50 crore and borrowings below ₹25 crore, if they have not defaulted in filing under s.137 or s.92.
Small teams find SoD hardest, because one accountant may do everything. There, compensating controls fill the gap: owner review of bank statements, maker-checker approval in the banking portal, or a monthly review of reconciliations.
| Duty | Example task |
|---|---|
| Authorise | Approve a purchase or a payment |
| Record | Enter the bill or the payment in the books |
| Custody | Release funds or hold stock and cash |
| Reconcile | Prepare the bank or vendor reconciliation |
How it works
02 How it works
- Map each cycle
Such as procure-to-pay, and list its tasks.
- Find incompatible pairs
Such as creating a vendor and approving its payment.
- Assign tasks to different roles
So no role holds an incompatible pair.
- Enforce it in the system
With individual logins, role rights and approval limits.
- Add compensating controls
Where a small team cannot avoid overlap.
Worked example
03 Example
An example, not advice on your facts.
A Pune manufacturing firm handles a ₹3,20,000 supplier payment like this:
| Step | Person | Duty |
|---|---|---|
| Enter the purchase invoice | Accountant A | Record |
| Approve the payment | Finance Manager | Authorise |
| Release the funds | Accountant B | Custody |
| Prepare the bank reconciliation | Accountant A | Reconcile, reviewed by the Finance Manager |
No single person can both create and pay a bill. The Finance Manager's review of the reconciliation is a compensating check in a lean team.
Watch out
04 Common mistakes
- One person owning the whole cycle. At minimum, separate authorising from recording and paying.
- Segregation on paper only. Shared logins let one person do everything.
- No compensating control in small teams. Overlap without review leaves the gap open.
- Access creep. Rights pile up as people change roles. Review system access regularly.
- Treating maker-checker as full SoD. Maker-checker is one control. If the same user can create a vendor, raise the bill and release the payment, duties are still not segregated.
Questions
05 Questions people ask
- What is another word for segregation of duties?
- It is also called separation of duties or division of duties. A closely related term is the maker-checker control, where one person prepares a transaction and a second person approves it.
Need help with segregation of duties? See our SOP Drafting & Implementation or Accounts Payable Outsourcing.
Review and sources
Sources: ICAI study material ch.10 (G.S.R. 583(E), 13 Jun 2017)
