Skip to content

What is segregation of duties in AP? Definition and example

Accounts payable and procure-to-pay

Definition

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.

DutyShould not also haveWhy
Vendor master changesInvoice entry or payment releaseCould create a fake vendor and pay it
Invoice entryInvoice approvalCould enter and approve a false bill
Invoice approvalPayment releaseCould approve and pay without review
Payment releaseBank reconciliationCould pay and hide it in the reconciliation
Payment releaseVendor bank detail changesCould 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.

PaymentAmountBelow $5,000 threshold?
Sep 14, 2026$4,800Yes
Oct 2, 20264,950Yes
Oct 26, 20264,900Yes
Total$14,650

The payments were coded to consulting expense, so Thornbury reclassifies them as a theft loss while it pursues recovery.

DateAccountDebitCredit
Nov 2, 2026Loss from employee theft14,650
Consulting expense14,650
Total14,65014,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.

TermWhat it isHow it differs from segregation of duties
Internal controlsPolicies and procedures that give reasonable assurance that financial reporting is reliable and assets are protectedThe whole system; SoD is one control
Approval workflowRouting rules that send an invoice or payment to the right approvers, often by amount, department, or vendorSets who approves; SoD sets who can't do two things
Payment approvalAuthorization step, often by amount threshold, in which a designated person approves a payment before funds are released to a supplierOne of the duties to separate
Fraud riskThe risk that someone inside or outside the company will misappropriate assets or misstate the financial statements on purposeWhat 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.

  1. Vendor changes: Review every new vendor and bank detail change
  2. Payments: Review payments by vendor, especially just under thresholds
  3. Access: Check that AP system roles still match job duties
  4. 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