> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/revenue/subscriptions/subscription-billing-status-and-activating-pausing-or-canceling.md).

# Subscription billing, status, and activating, pausing, or canceling

A subscription moves through statuses: Draft, Scheduled (saved with a future start date - stored as not\_started), Active (billing on schedule), Paused, Canceled, and Complete. A draft subscription is started with Activate Subscription.

Activation requires an email address for the recipient under **Contact > To**. If the selected contact has no email, the error message names the contact and explains how to continue: add an email to that contact, or choose another recipient with an email address, then Save and try Activate Subscription again. Creating a subscription from a contact's page can prefill that contact, so a name in To does not necessarily mean an email is on file.

If a Draft sits past its start date, reopening or refreshing it moves the schedule shown in Duration forward: the start date moves to today, and a fixed end date moves with it so the subscription keeps the same length (for example, a draft that ran one month still runs one month). You can choose today or a future start date, but not a past date. Review and Save the updated schedule before activating. Essential only does this while the subscription is a Draft; it does not move a live subscription's dates.

Once active, the action menu offers Pause Subscription (stops generating invoices until resumed), Resume Subscription, and Cancel Subscription (stops future billing for good; existing invoices remain due).

Each cycle it bills the recurring total either by automatically charging a saved payment method or by emailing the invoice to the customer to pay, depending on its type. The next invoice date - shown as Next invoice on in the header and Next invoice send date in the settings - is only meaningful while the subscription is active or scheduled; a paused, canceled, or completed subscription has no upcoming invoice.

Use the subscription's own controls for status changes. The Essential Assistant can read and explain a subscription, but it does not activate, pause, resume, or cancel it for you.

> **Where to find it:** On the open subscription, the Activate / Pause / Resume / Cancel controls in the action bar at the top

## Related guides

* [Do I need Stripe for recurring invoices?](/revenue/subscriptions/do-i-need-stripe-for-recurring-invoices.md)
* [A subscription's generated invoices and metrics](/revenue/subscriptions/a-subscriptions-generated-invoices-and-metrics.md)
* [Auto-charge vs manual billing on a subscription](/revenue/subscriptions/auto-charge-vs-manual-billing-on-a-subscription.md)
* [Create a subscription for recurring invoices](/revenue/subscriptions/create-a-subscription-for-recurring-invoices.md)
* [See and browse your subscriptions (the Subscriptions page)](/revenue/subscriptions/see-and-browse-your-subscriptions-the-subscriptions-page.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.withessential.com/revenue/subscriptions/subscription-billing-status-and-activating-pausing-or-canceling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.