Payouts

Track scheduled, processing, paid, and failed seller payouts with destination and reconciliation context. The screen connects Payouts and Balances so product teams can find the “Export payouts” action while checking scheduled and processing.

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

Payouts
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Export payouts

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 “Export payouts” action without losing sight of scheduled, processing and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Export payouts is clearly available where the task happens.
  • Main view: Payouts keeps the starting point obvious.
  • Connected view: Balances supplies nearby context.
  • Metric: Scheduled is visible with a meaningful value.
  • Another signal: Processing helps people judge what to do next.
  • Representative record: Paid · 68% makes the example specific.
  • Second record: Processing · 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 payouts without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for balances; clarify who can continue.
  • Success after choosing Export payouts; 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

Payouts → Balances → Export payouts → Review outcome

Patterns used

Analytics, Payouts, Balances, Accounts, 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 Paid · 68% with Processing · 18%. Make scheduled clear, then use processing 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 “Export payouts” action. The happy path alone is not enough.

Related UI examples: Inventory Management, Returns & Refunds, Orders Admin.

Start from this in Figr

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

Open Figr