When automatic advancement or collection is turned off, keep a finalized open invoice in accounts receivable but replace platform-driven assumptions with an explicit human owner and next action. The setting does not make the invoice uncollectible, and it does not provide a collection date. Forecast timing only from current payment evidence, agreed terms, and a documented manual workflow.

The platform state changes the work queue

Stripe explains that invoices begin as drafts and must become open before they can accept payment. Its automatic-advancement control can enable or disable activities such as invoice emailing, reminders, retries, and automatic payment attempts, depending on the invoice and configured workflow. Paid, void, and uncollectible invoices do not continue automatic advancement.

For a small SaaS company serving invoiced enterprise customers, pausing advancement can be deliberate: finance may be resolving a contract issue, validating billing, or controlling customer communication. But the pause removes system-generated actions that a forecast might otherwise assume will occur.

Use the autocharge-versus-send-invoice guide to identify the collection method. If the record is still a draft, the draft invoice boundary applies instead.

Add a manual control record

For each affected open invoice, preserve:

  • invoice status, amount, due date, and collection method;
  • automatic-advancement state and the time it changed;
  • which automated emails, retries, or attempts are disabled;
  • reason for the pause, when available;
  • named owner and next review date;
  • customer-side evidence such as accepted invoice or payment commitment; and
  • the trigger for resuming automation or taking a manual action.

Do not move the invoice out of AR solely because automation is off. Do not leave a prior expected week unchanged solely because the platform once had retries scheduled. Reassess the timing assumption using the remaining evidence. If no support exists, mark the week unassigned and keep the item in the action queue.

Recheck the state at every forecast refresh. A resumed workflow can create a new reminder or payment attempt, while a continued pause leaves the named owner responsible for the next supported action.

The AR follow-up ownership workflow helps route manual exceptions without turning AR Pulse into a reminder system.

Decision rule

Automation state determines who must act; it does not determine whether cash will arrive. Keep the invoice visible, assign manual ownership, and use only current evidence for the four-week range.

AR Pulse analyzes an authorized receivables export and returns a ranked action list plus a four-week collections view. It does not change billing settings, retry payments, or contact customers. Small SaaS finance teams can apply for AR Pulse.