What is segregation of duties in AP? Definition and example
Accounts payable and procure-to-pay
Segregation of duties in AP is splitting key accounts payable tasks, such as setting up vendors, entering invoices, approving them, and releasing payments, among different people, so no one can both commit and conceal an error or fraud. It's a core internal control that auditors test.
- Type
- Internal control
- Roles
- Separate incompatible duties
- Small teams
- Compensating reviews
- Audit trail
- Named users and approvers
Which AP duties should be separated?
Keep apart the duties that, combined, let one person create a payment and hide it.
| Duty | Should not also have | Why |
|---|---|---|
| Vendor master changes | Invoice entry or payment release | Could create a fake vendor and pay it |
| Invoice entry | Invoice approval | Could enter and approve a false bill |
| Invoice approval | Payment release | Could approve and pay without review |
| Payment release | Bank reconciliation | Could pay and hide it in the reconciliation |
| Payment release | Vendor bank detail changes | Could redirect payments |
Segregation of duties example
Example: At Thornbury Distribution, one AP clerk can edit vendors and release payments. Between Tuesday, September 1 and Friday, October 30, 2026, the clerk adds a fake vendor and pays it three invoices, each under the $5,000 second-approval threshold. A vendor master change report reviewed on Monday, November 2 finds it. All amounts are illustrative.
| Payment | Amount | Below $5,000 threshold? |
|---|---|---|
| Sep 14, 2026 | $4,800 | Yes |
| Oct 2, 2026 | 4,950 | Yes |
| Oct 26, 2026 | 4,900 | Yes |
| Total | $14,650 |
The payments were coded to consulting expense, so Thornbury reclassifies them as a theft loss while it pursues recovery.
| Date | Account | Debit | Credit |
|---|---|---|---|
| Nov 2, 2026 | Loss from employee theft | 14,650 | |
| Consulting expense | 14,650 | ||
| Total | 14,650 | 14,650 |
With vendor setup and payment release split, the fake vendor would have needed a second person to create it.
How can a small AP team segregate duties?
A small team can't always split every task, so it adds review controls that would catch what the overlap allows.
- Owner or controller review: Monthly review of vendor changes and payments
- Bank-side controls: Dual approval for payments, and positive pay
- Reports: Vendor master change and payments-by-vendor reports, signed off
- Independent reconciliation: Someone outside AP reconciles the bank
What is segregation of duties confused with?
Segregation of duties is most often confused with approval limits and with internal controls in general.
| Term | What it is | How it differs from segregation of duties |
|---|---|---|
| Internal controls | Policies and procedures that give reasonable assurance that financial reporting is reliable and assets are protected | The whole system; SoD is one control |
| Approval workflow | Routing rules that send an invoice or payment to the right approvers, often by amount, department, or vendor | Sets who approves; SoD sets who can't do two things |
| Payment approval | Authorization step, often by amount threshold, in which a designated person approves a payment before funds are released to a supplier | One of the duties to separate |
| Fraud risk | The risk that someone inside or outside the company will misappropriate assets or misstate the financial statements on purpose | What SoD reduces |
Quick test: if one person can set up a vendor, approve its bill, and release the payment, duties aren't segregated.
Segregation of duties vs maker-checker
Maker-checker requires a second person to approve each transaction; segregation of duties keeps whole roles apart, such as vendor setup and payment release. Maker-checker is one way to apply segregation of duties to a single step.
Segregation of duties at month end
At month end, you review access and the reports that compensate for overlaps, as part of the month-end close.
- Vendor changes: Review every new vendor and bank detail change
- Payments: Review payments by vendor, especially just under thresholds
- Access: Check that AP system roles still match job duties
- Bank reconciliation: Prepared and reviewed by someone outside AP
ERP role tools, such as SAP Access Control, can flag users whose roles conflict. our AP Agent uses amount-based approval tiers, posts nothing until a named approver signs off, and keeps a record of who did each entry, who approved it, and why.
Common segregation of duties mistakes
The most common segregation of duties mistakes split tasks on paper but not in the system.
- Shared logins: Two people on one account means no segregation
- Leaving old access: Role changes without access changes create conflicts
- Ignoring vendor master access: Vendor master access can enable fictitious vendors or redirected payments
- No review of overrides: Admin users can bypass every split