Tax Documents

Manage tax forms and supporting documents by entity, jurisdiction, tax year, due date, status, reviewer, and filing evidence. This example brings Documents and Entities together so finance and operations teams can find the next task without losing context.

It includes representative records such as FY26 corporate return and GST filing · September. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Tax Documents
Use this template in Figr

Template facts

Screen

Table

Primary action

Upload document

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 upload document while keeping documents, due soon and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Documents gives users an obvious place to start.
  • Supporting view: Entities keeps the related context close.
  • Primary action: Upload document stays visible when people need it.
  • First signal: Documents shows a useful value (86).
  • Second signal: Due soon gives additional context (7).
  • Sample record: FY26 corporate return.
  • Next record: GST filing · September.

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

Documents → Entities → Upload document → Review outcome

Patterns used

Table, Documents, Entities, 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 documents and entities. People need to distinguish FY26 corporate return from GST filing · September. Keep documents 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 “Upload document”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Vendor Payments, Accounting Close, Expense Approval.

Start from this in Figr

Design a tax documents screen inside our existing product. Use our current components, tokens and content language. Include Documents and Entities views, credible records like FY26 corporate return, and a clear “Upload document” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr