Treasury KPIs: How to Measure and Monitor Performance

Treasury KPIs are the measures a treasury uses to track how well it's doing its job — across liquidity, efficiency, risk and cost. Treasury KPI monitoring is the routine around them: each measure has a data source, a cadence, a threshold and an owner who acts when it moves. Good ones make treasury performance visible, and what's visible can be managed and improved; the trap, as with all metrics, is measuring what's easy rather than what matters. A treasury with no KPIs is flying on feel; one with fifty is drowning in a dashboard nobody acts on. The skill is a handful of meaningful, actionable measures tied to what the function is actually trying to achieve. (This spans the whole treasury remit — cash, risk and systems — so the examples below cross those areas.)

Why measure

You can't manage what you can't see. KPIs turn "treasury feels like it's doing okay" into something objective — a number that shows whether the cash forecast is actually improving, whether payments are getting more automated, whether risk is within bounds. They create accountability, surface drift before it becomes a problem, and give treasury a credible way to report its performance upward. Without them, good and bad treasuries look the same until something breaks.

The categories, with examples

Treasury performance splits into four areas, each with its own measures:

Liquidity and cash

• Cash forecast accuracy — how close forecasts are to actuals. The core measure of whether you can trust the forecast.
• Days cash on hand — how long the company could operate on available cash.
• Idle cash — balances sitting in accounts earning nothing, a sign of poor visibility or mobilization.

Efficiency

• Straight-through-processing rate — the share of transactions flowing without manual intervention. A direct measure of process health and risk.
• Cost per payment / manual effort — how much human effort the operation consumes.

Risk

• Hedge coverage ratio — how much of an exposure is hedged, against the policy target.
• Counterparty concentration — how much is exposed to any single bank or institution.
• Limit breaches — how often policy limits are exceeded.

Cost

• Bank fees — total banking cost, and whether fee analysis is recovering overcharges.
• Cost of funds — the effective cost of the company's borrowing.

Leading vs lagging

Some KPIs are lagging — they tell you what already happened (last quarter's forecast accuracy). Others are leading — they hint at what's coming (a rising share of manual transactions predicts future errors). A good set has both: lagging measures for accountability, leading ones for early warning. Relying only on lagging KPIs means you always learn about problems after they've cost you.

The measures, defined

Most arguments about treasury KPIs are really arguments about definitions — two people report the same measure from different denominators and then disagree about the business. So here is the arithmetic, the cadence and the owner for the common ones, in one place.

Two things that table deliberately does not do. It doesn't say what a good number looks like — the comparison that matters is your own baseline and its trend, not somebody else's, which is why "no baseline or target" is on the failure list below. And it doesn't repeat every measure named above: days cash on hand, idle cash, cost of funds and limit breaches are defined the same way, by writing down the numerator, the denominator, the period and the owner before anyone reports a number.

Treasury KPI monitoring: source, cadence, threshold, owner

Defining a KPI is half the work. Monitoring it is the other half, and it is a separate design: where the number comes from, how often someone looks, what value makes them act, and through which channel they find out. A KPI that is calculated correctly and looked at only when the board pack is due is being reported, not monitored.

Five decisions per KPI:

• Data source. The system the number is drawn from, named. If it takes a person and a spreadsheet to assemble, that is the first thing to fix — a hand-built KPI gets produced late and is the first to be dropped in a busy week. This is a reporting architecture question before it is a dashboard question.
• Cadence. Match it to how fast the measure can change, not to the reporting calendar. A balance or a limit can move within a day; forecast accuracy cannot be known until the period has closed.
• Threshold. The value at which someone must act. For risk measures it comes from the limits the policy sets; for operational ones it comes from the KPI's own baseline and trend. No threshold, no monitoring.
• Owner. One named role that receives the breach and is expected to respond — for the measures in the table above, the owner named there; for the rest, name one before the threshold is set.
• Channel: dashboard, alert or report. Covered below.

What each KPI is monitored from

The cadences and triggers here are common practice, not a standard, and the table deliberately contains no target values: the threshold is yours to set, from policy where there is one and from your own baseline where there isn't.

Dashboard, alert or report

The three channels do different jobs, and most monitoring problems are a KPI sitting in the wrong one.

• An alert is for a measure where a single event needs a same-day response: a missing statement, a limit breach, a counterparty over its limit. It should reach the owner without the owner going to look. Alerts on the data feeds themselves — interface monitoring — belong here too, because every KPI above is only as current as the feed underneath it.
• A dashboard is for a level someone checks routinely and acts on within days: liquidity headroom, idle balances, hedge coverage. It shows the current value against the threshold.
• A report is for measures that only mean something over a period and are discussed rather than reacted to: forecast accuracy, STP rate, fees, working capital, close. It shows the trend and carries commentary.

Putting a monthly measure on a live dashboard adds a tile nobody can act on; putting a limit breach in a monthly report means learning about it weeks late. And before any of it is trusted, the inputs have to be: a KPI built on incomplete or inconsistent data is a precise-looking wrong number, which makes data quality a precondition of monitoring rather than a separate project.

Choosing good KPIs

Good KPIs are few (a focused set beats a sprawling dashboard), meaningful (they reflect something that genuinely matters), actionable (someone can act on them), and tied to objectives (they measure progress toward what a corporate treasury does, not activity for its own sake). Each should have an owner and prompt a decision when it moves.

Treasury KPIs that measure activity, not outcomes

• Vanity metrics. Measuring what's easy (number of payments processed) rather than what matters (were they right, cheap, on time?).
• Too many KPIs. A huge dashboard that's reported but never acted on, so the signal drowns in noise.
• No action. KPIs that move the wrong way and prompt nothing — measurement as ritual.
• No baseline or target. Numbers with nothing to compare against, so you can't tell good from bad.
• Measuring activity, not outcome. Tracking how busy treasury is instead of how well it's achieving its goals.

Pick a small set of KPIs across liquidity, efficiency, risk and cost; make sure each is meaningful, actionable and owned; and use them to prompt decisions, not just fill a report — and treasury performance becomes visible, accountable and improvable. The point was never the dashboard; it's that what gets measured, and acted on, gets better.

See also measuring cash forecast accuracy, straight-through processing, and SAP Portfolio Analyzer for return and benchmark measurement on the investment book.