Payroll Admin

Run payroll with employee changes, gross pay, deductions, exceptions, approvals, and payment readiness visible before submission. The screen connects Payroll and Employees so product teams can find the “Run payroll” action while checking employees and gross pay.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Base pay · 72% and Variable pay · 14%, rather than an empty visual shell.

Payroll Admin
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Run payroll

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 “Run payroll” action without losing sight of employees, gross pay and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Run payroll is clearly available where the task happens.
  • Main view: Payroll keeps the starting point obvious.
  • Connected view: Employees supplies nearby context.
  • Metric: Employees is visible with a meaningful value.
  • Another signal: Gross pay helps people judge what to do next.
  • Representative record: Base pay · 72% makes the example specific.
  • Second record: Variable pay · 14% 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 payroll without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for employees; clarify who can continue.
  • Success after choosing Run payroll; 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

Payroll → Employees → Run payroll → Review outcome

Patterns used

Analytics, Payroll, Employees, Changes, 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 Base pay · 72% with Variable pay · 14%. Make employees clear, then use gross pay 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 “Run payroll” action. The happy path alone is not enough.

Related UI examples: Performance Reviews, Leave Management, Hiring Pipeline.

Start from this in Figr

Design a payroll admin screen for our existing software product. Use our real design-system tokens, components and product language. Show Payroll and Employees, include believable records such as Base pay · 72%, and make run payroll easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr