An open invoice list is a balance report. An accounts receivable action queue is a decision tool. The list answers which transactions remain unsettled. The queue answers which exceptions need attention now, who owns each next step, what evidence is missing, and how the item affects near-term cash timing.

Microsoft's receivables documentation makes a similar separation: aging snapshots store balances at a point in time, while collections activities, cases, disputed transactions, promises to pay, and unsettled payments organize the work around those balances. A small finance team does not need an enterprise collections system to apply that control.

What the open invoice list should preserve

The source list should remain complete enough to reconcile. Retain invoice identifier, customer, issue and due dates, original amount, open amount, transaction status, and the report cutoff. Include current invoices as well as overdue invoices when the job is a four-week cash forecast; an invoice can be current today and still be expected inside the planning horizon.

Do not remove low-priority invoices from the source population merely because no action is due. The list is the control total against which the action queue and forecast should tie.

The AR exceptions report template provides a compact structure for moving from the complete population to decision-ready exceptions.

What belongs in the action queue

Create a queue row when an invoice needs a decision or owned follow-up. Common reasons include:

  • a dispute, short payment, pending credit, or missing purchase order;
  • a promise that lacks a supported date or amount;
  • missing invoice-delivery or customer AP contact evidence;
  • a payment or credit that is recorded but not linked correctly;
  • a large or concentrated exposure that changes the cash range; or
  • stale evidence that requires a new review.

For each row, record the invoice, exception type, evidence, cash effect, priority, owner, next action, and review date. Use the follow-up ownership guide to avoid queues made only of notes with no accountable next step.

Rank by decision value, not age alone

Days overdue is useful context, but it is not a complete priority rule. An older small invoice with a clear payment date may require less attention than a newer high-value invoice blocked by a rejected billing record. Rank work by amount at risk, timing sensitivity, strength of evidence, blocker severity, customer concentration, and whether a concrete action can change the outcome.

The overdue invoice priority matrix shows how to combine those factors without pretending the score predicts payment.

Keep the queue tied to the ledger view

Every queue item should point back to a source transaction. When the source balance changes, close or revise the action rather than deleting its history. When an action is resolved but the invoice remains open, keep the invoice in the source list and decide whether a new timing assumption is supported.

This two-layer design prevents selective reporting. The open list remains the reconciled population; the queue remains a prioritized slice for action. Neither replaces the other.

AR Pulse analyzes an authorized QuickBooks receivables export to produce a ranked cash-action list and four-week collections range. It does not contact customers or predict payment outcomes. Apply for AR Pulse when the missing layer is a source-linked decision queue rather than another reminder list.