For finance teams
Agentic bookkeeping with controls you can actually audit.
The question isn't whether an agent can do bookkeeping. It's what happens when it gets something wrong. Here is our answer, in mechanisms rather than adjectives.
Book a walkthroughThe control surface
Four things the software will not let an agent do.
- 01Draft and send are separate operations.
Every mutating action splits in two. The agent holds the first. A human holds the second. This is enforced in the tool layer, not in a prompt.
- 02No agent touches money.
Accounts payable is remind-only by design. There is no payment capability to misuse.
- 03Tenant isolation fails closed.
If an organization context cannot be resolved, access is denied rather than defaulted. That behavior is covered by an automated test that runs on every build.
- 04No autonomous credential change.
No agent may create, reset, rotate, or disable a credential without explicit confirmation from a named human, for that exact account and action. Written policy, enforced in the operating rules of the system.
Where the agent stops
The split, drawn.
Draft
- Categorize a transaction
- Reconcile against the statement
- Prepare an invoice or reminder
- Compose the follow-up message
Approve
- Named user, recorded
- Editable before it goes
- Rejectable without side effects
Sent, posted, filed
- Invoice reaches the contact
- Entry lands in the ledger
- Attributed to the approver
There is no path from the left column to the right one that does not pass through a person. That is a property of the tool layer, not a setting, so it cannot be switched off for convenience. Money never appears in any column: accounts payable is remind-only.
Every action has a name on it.
Approvals, edits, sends, and org switches are all recorded against a user.
Not a log you have to reconstruct. A record with a person on it.
It replaces the bookkeeping seat, not your stack.
Bank feeds arrive through Plaid. QuickBooks history imports on day one, with optional continuous sync afterward. Multi-entity and consolidated reporting are available on Pro.
Your controller keeps the controls. Scotty does the volume.
The honest scope.
What does not exist today, stated here so your security team finds it on this page rather than in a call.
- No SSO, SAML, or SCIM today.
Accounts are created and managed directly. If your identity provider is a requirement rather than a preference, say so in the walkthrough and we will tell you honestly where it sits.
- No contractual uptime SLA today.
We will not put a number in a contract that we cannot yet stand behind with operating history.
Three steps, no procurement theater.
- 1A walkthrough on a real ledger, not a canned demo.
- 2Your security review, with this page and our documentation as the starting point.
- 3A scoped pilot on one entity before you commit anything wider.