Automatic collection and send-invoice collection should not receive the same forecast treatment. The collection method describes the next payment workflow; it does not prove that cash will arrive on a specific date.

Identify the invoice state first

Start with an issued open invoice. Keep draft, scheduled, and other upstream billing objects outside the open-AR population until the billing platform's status supports an issued receivable. Then record the collection method, due date or automatic-payment timing, payment-method readiness, and current payment status.

Stripe distinguishes invoice workflow states and supports automatic collection as a separate process. The small SaaS draft-invoice guide covers the status boundary before forecasting begins.

Forecast automatic collection

For an automatic-charge invoice, confirm that the invoice is open, the collection method is automatic, and the relevant payment setup is present. Treat the scheduled attempt as timing evidence, not observed cash. A failed attempt, authentication requirement, processor hold, or changed payment method can move the outcome.

Keep attempt date, attempt status, failure reason when available, owner, and next retry or review date. The failed SaaS invoice payment guide explains how to keep a failed attempt separate from the open balance.

Forecast send-invoice collection

For a send-invoice workflow, use the recorded due date as one input and add evidence from delivery, customer processing requirements, dated commitments, and payment history. Do not treat the absence of an automatic attempt as a failure; it is a different collection path.

Keep delivery status, due date, required buyer actions, commitment date, owner, and review trigger. The invoice due date versus expected collection date provides the evidence boundary.

Compare without collapsing the workflows

Use a common invoice-level schema with separate method-specific fields:

  • Common: invoice ID, customer, amount, currency, status, due date, open balance.
  • Automatic: payment-method readiness, attempt date, attempt outcome, retry or review date.
  • Send invoice: delivery evidence, buyer workflow, commitment, next follow-up or review date.

Both methods need reconciliation to actual settlement. A successful payment status and bank availability can occur at different times, so preserve those events separately.

When the collection method changes after the forecast snapshot, record who changed it, when it changed, the prior method, the current method, and the reason. Re-evaluate the evidence checklist instead of carrying the old workflow's timing assumption forward. If the invoice is already in an attempt or reminder sequence, confirm the current platform state before assigning the next action.

When the method remains valid but platform advancement is paused, use the automatic-advancement-disabled workflow to replace automated assumptions with a named manual owner.

Decision rule

Collection method changes the evidence checklist, not the definition of cash. Forecast one supported open amount, use method-specific timing evidence, and count a receipt only when observed. Small SaaS finance teams can apply for AR Pulse for an invoice-level action list and four-week collections forecast from an authorized export.