> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/bevica-select/faqs/email-customer-statements.md).

# Email customer statements

Run customer statements and email them to one or more customers.

Statements are a core credit-control tool. Emailing them from Business Central keeps the process consistent.

### Before you start

1. Confirm the customer is set up to receive statements.
   * On the **Customer Card**, check **Print Statements**.
2. Confirm a statement email address exists.
   * See **Document Layouts** guidance in [Customer and Vendor Facing Outputs](/documentation/guides/setup-and-configuration/importing_customer-_vendor_and_item_data-1.md).

### Send a statement for one customer

1. Open the **Customer Card**.
2. Select **Report**, **Statement**.
3. Set the statement options including the customer filter.
4. Set **Report Output** to **Email**.
5. Select **OK**.

### Send statements in bulk

1. From **Customer List**, select **Report**, **Statement**.
2. Set the statement options and use filters (for example, `Print Statements` = Yes).
3. Set **Report Output** to **Email** and optionally tick to print remaining statements.
4. Select **OK**.

#### Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

* Check **Email Outbox** for stuck messages.
* Check **Sent Emails** for confirmation.
* You can re-send an emailed statement from **Sent Emails**.
* If the wrong layout is used, check **Report Selections** and **Document Layouts**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.bevica.com/bevica-select/faqs/email-customer-statements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.