Move a SaaS customer from automatic charges to manual invoices

Confirm the customer's requested payment method, payment window, billing recipient and purchase-order requirements. Obtain the approval required by the business's credit policy. Changing the collection setting should follow an agreed commercial arrangement; it should not silently grant different terms simply because an account manager wants to stop a failing card retry.

Identify the first service period or invoice covered by the change. Tell the customer what will happen to charges already attempted and amounts still due. Keep this confirmation with the subscription record so support can answer whether a particular bill should be paid manually or is still subject to an automatic collection attempt.

Stripe distinguishes automatic charging from invoices sent for manual payment. Its documentation states that changing a subscription's collection method affects subsequently created subscription invoices. Existing invoices therefore need their own review; the new subscription setting is not proof that an earlier automatic attempt has been stopped or converted.

List open invoices, pending payment attempts and any payment currently processing. Have the billing administrator establish the supported treatment of each one before the customer sends money another way. Record the final outcome against the invoice. A change made while a payment is in flight deserves specific follow-up to avoid collecting the same obligation twice.

Preview the next invoice and check its due date, payer details, service period, purchase-order reference and supported payment instructions. Confirm the recipient can access the invoice and understands how to identify the payment. The customer should not have to infer that a saved card will no longer be charged from a different-looking email.

In an illustrative transition, an April renewal might remain on automatic payment while May begins a 30-day invoice arrangement. Keep April's payment status visible even after the subscription is changed. If May's invoice is generated early, check that the intended collection method applies to that already-created invoice rather than assuming the calendar month determines its behavior.

Name the person who will monitor due dates, resolve invoice rejections and apply receipts. Give that owner the approved terms and customer contact. Automatic retries and manual collections require different follow-up, so a customer should not disappear from both queues during the change. Agree how a failed or overdue manual payment will be escalated.

When cash arrives, reconcile it to the invoice and remittance rather than closing the balance from a promise to pay. If the customer pays several invoices together, preserve the allocation. Review the platform's overdue-subscription settings with the product owner so the access consequence is deliberate and consistent with the customer's terms.

Check that the intended invoice was delivered, paid and reconciled, and that no unintended automatic charge occurred. Reconcile the opening unpaid balance, new invoice, receipts and any credits. If the first cycle remains unpaid, document why and keep an owner on the exception instead of marking the transition complete because the configuration changed.

Update the cash forecast for the actual payment timing and retain the approved terms in the account record. Future sales or support staff need to know that the customer uses manual invoices and why. Review the arrangement again if the customer changes payment method or asks to return to automatic collection, including any outstanding invoices from the earlier method.