Invoice Detail

Inspect one invoice with line items, taxes, credits, payment status, billing contact, and downloadable documents in one place. This example brings Overview and Line items together so account administrators can find the next task without losing context.

It includes representative records such as Platform subscription and Additional seats. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Invoice Detail
Use this template in Figr

Template facts

Screen

Detail

Primary action

Download invoice

Pattern

Detail

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 invoice while keeping amount, tax 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: Line items keeps the related context close.
  • Primary action: Download invoice stays visible when people need it.
  • First signal: Amount shows a useful value (1,240).
  • Second signal: Tax gives additional context (112).
  • Sample record: Platform subscription.
  • Next record: Additional seats.

States worth designing

  • Record not available: say what changed, protect progress, and offer a clear next step.
  • Details refreshing: say what changed, protect progress, and offer a clear next step.
  • Incomplete evidence: say what changed, protect progress, and offer a clear next step.
  • Action complete: say what changed, protect progress, and offer a clear next step.
  • Record read-only: say what changed, protect progress, and offer a clear next step.
  • History not available: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → Line items → Download invoice → Review outcome

Patterns used

Detail, Overview, Line items, contextual actions, error recovery

Why these choices work

Emphasize record status, next action and recent changes. Put secondary history nearby without competing with the primary task.

Pay attention to overview and line items. People need to distinguish Platform subscription from Additional seats. Keep amount 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 invoice”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Trial Expiry, Payment Failure Recovery, Credit Balance.

Start from this in Figr

Design a invoice detail screen inside our existing product. Use our current components, tokens and content language. Include Overview and Line items views, credible records like Platform subscription, and a clear “Download invoice” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr