FIGR / UI TEMPLATE

Accounting Close

Coordinate month-end close tasks across reconciliations, journal entries, approvals, owners, dependencies, deadlines, and sign-off. This example brings Checklist and Reconciliations together so finance and operations teams can find the next task without losing context.

It includes representative records such as Bank reconciliation and Revenue recognition. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Accounting Close

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Board

Primary action

Add close task

Pattern

Board

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps with

Finance and operations teams need to add close task while keeping tasks, complete and exceptions visible. The interface should show what changed and who should act next.

What to look for

  • Main workspace: Checklist gives users an obvious place to start.
  • Supporting view: Reconciliations keeps the related context close.
  • Primary action: Add close task stays visible when people need it.
  • First signal: Tasks shows a useful value (42).
  • Second signal: Complete gives additional context (68%).
  • Sample record: Bank reconciliation.
  • Next record: Revenue recognition.

States to consider

  • No cards in this stage: say what changed, protect progress, and offer a clear next step.
  • Movement in progress: say what changed, protect progress, and offer a clear next step.
  • Move blocked by rules: say what changed, protect progress, and offer a clear next step.
  • Ownership updated: say what changed, protect progress, and offer a clear next step.
  • Archived item restored: say what changed, protect progress, and offer a clear next step.
  • Permission to edit missing: say what changed, protect progress, and offer a clear next step.

Where it fits

Checklist → Reconciliations → Add close task → Review outcome

Patterns in this screen

Board, Checklist, Reconciliations, contextual actions, error recovery

UX choices to review

Use real domain stages with a clear owner. Confirm high-impact moves and explain when permissions or missing work block an item.

Pay attention to checklist and reconciliations. People need to distinguish Bank reconciliation from Revenue recognition. Keep tasks 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 “Add close task”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Tax Documents, Fraud Review Queue, Vendor Payments.

Try a similar screen in Figr

Design a accounting close screen inside our existing product. Use our current components, tokens and content language. Include Checklist and Reconciliations views, credible records like Bank reconciliation, and a clear “Add close task” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