Compliance & Trust

Verified Autonomous Finance

How a sealed mission bounds what an AI agent may pay, and how every payment is reconciled back to the approved intent - held or flagged if it drifts.

Updated 10 min read1 labOwner / FounderAccountant

When an AI agent can initiate a payment, the risk question changes from “is the model good?” to “should this specific transfer happen, given what a human actually approved?” Verified Autonomous Finance answers that by sealing a mission around the agent before it can move a dollar, and by reconciling every payment back to that mission afterward. This doc covers the Mission Envelope, the reconciliation states, and the shadow-mode posture.

The Mission Envelope

Before an agent may act, a controller writes a Mission Envelope: the approved invoice IDs, the approved vendors, the source account, a per-payment cap, an aggregate cap, prohibited actions, and an expiry. The envelope is sealed with a cryptographic hash, and the agent inherits authority only within it. Nothing outside the envelope is authorized.

  • Approved invoices and vendors are listed explicitly
  • A per-payment cap and an aggregate cap are set
  • Prohibited actions are stated
  • An expiry (TTL) bounds the mission in time
  • The whole envelope is sealed with a hash

Intent versus state

After the run, reconciliation diffs what was approved against what actually happened and labels every line. This is where drift becomes visible.

OutcomeMeaning
verifiedMatches an approved invoice, vendor, and the caps
permitted exceptionDiffers, but inside a pre-authorized tolerance
heldOutside the envelope - added late, over cap, vendor changed
unauthorized varianceA payment with no approved basis at all
unable to verifyEvidence missing - never silently passed
The five reconciliation outcomes

Catching drift mid-run

Reconciliation happens after the fact, but session governance happens during the run. A session is bound to the sealed mission and every proposed step is checked in real time. A single risky step is held; a compromised session - mission expired, executing-agent identity changed, mission hash tampered - is halted entirely.

Hands-on labs

Practice against a realistic scenario. Each lab lists the steps, what you should see, and the checkpoints that confirm you got the same result.

Lab 1

Seal a mission and reconcile a run

Scenario

Northwind approves 38 invoices totalling $412,000 for its AP agent to pay this cycle. After sealing, one extra invoice is added to the queue and one vendor’s bank account changes.

Steps

  1. 1

    Create a Mission Envelope with the 38 approved invoices, the source account, and a $412,000 aggregate cap; seal it.

    Expected: A sealed mission with a hash and an expiry.

  2. 2

    Run the agent in shadow mode and open the reconciliation.

    Expected: 36 lines verified; the late-added invoice and the changed-bank vendor are labelled held.

  3. 3

    Open the assurance receipt for the run.

    Expected: A sealed sha256 receipt summarizing every line’s outcome.

Checkpoints - you got it right if…

  • The late-added invoice was held, not paid
  • The bank-change vendor was held for confirmation
  • The run produced a sealed assurance receipt

Frequently asked questions

What is Verified Autonomous Finance?

It is a control that lets an AI agent run a pay run only inside a human-approved, cryptographically sealed mission, then reconciles every payment back to that approved intent and holds anything that drifts outside it.

Does it move money?

Not on its own. It runs in shadow mode by default - it decides and proves what should have been held or blocked without disbursing. You enable enforcement when you trust the record.

What is the difference between reconciliation and session governance?

Reconciliation checks after the run finished; session governance checks during the run and can stop a bad step before it completes or halt a compromised session entirely.

What compromises a whole session?

A change to the executing agent’s identity, a tampered mission hash, or an expired mission window - any of which halts the session rather than holding a single step.

Previous in Compliance & TrustAction GovernanceNext in Compliance & TrustThe Decision Ledger

Keep going

Compliance & TrustAction GovernanceRead docCompliance & TrustThe Decision LedgerRead docCompliance & TrustGoverned-Action EvidenceRead doc

Go deeper in the guides

AI Finance OSWhat Is an AI Finance Operating System?Read guideMonth-End CloseThe Month-End Close Checklist: Every Step, Day by DayRead guide

Ready to try it in your own workspace?

Fintra is the AI Finance Operating System for SMBs - accounting, payroll, planning, HR, and compliance under one login, with governed AI doing the heavy lifting.

Talk to us