Agent capital reference
Treasury and Accounting
How to account for autonomous agent spend: ledgers, reconciliation, receipts, approvals, refunds, fees, settlement, and audit trails.
Updated
2026-07-06
Status
Source-backed. Educational. Not financial advice.
Key facts
What this page establishes
- Agent spend should be recorded from intent through settlement, not only after money moves.
- A useful ledger links task, policy decision, authorization, settlement, receipt, fee, and refund evidence.
- Failed and denied attempts belong in the treasury/risk record because they expose misuse and control gaps.
- Accounting classification should use task purpose and merchant evidence, not rail labels alone.
Agent spend creates an accounting problem before it creates a finance dashboard problem. A human cardholder can explain a purchase after the fact. An agent may execute hundreds of small purchases, retries, partial settlements, failed authorizations, and refunds without a useful memory of why each event happened. Treasury needs a record that does not depend on the model remembering its plan.
The ledger should start at intent, not settlement. If the first record appears only after money moves, the organization has lost the most important evidence: why the agent believed the payment was allowed, what policy approved it, and what task the spend served.
"cryptographic audit trail"
A useful event model
A treasury-ready agent payment has at least six events:
- Intent created: the agent requests authority to spend for a task.
- Policy evaluated: the budget, counterparty, category, and risk controls are checked.
- Authorization issued: the wallet signs, card authorizes, or payment token is created.
- Settlement observed: the rail confirms payment, transfer, or capture.
- Receipt matched: invoice, API response, service usage, or order confirmation is attached.
- Ledger classified: expense category, asset movement, fee, refund, tax treatment, and owner are assigned.
Failed attempts belong in the same log. A denied card authorization, invalid x402 signature, or blocked wallet recipient may be more valuable to risk teams than a successful low-risk transaction.
Reconciliation by rail
| Rail | Primary evidence | Common exception |
|---|---|---|
| x402 | payment requirements, signed payload, facilitator response, transaction reference | resource delivered but settlement evidence missing from treasury export |
| Card issuing | authorization ID, merchant data, capture, clearing, refund, dispute record | merchant category or descriptor does not match the agent's stated purpose |
| Stablecoin transfer | wallet address, transaction hash, chain, asset, amount, recipient metadata | recipient identity is weak or refund path is unclear |
| ACP checkout | checkout session, merchant order, payment token constraints, receipt, fulfillment status | agent-selected item differs from user mandate or return workflow |
Chart-of-accounts design
Agent spend should not be classified only by rail. "USDC transfer" or "virtual card purchase" is not a useful expense category. The chart of accounts needs task context: compute, data, software, research, transaction fee, customer reimbursement, inventory, refund, dispute, or capital movement. The agent can suggest a classification, but finance should keep deterministic mapping rules for recurring vendors and payment types.
A useful record links the accounting entry back to the agent session and policy version. When a budget is changed, the historical entry should still point to the rule that existed at authorization time. That matters for audits and for post-incident review.
Controls finance should ask for
- Budget owner: every agent wallet or card maps to a human or department.
- Expense purpose: every payment carries a task or mandate ID.
- Receipt path: the system knows where proof of service or order confirmation should appear.
- Refund path: the system knows which rail and account receive reversals.
- Exception queue: unmatched settlements, over-budget attempts, and unknown merchants are reviewed.
- Policy versioning: old decisions remain explainable after limits change.
Honest boundary
This page is not accounting advice. The right treatment for crypto assets, stablecoins, card liabilities, refunds, and fees depends on jurisdiction, entity type, and accounting policy. The practical point is narrower: agent spend should emit evidence in a shape that accountants, treasury teams, and auditors can use without reconstructing the agent's hidden chain of thought.