Rent Payments

Track tenant rent, due dates, payment methods, late balances, credits, and receipts across properties. This example brings Payments and Balances together so property teams can find the next task without losing context.

It includes representative records such as Unit 4B · Oct rent and Unit 12A · Sep late. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Rent Payments
Use this template in Figr

Template facts

Screen

Table

Primary action

Record payment

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to record payment while keeping due this month, collected and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Payments gives users an obvious place to start.
  • Supporting view: Balances keeps the related context close.
  • Primary action: Record payment stays visible when people need it.
  • First signal: Due this month shows a useful value (284k).
  • Second signal: Collected gives additional context (91%).
  • Sample record: Unit 4B · Oct rent.
  • Next record: Unit 12A · Sep late.

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

Payments → Balances → Record payment → Review outcome

Patterns used

Table, Payments, Balances, 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 payments and balances. People need to distinguish Unit 4B · Oct rent from Unit 12A · Sep late. Keep due this month 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 “Record payment”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Property Inspection Checklist, Occupancy Analytics, Property Manager Dashboard.

Start from this in Figr

Design a rent payments screen inside our existing product. Use our current components, tokens and content language. Include Payments and Balances views, credible records like Unit 4B · Oct rent, and a clear “Record payment” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr