Treasury Dashboard

Monitor cash across banks, currencies, entities, investments, upcoming obligations, and liquidity risk from one treasury view. This example brings Overview and Accounts together so finance and operations teams can find the next task without losing context.

It includes representative records such as Operating cash · 6.2M and Reserve accounts · 3.1M. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Treasury Dashboard
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Move funds

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Finance and operations teams need to move funds while keeping cash, available and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Overview gives users an obvious place to start.
  • Supporting view: Accounts keeps the related context close.
  • Primary action: Move funds stays visible when people need it.
  • First signal: Cash shows a useful value (12.8M).
  • Second signal: Available gives additional context (9.4M).
  • Sample record: Operating cash · 6.2M.
  • Next record: Reserve accounts · 3.1M.

States worth designing

  • No results for the selected range: say what changed, protect progress, and offer a clear next step.
  • Refreshing with old values visible: say what changed, protect progress, and offer a clear next step.
  • Metric source unavailable: say what changed, protect progress, and offer a clear next step.
  • Filter changed the interpretation: say what changed, protect progress, and offer a clear next step.
  • Export preparing: say what changed, protect progress, and offer a clear next step.
  • Restricted data hidden: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → Accounts → Move funds → Review outcome

Patterns used

Analytics, Overview, Accounts, contextual actions, error recovery

Why these choices work

Keep the time range and metric definition visible. Let people see which segment or filter produced the result, then explain missing or delayed data.

Pay attention to overview and accounts. People need to distinguish Operating cash · 6.2M from Reserve accounts · 3.1M. Keep cash visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Move funds”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Cash Flow Forecast, Corporate Cards, Bank Reconciliation.

Start from this in Figr

Design a treasury dashboard screen inside our existing product. Use our current components, tokens and content language. Include Overview and Accounts views, credible records like Operating cash · 6.2M, and a clear “Move funds” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr