Early access · segregation of duties for close agents

Your close agents can't approve their own entries.

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.

Or try the demo first · about a minute, works on a phone

JE-1128 · accrualheld
Dr 6420 Professional fees48,500.00
Cr 2110 Accrued liabilities48,500.00
  1. close-agent-a · preparedkey ca-7f3e
  2. close-agent-a · approverefused
  3. close-agent-b · same modelrefused
  4. Controller · sign-offwaiting

Synthetic example. No agent approves its own work.

Why this matters now

Agents collapse the roles that segregation of duties keeps apart.

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).

One service account

Every close agent posts as the same user. The ERP log says "integration-bot" prepared it and "integration-bot" approved it.

One model behind every agent

A second agent on the same model shares the first one's blind spots. That's a second opinion in name only.

A sign-off with no trail

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

An agent booked an accrual. Try to get it approved.

Northwind Parts (a made-up company) is closing November. Its close agent prepared the entry below. Work through the three steps in order.

JE-1128 · accrual · draftNorthwind Parts (fictional)
Closing period
Nov 2026
Posts to period
Dec 2026
Prepared by
close-agent-a · key ca-7f3e · model vendor A
Support
Invoice INV-3307, outside counsel, services Nov 1–30, received Dec 4
AccountDebitCredit
6420 Professional fees48,500.00
2110 Accrued liabilities48,500.00
  1. The agent that prepared it
  2. A second agent, same model vendor
  3. A model from vendor B

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

Separate keys, an outside check, and a sign-off you can prove.

01

One key per agent

Each close agent gets its own identity instead of a shared service account. Every entry records which agent prepared it.

02

Preparer can't approve

The gate refuses an approval from the key that prepared the entry, and from any agent on the same model.

03

A different vendor checks

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.

04

The controller signs

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

For finance teams, and for the vendors who sell to them.

  • Controllers, CAOs and SOX leads. At public and IPO-prep companies putting agents into the close: show who prepared, who checked and who approved each entry, without a spreadsheet of screenshots.
  • AI-native accounting vendors. Your customers' SOX reviews will ask how your agents' entries get approved. Ship per-agent keys and signed approvals with your product.
  • Evidence, not a verdict. We don't audit you and can't promise an audit outcome. Close of Record keeps records your auditor can check for themselves.

Show that no agent approved its own journal entry.

Early access is free while we build it. Leave your work email and we'll be in touch.