Rent delinquency report: age open charges at a fixed date

Equal resident balances can contain different overdue charges. Preserve payment applications, credits, and reversals before assigning aging buckets.

Kartik Deshpande··6 min read

You download a rent delinquency report, compare it with receipts, and find residents who paid but still show overdue amounts. Rebuild the position at a fixed date using individual rent charges and the payments applied to them. Age each remaining charge from its due date, then show unapplied cash and disputed amounts alongside the result.

A resident’s net balance cannot tell you which month remains unpaid. A payment toward October can leave September open, while an unallocated receipt can reduce the displayed account balance without settling either charge. Keep the charge-level detail behind the overdue queue so the reviewer can distinguish missing cash from a missing application.

Freeze the cutoff and the aging basis

Record the report’s as-of date, included properties, currency, and approved rent-charge categories before exporting. State the local cutoff time and timezone when transaction timestamps matter. Keep the generation timestamp separate: a report generated on November 21 for November 20 needs the position at the earlier cutoff, not today’s open balances with yesterday’s label.

Intuit’s QuickBooks aging instructions distinguish aging against today from aging against the report date. Zoho Books’ receivables documentation also separates invoice-date and due-date aging. For this overdue-rent workflow, use the due-date basis approved by the reporting owner and save that setting with the output.

Confirm that the source can reconstruct charge balances at the chosen date. DoorLoop’s A/R aging documentation warns that its backdated summary view omits aging buckets. A date selector alone does not prove that an export contains historical balances and historical buckets; preserve the detailed transactions needed for the approved reconstruction.

Join payments to charges before calculating open rent

Start with property, unit, lease, and charge IDs, plus charge category, original amount, and due date. Retain payment IDs, application IDs, applied amounts, and the effective dates of applications or reversals. Property ID belongs in the join because Unit 101 can exist at several properties. Use the rent-roll snapshot to check lease identity and occupancy context without substituting contract rent for billed charges.

For each eligible charge, apply the owner-approved rule to its billed amount, valid payment applications, approved credits, and reversals effective by the cutoff. A partial payment leaves the remainder on that charge. A reversed payment application restores the corresponding open amount. Preserve the original and reversing references so the same reversal cannot be counted twice.

Keep unapplied receipts separate until the source owner confirms their allocation. DoorLoop defines them in its lease-payment documentation as payments with an unapplied amount and provides a separate report for them. Flag the resident and receipt for review; the reporting process should not invent which charge the money settles.

Distinguish a disputed charge from a posted credit, and a payment promise from an applied payment. Keep dispute status, disputed amount, supporting reference, and review owner beside the open charge. If finance approves a separate presentation of disputes, show the bridge from total open rent to the review population. An unresolved disagreement should not disappear through an undocumented filter.

Reconcile equal balances with different aging

Consider a hypothetical property with two leases, A and B, as of the end of November 20, 2026. Each has a $1,500 rent charge due September 1 and another $1,500 due October 1. Each received $1,100: $1,000 was applied to a charge, $100 remains unapplied, and $100 of the applied payment was reversed before the cutoff. Each also has a $200 approved credit, applied to the other charge. No other movements exist in this example.

Lease / charge dueBilledCash appliedPayment reversalCredit appliedOpen rentDays past due
A / Sep 1$1,500$1,000$100$0$60080
A / Oct 1$1,500$0$0$200$1,30050
B / Sep 1$1,500$0$0$200$1,30080
B / Oct 1$1,500$1,000$100$0$60050

For A’s September charge, open rent is $1,500 minus $1,000 plus the $100 reversal, or $600. Its October charge is $1,500 minus the $200 credit, or $1,300. Both leases therefore have $1,900 of open charges. Subtracting each lease’s $100 unapplied receipt would produce the same $1,800 net account position, while hiding which charge remains open.

