Segregation of duties is a basic control activity under COSO: no single actor should be able to initiate, approve and record a transaction without an independent check. The PCAOB keeps finding the classic failure, the same individual able to prepare and post journal entries without approval or a compensating control (PCAOB, 2025).
AI agents raise the stakes. KPMG notes that agentic workflows can collapse traditionally separate roles into a single orchestrated process (KPMG, 2026). PwC points out that the conflict often sits in the orchestration layer between systems, where no single system’s controls can see it (PwC, 2026). engini is that layer, so it is where agent duties should be split.
How agents break SOD
- One agent with one broad token can create, change and post.
- One integration account does every job, so the ERP cannot tell duties apart.
- The person running the agent gains, through it, rights they do not hold.
- Conflicts span systems, such as a vendor created in one and paid from another.
Split agent duties like people’s
In engini, each duty gets its own toolset: a preparer toolset with tools to create journal entries or vendor bills, a reviewer toolset with read-only tools, and nothing that posts or pays unless that is the agent’s single job. Each toolset uses its own connection, and each connection’s ERP role matches that duty, so the ERP enforces the split too. Toolsets belong to the user who made them, so someone using an agent cannot widen it.
Use personal connections where the ERP should apply that person’s own SOD role. Every run is recorded under the user who triggered it. engini cannot hold an action for approval, so keep approval and posting where they already live: with a different person, in the ERP’s own approval routing.
NetSuite
SAP S/4HANA