Finance controls
Segregation of duties in accounts payable: the rules that matter
The handful of AP duty conflicts auditors test first, and practical ways to enforce them in a lean team.
7 min read · Updated 1 November 2026
On this page
Why it matters
Segregation of duties (SoD) means no single person can both commit the company to a payment and make or hide it. In accounts payable, most fraud and most serious errors exploit a missing separation.
The conflicts to avoid
- Creating or changing a vendor (especially bank details) and approving or releasing payments to that vendor.
- Entering a bill and approving the same bill.
- Requesting a purchase and approving the purchase order.
- Approving a bill and releasing the payment run.
- Posting manual journals and approving them.
Enforcing it in NetSuite
- Roles and permissions: separate the roles that maintain vendors, enter bills, approve and pay.
- Approval routing: the preparer is never the approver; workflows route around the requester.
- Vendor change control: a second person confirms bank detail changes before the next payment.
- Amount limits: above a threshold, decisions are made inside NetSuite with full context.
Small teams
When two people run finance, perfect separation is impossible. Compensate with:
- an independent review of the payment run and vendor changes by a manager or the CFO;
- a monthly review of approvals made, by someone outside AP;
- warnings shown to the approver when bank details changed recently or a vendor is new.
Keep chat approvals inside the rules
Approving from Teams or Slack must not become a shortcut around SoD. A controlled approval app executes NetSuite's own approve action, so the same routing, limits and separation apply — and there is no administrator override from chat.
