One service account
Every close agent posts as the same user. The ERP log says "integration-bot" prepared it and "integration-bot" approved it.
Early access · segregation of duties for close agents
Every agent gets its own key. The agent that books an entry can't approve it, a model from a different vendor re-checks it, and the controller's sign-off is recorded, ready for your auditor.
| Dr 6420 Professional fees | 48,500.00 |
| Cr 2110 Accrued liabilities | 48,500.00 |
Synthetic example. No agent approves its own work.
Why this matters now
Audit guidance on agentic AI in financial reporting warns that these workflows can merge preparer and reviewer into one automated process, and that sharing a model or a service account makes it worse.
"Agentic AI workflows could compromise segregation of duties policies by collapsing traditionally separate roles into a single orchestrated process. This risk is amplified when agents use a shared model."
"Using shared service accounts can further weaken the audit trail."
Source: KPMG, "Agentic AI workflows in financial reporting: Risk, governance, and control considerations" (2026).
Every close agent posts as the same user. The ERP log says "integration-bot" prepared it and "integration-bot" approved it.
A second agent on the same model shares the first one's blind spots. That's a second opinion in name only.
Someone clicked approve in a chat window. Months later, nobody can show which entry, which amounts or which person.
For calendar-year companies, year-end testing of internal control over financial reporting (ICFR) happens in the first months of the year. That's when this question gets asked.
Try it · synthetic data
Northwind Parts (a made-up company) is closing November. Its close agent prepared the entry below. Work through the three steps in order.
| Account | Debit | Credit |
|---|---|---|
| 6420 Professional fees | 48,500.00 | |
| 2110 Accrued liabilities | 48,500.00 |
Everything here is fictional and runs in your browser with no network calls. The signature is real Ed25519, made with a key generated in your browser for this demo.
How it works
Each close agent gets its own identity instead of a shared service account. Every entry records which agent prepared it.
The gate refuses an approval from the key that prepared the entry, and from any agent on the same model.
A model from a different vendor re-reads the entry against its support and flags what doesn't match: the period, the amount, the account.
A person in an approver role confirms or fixes it, with a reason. The sign-off is signed over a digest of that exact entry.
Two kinds of teams
Early access is free while we build it. Leave your work email and we'll be in touch.