Cancel the subscription when the recurring subscription should end. Use one-course Dismiss only when you intentionally need to remove that course enrollment without claiming that billing has stopped. Systeme.io documents subscription cancellation as taking effect just before the next expiration date and removing the resource automatically. Its course-revocation instructions keep the student in the list.
This guide is for a solo teacher handling an existing course subscription. It does not cover an installment offer, a refund, or a payment dispute. Reference + Worksheet: official Help Center pages checked October 30 and October 27, 2026. No subscription, enrollment, payment, refund, or access change was performed for this article.
Choose the result before choosing the control
End the subscription
Use the cancellation path. The documented boundary is just before the next expiration date; the resource is then removed automatically.
Do not promise immediate removal unless the actual subscription record supports it.
Remove one course enrollment
Use that course enrollment’s Dismiss action. The student remains in the Students list.
The revocation page does not establish that a subscription, charge, or refund changed.
Original decision map based on documentation; it is not a billing test or a systeme.io screenshot.
Ask three questions in order
- Should the recurring subscription end? If yes, treat cancellation as the primary task. Do not substitute an access-only action.
- Should access to only one course change while the subscription state stays separate? If yes, review that course enrollment’s Dismiss path and record the billing state independently.
- Is the request actually for a refund, installment-plan change, or payment dispute? Stop here. The two Help Center pages used for this guide do not complete those jobs.
Systeme.io’s cancellation article says installment offers do not use its subscription-cancellation path. Confirm the price-plan type before making a promise. “Monthly payments” is not enough evidence that an offer is a subscription.
Write the buyer-facing boundary
Subscription-ending note: “Your subscription is scheduled to end just before the next expiration date shown in the account. Course access is expected to be removed automatically at that boundary. I will keep the case open until the subscription and access records are checked.”
Access-only note: “Access to [course name] is being handled as a course-enrollment change. This message does not confirm a subscription cancellation, refund, or payment change.”
Replace the bracketed course name with the exact internal name before using the second note. Do not send either version until the learner’s request, price-plan type, and intended date agree.
Record both states before any action
Copy the subscription-and-access change note
Private learner or case reference: no public email address
Offer and exact course: internal names
Price-plan type: subscription / installment / one-time / Not checked
Next expiration date and timezone: account value / Not checked
Recurring subscription should end: yes / no / unclear
Course access should end: at expiration / one-course change / stay available / unclear
Refund or dispute requested: separate status / not requested / unclear
Chosen task: cancellation review / one-course Dismiss review / separate payment help / no change
Subscription result: actual state and source / Not tested
Course-access result: actual state and source / Not tested
Next action and owner: one concrete step
Keep names, email addresses, payment references, and private checkout links out of shared copies. This note coordinates two records; it is not proof of cancellation, a refund, or access removal.
Keep cancellation and revocation evidence separate
The official subscription-cancellation guide documents the end boundary and automatic resource removal. The separate course-revocation guide documents Dismiss for one enrollment. Neither page, by itself, proves a refund or resolves a disputed charge.
Not tested here: no live subscription or enrollment was opened. The exact interface, the account’s stored expiration timestamp, and the result after either action remain unverified until an authorized person checks that specific record.
Finish when the two records agree
You can finish without changing anything if the request or price-plan type is unclear. After an authorized action, close the case only when the subscription record and course-enrollment record match the promise. A success message from one menu is not evidence about the other record.
Planning when a new subscription should begin access? Use the first-payment access decision. If you have already decided on an access-only change and need to choose between Dismiss and deleting the entire student, use the one-course revocation versus student-deletion guide.
Official sources
How to cancel a subscription to systeme.io or an offer hosted on systeme.io (updated June 25, 2026; checked October 30, 2026) and How to revoke a student’s access to a course (updated May 29, 2026; checked October 27, 2026). No affiliate links.