A year ago, finance asked whether AI was worth trying. Now it is setting budgets, caps, and allowances. Every one of those controls measures the same thing: what AI costs.
None of them measures whether you can trust what it says.
Finance can see the bill to the penny. It still cannot see whether the answer behind it is any good. And this quarter, that is the gap that matters.
The cost equation is changing. CFO Brew reports that the era of unconditional AI access is over, and finance leaders are working out how to set limits for teams and individuals. Flexera’s CFO splits the problem in two: productivity AI that everyone gets, and consumption AI (developers on coding assistants, for example) that runs on allowances. His division of labor is clean, with the business owning the use case, finance setting the guardrails, and IT keeping usage visible, safe, and controlled.
That is the right conversation. It is also only half of one.
The bill is easy to see. The value isn’t.
As DoiT’s field CTO, Amit Kinha, tells CFO Brew that CFOs get the bill, but the gains are hard to quantify. So the controls that get built are the ones finance can measure: budgets, allowances, caps by team. Clay’s controller, Steve Sidhu, suggests starting broad and tightening over time, without scaring people off experimenting.
All sensible. All about cost.
Cost controls answer one question: how much are we spending? They say nothing about the question the CFO gets asked next: Can we trust what the AI told us?
The guardrail nobody is setting
At a recent panel, Sidhu told a room of finance leaders that most of them probably already have an AI assistant connected to their ERP and are doing real financial work with it. Good. That is where the work is heading.
Now picture the review. Someone asks the AI where cash will land at month-end, and it gives a number. The controller asks where that number came from. Which transactions? Which assumptions? If you ask again tomorrow with no new data, do you get the same number?
If nobody can answer, you don’t have an insight. You have a guess with good formatting. A cap on tokens won’t fix that, and neither will a bigger budget.
What a defensible answer looks like
SmartResearch is built for the second guardrail: the one on answers.
Ask it a plain-English question about cash, vendor trends, collections, or aging, and you get a grounded answer in seconds. But the interface isn’t the point; after all, any frontier model can draw a convincing chart. What makes an answer defensible is what sits underneath:
- Transaction-level ERP data, not the reporting layer, so the answer starts where the money actually moved.
- Context from the agents’ own work. The agents already know what’s in the inbox: vendors asking about payment, customers promising to pay, invoices in dispute. A report can’t see that.
- A finance semantic layer, so the AI understands the domain, not just the documents.
Then the part a CFO cares about most. Every answer ships with its source data, its confidence, and its reasoning. And it’s deterministic: ask the same question twice, and you get the same answer, unless the underlying data changed.
That is the difference between an answer you can use and an answer you can defend.
The test: the CFO pushes back
Picture the weekly cash meeting. The CFO looks at next month’s projected cash position and asks the question every CFO asks. Why is it lower than we thought?
With a spreadsheet, someone says they’ll get back to you. With an AI answer nobody can trace, someone says the model thinks so.
With SmartResearch, the answer arrives with its trail: the receivables that slipped, the payables that landed earlier than planned, what the system is confident about and what it isn’t. The CFO can challenge any link in the chain and see the source. The meeting moves on to the decision instead of stalling on the number.
Why now
Finance is setting AI limits this quarter. The habits that form now will decide which tools the Office of the CFO uses, which data they touch, and which answers get trusted in the boardroom.
Spend guardrails are table stakes. The CFOs who pull ahead will also hold AI to the standard they hold everything else to: show the source, show the reasoning, and be able to defend it.
Set the limits on cost. Then ask for the work behind every answer.
See it in your own question. Book a SmartResearch demo and bring the number you’d least like to defend.