Build your SoD matrix offline with a live conflict checker. Pre-labeled fields for finance processes including AP, AR, GL, payroll, and treasury. Download the free template and start today.
| Process | Authorize | Custody | Record |
|---|---|---|---|
| AP Invoice | Manager | AP Clerk | GL Team |
| Vendor creation | Controller | N/A | AP Clerk |
| Payment release | CFO | Treasury | GL Team |
| AR Credit memo | Manager | AR Clerk | AR Clerk |
| Process | Authorize | Custody | Record |
| Vendor payments | Finance Controller | Treasury Manager | AP Executive |
| Payroll processing | HR Head | Treasury Manager | Payroll Analyst |
| Bank reconciliation | Finance Controller | Treasury Manager | GL Accountant |
| Journal entries | CFO | Not applicable | GL Accountant |
| Petty cash | Office Manager | Office Manager | Accounts Executive |
| Process | Check | Result |
| Vendor payments | No role holds two duties | Clear |
| Payroll processing | No role holds two duties | Clear |
| Bank reconciliation | No role holds two duties | Clear |
| Petty cash | Office Manager authorizes and holds cash | Conflict |
| Maker and checker must be different users | All processes |
| Access rights reviewed every quarter | Finance Controller |
| Conflicts need a compensating control | CFO approval |
This segregation of duties policy template lays out who authorizes, who holds custody and who records for each finance process, then checks the matrix for conflicts.
Download it free with your business email. It has a pre-built SoD matrix covering AP, AR, GL, payroll, and treasury functions.
List each financial process in scope. For each, identify who authorizes, who has custody, and who records the transaction.
Review the matrix for rows where the same role appears in more than one column. These are SoD conflicts that need mitigating controls.
Get management approval, document mitigating controls for any accepted conflicts, and schedule the next review cycle.
Ready to run your first segregation of duties policy? Start from a layout that already works.
SoD splits critical financial tasks among multiple people so that no single individual controls all stages of a transaction. The three core functions are authorization, custody, and recording.
Map every financial process that involves money, assets, or reporting. AP, AR, payroll, treasury, and journal entries are the most common starting points.
For each process, identify who authorizes (approves), who has custody (handles the asset or payment), and who records (posts to the ledger).
Create a matrix mapping processes to roles. Flag any cell where the same person or role appears in more than one duty column.
For each conflict, either reassign the duty to a different role or document a compensating control (supervisory review, dual approval, system restriction).
Review the matrix whenever roles change. Access creep (gradual accumulation of permissions) is the most common source of new SoD conflicts.
Want these terms next to the numbers?
Segregation of duties (SoD) is an internal control that divides critical tasks among multiple people to prevent fraud and errors. No single person should be able to initiate, approve, and record a financial transaction.
SoD prevents unauthorized transactions, reduces fraud risk, and satisfies audit requirements. Regulators and auditors expect documented SoD policies for SOX compliance, internal audits, and financial reporting.
The three core functions are authorization (approving transactions), custody (handling assets or payments), and recording (posting entries to the ledger). No one person should perform all three for any transaction.
Yes. No cost, no account, no watermark. You only need a business email to download it.
Review your SoD policy at least annually, or whenever there are organizational changes like new hires, role changes, or system migrations. Regular reviews catch access creep and role conflicts.
An SoD conflict occurs when one person has access to two or more incompatible duties. For example, if the same person can create vendors and approve payments, they could create a fake vendor and pay themselves.
Templates work for small teams with stable roles. When you have 50+ users, frequent role changes, or audit findings around access conflicts, automation tools like Bluecopa can continuously monitor SoD conflicts across your ERP.