An aging report can count from either the invoice date or the due date, and the choice between invoice date and due date on an aging report changes which bucket every unpaid invoice falls into. Counting from the invoice date starts the clock the moment you bill the customer, so long-term credit balances look old even when the customer is still within terms. Counting from the due date starts the clock at the payment deadline, so only genuinely late invoices appear in the overdue columns. Most small-business accounting platforms use the due date by default; larger enterprise systems typically let you pick.
What Each Anchor Date Actually Means
The invoice date is the calendar day you generate the bill. It marks when the transaction hit your books, regardless of when the customer is expected to pay. Aging from the invoice date gives you a fixed, consistent reference point, but every open invoice accumulates days from the moment of sale. Long credit terms will make your receivables look worse than they are because a Net 60 invoice on day 45 shows up as “45 days old” even though the customer is not late.
The due date is the deadline printed on the invoice. Aging from the due date means the counter sits at zero until the customer actually misses the payment window. An invoice in the 31–60 day bucket is genuinely 31 to 60 days late, not just 31 to 60 days old.
QuickBooks Online, for example, ages from the due date with no built-in option to switch. SAP, Oracle, and other enterprise platforms typically let you configure either method. If your software doesn’t give you a setting, you are almost certainly aging from the due date.
The Same Invoice, Two Different Buckets
Suppose you issue a $5,000 invoice on January 1 with Net 30 terms, making the due date January 31. You run your aging report on February 15.
- Aged from the invoice date, 45 days have passed. The invoice lands in the 31–60 day bucket.
- Aged from the due date, 15 days have passed since it went late. The invoice lands in the 1–30 day past-due bucket.
Same customer, same money owed, different picture. Multiply that across hundreds of open invoices and the two methods can produce very different reads on receivables health. A company aging from the invoice date might see a portfolio that looks heavily past due; due-date aging on the same data would show most balances only mildly late. Neither is wrong. You just need to know which one you’re looking at before you make a decision based on it.
How Credit Terms Set the Gap
Credit terms like Net 30, Net 60, or 2/10 Net 30 determine the distance between the invoice date and the due date, and that distance is exactly what makes the two methods diverge. Under Net 30, the customer has 30 calendar days from the invoice to pay in full. Under 2/10 Net 30, they can take a discount (commonly 2% to 5%) for paying within 10 days, with the full balance due at 30. The longer the terms, the more the two aging methods will disagree at any given moment.
When no credit terms are written into the contract for a sale of goods, the Uniform Commercial Code fills the gap. Under UCC Section 2-310, payment is due at the time and place the buyer receives the goods, essentially payment on delivery. That default rarely applies in practice because most B2B contracts specify credit terms, but it matters for aging: if you have a customer with no formal terms and you age from the due date, day zero is the delivery date, not the invoice date. If delivery and invoicing happen days apart, which is common when invoices go out in batch runs, your aging math shifts accordingly.
How Aging Buckets Work
The calculation is straightforward. Subtract the anchor date from today’s date to get days outstanding, then drop each invoice into the appropriate bucket. Standard intervals look like this:
- Current (0–30 days): not yet past due, or only recently so.
- 31–60 days: mildly overdue. Most collection teams start making calls here.
- 61–90 days: moderately overdue. Payment plans or escalation letters typically go out.
- Over 90 days: seriously delinquent. Most likely to become uncollectible.
Some businesses add finer bands (91–180, 181–365, over 365) when they need to calculate an allowance for doubtful accounts. That calculation applies a progressively higher loss rate to each older bucket, reflecting the fact that a six-month-old receivable is far less likely to be collected than a 30-day-old one. Under GAAP, these layered estimates feed the allowance that reduces reported receivables on the balance sheet. For public companies and many larger private ones, FASB’s current expected credit loss standard (ASC 326, often called CECL) specifically contemplates aging schedules as one method for estimating lifetime credit losses on trade receivables.
The anchor date you picked at the top of this article is what determines which bucket every invoice sits in, which in turn determines the loss rate applied. Two companies with identical receivables can report different allowances if one ages from the invoice date and the other from the due date.
How the Choice Drives Collection Escalation
Aging buckets are a decision framework, not just a snapshot. A common escalation ladder ties actions to thresholds:
- 1–30 days past due: automated reminders or statements.
- 31–60 days: direct calls from the accounts receivable team.
- 61–90 days: formal demand letters, suspension of further credit.
- Over 90 days: referral to a collection agency or legal action.
Collection agency fees scale with the age of the debt. Accounts referred under 90 days generally command lower contingency rates than older accounts because fresher debts are easier to recover. Accounts outstanding for six months or more carry significantly higher fees, and if litigation is needed, contingency rates can climb to 50% of the recovered amount. A report that understates how old your receivables are (by anchoring in a way your team doesn’t understand) delays escalation and costs money on the back end.
For federal contractors, the anchor date has a direct dollar consequence. Under the Prompt Payment Act, 31 U.S.C. § 3902, federal agencies that miss a payment deadline must pay interest to the contractor for every day the payment is late, starting the day after the required payment date. For the first half of 2026, that interest rate is 4.125%.1Federal Register. Prompt Payment Interest Rate; Contract Disputes Act The aging report documents how many days late the payment is, and by extension how much interest is owed. Here the due date isn’t a choice at all; the statute anchors to it.
Bad Debt Write-Offs Rely on the Aging Trail
An aging report is the primary evidence businesses use to decide when a receivable has gone from slow to worthless. The IRS allows a business bad debt deduction, but only if the amount owed was previously included in gross income, meaning cash-basis businesses generally cannot deduct unpaid invoices they never recorded as revenue.2Internal Revenue Service. Topic no. 453, Bad Debt Deduction
For accrual-basis businesses, the deduction is available once the debt becomes worthless. The IRS looks at facts and circumstances: has the customer gone bankrupt, have collection efforts been exhausted, would a court judgment be uncollectible. You don’t have to wait until a debt is due to determine it’s worthless, and you don’t have to sue, but you do need to show reasonable collection steps.2Internal Revenue Service. Topic no. 453, Bad Debt Deduction The deduction must be taken in the year the debt becomes worthless; miss it and you’ll need an amended return. An invoice sitting in the “over 365 days” bucket with unanswered demand letters and a bankrupt customer tells a clear story. An invoice written off after 45 days with no collection effort does not.
Disputes and Partial Payments
Disputed invoices are the most common source of misleading aging data regardless of which anchor date you use. A customer contests a $12,000 invoice on day 5, the dispute drags on for two months, and suddenly a 60-day-old receivable sits in the overdue column even though it isn’t really delinquent. The fix is a separate status category. Tag invoices as “Disputed,” “In Payment Plan,” or “Legal Action Pending” so they don’t contaminate the aging analysis. The clock typically keeps running for record-keeping, but management should review disputes on a separate track. Under UCC Section 2-607, a buyer who has accepted goods must notify the seller of any defect or breach within a reasonable time, so a customer who disputes an invoice months after delivery with no prior complaint is in a different posture than one who objected on receipt.
Partial payments work differently. When a customer pays $3,000 against a $10,000 invoice, most systems keep the remaining $7,000 in the original aging bucket tied to the invoice’s anchor date. The balance does not reset to current just because some money arrived. That’s the correct treatment. Otherwise partial payments would constantly push delinquent balances back into younger buckets and hide collection problems.
Pick One and Write It Down
The anchor date flows through everything: which bucket an invoice sits in, when your team escalates, how much allowance you book, when you can write a balance off, and how much Prompt Payment interest a federal agency owes you. If your system ages from the due date but your team mentally tracks from the invoice date, the disconnect will eventually cause a missed collection window or an inaccurate allowance calculation.
Check what your accounting software actually does. Confirm it matches how your credit and collections staff read the report. Then document the choice in your accounting policies so everyone reading a report knows what “30 days” means in your system.