[ SOX / Segregation of duties ]

Segregation of duties for AI agents

An agent that can create a vendor and pay it, or prepare a journal entry and post it, collapses the separation your controls depend on. engini lets you split agent work the way you split people’s: separate toolsets for separate duties, each on its own account, with every run tied to the person who started it, while approval and posting stay with a different person in the ERP.

NetSuiteSAP S/4HANACOSO principle 10Journal entries
Read about engini skills →
Prepare and post, kept apart
  1. Preparer agenttoolset: create journal entries; preparer account
  2. NetSuite logo
    Entry created, pendingthe ERP’s approval routing applies
  3. Reviewer agenttoolset: read only; flags anomalies
  4. A person approves in the ERPcontroller, separate role, separate login
Illustration of the flow on this page, not a product screen.
What it is
Separation of duties carried over to agents
Control area
COSO principle 10; SOD in financial applications
engini provides
Separate toolsets and connections per duty; runs tied to people
You still own
The SOD matrix, approval and posting in the ERP, periodic review
[ 01 / The problem ]

Agents can collapse duties you spent years separating

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.

[ 02 / How it works ]

Map duties to toolsets, accounts and people

01 / Map

Start from your SOD matrix

List each agent duty, such as prepare, review, post, pay, and mark which combinations conflict.

02 / Split

One toolset per duty

Build a toolset per duty with only its tools, each on a connection whose ERP role matches that duty.

03 / Attribute

Tie runs to people

Use personal connections where the ERP should apply that person’s role. Every run is recorded under the user who triggered it.

04 / Review

Check combinations

Review toolsets, connections and MCP servers each period for conflicting combinations, across systems, not only inside one.

[ 03 / What the agent reads and writes ]

Where separation is enforced

SystemRecordsAccess
engini toolsetsOne per duty; owner-only; enforced on the server for CLI, SDK and REST APIScope
engini connectionsOne per duty, each with an ERP role that matches itIdentity
engini MCP serversEach limited to the connections and tools chosen at setupScope
NetSuite or SAP S/4HANARoles, authorizations and approval routingERP control
engini History and audit logEvery run under the user who triggered itRecorded
[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the word separate under the line "One toolset per duty", and three labels: prepare, review, approve in ERP

Editorial image: duties kept apart.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account using my "preparer" NetSuite connection: on the last business day of each month at 9:00, read the accruals schedule from the "Accruals" Google Sheet and create one NetSuite journal entry per row, leaving each entry for approval in NetSuite. Post the list of created entries to #close in Slack.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

What separates duties, and what does not

Enforced

Toolsets per duty

Each agent sees and can call only the tools in its toolset, enforced on the server for CLI, SDK and REST API calls. Toolsets are owner-only.

Enforced

Accounts per duty

Each toolset or MCP server uses its own connection, and the ERP role on that connection limits what the duty can do.

Recorded

Runs tied to people

Every run is recorded under the user who triggered it, so actions stay attributable even on shared accounts.

Not offered

No approval gate

engini does not inspect content, block an action by its values, or hold an action for approval. Keep approval and posting with a different person in the ERP.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect your systems, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can one AI agent create and post a journal entry through engini?

Only if you give it both tools on an account that can do both. To keep SOD, give the preparing agent create tools on a preparer account and leave approval and posting to a different person in the ERP.

How does engini enforce the split?

Each agent gets a toolset with only its duty’s tools, enforced on the server for CLI, SDK and REST API calls, and each toolset uses a connection whose ERP role matches the duty. MCP servers are limited to the connections and tools chosen when they are set up.

Can a person widen an agent’s access by using it?

A toolset belongs to the user who made it; through the API, CLI or SDK another user gets "not found". A person can still combine two connections they hold, which is why ERP role design and periodic review remain your primary SOD controls.

Does engini check the content of an action, such as an amount?

No. engini does not inspect content or block an action by its values, and it has no approval step. Put amount thresholds and approvals in the ERP’s own approval routing.

What about conflicts across systems?

Review them across the whole chain, not only inside one system. Because agent access to each system runs through engini connections, toolsets and MCP servers, engini is the place to list who and what can reach each step.