Segregation of Duties Checklist

A structured checklist for mapping incompatible duties, detecting SoD conflicts in ERP roles, documenting mitigating controls, and maintaining ongoing compliance across your finance organization.

Free download Excel, Word & PDF 28+ compliance tasks
NP
DS
MR
+
Used by 2,100+ compliance teams
Segregation of Duties Checklist
Duty Mapping (Week 1)
Inventory all finance roles and permissions
Define incompatible duty pairs per process
Conflict Detection (Week 2)
Run SoD conflict report from ERP
Classify conflicts by risk level
Remediation (Week 3)
Reassign conflicting roles where possible
Document mitigating controls for accepted risks
Monitoring (Ongoing)
Schedule quarterly SoD reviews
Integrate SoD checks into user provisioning
38% Complete — 3 of 8 tasks done

Build your segregation of duties checklist

Check off tasks, assign owners, and set due dates. The live preview updates as you work through each compliance phase.

1

Duty Mapping (Week 1)

Inventory all finance roles and permissions
Define incompatible duty pairs per process
Map duties to the four SoD categories (authorize, custody, record, reconcile)
Extract ERP role assignments and transaction codes
Identify high-risk process areas (AP, AR, payroll, treasury)
Build the SoD conflict ruleset matrix
Validate ruleset with process owners
2

Conflict Detection (Week 2)

Run SoD conflict report from ERP
Classify conflicts by risk level (high, medium, low)
Identify users with conflicts across multiple processes
Check for super-user or firefighter access violations
Cross-reference conflicts against actual transaction history
Document conflict findings with evidence
Review conflict report with management
3

Remediation (Week 3)

Reassign conflicting roles where operationally feasible
Remove unnecessary access and dormant accounts
Document mitigating controls for accepted risk conflicts
Define monitoring procedures for each mitigating control
Obtain management sign-off on accepted risk conflicts
Implement role redesign in ERP (custom roles, composite changes)
Rerun conflict report to confirm remediation
4

Monitoring (Ongoing)

Schedule quarterly SoD conflict reviews
Integrate SoD checks into user provisioning workflow
Set up automated alerts for new SoD violations
Review mitigating control effectiveness each quarter
Update SoD ruleset when processes or systems change
Report SoD status to audit committee annually
Archive SoD evidence for external audit
Live preview
Segregation of Duties Checklist
Period:
0
Done
28
Pending
28
Total

Implement segregation of duties in five steps

1

Map duties

Inventory every finance role and permission. Define which duty pairs are incompatible across authorize, custody, record, and reconcile functions.

2

Detect conflicts

Run SoD conflict reports from your ERP. Classify each conflict by risk level and cross-reference against actual transaction history.

3

Remediate

Reassign roles where feasible, remove unnecessary access, and document mitigating controls for conflicts that must be accepted.

4

Validate

Rerun conflict reports to confirm remediation worked. Get management sign-off on any remaining accepted-risk conflicts.

5

Monitor

Schedule quarterly reviews, integrate SoD checks into user provisioning, and set up automated alerts for new violations.

Download a ready-to-use SoD template

Excel (.xlsx)

Pre-built with conflict matrix, role-permission mapping, risk classification, and mitigating control documentation columns.

Word (.docx)

Print-friendly SoD workpaper with conflict descriptions, remediation plans, and management sign-off sections.

PDF

Locked format for audit archives. All 28+ tasks grouped by phase with risk level and owner columns.

A 4-week SoD review cycle, mapped out

A typical SoD review runs over three weeks of active work plus ongoing monitoring. Here is how each phase maps to the cycle.

W1
Duty Mapping
  • Inventory roles
  • Define conflicts
  • Map SoD categories
  • Build ruleset
W2
Detection
  • Run conflict reports
  • Classify by risk
  • Check super-users
  • Document findings
W3
Remediation
  • Reassign roles
  • Remove excess access
  • Mitigating controls
  • Rerun reports
Ongoing
Monitoring
  • Quarterly reviews
  • Provisioning checks
  • Automated alerts
  • Annual reporting
MappingDetectionRemediationMonitoring

Automate SoD monitoring and compliance

Bluecopa enforces segregation of duties through role-based access controls, real-time conflict detection, and a complete audit trail for every transaction.

Get a Demo →

How segregation of duties works

