Vendor Payments

Schedule and track vendor payments with invoice match, approval state, payment rail, due date, bank status, and exception handling. This example brings Due and Scheduled together so finance and operations teams can find the next task without losing context.

It includes representative records such as AWS · INV-8842 and Figma · INV-1184. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Vendor Payments
Use this template in Figr

Template facts

Screen

Table

Primary action

Schedule payment

Pattern

Table

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 schedule payment while keeping due this week, amount due and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Due gives users an obvious place to start.
  • Supporting view: Scheduled keeps the related context close.
  • Primary action: Schedule payment stays visible when people need it.
  • First signal: Due this week shows a useful value (18).
  • Second signal: Amount due gives additional context (684k).
  • Sample record: AWS · INV-8842.
  • Next record: Figma · INV-1184.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Due → Scheduled → Schedule payment → Review outcome

Patterns used

Table, Due, Scheduled, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to due and scheduled. People need to distinguish AWS · INV-8842 from Figma · INV-1184. Keep due this week 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 “Schedule payment”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Expense Approval, Tax Documents, Corporate Cards.

Start from this in Figr

Design a vendor payments screen inside our existing product. Use our current components, tokens and content language. Include Due and Scheduled views, credible records like AWS · INV-8842, and a clear “Schedule payment” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr