Invoice Management

Track invoice status, aging, payment risk, customer balances, and collection follow-ups in one finance operations view. The screen connects Invoices and Customers so product teams can find the “New invoice” action while checking outstanding and overdue.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Current · 68% and 1–30 days · 18%, rather than an empty visual shell.

Invoice Management
Use this template in Figr

Template facts

Screen

Analytics

Primary action

New invoice

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “New invoice” action without losing sight of outstanding, overdue and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New invoice is clearly available where the task happens.
  • Main view: Invoices keeps the starting point obvious.
  • Connected view: Customers supplies nearby context.
  • Metric: Outstanding is visible with a meaningful value.
  • Another signal: Overdue helps people judge what to do next.
  • Representative record: Current · 68% makes the example specific.
  • Second record: 1–30 days · 18% shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading invoices without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for customers; clarify who can continue.
  • Success after choosing New invoice; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Invoices → Customers → New invoice → Review outcome

Patterns used

Analytics, Invoices, Customers, Collections, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Current · 68% with 1–30 days · 18%. Make outstanding clear, then use overdue to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “New invoice” action. The happy path alone is not enough.

Related UI examples: Subscription Billing, Expense Management, Budget Planning.

Start from this in Figr

Design a invoice management screen for our existing software product. Use our real design-system tokens, components and product language. Show Invoices and Customers, include believable records such as Current · 68%, and make new invoice easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr