Transaction Ledger

Review every account transaction with date, counterparty, category, source, amount, balance impact, status, and reconciliation context. This example brings Transactions and Accounts together so finance and operations teams can find the next task without losing context.

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

Transaction Ledger
Use this template in Figr

Template facts

Screen

Table

Primary action

Export ledger

Pattern

Table

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 export ledger while keeping transactions, credits and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Transactions gives users an obvious place to start.
  • Supporting view: Accounts keeps the related context close.
  • Primary action: Export ledger stays visible when people need it.
  • First signal: Transactions shows a useful value (18.4k).
  • Second signal: Credits gives additional context (2.8M).
  • Sample record: Stripe payout · Northstar.
  • Next record: AWS infrastructure charge.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Transactions → Accounts → Export ledger → Review outcome

Patterns used

Table, Transactions, Accounts, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to transactions and accounts. People need to distinguish Stripe payout · Northstar from AWS infrastructure charge. Keep transactions 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 “Export ledger”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Bank Reconciliation, Cash Flow Forecast, Treasury Dashboard.

Start from this in Figr

Design a transaction ledger screen inside our existing product. Use our current components, tokens and content language. Include Transactions and Accounts views, credible records like Stripe payout · Northstar, and a clear “Export ledger” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr