Billing History

Review past invoices and charges with period, amount, payment method, status, downloadable receipts, and failed-payment context. This example brings History and Invoices together so account administrators can find the next task without losing context.

It includes representative records such as INV-2026-009 · September and INV-2026-008 · August. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Billing History
Use this template in Figr

Template facts

Screen

Table

Primary action

Download CSV

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 download csv while keeping invoices, paid and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: History gives users an obvious place to start.
  • Supporting view: Invoices keeps the related context close.
  • Primary action: Download CSV stays visible when people need it.
  • First signal: Invoices shows a useful value (24).
  • Second signal: Paid gives additional context (23).
  • Sample record: INV-2026-009 · September.
  • Next record: INV-2026-008 · August.

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

History → Invoices → Download CSV → Review outcome

Patterns used

Table, History, Invoices, 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 history and invoices. People need to distinguish INV-2026-009 · September from INV-2026-008 · August. Keep invoices 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 “Download CSV”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Usage Metering, Seat Management, Payment Methods.

Start from this in Figr

Design a billing history screen inside our existing product. Use our current components, tokens and content language. Include History and Invoices views, credible records like INV-2026-009 · September, and a clear “Download CSV” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr