> 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/do-i-need-stripe-for-recurring-invoices.md).

# Do I need Stripe for recurring invoices?

Recurring invoices in Essential are subscriptions. Stripe is required for automatic charging, but it is not required for every recurring invoice workflow.

Without Stripe, you can use manual subscription billing: Essential generates invoices on the recurring schedule and either emails them or, for customers who don't use email, files a Print and Mail task so your team posts them; the customer pays outside auto-charge. If your business has Stripe connected, you can choose automatic charging when a saved payment method is available.

Connect Stripe under Settings -> Invoicing if you want auto-charge. If Stripe is not connected or not available for your business, use the manual billing option.

> **Where to find it:** On a subscription, Activate Subscription; connect Stripe in Settings -> Invoicing

## Related guides

* [Auto-charge vs manual billing on a subscription](/revenue/subscriptions/auto-charge-vs-manual-billing-on-a-subscription.md)
* [A subscription's generated invoices and metrics](/revenue/subscriptions/a-subscriptions-generated-invoices-and-metrics.md)
* [See and browse your subscriptions (the Subscriptions page)](/revenue/subscriptions/see-and-browse-your-subscriptions-the-subscriptions-page.md)
* [Subscription billing, status, and activating, pausing, or canceling](/revenue/subscriptions/subscription-billing-status-and-activating-pausing-or-canceling.md)
* [What the subscription page shows](/revenue/subscriptions/what-the-subscription-page-shows.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/do-i-need-stripe-for-recurring-invoices.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.