Expense Approval

Review employee expenses with merchant, category, receipt, policy flags, project context, and approve or reject actions in one queue. This example brings Needs review and Flagged together so finance and operations teams can find the next task without losing context.

It includes representative records such as Conference travel · 1,840 and Design software · 420. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Expense Approval
Use this template in Figr

Template facts

Screen

Inbox

Primary action

Approve selected

Pattern

Inbox

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 approve selected while keeping waiting, flagged and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Needs review gives users an obvious place to start.
  • Supporting view: Flagged keeps the related context close.
  • Primary action: Approve selected stays visible when people need it.
  • First signal: Waiting shows a useful value (28).
  • Second signal: Flagged gives additional context (5).
  • Sample record: Conference travel · 1,840.
  • Next record: Design software · 420.

States worth designing

  • No items match the selected filter: say what changed, protect progress, and offer a clear next step.
  • Message or task loading: say what changed, protect progress, and offer a clear next step.
  • Reply or assignment failed: say what changed, protect progress, and offer a clear next step.
  • Item resolved: say what changed, protect progress, and offer a clear next step.
  • Escalation required: say what changed, protect progress, and offer a clear next step.
  • Permission to read restricted content missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Needs review → Flagged → Approve selected → Review outcome

Patterns used

Inbox, Needs review, Flagged, contextual actions, error recovery

Why these choices work

Keep the current item close to its history, owner and urgency. Put the next action on the record rather than making people open several panels.

Pay attention to needs review and flagged. People need to distinguish Conference travel · 1,840 from Design software · 420. Keep waiting 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 “Approve selected”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Corporate Cards, Vendor Payments, Treasury Dashboard.

Start from this in Figr

Design a expense approval screen inside our existing product. Use our current components, tokens and content language. Include Needs review and Flagged views, credible records like Conference travel · 1,840, and a clear “Approve selected” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr