An accounts receivable aging report groups unpaid customer balances by how long they have been outstanding or overdue. It helps a team decide which records and customer conversations need attention. Before using it, establish the date, aging method and transactions included in the report.
Check the report basis first.
A report is a view at a particular date. Its buckets depend on the product’s settings, such as whether age is measured from an invoice date or a due date. Read those settings rather than assuming that two exports use the same basis.
Use the same date and scope when comparing reports. Confirm which company, currency or customer filters apply. If two totals differ, check those settings before treating the difference as a problem in the underlying records.
Read the amount before interpreting the percentage.
In a fictional report, one customer has ₱18,000 current and ₱6,000 overdue, giving a total open balance of ₱24,000. On that report’s stated basis, the overdue share is ₱6,000 ÷ ₱24,000 × 100 = 25%.
The calculation describes the distribution of this sample balance. It does not estimate the chance of collection. If the overdue invoice is disputed or a receipt is awaiting application, the next action may be a record check before a customer reminder. The report date, aging basis and document context still control interpretation.
| Bucket | Open amount | Review implication |
|---|---|---|
| Current | ₱18,000 | Check dates and payment terms before interpreting. |
| Overdue | ₱6,000 | Open the relevant invoice and inspect receipts, credits or disputes. |
| Total | ₱24,000 | Use the same population and currency for the ratio. |
| Overdue share | 25% | A descriptive ratio, not a collection forecast or loss estimate. |
Read the buckets as prompts for review.
A current bucket and a series of older buckets make it easier to see where outstanding balances are concentrated. The exact labels and ranges vary by system. Older balances may deserve a closer look, but a bucket alone does not explain why an amount remains unpaid.
- Check whether the bucket is based on invoice or due date.
- Distinguish the total balance from the amount in each bucket.
- Look for a small number of invoices driving a large balance.
- Open the detail when a summary raises a question.
Move from the summary to invoice context.
Before following up, check whether the invoice was sent to the right contact, whether a payment or credit needs review, and whether a dispute is already being handled. Use your team’s accounting process to resolve transaction questions.
The report does not, by itself, decide whether a balance should be adjusted or written off. Accounting treatment and collection decisions require the appropriate review.
Keep the follow-up usable.
Record a clear next step, an owner and a review date. Separate a customer conversation from an accounting correction so each reaches the right person. At the next review, check what changed in the source records as well as what was discussed.
A simple weekly review note can make the report easier to act on without turning it into a separate, competing ledger.
If you are new to the terminology, start with the accounts receivable and accounts payable distinction. Intuit’s aging-report guide provides background on summary and detailed report views; the month-end close checklist helps organize the wider period review.
- Customer and invoice reference.
- Issue to clarify, supported by the relevant record.
- Person responsible for the next action.
- Next review date and outcome once confirmed.
Calculate an overdue share consistently.
For a consistent report, calculate the overdue share as overdue receivables divided by total open receivables, multiplied by 100. State the aging basis and date. If the total is zero, report the ratio as not applicable.
Keep the period, population and definitions consistent when comparing results. These are suggested measures, not industry benchmarks or observed FilWorx customer outcomes.
Sources & further reading.
Further reading from the original publishers. Product documentation describes that publisher’s product; it does not establish FilWorx capabilities.