How to Read an Aging Report for Overdue Dues

What an aging report actually does

An aging report for overdue dues groups every open balance in a community not into one lump sum, but by how long it has been outstanding: 30 days, 60 days, 90 days, and beyond. Most management teams work from a single number — "total unpaid" — and that one figure can't distinguish a unit that's three days late from one that hasn't paid in six months. Those are fundamentally different problems that call for different responses: one needs a gentle nudge, the other is on the edge of needing a formal process.

Not knowing how to read the report is actually a bigger problem than the report being incomplete. Many managers look at their table and fixate on whichever unit owes the most money, when the real priority in aging logic isn't the amount — it's the duration. A small balance that crosses 90 days is a more urgent signal than a large balance that just appeared, because the longer a debt sits unpaid, the less collectible it typically becomes.

What the 30-60-90 day breakdown tells you

The standard aging breakdown splits into four bands, and each one suggests a different action:

• 0-30 days: Still within normal range. Most units land here for ordinary reasons — forgetfulness, a payday that doesn't line up with the due date. An automatic app notification is usually enough.
• 31-60 days: Now worth watching. Units in this band should get a more formal reminder by email or text, stating the exact balance and the payment deadline clearly.
• 61-90 days: The point where management should reach out directly. A phone call or a face-to-face conversation belongs here, to clarify whether the resident is facing a genuine payment difficulty or simply missed the earlier notices.
• 90+ days: The band where a formal process becomes worth considering — a written notice, a proposed payment plan, or, if needed, starting legal enforcement.

The value of this breakdown is that it removes the monthly guesswork of "who should I remind, and when." Once the thresholds are defined once, which unit falls into which band becomes visible automatically.

Look at the distribution, not just the total

A community's total unpaid balance might read as $50,000 — but that number alone tells you almost nothing. If 80% of it sits in the 0-30 day band, the situation is actually healthy: that's just the normal churn of monthly lateness, and most of it will likely clear within the week. But if 60% of that same total sits in the 90+ day band, the community has a real collection problem, and it won't resolve on its own.

That's why the first thing worth checking in an aging report isn't the total figure — it's the percentage distribution across bands. In a healthy community, most of the balance sits in the 0-30 day band, and the amount drops off sharply as the bands get older. When that pattern inverts — when the 90+ band is larger than the others — it's a sign that the reminder process broke down somewhere, or was never running consistently. We covered a related angle in improving dues collection rates around staged reminders; the aging report is the tool that actually measures whether that staged process is working.

Which units keep reappearing

The real value of an aging report shows up when it's read as a month-over-month comparison rather than a single snapshot. A unit landing in the 31-60 day band this month is unremarkable on its own; but the same unit showing up in the 60+ band for six months in a row is a different signal — that unit likely has a structural payment issue that repeated reminders alone won't fix.

Catching that pattern requires keeping and comparing past periods' aging reports. With paper records or a fresh spreadsheet every month, that comparison practically never happens, because each period starts a new file and lining it up against the previous one takes separate effort. In a system-based aging report, past periods are kept automatically, so the answer to "how many months has this unit been sitting in the 60+ band" is visible in a single glance.

Connecting the aging report to the collection process

Watching the report isn't enough on its own — each band needs to trigger the next step automatically. The aging and collection performance module inside Site-Park groups receivables by due-date range automatically and surfaces problem units at the top of the list. Once a unit crosses the 90-day threshold, management doesn't have to check separately — the system flags that it's now a candidate for formal process. Because late-payment interest accrues automatically across the bands, how much interest has built up at each stage shows on the same screen.

This connection also prevents earlier steps from getting skipped. When a unit lands directly in the 90+ band, having a record of which reminders it received at the 30- and 60-day marks means that when the case moves into legal enforcement, there's a concrete communication history behind it — one that strengthens management's position both legally and in any dispute with the resident.

Presenting the aging report at a general assembly

One of the most common questions at a general assembly is "what's the state of unpaid dues?" Answering with a single total figure tends to breed distrust — owners follow up with questions like "where does this number come from, which units does it include" that a lump sum can't answer. Presenting the aging distribution by band gives a far more convincing answer: how much is recent lateness, and how much is a long-standing balance already in formal process, become two separate, visible figures.

That transparency also demonstrates the board's own performance. A board that can show the total sitting in the 90+ band shrinking period over period has concrete evidence that its collection process is actually improving.

Common mistakes

A few recurring mistakes show up when communities read aging reports. The first is fixating only on whichever unit owes the largest amount and ignoring how long it's been outstanding — a small balance stuck open for a long time can be more urgent than a large one that just appeared. The second is checking the report only once at month-end; a quick weekly look catches the moment a unit moves from one band to the next and allows for earlier action. The third is leaving the 30-60-90 thresholds fixed regardless of a community's actual payment rhythm — some communities have a different due date pattern, and the bands should shift accordingly. The fourth, and most common, mistake is letting only accounting see the detailed aging data while the board sees only the total figure; when both sides see the same distribution, they share a common language about which unit is at which stage.

Conclusion

An aging report for overdue dues is one of the most practical tools for turning collection from guesswork into something data-driven. Reading the 30-60-90 day breakdown correctly clarifies which unit needs what kind of attention and when, and it makes the real risk behind a total balance figure visible. If your community's collection data still lives as a single lump-sum number, get in touch with the Site-Park team to talk through setting up an aging report.