When a payment is detached from a paid SaaS invoice, separate the cash event from the invoice application event. Reopen the supported receivable state, preserve the original receipt, and assign a new collection week only after current evidence supports what will happen next. Payment detachment does not automatically mean cash was refunded or lost.

Stripe's payment-application documentation explains that unapplying a payment can move an invoice back to Open, Past Due, Partially Paid, or Failed. It also warns that downstream systems must be prepared for a paid invoice to reopen. For a small SaaS finance team, the important control is an event bridge rather than a silent status replacement.

Record four separate states

| State | Evidence to preserve | Cash-forecast treatment | | --- | --- | --- | | Original invoice | Invoice ID, amount, due date, collection method | Source receivable before payment | | Observed payment | Payment ID, amount, receipt date, settlement evidence | Actual cash under the applicable cutoff | | Detachment | Event ID, timestamp, reason or owner | Reconciliation exception; not a second cash event | | Reopened invoice | Current open balance and status | Review for new timing; do not reuse the old week automatically |

Do not erase the payment because the invoice reopened. Do not count the reopened balance as an additional sale. Preserve the event sequence so accounting, billing, and cash views can be reconciled.

Decide whether cash moved

Detachment changes the relationship between a payment and an invoice. It does not by itself prove that funds left the bank, returned to the customer, or failed to settle. Check the payment and settlement records separately.

If cash remains observed, classify the issue as an application exception until the payment is reapplied or otherwise resolved. If a refund or reversal is separately observed, record that cash-out event under its own date. If the invoice remains open after correction, forecast only the supported residual.

The cash application versus forecasting comparison separates those two jobs. The returned-payment guide covers the different case where the payment itself is reversed and the receivable reopens.

Reset the automation assumption

Stripe notes that automatic collection is off by default after an invoice is reopened. A finance team should therefore inspect the current collection configuration rather than assuming reminders or retries resumed. Stripe's automatic-collection documentation describes those workflow controls.

Add an internal owner and next review date for:

  • reapplying the payment to the correct invoice;
  • reconciling billing events to the accounting source;
  • confirming whether automatic collection should be active;
  • reviewing any customer-facing workflow through the authorized billing owner; and
  • updating the four-week view after the source balance is verified.

Forecast rule

A reopened invoice returns to the review population, not automatically to its previous forecast week. Preserve the prior forecast and actual payment outcome, document the detachment, verify the current open balance, and then use fresh evidence for the next timing decision.

AR Pulse analyzes an authorized QuickBooks receivables export. It does not operate Stripe, reapply payments, contact customers, or change accounting records. Small SaaS teams can apply for AR Pulse when reopened invoice states need a traceable four-week cash review.