Disclosure: this post may contain affiliate links; AditsBlogs may earn a commission at no extra cost to you.
A customer pays on November 3. When your team reruns the October 31 accounts receivable aging report, the invoice is gone. The current balance may be correct, but the October snapshot has lost a balance that was still open at month-end.
An accounts receivable aging report groups unpaid balances by how overdue they are. A month-end report needs two separate answers for each item. How much was open at the cutoff? How many days past due was it on that date?

Fix the reporting cutoff before calculating age
For a month-end snapshot, use the accounting system’s historical open-item report or reconstruct the position from transactions and their applications through the accounting cutoff. Set the cutoff explicitly. Saving a current open-invoice list a few days later and changing its date in a spreadsheet can miss invoices paid between close and export.
Keep the accounting cutoff separate from the date basis used to assign buckets. For a collections view, the contractual due date tells you when the invoice became overdue. The invoice date answers how long ago it was issued. Some tools let you choose either. Microsoft documents transaction date, document date and due date as distinct options for customer aging snapshots. Microsoft Dynamics 365 customer aging snapshot documentation
Age the open amount, including partial payments
Use one row per open invoice or scheduled installment, depending on how your system records due dates. Include the customer ID, document ID, due date, currency and open amount at the cutoff. Assign each positive balance to one bucket. A simple setup uses current for due dates on or after the report date, followed by 1–30, 31–60, 61–90 and 91+ calendar days past due. Flag missing due dates separately so they remain visible in the total.
Fictional example. A $1,000 invoice was due on October 20, 2026. A $300 payment was applied on October 28. The remaining $700 was paid and applied on November 3. Assume each payment and application was accounted for on the dates shown.
| Report cutoff | Open balance | Aging result |
|---|---|---|
| October 31, 2026 | $700 | 11 days past due, in the 1–30 bucket |
| November 3, 2026, after posting | $0 | Closed |
The November payment changes the current collections view. The October snapshot still shows $700. Keep the later payment in a separate follow-up field if reviewers need to see what has cleared since close.
Tie the total back to the ledger
Compare the report with the receivables subledger and the relevant general ledger control accounts for the same accounting cutoff, entities and currency basis. Keep unapplied cash and credits visible, with their treatment documented. A collections list may show gross open invoices while the ledger comparison includes eligible credits or cash. Show those items separately and explain how the two views reconcile. Oracle’s guidance calls for consistent parameters between its aging and reconciliation reports, including how they treat credits and unapplied cash. Oracle Receivables Aging by General Ledger Account documentation
If the total is off, check for missing accounts, duplicate rows introduced by payment joins, entries posted directly to a control account, and inconsistent exchange-rate or cutoff settings. Record each difference with an owner and supporting evidence. Our reconciliation exception log guide shows how to document what you found and who will follow up.
Keep enough detail to reproduce the report
Save the report parameters and the source extract with the signed-off snapshot. Test an invoice due on the cutoff date, one exactly 30 days overdue, and one paid the following day. Verify that each item appears once, lands in the expected bucket and contributes the right amount to the total. Record a separate refresh time for any live collections view so readers know which version they are looking at.
If your finance team or software product needs a clear reporting guide, talk to AditsBlogs about content writing. We write process guides and product documentation that explain what a number includes and how a reader can verify it.
STAY CONNECTED
More from AditsBlogs, in your inbox
Get occasional updates on new guides, tools, games and creative posts.


