# Treasury KPIs: How to Measure and Monitor Performance

Source: https://gravam.com/blog/treasury-kpis-measuring-treasury-performance
Author: Tan Gravam
Published: 2026-07-24
Updated: 2026-10-04
Reviewed: 2026-10-04
Summary: Treasury KPIs measure liquidity, efficiency, risk and cost. How to define them, and how treasury KPI monitoring works: source, cadence, threshold, owner.

**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](https://gravam.com/topics/cash-and-liquidity-management), [risk](https://gravam.com/topics/treasury-risk-management) and [systems](https://gravam.com/topics/treasury-systems-architecture) — 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](https://gravam.com/blog/how-to-measure-cash-forecast-accuracy).
- **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](https://gravam.com/blog/how-to-achieve-global-cash-visibility) or mobilization.

### Efficiency

- **Straight-through-processing rate** — the share of transactions flowing [without manual intervention](https://gravam.com/blog/straight-through-processing-in-treasury). 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](https://gravam.com/blog/what-is-treasury-risk-management), against the policy target.
- **Counterparty concentration** — how much is exposed to any single [bank or institution](https://gravam.com/blog/counterparty-and-credit-risk-in-treasury).
- **Limit breaches** — how often policy limits are exceeded.

### Cost

- **Bank fees** — total banking cost, and whether [fee analysis](https://gravam.com/blog/bank-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.

| KPI | How it is calculated | Typical frequency | Who owns it | Leading or lagging |
| --- | --- | --- | --- | --- |
| **[Cash visibility](https://gravam.com/blog/how-to-achieve-global-cash-visibility)** | Balances treasury can see without manual collection ÷ total group balances. Count it by value or by number of accounts — both are used, so state which | Daily | Cash manager / treasury operations | Leading |
| **[Cash forecast accuracy](https://gravam.com/blog/how-to-measure-cash-forecast-accuracy)** | Forecast against actual for a fixed horizon: absolute error ÷ actual. Absolute error sizes the miss and signed variance shows bias, so most sets report both rather than choosing | Monthly, per horizon | Forecast owner (usually a treasury analyst) | Lagging |
| **[Straight-through-processing rate](https://gravam.com/blog/straight-through-processing-in-treasury)** | Transactions completing with no manual intervention ÷ all transactions in the period. The number turns on what counts as a touch — re-keying only, or any manual approval — so fix that first | Monthly | Treasury operations | Leading |
| **[Bank fees](https://gravam.com/blog/bank-fee-analysis)** | Total charges billed across all banks in the period, compared line by line against the agreed price schedule | Billed monthly, reviewed quarterly | Treasury operations / cash manager | Lagging |
| **DSO, DPO and the [cash conversion cycle](https://gravam.com/blog/working-capital-and-cash)** | CCC = DSO + DIO − DPO. DSO = receivables ÷ credit sales × days in period; DPO = payables ÷ cost of goods sold × days in period — some houses use purchases instead of COGS, so pick one and keep it | Monthly | Credit control, operations and procurement own the levers; treasury reports the cycle | Lagging |
| **Hedge ratio against [policy](https://gravam.com/blog/treasury-risk-management-policy)** | Notional hedged ÷ exposure in scope, read against the target or band the policy sets. Whether "in scope" means forecast or booked exposure is a policy question, not a spreadsheet one | Monthly, or whenever exposures are captured | Risk manager | Leading |
| **[Counterparty concentration](https://gravam.com/blog/counterparty-and-credit-risk-in-treasury)** | Exposure to one institution ÷ total exposure, read against the per-counterparty limit. Cash, deposits and derivative mark-to-market can be aggregated or tracked separately; the policy decides | Monthly; daily where balances move | Risk manager / treasurer | Leading |
| **Days to close** | Days from period end to treasury's numbers being signed off. Working days or calendar days, to first draft or to final sign-off — four combinations, so name the one you mean | Monthly | Treasury accounting | Lagging |

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](https://gravam.com/blog/treasury-reporting-and-analytics-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](https://gravam.com/blog/risk-appetite-and-limits-in-treasury); 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

| KPI | Data source | Monitoring cadence | What triggers action | Channel |
| --- | --- | --- | --- | --- |
| **Cash visibility** | Bank statement feeds against the account inventory | Daily | An account with no statement received | Alert |
| **Days cash on hand** | The [daily cash position](https://gravam.com/blog/how-to-build-a-daily-cash-position) and the operating cost base from the ERP | Weekly, daily under stress | Falling below the floor the liquidity policy sets | Dashboard |
| **Idle cash** | Daily position, per account | Daily | A balance above the account's target left unswept | Dashboard |
| **Cash forecast accuracy** | Forecast snapshots against actuals from statements | Monthly, per horizon | Error outside the agreed band, or a persistent bias one way | Report |
| **Straight-through-processing rate** | Payment and reconciliation logs in the TMS or ERP | Monthly; exceptions daily | The rate dropping against its baseline; a growing repair queue | Report, with a daily queue |
| **Cost per payment / manual effort** | Bank billing plus payment volumes; time spent, where it is recorded | Quarterly | A rising trend | Report |
| **Hedge ratio** | Exposures and hedge deals in the TMS | Monthly, and at each exposure update | Coverage outside the policy band | Dashboard and report |
| **Counterparty concentration** | Balances, deposits and derivative valuations by counterparty | Daily where balances move | Exposure approaching or over a counterparty limit | Alert |
| **Limit breaches** | The limit checks themselves | Continuous | Any breach | Alert |
| **Bank fees** | Bank billing statements against the agreed price schedule | Quarterly | A charge that does not match the schedule | Report |
| **Cost of funds** | Debt and facility records in the TMS, interest paid from the ERP | Monthly or quarterly | Drift against budget or against the previous period | Report |
| **DSO, DPO, cash conversion cycle** | ERP receivables, payables and inventory | Monthly | The cycle lengthening against baseline | Report |
| **Days to close** | The close calendar and sign-off dates | Monthly | A close that runs past the agreed day | Report |

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](https://gravam.com/blog/interface-monitoring-and-reconciliation) — 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](https://gravam.com/blog/treasury-data-quality-and-governance) a precondition of monitoring rather than a separate project.

## Choosing good KPIs

> The test for a KPI: if it moved the wrong way, would someone _do_ something? If yes, it's a real KPI. If it would just be noted and filed, it's a vanity metric taking up space. Measure the few things that would actually change a decision.

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](https://gravam.com/blog/what-does-a-corporate-treasury-do), 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](https://gravam.com/blog/how-to-measure-cash-forecast-accuracy), [straight-through processing](https://gravam.com/blog/straight-through-processing-in-treasury), and [SAP Portfolio Analyzer](https://gravam.com/blog/sap-portfolio-analyzer) for return and benchmark measurement on the investment book._

## Questions this article answers

**Q: What are treasury KPIs?**

Treasury KPIs are the key performance indicators a treasury function uses to measure how well it's doing its job — across liquidity (like cash forecast accuracy and days cash on hand), efficiency (like straight-through-processing rate and cost per payment), risk (like hedge coverage and counterparty concentration), and cost (like bank fees and cost of funds). Good KPIs make treasury performance visible so it can be managed and improved, and give the function objective measures to report and be accountable against.

**Q: What are good examples of treasury KPIs?**

Common ones include: cash forecast accuracy (how close forecasts are to actuals); days cash on hand (how long the company could operate on available cash); idle cash (balances earning nothing); straight-through-processing rate (share of transactions flowing without manual intervention); hedge coverage ratio (how much exposure is hedged); counterparty concentration (how much is exposed to any one bank); and total bank fees. The right set depends on the treasury's objectives — a handful of meaningful, actionable measures beats a large dashboard nobody acts on.

**Q: What is treasury KPI monitoring?**

Treasury KPI monitoring is the routine of checking a defined set of treasury measures against thresholds, on a fixed cadence, with a named person responsible for acting when one moves. It has five parts: a data source for each KPI (bank statements, the TMS, the ERP, the forecast, bank billing), a cadence that matches how fast the measure can change (daily for cash and limits, monthly for accuracy, cost and working capital), a threshold taken from policy or from the KPI's own baseline, an owner, and a channel — a dashboard or alert for measures that need a same-day reaction, a periodic report for the ones that are reviewed and discussed. Reporting a KPI is not monitoring it; monitoring means a breach triggers an action.

**Q: How do you choose the right treasury KPIs?**

Pick a small number of measures that are meaningful (they reflect something that genuinely matters), actionable (someone can do something about them), and tied to the treasury's actual objectives. Avoid vanity metrics that are easy to measure but don't reflect real performance, and resist measuring everything — a focused set that drives action beats a sprawling dashboard that just gets reported. Each KPI should have an owner and prompt a decision when it moves the wrong way.