> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/store-manager/manage-accounts-receivable/printing-or-emailing-statements.md).

# Print or email statements

This topic describes how to print or email statements for AR accounts after you close the billing cycle.

{% hint style="info" %}
Before you can email statements you must set up SMTP in Store Administrator. You can set up SMTP under **Configuration** | **SMTP**. You must also enter an e-mail address for the AR account in Store Manager under **Setup** | **Account** | **Communication**. It is possible to set up SMTP for most Microsoft email services (for example, outlook.com or 365office.com) but at this time it is not possible to set up SMTP for other email services like gmail.com. Always test the SMTP set up in Store Administrator to ensure emails can be sent and received.
{% endhint %}

Store Manager does not automatically print or email statements after you close the billing cycle. Instead, you have to manually print or email the statements for your AR accounts.

1. Click **Customer**.
2. Click **Print Statements**.
3. Select the **Closing Date** that you selected when you closed the billing cycle.
4. From **Delivery Method**, select **Print** or **E-Mail**.
5. From **Filter**, select **Standard** or **Advanced**.
6. Do one of the following:

* If you selected **Standard**, select the account group(s) for which you want to print or email statements.
* If you selected **Advanced**, enter filter criteria to select the AR accounts for which you want to print or email statements.

7. Click **Finish**.
8. If you are printing statements, enter a file name and select the location where you want to save the file.
9. Click **OK** to confirm the statements were printed or emailed.


---

# 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://docs.rmhpos.com/store-manager/manage-accounts-receivable/printing-or-emailing-statements.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.
