> 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/invoices/send-statements-to-several-customers.md).

# Send statements to several customers

Review and send statements for several customers in one workflow. Each recipient receives a separate email with a PDF and secure link.

> **Where to find it:** Invoices → By customer → Send statements, or Invoices → All invoices → Bulk Actions → Send statements.

**By customer** groups previously sent open invoices into one row per customer. Review total and past-due balances, aging, invoice count and the last sent statement. Search customers, sort columns, or filter by past-due balance, minimum balance and aging. Select customers across pages, then select **Send statements** to review their recipients. Pending payments remain in the balances until confirmed.

1. Choose up to 50 customers. The header checkbox selects matching customers across pages; clearing it preserves selections outside the current search. A single customer is selected automatically.
2. Select **Open invoices** or **Account activity** and its date range. Open statements can be limited to past-due invoices.
3. Choose recipients directly beside each selected customer. Defaults are prefilled; after a successful manual or bulk send, those recipients are remembered for that billing profile. Add or remove addresses, then select **Review recipients**.
4. Review each customer, billing profile, recipient, brand, invoice count, and balance. Each selected row is one email. Clear any rows you do not want to send. A single eligible row is selected automatically, with no search or checkbox. Newly entered recipients require confirmation of the property access shown.
5. For skipped customers, use **Recipients & preferences** to update their statement recipients, then review again.
6. Select **Send statements**. The button includes the number selected, up to 100 emails per submission.
7. Review delivery results before closing. Each saved statement is also available in the customer's statement history.

Remembered recipients do not change automatic-statement preferences. Recipient access is checked again for each send.

Statements remain separate by customer, billing profile and brand. Invoices are not resent, and sending a statement does not collect a payment. Recipient defaults and automatic-statement opt-outs are managed in [statement settings and customer preferences](/revenue/invoices/configure-and-automate-statements.md).

Statement options load your current saved defaults before **Review recipients** becomes available. If settings cannot load, select **Retry**. Hover or focus the underlined selection count or review heading for delivery details.

If a connection fails, retrying the same submission preserves confirmed sends. Check History before starting a fresh submission, especially when delivery is shown as unconfirmed.


---

# 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/invoices/send-statements-to-several-customers.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.