Pull up an AR aging report and the buckets can look wrong at first glance. An invoice that feels overdue sits in the 0-30 column. One you'd forgotten about shows up in 90+. The buckets aren't broken. They're all measured against one date you probably didn't set on purpose: the aging date. If you searched for an aging date accounts receivable definition to figure out why, here it is.
What is an aging date on an AR or AP aging report?
The aging date is the single as-of date the report ages every open balance against. Take aging date minus invoice date (or bill date) to get the age. That day count sorts the balance into a bucket: current, 1-30, 31-60, 61-90, or 90+. Change the aging date and every bucket shifts, even though no invoice moved. Most software defaults the aging date to today or the report's run date. You can usually override it. That override matters most at month-end close.
- The aging date is the as-of date, not the invoice date or the due date - it's the single reference point every balance gets measured against.
- Bucket placement is simple math - aging date minus invoice date equals the day count, and the day count picks the bucket.
- Report date and aging date aren't always the same day - a close report pulled a few days late can still age off the period-end date, not the day you ran it.
- The due date is a separate concept entirely - it drives when a balance becomes "late," while the aging date just tells you how many days have passed.
- Getting this wrong skews both sides of the business - it misprioritizes AR collections and misorders AP payment scheduling.
- Most tools let you override the default - checking what aging date a report actually used takes ten seconds and saves a wrong read at close.
These three dates get confused constantly, and they're not interchangeable.
Here's a worked example. An invoice is dated May 3. The aging date on the report is June 30. Count the days: May 3 to June 30 is 58 days. Fifty-eight days lands in the 31-60 bucket. Not 61-90. Not current. That's true even if someone doesn't read the report until July 2.
Subtract the invoice date from the aging date to get the day count, then match that count to whichever bucket range it falls into. The report date doesn't enter the calculation at all.
The most common mistake: assuming "today" is always the aging date. A month-end close report pulled a few days late should still age off the period's last day, not the day someone opened it. Confirm the aging date before trusting any bucket total, especially around close.
Categorizes the routine. Flags what needs you.
See Growthy on a sample book. Read-only bank access.
Get startedGet the aging date wrong and both sides of the ledger get a bad read. On the AR side, invoices land in the wrong bucket, so collections effort goes toward accounts that aren't as overdue as they look. Read more on bucket mechanics in the AR aging report guide. On the AP side, the same math error skews payment timing. See the AP aging report guide for how that side works.
For bookkeepers running a stack of QBO clients, this isn't a one-time check. Every client's close depends on it being set correctly, every month.
Most accounting software defaults the aging date to today or to the date you generate the report. That default works fine for a quick daily check. It works poorly for month-end close. There, you need the aging date locked to the period-end, not to whatever day you opened the report.
Look for an as of date aging report field or override option before running one near close. Comparing aging across a portfolio of clients? Keeping that setting consistent is easier from one place. See Growthy's multi-client dashboard for a view built around that comparison. If the portfolio itself is the problem, too many clients for the hours, Bobby's newsletter, Scaling Clients, covers the capacity side of that work.
No. The aging date is the as-of date balances are measured against; the report date is just when the report ran.
No. Bucket placement uses aging date minus invoice date only. Due date determines when a balance is officially late.
Set your aging date deliberately, especially at close, and the buckets tell you the truth. Get started with Growthy to keep every client's aging report consistent without hunting for an override field each month.
Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice.
