Bank Reconciliation

Match bank transactions to ledger entries, surface discrepancies, review suggested matches, and close reconciliation periods with confidence. This example brings Unmatched and Suggested together so finance and operations teams can find the next task without losing context.

It includes representative records such as Stripe settlement mismatch and AWS charge duplicate. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Bank Reconciliation
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Reconcile selected

Pattern

Workspace

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 reconcile selected while keeping unmatched, suggested matches and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Unmatched gives users an obvious place to start.
  • Supporting view: Suggested keeps the related context close.
  • Primary action: Reconcile selected stays visible when people need it.
  • First signal: Unmatched shows a useful value (18).
  • Second signal: Suggested matches gives additional context (42).
  • Sample record: Stripe settlement mismatch.
  • Next record: AWS charge duplicate.

States worth designing

  • First-use empty state: say what changed, protect progress, and offer a clear next step.
  • Data panel loading: say what changed, protect progress, and offer a clear next step.
  • Stale status or conflict: say what changed, protect progress, and offer a clear next step.
  • Action completed: say what changed, protect progress, and offer a clear next step.
  • Insufficient permission: say what changed, protect progress, and offer a clear next step.
  • Network retry: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Unmatched → Suggested → Reconcile selected → Review outcome

Patterns used

Workspace, Unmatched, Suggested, contextual actions, error recovery

Why these choices work

Give the main job visual priority, keep supporting signals nearby and surface exceptions where people must act.

Pay attention to unmatched and suggested. People need to distinguish Stripe settlement mismatch from AWS charge duplicate. Keep unmatched 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 “Reconcile selected”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Transaction Ledger, Cash Flow Forecast, Treasury Dashboard.

Start from this in Figr

Design a bank reconciliation screen inside our existing product. Use our current components, tokens and content language. Include Unmatched and Suggested views, credible records like Stripe settlement mismatch, and a clear “Reconcile selected” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr