Vertical agentic orchestration · treasury

Where agentic plays in treasury, and where it does not

An outside read of the category: the distinction most buyers cannot yet make, and which recurring treasury decisions are genuine candidates for judgement rather than a threshold.

Part one

Chat, copilot, agent#

Nearly every vendor in treasury now says agent, and a good share of them mean chat. The distinction is not academic: it decides where the work sits, and therefore whether anything about the treasurer’s week actually changes.

	Chat	Copilot	Agent
What it is	Another way to ask questions of the same data	Chat inside the workspace, aware of the screen, drafting the next step	Has a goal, runs on a schedule, produces the output without being asked
Who starts it	The human, every time	The human, every time	Nobody. A trigger does
Where the work sits	Entirely with the human	Mostly with the human	With the system, inside rules the customer sets
What it removes	A query here and there	Friction from work the human is still doing	The work

Treasury differs from every other orchestration domain in one respect that governs the whole design: the actions are largely irreversible and priced in cash. A released payment is gone, an executed sweep has a value date, and the sign-off chain runs outside treasury entirely — CFO, external auditor, sometimes an audit committee. So the delegation ladder is a control rather than a preference, and the system’s ability to decline to act and say why matters more than its ability to act.

Three layers, and only one of them is agentic

Already solved — connectivity

Getting the position right

Bank connections, overnight statement ingestion, multi-entity and multi-currency consolidation, reconciliation, the dashboard. Considerable engineering, and largely finished.

Test — is the answer a fact about what happened? Then it is data, not judgement.

Already solved — rules

Thresholds and scenarios

Alerting when a balance drops below a buffer or an exposure passes a limit. Running a stated scenario and reporting the impact by week and entity. Where the rule can be written down, a rules engine applies it perfectly.

Test — can it be expressed as if this, then flag that? Then it is a monitor. Do not reason about it.

The remainder — agentic

Choosing the response to the breach

A monitor tells you the buffer is broken. It does not tell you whether to sweep, draw the facility, defer a payment run or do nothing — because those are all policy-compliant, they cost different amounts, and the right one depends on cut-offs, tax, forecast confidence and who you would rather not call.

Test — do two good treasurers disagree, and can both defend the answer? Only then is there something to teach.

Part two

Nine decisions that recur every month#

DecisionWhat sets it offWhat a treasurer actually chooses between

The daily position and how to fund it

An entity is short against its bufferDaily, before cut-off

Overnight statements land and one entity sits below its minimum operating balance.

Sweep from an approved intercompany pair · draw the facility · defer a discretionary payment run within supplier terms · do nothing, it is inside tolerance

Cash is sitting idle above the bufferDaily

Group surplus exceeds what the policy requires held.

Place it at the horizon the forecast confidence supports · pay down the drawn facility · hold it because a known outflow lands inside the term

The data is not good enough to decideAny run

A statement is missing, or unreconciled items sit above the threshold.

Refuse to run and say which entities are missing · run on partial data and flag it · wait for the feed. The first is the right answer, and the hardest to demo.

The forecast and reality diverged

Actuals came in away from forecastMonthly, and after close

The gap needs decomposing to driver, entity and counterparty.

Treat it as a timing shift · treat it as a structural change and propose a named assumption change · flag it as noise and leave the model alone

A major customer is paying later than modelledPattern across periods

Collections behaviour has moved, not just slipped once.

Re-forecast on observed behaviour · escalate to collections · adjust the terms at renewal · absorb it in the buffer

The board wants the downsideAhead of the board cycle

A stress set is needed: collections slippage, largest-customer delay, a rate move on the revolver.

Which scenarios, at what severity, over what horizon — and which ones drawn from the group’s own history that nobody thought to ask for

Policy is breached, or about to be

Too much cash at one bankContinuous

Concentration passes the per-institution limit in the policy.

Move it and accept the cost · request a temporary limit waiver · net it against a facility at the same institution

Currency exposure passes a hedging triggerContinuous

Net exposure moves past the point the policy says to act.

Hedge now at the quoted rate · hedge a portion · net internally first · escalate, because the policy is ambiguous here

An approval has been sitting too longTimer

A payment or a funding action has aged past the policy window with nobody acting.

Escalate to the next approver · release under a standing delegation · let it lapse and re-raise · call the person