Cash Flow Forecast

Forecast cash position from expected inflows, planned spend, payroll, invoices, scenarios, and uncertainty across future periods. This example brings Forecast and Scenarios together so finance and operations teams can find the next task without losing context.

It includes representative records such as Base case · 4.1M ending and Hiring plan · 3.6M ending. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Cash Flow Forecast
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Create scenario

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 create scenario while keeping cash today, 90-day low and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Forecast gives users an obvious place to start.
  • Supporting view: Scenarios keeps the related context close.
  • Primary action: Create scenario stays visible when people need it.
  • First signal: Cash today shows a useful value (4.8M).
  • Second signal: 90-day low gives additional context (3.2M).
  • Sample record: Base case · 4.1M ending.
  • Next record: Hiring plan · 3.6M ending.

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

Forecast → Scenarios → Create scenario → Review outcome

Patterns used

Analytics, Forecast, Scenarios, 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 forecast and scenarios. People need to distinguish Base case · 4.1M ending from Hiring plan · 3.6M ending. Keep cash today 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 “Create scenario”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Bank Reconciliation, Treasury Dashboard, Transaction Ledger.

Start from this in Figr

Design a cash flow forecast screen inside our existing product. Use our current components, tokens and content language. Include Forecast and Scenarios views, credible records like Base case · 4.1M ending, and a clear “Create scenario” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr