Use invoice age to organize attention, then add the reason for nonpayment, the person responsible and the next useful action. A collections worklist should distinguish routine follow-up, disputes, missing evidence, promised payments and unapplied receipts so the team can move each balance forward.
Use age as context, not the whole explanation
Two invoices can be thirty days overdue for different reasons. One customer may have missed a scheduled payment; another may be waiting for a delivery sign-off from your team. Sending both the same message is easy to automate, but it leaves one of the actual blockers untouched.
Keep aging and case status as separate information. Preserve the original dates while recording the current explanation. A disputed invoice does not become younger because someone opened a case, and a payment promise does not erase the remaining balance.
Give each open item a next move
A practical worklist needs enough context to act without opening six unrelated systems. Start with the invoice, amount and due date, then add blocker, owner, next action, due time for that action and links to evidence. Record the last meaningful customer response alongside the next step.
For example, “Delivery acceptance pending; project manager to provide signed record by Thursday; collector to reply after review” describes a sequence. The collector can see both the dependency and the person who can remove it. This is an illustrative operating pattern, not a required software field layout.
- Routine follow-up: the invoice is supported and the next contact is scheduled.
- Investigation: a specific objection needs evidence or clarification.
- Decision: a credit, correction or sensitive message needs authorization.
- Commitment: the customer named a payment date that needs a later check.
- Cash application: a receipt exists but its allocation or residual needs work.
Pause the action that no longer fits
Proper’s Arlo Table Stakes story shows reminders following plans while disputes reach their owner and promises receive a next check. That distinction helps explain what an evaluation should prove: a customer response must be able to change the workflow, not merely appear in an inbox next to it.
Ask which messages stop when a case enters investigation and what restarts follow-up. Avoid leaving an invoice paused indefinitely. A pause should have an owner, reason and review date. When ownership changes, the evidence and pending decision should travel with the case.
Review progress through resolved blockers
In a team review, ask what changed since the last check. Was the sign-off obtained? Was the corrected reference accepted? Did the promised receipt arrive? These questions reveal movement more clearly than counting emails sent. Retain activity counts where useful, but do not confuse communication volume with completed work.
An effective demonstration includes a response that changes the next step, an absent owner and a receipt that cannot be matched confidently. Confirm the plan, permissions and connections that support the shown behavior. A clean demonstration should make unresolved cases understandable as well as celebrate cleared ones.
Questions & answers
Should a disputed balance disappear from the worklist?
No. It should have a distinct state and owner. The collection action may pause while the investigation proceeds, but the unresolved balance and its next check should stay visible.
Is the oldest invoice always the first one to work?
Age is one input. Your team may also consider amount, evidence readiness, customer commitments, dependencies and its own policy. Make those choices explicit instead of hiding them in an unexplained score.