Use GOVENANT and an AI finance agent + your GL together — govern the AI accounting & finance agents, not the framework. The ledger is already the substrate. Make the agents answer to it.
A controller deploys agents to reconcile accounts and prep month-end close for a company processing 50,000 transactions a month.
A reconciliation job that “ran” is not an account that reconciles; a posted entry the agent claims is not one a human authorized. Segregation of duties lives in a policy PDF, not in the system — and the exceptions are exactly what a job-success dashboard hides.
Completion keyed to the accounting outcome, money-moving actions pinned to approval as gates, exceptions kept as an honest log. The sweep — SELECT-only over the ledger — surfaces three accounts marked reconciled with unexplained variances, and hands the auditor the exception log they trust most.
The substrate: The general ledger and finance systems of record: posted entries, reconciliations, cleared invoices, closed periods — an audit trail built for exactly this.
The path — Native substrate: The platform already produces records that map to the standard — the sweep reads what it already keeps.
| GOVENANT shape | an AI finance agent + your GL source |
|---|---|
| Action ledger | The general ledger — posted entries are append-only by design |
| Ownership gate (segregation of duties) | Payments, transfers, adjustments — pinned to human approval, enforced not documented |
| Verified outcome | The account reconciles / the item clears — not “the job ran” |
| Miss log | Accounts marked reconciled with unexplained variance — the exceptions auditors trust most |
-- "Job succeeded" is not "account reconciles". Keyed to the accounting outcome.
create or replace view gov_reconciliation as
select a.id as account, r.ran_at,
(abs(a.gl_balance - a.source_balance) < 0.01) as reconciled -- verified
from account a
join recon_run r on r.account_id = a.id and r.by_agent;The substrate shapes and acceptance tests are open (CC BY 4.0): developer integration · the portable schema.
Wear the Built-on badge with a real mapping; publish self-assessed levels with probe logs — never “certified,” and complementary to (not a replacement for) SOC 2, financial audit, or controls attestations. A reproducible delivery-and-exception record is exactly the evidence those reviews ask for.
It will never say “supported” or “certified” before a working example lands and its record is public — progress lives in the GitHub issue. Holding our own examples to the standard’s claims discipline is the product.
All sample projects · Govern AI accounting & finance agents · All integrations · Run the audit