> 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/auto-charge-vs-manual-billing-on-a-subscription.md).

# Auto-charge vs manual billing on a subscription

Each subscription bills one of three ways, chosen in the Payment section of its settings. Automatic charges a saved payment method on file every billing period - "Automatically charge a payment method on file" - so the customer doesn't have to do anything.

When you pick it, you select which of the customer's cards or bank accounts to charge, and you can add a new payment method right there. If the type is automatic but no payment method is selected, the subscription can't be saved.

Manual instead emails the invoice and a PDF copy to the customer each period for them to pay themselves, and lets you write a custom message that goes out with it. The automatic option is only offered when your business has a verified Stripe connection with a payment provider set up - auto-charging literally needs Stripe to move the money.

If your business doesn't have that (for example, in a region Stripe doesn't serve), the automatic choice isn't shown at all: you choose between emailing the invoice and printing and mailing it.

## Print and mail the invoice

Some customers don't use email. Pick "Create task to print and mail invoice to customer" and Essential sends nothing. Each billing period it still creates the invoice as usual, and it adds a task to the Invoices › Print and Mail folder on the Tasks page so your team knows an invoice is waiting to be printed and posted. Open the task, use Open Invoice to Print to print or download the invoice from its page, put it in the mail, and mark the task complete.

To print several waiting invoices in one job, select their tasks in **Tasks → Invoices → Print and Mail** and click **Print Invoices**. See [Print several invoices together](/field-operations/tasks/what-creates-invoices-tasks.md#print-several-invoices-together).

A print-and-mail subscription needs no email recipient, so the Contact section is hidden. The printed invoice still carries the online payment link, so the customer can pay online or by check as usual. Switching an existing subscription to print and mail stops future emails; invoices already emailed are unaffected.

So subscriptions work any of these ways, but unattended auto-charge specifically depends on a verified Stripe connection.

> **Where to find it:** On the subscription page, open the settings panel below the invoice template and find the Payment section, where you choose between automatic charging, emailing the invoice to pay manually, and printing and mailing it.

## 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)
* [See and browse your subscriptions (the Subscriptions page)](/revenue/subscriptions/see-and-browse-your-subscriptions-the-subscriptions-page.md)
* [What the subscription page shows](/revenue/subscriptions/what-the-subscription-page-shows.md)
* [Create a subscription for recurring invoices](/revenue/subscriptions/create-a-subscription-for-recurring-invoices.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/auto-charge-vs-manual-billing-on-a-subscription.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.