Rent
Rent receivables aging
A report that groups unpaid tenant charges by how long each balance has been outstanding, while preserving the unit, charge, payment, and cutoff-date detail behind it.
Glossary
Rent
Rent receivables aging turns an undifferentiated total such as “tenants owe $4,200” into a time-based working list. Open charges are usually placed into consistent age buckets measured from their due dates, such as current, 1–30 days past due, and older periods. The report should identify the property, unit, resident account, original charge, payments or credits applied, remaining balance, due date, and the date on which the report was run.
For a small landlord, the cutoff date and transaction detail matter more than fancy buckets. A payment received after the cutoff should not be backdated into the report, and a deposit, owner contribution, or unrelated fee should not be allowed to mask unpaid rent. Tie every aged balance to the tenant ledger so you can distinguish a genuinely unpaid charge from a posting error, an unapplied payment, an approved adjustment, or a returned ACH payment.
Aging describes timing; it does not decide what is collectible or what action to take. Before sending a reminder or considering a payment arrangement, verify the signed lease, the ledger, pending payments, and any dispute or assistance application. Keep collection status separate from the accounting balance: a charge can remain open while communication or review is underway, and a disputed item should not silently disappear merely to make the report look cleaner.
Use the aging report as a recurring control. Compare this week with last week, assign an owner and next review date to material balances, and reconcile the total back to the rent ledger. That creates an audit trail for follow-up without pretending that every old balance has the same cause, likelihood of collection, or lawful remedy.
Aging workflow and worked schedule
Age open charge components from applicable due dates at a cutoff after valid payments, credits, reversals, and disputes. Reconcile detail to control.
Example: at June 30, $400 from May and $900 from June less a $300 payment to May leave $100 older and $900 current. A disputed $100 fee stays in a separate review state.
Disposition framework and edge cases
Classify collectible, plan, disputed, assistance pending, legal review, authorized write-off, or unresolved. Handle partial payments, unapplied cash, returns, subsidies, and inherited balances.
Bucket mechanics need a declared policy
Aging usually measures elapsed days from each open charge’s due date to the report cutoff, but some systems use charge date or another configured convention. State the policy on the report. A common presentation is current, 1–30, 31–60, 61–90, and 90+ days; those labels are reporting bands, not universal legal stages.
Apply valid credits and settled payments under the documented allocation policy before bucketing. Keep pending payments, disputed charges, payment-plan balances, assistance amounts, returned payments, and authorized write-offs visible as statuses or separate columns. A total can be mathematically correct and still be operationally misleading if those states are hidden.
Human decision framework for an aged item
Age is only one input. The next action also depends on amount, occupied or former status, payment promise, dispute, assistance or subsidy state, prior communication, source completeness, and the current jurisdiction-specific process. Automation can assemble the record and route a case; it should not infer a legal remedy from a bucket.