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
Use this template in Figr

Template facts

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 users do

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.

Key elements

  • 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 worth designing

  • 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 this screen sits in the flow

Checklist → Reconciliations → Add close task → Review outcome

Patterns used

Board, Checklist, Reconciliations, contextual actions, error recovery

Why these choices work

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.

Start from this 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