Spending controls finance signs off on
Write the policy, set the approval matrix, and review each agent payment's rule, approver, and receipt.
The controls a controller asks for
Spend policy
Company rules apply to every agent. Team rules narrow them for one department, and agent rules narrow them for one job. A denial at any layer stops the payment.
Approval matrix
For wallet payments, route requests by amount, category, or new recipient to approver roles or named members. Set how many approvals a request needs, the order, escalation, and expiry.
Change control
Owners and admins can change a policy. Team managers can tighten their own team's rules. Each change saves a numbered version you can compare or restore.
Receipts
Review receipts in Conto or retrieve payment records through the API.
Month-end review
Export payment records with their decisions and approvals for account matching.
Audit log
Each entry is linked to the one before it by a hash, so an edited or deleted entry fails verification. Owners and admins on Builder or Enterprise can export it as CSV.
The request, the approval, and the receipt
A request waits with its rule and budget. A paid request keeps its receipt, with the policy that approved it.
procurement-agent wants to pay Kestrel Data
kestreldata.io · data · first payment
- Rule
- Trust score below 70
- Budget left
- $15,900 of $40,000
- Waiting
- 4 minutes
Northwind Ops
Over weekly limit · 12 minutes
- Agent
- procurement-agent
- Category
- Compute
- Policy
- compute-spend-v3
- Transaction
- 0x9f2c…a8e1
Trail
- Requested09:14:02
- Approved by policy09:14:02
- Executed onchain09:14:05
- Settled09:14:11
- Reconciled09:15:00
The payments too big to auto-clear
Try a request above the approval threshold and review the rule that paused it.
Run the supply chain demo