An invoice payment that has been initiated but remains pending should not count as collected cash. Keep the invoice and payment states visible, assign a review trigger, and move the amount into actual cash only after the relevant receipt or settlement evidence is observed.
`Pending invoice` is not one universal accounting status. It can describe a draft or approval workflow, a payment attempt, a processor review, or an invoice that remains open while another event is pending. Identify the object that is pending before changing the forecast.
Separate the records
Stripe documents a case where an open non-subscription invoice waiting for an initiated payment can show a Pending badge in the invoice list while the details page still shows Open. That is a useful warning: a payment workflow event and the invoice's accounting status can coexist without proving available cash.
Track at least four events:
| Event | Evidence | Forecast treatment | | --- | --- | --- | | Invoice issued | Invoice ID, amount, due date, open status | Eligible for invoice-level review. | | Payment initiated | Attempt or payment reference and timestamp | Raises a pending exception; not cash. | | Payment succeeded or recorded | Platform or accounting status | Reconcile to the invoice; still separate from bank availability. | | Deposit or settlement observed | Bank or processor settlement evidence | Count in actual cash under the reporting cutoff. |
The invoice payment-date versus deposit-date guide describes the same timing boundary for QuickBooks records.
Give pending a bounded action
Pending is not a permanent category. Record the payment reference, invoice ID, amount, initiation time, current status, expected platform review point when supplied, owner, and next check time. If the platform provides a required customer action or failure reason, store that source value without translating it into a guaranteed outcome.
Use a two-part label such as `payment_pending`, `approval_pending`, `delivery_pending`, or `settlement_pending` plus the invoice's source status. The label should tell the reviewer what evidence is missing and which owner can resolve it.
If an approved invoice never enters the stated buyer run, use the missed payment-run framework to retire the expired week and request fresh dated evidence.
Do not keep both the original invoice amount and the pending payment as two forecast inflows. The payment is a status attached to the same cash path. Likewise, do not remove the invoice from every operational view: finance still needs to reconcile the open balance and ensure the payment resolves correctly.
If funds are held after a successful payment event, use the processor-hold decision framework to preserve the distinction between customer payment and bank availability.
Update the forecast without rewriting history
When payment is initiated after the forecast snapshot, append the new event. You may update confidence or the next review date when the event is relevant, but retain the prior expected week and rationale for later comparison.
When the payment succeeds, reconcile the applied amount to the invoice. When cash is observed, move it from forecast to actual using the agreed receipt cutoff. When the payment fails or is canceled, restore the unresolved collection action and retain the status history.
For automatic collection workflows, the small SaaS collection-method comparison shows which fields belong to an attempt versus a send-invoice path.
Decision rule
Pending means “verify the payment path,” not “cash collected” and not “payment failed.” Preserve one invoice amount, one linked payment record, a named owner, and a dated review trigger. Finance teams can apply for AR Pulse for an invoice-level action list and four-week range that keeps source statuses separate from observed receipts.