Accounts receivable ageing: turn overdue invoices into specific actions
Suppose that on 31 October, two invoices sit on the overdue side of the aged receivables report. The customer's buyer says one lacks its purchase order (PO) number. The other has been paid, but the receipt is still unallocated in the ledger. Sending the same reminder to both delays both fixes and irritates a customer who has already paid. An ageing report becomes useful when each open line carries an evidenced reason, an owner and a next step.
Set the dates and the basis first
An ageing report depends on two dates. The cutoff decides which transactions count as open, and the ageing date decides how late each one is. The basis matters too. On 30-day terms, an invoice aged from its document date looks a month older than the same invoice aged from its due date.
Microsoft's documentation for Dynamics 365 Finance keeps these as separate settings. It offers ageing by due date, transaction date or document date, uses each transaction's payment terms for the due-date option, and can show transaction detail and unsettled payments. Other products use their own labels and defaults. For a collection review, we recommend setting the cutoff and the ageing date to the same day and ageing by the agreed due date.
Sources and context, checked :
A worked review on 31 October
This hypothetical review uses generic currency units. Balances are shown after recorded credits and allocated receipts. One receipt has arrived but is unallocated, so it appears as evidence beside an invoice instead of being netted against it.
On 30-day buckets, A101 falls in 31 to 60 days and B205 in 1 to 30. Resolve the B205 receipt before treating that invoice as a collection item.
| Invoice | Open amount | Agreed due date | Age on 31 October | Evidence and next action |
|---|---|---|---|---|
| A101 | 2,400 | 30 September 2026 | 31 days overdue | Buyer says the PO number is missing. Confirm the correct PO, resend the corrected invoice to the approved billing contact and set a follow-up date. |
| B205 | 1,200 | 15 October 2026 | 16 days overdue | A bank receipt and remittance appear to match. Verify payer, amount and reference, then allocate before any reminder. |
| C310 | 900 | 15 November 2026 | Not yet due | Confirm delivery and that the customer received the invoice. Report it as current. |
Find the cause before chasing
Each line needs a cause before it needs a reminder. A missing reference is an admin task: correct the invoice details and resend it. An unallocated receipt is a ledger task: verify the payer and allocate it. A dispute about price, quantity or service goes to the person who can settle it, and automated reminders on that invoice should pause meanwhile. Agree the resolution or escalation route with that person. For an undisputed, correctly issued invoice with no matching receipt, choose the next collection step under your agreed terms and approval limits. How firmly to make contact or escalate any item depends on those terms and its circumstances.
Keep the agreed due date fixed. If the customer promises to pay A101 on 14 November, record that in a separate promised-date field. The invoice is still 31 days overdue on 31 October. If terms are formally renegotiated, record who approved the change and keep the original history.
An old balance is a prompt to review collectability, and age alone settles nothing for tax. For US federal tax, the IRS ties a business bad debt deduction to facts such as worthlessness and reasonable collection steps, and says cash-method taxpayers generally cannot deduct amounts never included in income.
Sources and context, checked :
Give each line an owner and a date
For each open item, we suggest keeping the customer and invoice reference, agreed due date, remaining balance, dispute reason, evidence link, last contact, any promised date, owner, next action and follow-up date.
This week, take the three oldest material open items and resolve each against evidence: allocate the receipt, correct the document, route the dispute or send a reminder the customer can act on. Record what was done and the next date before moving on to the rest of the bucket.