Define the example’s buckets as current for charges not yet past due, then 1-30, 31-60, 61-90, and 91 or more calendar days past due. Age begins the day after the due date. September 1 to November 20 is 80 days, so A has $600 and B has $1,300 in 61-90. October 1 to November 20 is 50 days, putting A’s $1,300 and B’s $600 in 31-60. The portfolio has $1,900 in each populated bucket, totaling $3,800.

If $300 of A’s October charge is disputed, retain it within the $1,300 open amount and mark that portion for review. Do not subtract it a second time as though a credit had been posted. These bucket boundaries describe this reporting example; they do not establish grace periods, notice deadlines, or permission to take collection action.

Preserve separate evidence for amount, age, and review
Open amount

Charge and applied movements

Age

Due date and fixed cutoff

Review status

Dispute or unapplied receipt

Equal account totals can hide different overdue charges. Review status adds context without inventing a payment application.

Validate the queue and retain its version

Compare charge counts and open totals with the source detail for each property before aggregating. Investigate duplicate IDs, missing due dates, applications larger than their charges, and receipts without an allocation. A bucket sum can match the grand total even when the payments belong to the wrong lease, so review identifiers as well as arithmetic.

Publish exceptions with their owner and source reference. Missing due dates need an explicit unaged category, since assigning them to current or oldest changes the queue. Exclude future-due balances from the overdue total while keeping them available for reconciliation. Protect resident contact information when a portfolio recipient needs only property totals.

Retain the approved extract, definition version, and report cutoff. If a later correction changes an earlier period, preserve the issued version and label the revised one. Use the property management reporting pack for current-period collection ratios; that charge-cohort measure answers a different question from the dated overdue balance here.

Where Permute fits in a recurring overdue-rent review

Permute sells the context layer between business data and the AI tools people already use. We can connect approved exports in Excel, Google Sheets, or Google Drive, reconcile property and charge references, and retain the evidence behind a reporting view. The approved rules can then support a recurring report alongside questions in Claude, ChatGPT, or Copilot.

We apply your declared rent scope, application rules, and cutoff to permitted records. A property operations lead can ask which overdue charges have unapplied receipts or unresolved disputes and inspect the underlying references. The rule stays attached to the result (including its effective version), so a later change can be explained without silently replacing an earlier basis.

Explore a permitted rent-receivables export

Start with a dated charge list and its payment-application detail, with personal fields limited to what the review needs.

Keep accounting decisions and collection actions with owners

For this reporting workflow, we read the approved sources and do not post payment applications or change resident ledgers. We do not choose accounting treatments, determine legal delinquency, issue notices, or assess fees. Finance and property owners approve the reporting definitions and resolve disputed records. Source history limits what can be reconstructed; a current balance alone cannot recreate an earlier charge position.

A rent delinquency report should preserve the charges still open at a stated cutoff and explain their age. Match valid applications, credits, and reversals before assigning buckets. Keep unapplied money and disputes visible so equal net balances do not conceal different overdue positions. Release the queue with its evidence, exceptions, and approved definition version.

Review the gap between receipts and overdue rent

Bring a redacted aging export, payment-application detail, and one case whose amount or bucket you cannot reconcile.

Questions about rent delinquency reporting

Should balances from former residents stay in the report?

Keep resident status separate from the charge’s open status. If the approved review includes former residents, retain those rows with a status filter so they can be reviewed apart from current leases. A move-out date alone does not document settlement of a charge.

What if the export has receipts but no payment applications?

Ask the source owner for the charge allocation detail or an approved report that preserves it. Until that evidence exists, show the reconciliation limitation instead of assigning receipts to the oldest charge by assumption. That allocation could change both the open amount and its bucket.

How should a property-manager handover affect the queue?

Retain source-manager IDs and map them to stable property, lease, and charge identities. Reconcile the transferred opening balances with the earlier detail before adding new-period activity. Flag an opening balance without its due-date history as unaged until the responsible owner supplies or approves the missing information.