An accounts receivable aging report tells you how long balances have been open. An invoice pipeline tells you what must happen next. Use both: preserve the accounting snapshot from aging, then add operational stages for delivery, approval, payment evidence, receipt, and reconciliation. Do not treat a movement from one aging bucket to another as progress.

Microsoft's collections documentation describes a centralized collections view built from customer and transaction information. Recent practitioner discussion frames the same work as a pipeline because an invoice can be valid and overdue while still waiting on a specific operational event. The useful synthesis for a small finance team is one invoice record with separate accounting and workflow fields.

Keep aging as the source snapshot

Start with the authorized report date, customer, invoice identifier, invoice date, due date, original amount, open balance, and aging bucket. These fields answer what the accounting source reported at a point in time. Do not overwrite them with a later email status or a forecast assumption.

An aging bucket is not a workflow stage. A 31-day-old invoice may be waiting on approval, scheduled for payment, disputed, partially paid, or simply untouched. Those states imply different next actions and different confidence in near-term cash.

Use a compact invoice pipeline

| Pipeline stage | Minimum evidence | Forecast treatment | | --- | --- | --- | | Issued | Invoice exists in the source with an open amount | Keep in AR; timing may still be unassigned | | Delivered | Buyer receipt or delivery status is observed | Record delivery separately from payment intent | | Blocked | A named approval, document, dispute, or setup issue exists | Assign an owner and review date; avoid unsupported timing | | Promised or scheduled | Amount, scope, and date are stated | Use as labeled timing evidence, not assured cash | | Payment processing | Remittance or processor status exists | Reconcile status; do not count a future receipt twice | | Received | Cash is observed under the review cutoff | Record actual cash and reduce only the supported amount | | Reconciled | Payment is tied to the correct invoice balance | Close or carry the verified residual |

An invoice may move backward. A returned payment can reopen a balance. A new dispute can replace a promise. Preserve the prior stage and timestamp instead of silently changing history.

Add ownership and exit criteria

Each active stage needs an internal owner, next action, next review date, and exit criterion. For example, `blocked: missing PO` should identify who will obtain the PO and what evidence moves the invoice to delivered or approved. `Payment processing` should identify the remittance reference or processor status needed before the row becomes received.

Use the open invoice list vs. AR action queue comparison to decide which invoices need active work. Use the overdue invoice priority matrix to rank material exceptions when the team cannot address every row at once.

Reconcile the pipeline to the forecast

The pipeline should not create a second ledger. At each forecast refresh, reconcile every source-row open balance into exactly one state: assigned to a forecast week, later than the horizon, blocked, or unassigned. Then reconcile received cash to the accounting source under a defined cash-receipt cutoff.

The resulting view answers three questions that aging alone cannot: what changed, who owns the next event, and what evidence supports cash timing. Aging still supplies the population and amount control.

AR Pulse analyzes a customer-provided QuickBooks receivables export and returns a ranked cash-action list plus a four-week collections range. It does not contact customers, change accounting records, or promise payment outcomes. Apply for AR Pulse when a static aging needs an operational decision layer.