Automate Coaching Billing and Subscription Renewals
Nour
Founder, Coachful
Coaching billing and subscription renewals work well when the recurring collection matches the service the client actually agreed to buy. Define the amount, interval, continuing work and ending process first. Then configure collection and communications, with a person responsible for checking exceptions and the client's next decision.
A subscription schedule can request the next payment. It cannot decide whether the service remains useful, establish agreement to a different price or prove that access ended correctly. The fictional case below follows an existing Program into recurring payments, a failed renewal, actual recovery and an ending that deliberately preserves resource access.
Choose the correct commercial arrangement
| Arrangement | Illustration | What the client needs to understand |
|---|---|---|
| Rolling monthly service | £300 monthly until properly stopped. | The recurring service, charge date, amount and cancellation process. |
| Finite package in installments | £900 total paid as three £300 installments. | The total commitment and finite payment count, separate from delivery dates. |
| Fixed term with another decision | An engagement ends on 31 December; another term needs agreement. | There is no further agreed term merely because the coach proposes one. |
| Corporate invoice arrangement | A buyer pays monthly through procurement. | Actual buyer approval, invoices, due dates and permitted service before settlement. |
Three payments of the same amount can describe very different bargains. Do not convert a completed package into an indefinite subscription because it is convenient to reuse a monthly amount. Equally, do not promise that canceling a payment instruction settles every obligation under a fixed package. Check the actual agreement and applicable rights.
Separate the client's coaching purpose from the payer's administrative role. A sponsor may receive invoices without receiving private reflections. A person copied on a billing email does not automatically gain authority to change the participant's service or inspect their coaching records.
Develop six controls before switching on recurring collection
Write a service promise with real limits
Describe what each paid period provides: sessions or other work, quantities, response boundaries and relevant access. Count preparation and follow-up as well as scheduled contact. Explain what happens to an unused allowance and what is excluded; do not assume the payment interval creates an entitlement.
An existing Program's resources, schedule and session configuration remain separate things to inspect. A recurring-payment request is a collection arrangement attached to that enrollment. It does not invent extra calls, private support or a new curriculum. Configure and verify any actual delivery changes through their appropriate workflows.
Make agreement and price changes understandable
State price, currency, interval, first charge, term and ending route before authorization. Identify whether future service continues automatically or needs a new decision. Avoid using an unclear renewal notice to introduce a new minimum commitment.
For UK trader-to-consumer arrangements, the CMA's fair-contract guidance, updated July 2026, addresses transparent terms, meaningful renewal information and cancellation obstacles. Corporate relationships and other jurisdictions can differ. Have the actual terms and notices reviewed for the relationship; this guide's fictional wording is not a legal template.
A new public price is not evidence that a particular existing subscription has changed. Check the actual purchase, saved price and authorized change. If proposing a change, explain what changes, when and what choices the client has. Record a proposal separately from an agreed and implemented change.
Distinguish requested, authorized and paid
A sent payment link is not approval. Approval of future recurring collection is not an immediate payment when the first charge is scheduled later. A processing payment is not confirmed settlement. Keep those states visible rather than reporting every created request as revenue.
Use the actual subscription, invoice and payment references. A successful collection is different from a receipt email or a bank payout. Fees, refunds, timing and currencies need their own reconciliation. A recurring-revenue figure is not certain cash in the bank.
Configure the right communications
Decide which messages the processor sends and which the coaching business owns. Avoid two conflicting notices with different dates or amounts. Check recipient, collection method, secure management destination, timing and actual delivery evidence.
Stripe's current Automate customer emails documentation distinguishes renewal reminders for automatically charged subscriptions from reminders for unpaid recurring invoices sent for payment. Its configured timing and recipient timezone matter. A reminder feature does not guarantee that a particular person received or acted on an email.
Use the current authorized secure route for billing changes. Never ask someone to send full card details through a coaching message or email. Keep personal coaching material out of payment reminders and accounting payloads.
Own payment exceptions rather than only retries
A failed renewal can mean that the client needs help updating a method, that the amount is disputed or that a cancellation was not implemented. Recheck the record and any recent request before sending another generic reminder. Do not create a second subscription to repair the first one's unpaid invoice.
Stripe's current retry guidance explains configurable retry policies and situations where a new payment method or other action is necessary. The actual next attempt and result matter; a planned retry is not recovered revenue. A human owner must resolve uncertainty about payment and service.
Decide billing, service and access at an ending
Stopping future charges, ending coaching work and retaining selected resources can have different dates and effects. Confirm each deliberately. A cash refund, outstanding balance, restored session credit and continuing library permission are also different records.
Pausing collection is particularly easy to misunderstand. Stripe's current payment-collection guidance states that a subscription can remain active and invoices continue while collection is paused. That is different from a promised service break or a completed cancellation. Use the controls that produce the agreed result and verify it afterward.
Complete an existing-client recurring setup in Coachful
Coachful is our #1 recommendation for organizing this coaching billing and delivery workflow. A client who already has a Program can approve recurring payments without a duplicate enrollment, while the coach checks the actual price, schedule and access treatment. The client still needs to authorize collection; a coach's configuration is not permission to charge.
The released route is Clients > joined client > Billing > Recurring payments > Start recurring payments. In Simple mode, More options reveals Billing. The Program's Purchases row also has the supported shortcut. The person needs an app account, the workspace needs its connected Stripe account and the staff member needs Payments permission.
The request offers the Program's recurring price or a custom price for that client. A custom amount does not rewrite the Program's public price. Review amount, currency and frequency. Choose the appropriate first-payment option: approval today, a configured free trial or a date. Choose payments until stopped or a defined payment count, and review what happens when payments stop.
Pause access and Keep access have different effects. Use the option that matches the actual bargain. A dated first payment can leave free access in place until that date; it is not an already collected first payment. Creating the request does not itself charge or alter access.
The client signs in, reviews the terms and approves on the hosted payment page. Track the resulting state and actual payment separately. Active requests have Stop at end of period; clients can manage or cancel from the Program page. Use the supported record rather than a note saying that someone probably stopped it.
Follow a complete fictional renewal lifecycle
All names, dates, messages and results in this case are fictional. Maren coaches Luka, who already has a granted ongoing Program containing a resource library and private worksheets. The Program community is disabled. There is no unpaid earlier purchase, and no old automatic collection needs to be retired.
They agree a rolling service starting 1 November 2033: £300 GBP per calendar month for the continuing Program and one coach review of a submitted reflection each month. Maren returns that feedback through their authorized private conversation within two working days of the agreed submission. The service includes no new one-to-one session credits or unlimited between-session advice.
The reviewed arrangement allows Luka to stop before the next monthly charge without a new minimum term. Monthly coach reviews end with the paid service, while library and existing worksheet access remain under the separately agreed continuing permission. The price is a final reviewed input for this fictional case, not a tax classification or a recommended market rate.
Show approval before the first charge
On 6 October, Maren creates a recurring request for the existing Program using a custom £300 monthly price, first payment on 1 November, payments until stopped and Keep access. There is no setup fee and no trial. The review states that nothing is due that day.
Luka signs in on 7 October, checks the same terms and approves the hosted request. Maren verifies the dated first-payment state. She does not report £300 collected on 6 or 7 October. The request is accepted before its applicable link expiry; she does not assume an unaccepted dated link remains valid indefinitely.
On 1 November, the first £300 payment actually succeeds. Maren checks its original invoice and payment references, the existing Program enrollment and Luka's accessible resources. Progress remains on the same enrollment. She does not create a second enrollment or an additional manual £300 invoice.
Luka submits the agreed November reflection on 9 November, and Maren returns the actual feedback on 10 November through their private conversation. Saving a private coach-team review alone would not deliver it. They discuss the usefulness of the feedback separately from payment success.
Send a complete and accurate renewal notice
Maren owns a manual service-and-billing notice in this case. She checks that no conflicting provider renewal email is configured for the same purpose. This choice is part of the fictional arrangement, not a claim that Coachful has a universal fourteen-day renewal trigger.
Subject: Your £300 coaching renewal on 1 December
Hello Luka,
Your current monthly coaching arrangement is scheduled to continue on 1 December 2033 at £300 GBP for December. It includes your Program resources and one review of your submitted reflection, returned through our private conversation within two working days of the agreed submission. It does not add one-to-one session credits.
You can manage or cancel the recurring payment from your Program page before the next charge. You can also contact me through our existing private conversation if the arrangement needs clarification. We can review whether continuing is useful; you do not need to accept a different package to end this one.
If you stop, future monthly coach reviews end with the paid service. The library and existing worksheet access remain under our agreed continuing permission. Please tell me if a payment or cancellation record looks wrong so I can check it before further collection.
Maren sends that notice on 17 November, fourteen days before the scheduled charge. Luka confirms receipt on 18 November and asks about a £330 price on a different new-buyer Offer. Maren checks his existing £300 recurring record and confirms that no price change has been agreed or applied to him. The notice is not silently rewritten as a £330 authorization.
Luka chooses to continue December under the same scope. The review records that choice and the useful November feedback; it does not claim coaching caused a workplace promotion or that automatic payment proves satisfaction.
Resolve an actual failed renewal on its original invoice
The scheduled 1 December attempt fails. The December invoice remains unresolved, and no successful second payment is recorded yet. Maren checks Luka's recent messages and confirms there is no cancellation or amount dispute before following up.
Hello Luka, the £300 December payment on your existing subscription did not complete. Our agreed December amount and scope have not changed. Please use the authorized secure payment-update route for that subscription, or contact me if the amount is wrong. Please do not send card details in this conversation.
Your library access remains in place under our Keep access arrangement. I will check the actual payment result and confirm the billing position rather than asking you to buy the service again.
Luka uses the configured secure provider route to update the relevant payment method. On 3 December, the existing invoice is successfully paid on a subsequent collection attempt. The date is an observed fictional result, not a promised retry interval. Maren checks the same invoice, successful payment reference and remaining balance of zero.
She stops the pending manual reminder because the balance is no longer unresolved. She does not create another £300 payment request or treat the first failed attempt as a third payment. The service remains within the original December agreement, and Keep access means no invented resource suspension is reported.
Luka submits his December reflection on 8 December, and Maren returns feedback on 9 December through the agreed conversation. That is the second actually delivered monthly review. Payment recovery did not automatically complete the review or send its feedback.
Complete the client's ending request
On 20 December, Luka says he does not want January's monthly service. Maren accepts the clear request without requiring an exit survey or a different purchase. She opens the active recurring record, uses Stop at end of period and checks the displayed ending date against the next billing boundary.
Hello Luka, your monthly paid coaching service will finish after December, and I have checked that the recurring payment is set to stop before the January collection. No further monthly coach review is agreed for January.
Your November and December payments were £300 each, totaling £600 received. The December invoice is paid following the successful 3 December collection. No additional balance or refund request is outstanding in this case.
As agreed, your Program library and existing worksheet access remain through Keep access. That permission does not include further monthly coach feedback. I will check the ended billing state and retained access after the scheduled boundary and confirm the result.
On 1 January, Maren verifies that the recurring record has ended and that no January charge or new recurring invoice has been created for it. On 2 January, Luka opens the library and confirms his existing worksheet history remains available. Maren confirms both results to him. The remaining access is intentional, not a cancellation failure.
Reconcile the final record instead of counting attempts
| Case record | Verified outcome | What it does not imply |
|---|---|---|
| 6–7 October request and approval | Dated recurring authorization accepted; nothing collected then. | A created or accepted request is not October revenue. |
| November invoice and payment | £300 successful on 1 November; first monthly feedback delivered. | Payment alone is not feedback delivery. |
| December invoice and payment | Failed 1 December; same invoice paid £300 on 3 December; second feedback delivered. | The failed attempt is not an additional successful payment. |
| Ending | No January collection; no January monthly review; agreed library access retained. | Stopped billing does not require deletion of every resource grant. |
Actual successful receipts total £600. There were two paid monthly invoices, two delivered feedback sets and one failed attempt. This is not a £900 three-payment package and not a forecast of twelve certain £300 payments. Processor fees, payout timing, tax and the cost of Maren's work require separate records.
For the document identity and accounting side, see coaching invoices and receipts. For a more developed unresolved-balance process, see payment retry and dunning.
Contrast a fixed-term continuation
Suppose a separate fictional client, Jules, has a £900 package ending 31 December, paid in three completed £300 installments. Its agreement requires a new decision for another term. The correct message says: “Your current package finishes on 31 December. No further term has been agreed. We can discuss whether another package would help, and you can choose not to continue.”
Jules declines another package. The coach confirms the original payment schedule has finished and no fourth installment is due, then handles remaining service and resource access under the actual package terms. There is no recurring £300 authorization to preserve merely because the previous installments looked like monthly billing.
This contrast prevents an apparent renewal rate from mixing unlike groups. A package intended to finish is not automatically a lost subscription. If measuring continuation, define who actually reached a comparable decision, what continued and which periods are included. The rate alone does not establish that billing automation caused retention.
Use this ordered billing and renewal checklist
- Confirm the bargain. Identify the buyer, participant, service, term, amount, currency and ending route.
- Choose the matching collection. Distinguish an ongoing subscription from finite installments or a new-term proposal. Check actual account connection and staff permission.
- Review authorization and delivery. Check the saved request, first-payment timing, existing enrollment and real access; obtain the client's approval.
- Assign communication ownership. Review provider emails, any custom notice, recipients, secure routes and evidence of receipt without duplicate messages.
- Check each actual result. Reconcile the original invoice/payment and service work. Resolve failures before sending another reminder.
- Review continuation honestly. Discuss usefulness and choices. Treat proposed service or price changes as proposals until appropriately agreed and implemented.
- Verify ending effects. Confirm stopped future collection, remaining balances or refunds, final service and intended retained access separately.
Troubleshoot recurring arrangements
The request is waiting, but the coach thinks billing started. Check actual approval and first-payment state. Explain expiry and send the appropriate current route. Do not count a sent link as collection or create multiple requests to force an answer.
The client received no renewal email. Check the actual owner, collection method, settings, recipient and available delivery evidence. A draft or feature switch is not a sent notice. Use appropriate human follow-up without inventing proof of delivery.
A client reports cancellation during recovery. Pause generic follow-up while the responsible person checks the request, subscription and invoice states. Correct the real issue rather than asking the client to update a card for an amount that may not be due.
The client still opens resources after billing ends. Inspect the agreed and saved access treatment and other grants. It may be intentional, as in the case. Do not restart billing or remove access merely to make the two records look identical.
Frequently asked questions
Do I need thirty-day and fourteen-day renewal emails?
There is no universal schedule in this guide. Use the actual agreement, applicable requirements and relevant provider capabilities. The fictional fourteen-day notice is a reviewed communication choice, not a statutory rule for all coaching.
Does stopping a subscription refund its last payment?
Check the actual request, applicable rights and refund record separately. Do not claim a refund from a cancellation note or restored session credit. The worked case has no outstanding refund request; other cases may need one.
Can I use recurring payments for a client already in a Program?
Coachful supports an authorized recurring request attached to an existing eligible enrollment. Review account, permission, price, timing and access prerequisites. Creating the request alone neither charges nor re-enrolls the person.
Does pausing collection end access?
Not necessarily. Provider collection controls and the coaching platform's access treatment differ. Agree the intended service and invoice effects, use supported controls and verify the actual state.
Can software decide whether the client should renew?
Software can organize recurring collection and records. The client and coach still review fit, scope and choices. Explore Coachful features for the billing and coaching workflows around those decisions.