Segregation of duties (SoD) is an internal control principle that divides critical financial tasks among different people so that no single individual can authorize a transaction, have custody of the related assets, record it in the books, and reconcile the account. The goal is to prevent fraud and errors by requiring collusion for any misstatement to go undetected.

1 Map duties

Break every financial process into its component duties: authorization, custody, recording, and reconciliation. Define which pairs of duties are incompatible when held by the same person.

2 Detect conflicts

Extract role assignments from the ERP and compare them against the conflict ruleset. Flag users who hold incompatible duties and classify each conflict by risk level based on the process and the potential for loss.

3 Remediate

Resolve conflicts by reassigning roles, removing excess access, or redesigning ERP roles. Where separation is not operationally feasible, document mitigating controls and define monitoring procedures.

4 Monitor continuously

Embed SoD checks into the user provisioning workflow so new conflicts are blocked before they start. Run quarterly reviews, set up automated alerts, and report SoD status to the audit committee annually.

Segregation of duties best practices

✓ Do this

  • ✓ Define SoD rules at the transaction-code level, not just the role level
  • ✓ Cross-reference access conflicts against actual transaction history
  • ✓ Build SoD checks into user provisioning so conflicts are caught before access is granted
  • ✓ Document every mitigating control with its monitoring procedure and owner
  • ✓ Review SoD quarterly and after every major system or org change
  • ✓ Include IT security and business process owners in the review, not just audit

✕ Avoid that

  • ✕ Treat SoD as a one-time project rather than an ongoing program
  • ✕ Accept all conflicts as "mitigated" without verifying the mitigating control works
  • ✕ Grant firefighter or super-user access without logging and post-review
  • ✕ Skip SoD analysis for non-production systems that copy production roles
  • ✕ Let managers approve their own access requests in the provisioning workflow
  • ✕ Rely on compensating controls as a permanent substitute for role redesign

Segregation of duties terms, explained

Incompatible Duties

Two or more responsibilities that, when combined in one person, create an unacceptable risk of fraud or error. The classic example: the person who authorizes payments should not also reconcile the bank account.

Mitigating Control

A compensating control put in place when a SoD conflict cannot be eliminated. It must be designed to detect misuse and must be monitored by someone independent of the conflicting duties.

Conflict Ruleset

A matrix that defines which duty pairs are incompatible. It is typically maintained at the ERP transaction-code or permission level and forms the basis of automated SoD conflict scanning.

Firefighter Access

Temporary elevated access granted to resolve a critical issue. It must be time-limited, logged, and reviewed after use. Unreviewed firefighter access is one of the most common SoD audit findings.

User Provisioning

The process of granting, modifying, and revoking system access. Embedding SoD checks into provisioning prevents new conflicts from being introduced when access is granted or changed.

Four-Way Separation

The principle that four functions should be held by different people for each financial process: authorization (who approves), custody (who holds assets), recording (who books entries), and reconciliation (who verifies).

Frequently asked questions about segregation of duties

Segregation of duties (SoD) is an internal control principle that divides critical tasks among different people so that no single individual controls all aspects of a transaction. The four key functions that should be separated are authorization, custody of assets, recording, and reconciliation.
SOX Section 404 requires management to assess and report on the effectiveness of internal controls over financial reporting. SoD is a foundational control: if one person can both create a vendor and approve payments to that vendor, the risk of fraudulent disbursements is high. Auditors routinely test SoD as part of their ICFR assessment.
The most common AP conflicts are: creating vendors and approving invoices, processing payments and reconciling the bank account, entering purchase orders and approving receipts, and maintaining the vendor master and processing payments. Each of these pairs allows a single person to create fictitious transactions and cover their tracks.
When full separation is not feasible, implement mitigating controls: manager review of all transactions processed by the conflicting user, automated exception reports, independent reconciliation by a different person, and periodic access reviews. Document each mitigating control, assign an owner, and test it regularly.
At minimum, quarterly. Additionally, run ad-hoc reviews after any major organizational change (restructuring, M&A), ERP upgrade or role redesign, or significant personnel changes. Embedding SoD checks into the user provisioning workflow provides continuous monitoring between reviews.
Yes. Platforms like Bluecopa enforce role-based access controls, run continuous SoD conflict scans against the conflict ruleset, and flag violations in real time. Automated monitoring catches new conflicts as soon as access is provisioned, rather than waiting for the next periodic review.

Related checklists