An archived SaaS product can still have customers being billed

A product catalog change can stop new purchases while existing customer obligations continue. Stripe's documentation states that archiving a product or price leaves existing subscriptions active until canceled. If the business intends to end a service, catalog cleanup alone is therefore insufficient evidence that billing or delivery has stopped.

Write down the commercial decision: stop selling to new customers, stop renewals after a date, migrate existing customers or discontinue all service. Assign a responsible owner and obtain review of contractual commitments and required communications. Each decision leads to a different customer population and a different set of billing actions.

Find every active, scheduled and paused subscription containing the product, including bundles and custom prices. Add customers served outside the standard platform if the business has manually invoiced agreements. Record paid-through dates, renewal dates, remaining prepaid balances, unpaid invoices and promised services that extend beyond the proposed retirement date.

Reconcile the list to product access records. Investigate customers receiving service without a current billing object and subscriptions billing customers who no longer have access. These differences may be intentional concessions or errors. Preserve the explanation so the retirement process does not accidentally cancel a valid agreement or leave an abandoned charge running.

A customer may continue through the existing term, agree to a replacement product or receive an approved credit or refund. Record the authorized outcome, effective date and supporting communication. Have the relevant adviser review disputed rights or nonstandard arrangements. Finance should execute the agreed resolution instead of choosing a convenient default based on which platform button is available.

For a hypothetical annual subscription paid through June, a proposed March shutdown leaves a period that needs an explicit resolution. A migration may satisfy the customer, but the replacement service and any price difference still need agreement and accounting review. Marking the old product inactive does not describe what happened to that remaining commitment.

Review each subscription's remaining invoices, future phases and renewal settings. Confirm whether a final usage charge or outstanding service item is expected. Compare any replacement subscription to the original one so the transition has neither an unapproved gap nor two charges for the same agreed service period.

After execution, run a fresh subscription export and search for the retired product and all its associated prices. Investigate every remaining match against the resolution register. Retain evidence of the final invoice or cancellation and verify customer access follows the approved timeline. Keep an owner for exceptions that cannot close until a later term ends.

Provide the accountant with prepaid balances, delivery dates, approved concessions and migration terms. The treatment of a remaining balance depends on the actual arrangement and accounting policy, so an archive flag is not a sufficient journal-entry instruction. Keep the customer's original invoice and the subsequent resolution connected in the workpaper.

Management reporting should also show whether recurring value ended, moved to a replacement or remains in a run-off group. Preserve a bridge for customers moved between products to avoid presenting an administrative migration as both a new sale and a separate loss. Close the retirement project when the final customer commitments and balances have been resolved, not merely when the catalog looks tidy.