Blog
Policy-Cited AI: Agents You Can Actually Audit
Explore these solutions:
Will an AI agent act on its own and break a rule nobody caught?
"Agentic" has become one of the most overused words in enterprise software, and treasury teams have good reason to be skeptical of it. An agent that monitors a process and takes action on your behalf is powerful exactly to the extent that it's constrained. An agent that can analyze and act without a clear tether to your actual guardrails is a liability that happens to be fast.
The concern is well-founded and increasingly mainstream. Maximor's CFO AI benchmark found that four in five finance leaders have experienced an AI hallucination firsthand, and only 14% say they fully trust AI outputs even after review. Strategic Treasurer's 2026 Treasury Technology Analyst Report, covered by CTMfile, describes agentic AI as a structural shift in how treasury professionals interact with systems, moving from procedural commands to outcome-driven instructions, which materially changes where and how human oversight has to sit in the workflow. The technology is moving fast, and the consensus among the people who'd be accountable for it is that the human checkpoint has to move with it.
The gap between "agentic" and actually accountable
Plenty of platforms can already reference your policy and answer basic questions about it. That's table stakes, not a differentiator anymore. The harder problem is what happens between the moment an agent notices something and the moment a human decides what to do about it.
If an agent can analyze a position and execute a change without a specific, checkable link back to the policy that justified it, you have a fast system rather than a governed one. And if the agent's reasoning can't be traced back to the actual clause it's operating under, "the AI decided" won't hold up to an auditor, a board or your own team six months later trying to understand why a position moved.
The GSmart difference: propose, cite, wait
Every GSmart agent follows the same discipline, regardless of which part of treasury it touches. It analyzes the position, proposes a specific action and cites the exact policy clause behind that proposal, not a paraphrase or a general justification. Then it waits. Nothing executes until a human approves it.
That discipline is built into the architecture. The math that determines whether a move is compliant runs on a deterministic core, not a language model, so the numbers behind a proposal can't be hallucinated. Generative AI's job is narrower and more specific: explaining the proposal in plain language and drafting the reasoning a human reviews before deciding. Keeping the two separate means the part of the system that touches money never depends on a model guessing correctly.
GSmart doesn't train, fine-tune or adapt any model on your data. The model behind every proposal is the same stock model every customer uses, and it never sees your data as training input. What sharpens over time is your context: the policy, rules, approvals and decisions your team has already made, captured and held so GSmart can draw on them the next time it proposes a move. The model is rented. Your memory is owned.
What this looks like on an ordinary morning
Take a treasury team running three operating accounts and a sweep account against a $14.2 million cash position, with a $2 million minimum floor per entity, a funding order that draws money markets before the revolver and a 40% concentration limit per bank. Done by hand, that morning rebalance means gathering balances, building a worksheet, checking the funding cascade, checking the policy, entering transfers and updating a tracker: roughly two hours rebuilt from scratch every day.
With a policy-cited agent in place, the same exercise becomes: the agent reviews every account, ranks every funding source, checks every constraint and proposes one specific move, for example a transfer from money market into the entity that fell below its floor overnight, with the reasoning shown inline and the exact policy clause cited. A human reviews it in minutes and approves or adjusts. The agent proposes; the person on the desk decides.
What to verify before you trust any agent with treasury actions
Ask three questions of any vendor pitching an "agentic" capability. Does every proposed action cite the specific policy clause behind it, not a general compliance statement? Is there a mandatory human approval step before anything executes, with no override setting that removes it for convenience? And is the math that determines compliance separate from the language model that explains it, so a hallucination in the narrative can't become a hallucination in the number?
If a vendor can't answer all three clearly, the word "agentic" is doing more marketing work than engineering work.
See a policy-cited agent propose its first move. Book a Demo >>
Frequently asked questions
Every agent proposes an action and cites the policy clause behind it, then waits for human approval before executing. You set the autonomy limits in Knowledge Studio.
A chatbot answers questions. A GSmart agent monitors a treasury process, proposes a specific action grounded in your policy and waits for a decision instead of only responding when asked.
Today, every action requires human approval before it executes. Where autonomy is enabled, it's elected by the client, configured inside their own policy limits, enforced deterministically and logged in full.
Ripple Treasury reserves the word "agent" for capabilities that genuinely monitor, decide and act within your policy. The GSmart stable is growing across forecasting, risk, liquidity and reporting, with more detail available on request.
Nothing executes. A GSmart agent's proposal sits until you approve, adjust or dismiss it, so no action reaches your accounts without a human decision in the loop.
See Ripple Treasury in action
Get connected with supportive experts, comprehensive solutions and untapped possibility today.
