What is Segregation of Duties in Accounts Payable?

Segregation of duties (SoD) in accounts payable is the internal control principle that divides financial responsibilities so no single person controls an entire transaction from invoice receipt to payment execution. If one person can create a vendor, enter an invoice, approve it, and send payment, they can pay themselves. SoD prevents that by requiring multiple people to complete the cycle.

Nearly 29% of businesses hit by fraud had zero internal controls over their AP process. And according to the ACFE 2024 Report to the Nations, organizations lose roughly 5% of revenue to occupational fraud annually. SoD does not eliminate fraud entirely, but it forces collusion — one person acting alone cannot complete a fraudulent payment. That single constraint stops the majority of AP fraud schemes before they start.

The Five AP Functions That Must Be Separated

Segregation of duties in accounts payable splits the invoice-to-payment cycle into five distinct functions, each assigned to a different person or role:

Function	Who Handles It	Why It's Separated
Vendor master setup	Procurement or AP Manager	Controls who gets paid — if combined with payment, enables phantom vendors
Invoice entry	AP Clerk	Records what's owed — if combined with approval, enables fictitious invoices
Invoice approval	Department Manager	Authorizes the spend — if combined with entry, removes the verification step
Payment execution	AP Specialist or Treasury	Sends the money — if combined with approval, enables unauthorized payments
Bank reconciliation	Accounting or Controller	Verifies what left the account — if combined with payment, hides discrepancies

The critical separation is between approval and payment. When the person who says "pay this" is different from the person who presses "send," you create a checkpoint that catches errors, duplicates, and fraud before cash leaves.

How SoD Works in Practice

A properly segregated AP workflow looks like this:

1. Vendor setup: Procurement adds a new vendor with verified bank details and a W-9. AP cannot create vendors.
2. Invoice receipt: The AP clerk receives the invoice, matches it to a purchase order, and enters it into the system.
3. Approval routing: The system routes the invoice to the appropriate manager based on amount and department. The approver confirms the goods or services were received.
4. Payment processing: A separate AP specialist batches approved invoices for payment processing. They cannot modify invoice amounts or vendor bank details.
5. Reconciliation: An accountant outside the AP team reconciles bank statements against payment records, catching any discrepancies.

Each handoff is a control point. Skip one, and you create a gap a single bad actor can exploit.

SoD for Small Teams (Under 5 People)

Perfect segregation requires at least three people in the payment chain. Teams of two or three cannot achieve full separation. The answer is compensating controls:

• Dual signatures on all payments above a threshold (commonly $5,000)
• Mandatory manager review of all vendor master changes weekly
• Automated duplicate detection to catch what a small team might miss
• Monthly reconciliation performed by someone outside daily AP operations (the owner, a part-time controller, or an external accountant)
• System-enforced rules that prevent the same user from entering and approving an invoice

Compensating controls are not a shortcut. They are the standard approach for small teams, and auditors accept them when properly documented.

Segregation of Duties vs Dual Authorization

Aspect	Segregation of Duties	Dual Authorization
Definition	Different people handle different steps	Two people approve the same step
Scope	Entire transaction lifecycle	Single decision point
Example	One person enters invoice, another approves	Two managers both sign off on a payment
Best for	Preventing end-to-end fraud	High-value transaction control

Most AP teams need both. SoD structures the workflow. Dual authorization adds extra scrutiny at high-risk points like large payments or new vendor setups.

When to Implement SoD

Implement segregation of duties when:

• Your team processes more than 50 invoices per month
• You are preparing for a SOX compliance or financial audit
• A single person currently handles vendor setup through payment
• You have experienced (or suspect) payment fraud or duplicate payments

Skip formal SoD only when:

• You are a solo operator paying fewer than 10 vendors per month — use bank-level controls and monthly self-reconciliation instead

Key Takeaways

• Definition: Segregation of duties in AP splits invoice entry, approval, payment, and reconciliation across different people
• Purpose: Prevents any single person from completing a fraudulent payment without collusion
• Core rule: The person who approves an invoice should never be the person who executes the payment
• Small teams: Use compensating controls (dual signatures, automated detection, external reconciliation) when full separation is not possible

Related Terms

• Accounts Payable Internal Controls - SoD is the foundation of AP internal controls
• Batch Payment Processing - Payment batching creates a review window that supports SoD
• Three-Way Matching - Verification control that complements SoD by validating invoice accuracy
• Accounts Payable KPIs - Metrics to measure whether your controls are working