Finance
Can I show my auditor who approved each payment, and why?
Agents already match invoices, chase payments and prepare the close. LeafCraft makes sure no one checks their own work, and every decision keeps both reasons.
What's changing in finance
Agents now post, match and pay
Vendor updates put agents inside AP, AR and the close. They act under the vendor's defaults.
Auditors ask about the agent
Who approved this payment, and why, now includes the agent's reasoning.
The AI bill is a new line nobody owns
Finance is asked to budget for AI work without knowing the cost per task.
Two risks the layer removes
The agents you can't see, and the model that gets retired.
Agents you don't know about
In finance, agents arrive through vendor updates and team pilots. LeafCraft finds all of them, gives each an owner, and brings it under your rules or removes it.
A model that gets retired
An agent built straight on one model has to be rebuilt and re-approved when that model is retired or repriced. On LeafCraft you switch the model for that agent in config and keep everything else. Months and a budget, saved.
- The model is retired or repriced
- Prompts, tests and sign-offs rebuilt
- Months of work, a new approval cycle
- The history stays with the old tool
- Pick another model for that agent
- Switching is a config change
- Test it against your own record first
- Rules, limits, owner and memory stay
Why it matters now
In finance, the agents arrived before the rules did.
Finance is where the rules were always strict: maker and checker, limits by amount, a trail for every payment. Agents arrived without those rules. The layer brings them back for every agent, bought or built: a named owner, a limit set before the run, a separate checker and a record your auditor accepts.
The core infrastructure
What LeafCraft runs for finance.
One team
Agents prepare, people decide above the limit, and a separate agent or person checks. No payment is approved by the one who prepared it.
How it works02Your rules
What each finance agent may post or approve alone, what it must pass to a controller, and what it may never touch. Escalation to named people, never silence.
How it works03Your memory
Every approval and rejection with who, when and the reason, next to the agent's reason. The trail your auditor asks for, in your own database.
How it works04Your budget
A cost limit per task, per agent and per agent type, set before the close or the payment run starts, so AI spend is a line you forecast.
How it worksAI and people, one team
Your finance team, with AI on the org chart.
The agent prepares the case. Your person makes the call and writes why. A separate audit agent checks the decision against your rules.
What changes for you
Matched INV-55120 to PO-9931 and GRN-2210.
Passed to Kavya Reddy.
Approved.
Checked the decision against the rules. Passed.
How it helps your people
Who it helps around finance.
Industries where it runs
Leaders who ask first
Questions teams ask
Can an agent approve payments?
Only up to the limit its record has earned. Above that, the agent recommends and a person decides, and both reasons are kept.
Does this replace our ERP?
No. Agents read and write to the ERP you already run. LeafCraft adds the rules, the limits and the record.
Can our auditors read the record?
Yes. It is kept on your side, unchanged, and exports in open formats on demand.
Bring one finance process.
We'll map who does the work, who decides and who checks, set the cost limits and show you the record.