Work overdue invoices in the order of decision urgency, not simply oldest first or largest first. A useful priority matrix combines amount exposure, timing evidence, blocker severity, customer concentration, and the presence of a named next action. Aging is an input, but it should not be the only sort key.
Use five keys in a fixed order
When the team cannot work every overdue invoice at once, sort first by immediate decision need, then by material cash exposure, blocker severity, evidence freshness, and ownership readiness. This prevents a large but fully owned routine item from crowding out a smaller invoice whose missing approval or broken commitment can still be resolved inside the forecast window.
The ordering is deliberately operational. It does not score a customer's character or prescribe contact tactics. It tells the finance team which internal evidence gap or decision should be handled next.
Start with a reconciled population
First confirm the report date, open balance, invoice identity, customer, due date, and any payments or credits. Intuit's AR aging documentation explains that aging reports organize outstanding balances by how long they are overdue. That helps describe the population; it does not reveal which internal action is most likely to change near-term cash.
Use the QuickBooks AR export checklist before applying priorities. A missing or duplicate row is a data-quality exception, not a collection priority.
Score the action, not the customer
Use a small set of transparent priority bands:
| Priority | Evidence pattern | Next internal move | | --- | --- | --- | | P1: cash-critical exception | Material near-term amount plus a dated blocker, broken commitment, or unresolved application issue | Name an owner and act or escalate now. | | P2: timing decision required | Open invoice has incomplete or stale timing evidence inside the forecast horizon | Refresh evidence and set a review date. | | P3: routine follow-up | Invoice is overdue but the next action and evidence path are clear | Execute the normal workflow and monitor. | | P4: reconcile first | Amount, status, customer, credit, or payment application is unclear | Resolve the source record before forecasting. |
Do not assign a higher band merely because an invoice is old. An old low-value item with a clear owner may be less urgent than a newer concentrated amount blocked by a missing buyer requirement. The customer-concentration guide helps expose that portfolio effect.
A customer credit hold can be a useful reason code when it changes an internal decision, but it is not proof that existing invoices were paid or rescheduled. Use the credit-hold versus open-invoice boundary to keep upstream order controls separate from the current receivable and its collection evidence.
Record a reason code
Every ranked item should include the invoice ID, open amount, priority, reason code, owner, next action, review date, and expected collection assumption if one is supportable. Useful reason codes include dispute, missing approval, broken promise, unapplied payment, delivery failure, concentration, and stale evidence. A reason code makes the ordering reviewable; it should not turn a weak assumption into a fact.
The follow-up ownership guide explains how to assign the internal work. AR Pulse does not contact customers or guarantee collections; it turns an authorized export into a ranked internal action list and four-week forecast. Finance owners who want that source-linked priority review can apply for AR Pulse.
Re-rank when evidence changes
Priority is a current decision, not a permanent customer label. Re-rank when a payment posts, a dispute changes, a commitment expires, an invoice is corrected, or a concentration exposure moves outside the forecast window. Preserve the prior snapshot so the team can explain why the order changed.
Decision rule
Reconcile first, rank by the next decision and near-term cash exposure, and attach an owner and review trigger to every high-priority exception. The AR Pulse example shows the intended action-list format for a source-linked receivables review.