Should the oldest invoice always be collected first?
No. Invoice age is important, but a practical collections queue also considers balance size, dispute status, promises to pay, customer history, project importance, prior outreach, and the operating obligations connected to the receivable. The oldest invoice may not be the highest-value next action.
- Age measures lateness, not actionability
- Disputed invoices need a different workflow
- Promises to pay should carry follow-up dates
- Large balances can deserve earlier attention
- Project obligations can change the urgency of a receivable
Accounts receivable teams often start with the oldest invoice at the top of the report. That is a reasonable default, but it is not always the best next action.
Age tells you how late an invoice is. It does not tell you why it is late, whether the customer has promised payment, whether the invoice is disputed, or how important the receivable is to near-term operations.
What aging is good at
Aging provides a consistent measure of lateness.
It helps answer:
- what is current,
- what just became overdue,
- what has been overdue for a month,
- what is becoming seriously delinquent,
- how the receivables portfolio is shifting over time.
That is essential information. The mistake is treating it as a complete priority model.
Add balance size
A $40,000 invoice that became overdue yesterday can matter more to near-term cash than a $400 invoice that has been overdue for 45 days.
That does not mean large invoices should always jump the queue. It means balance size is another relevant signal.
Add dispute status
An invoice under active dispute is not solved by sending the same reminder again.
Its next action may be:
- provide missing documentation,
- correct an invoice field,
- obtain internal approval,
- respond to a customer claim,
- escalate a commercial issue.
A disputed invoice should therefore be visible but routed differently from standard collections follow-up.
Add promises to pay
A customer who has committed to pay on a specific date creates a different workflow state.
Record the promised date and schedule the next review around it. Otherwise the team either contacts the customer too early or forgets to follow up when the promise is missed.
Add prior outreach
Repeatedly sending the same message without seeing the prior history creates noise and can damage the relationship.
The queue should make it obvious:
- when the customer was last contacted,
- who contacted them,
- what happened,
- what the next action is.
Add job and operating context
Project businesses have another useful signal: what operating obligations are connected to this receivable?
A customer milestone may support upcoming contractor payouts, travel, or vendors associated with the same project. A delayed payment can therefore create operational pressure that is invisible in the aging bucket alone.
That is why invoice aging workflow software should connect the invoice to the job rather than treating receivables as detached rows.
Build a simple priority model
A practical collections priority can combine:
- age,
- open balance,
- promise-to-pay status,
- dispute status,
- customer history,
- job context,
- operating urgency,
- last action date.
A team does not need a black-box score to benefit. Even a transparent set of rules can improve consistency.
For example:
Priority A: material balance, overdue, no active dispute, no recent response.
Priority B: overdue with promise date approaching or just missed.
Priority C: disputed and assigned to a resolution owner.
Priority D: low balance with recent customer engagement and no immediate operating effect.
The actual thresholds should fit the business.
Use aging for measurement and a worklist for execution
These are complementary tools.
The aging report is excellent for portfolio visibility and financial review. The worklist is better for day-to-day execution.
Kelvaro Collect uses the collections-control model: invoice context, aging, reminder history, filters, and a prioritized worklist. Kelvaro Cash can then bring supported receivables into a broader action queue alongside payout and funding issues.
Frequently asked questions
What is an invoice aging report?
An invoice aging report groups open receivables by how long they have been outstanding, commonly using current, 1 to 30, 31 to 60, 61 to 90, and more-than-90-day buckets.
What makes a receivable high priority?
Priority depends on the business, but common signals include age, open balance, payment commitment, dispute status, customer history, and the operating effect of delayed cash.
Should disputed invoices stay in A/R aging?
They generally remain open receivables until resolved, but operationally they should be distinguished from normal overdue invoices so the next action addresses the dispute rather than repeating standard collection reminders.