> 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/configure-pos-and-store-manager/accounts-receivable/setting-up-email-message.md).

# Email message

This topic describes how to configure a default email message for emailed AR account billing statements.

When you generate statements, you have the option of automatically emailing the statements to account holders. Use the email message set up screen to define the subject, body text, and signature of the emails that Store Manager sends.

{% 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 **Customer** | **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 %}

1. Click **Setup**.
2. Expand **Customer**.
3. Expand **Accounts Receivable**.
4. Click **Email Message**.
5. Edit the email subject, body, and signature.

{% hint style="info" %}
In the Subject, `<ClosingDate>` is a variable that pulls in the Closing Date that you used when you closed the billing cycle.
{% endhint %}

5. Click **OK** to save your changes.
6. Click **OK** to confirm.


---

# 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/configure-pos-and-store-manager/accounts-receivable/setting-up-email-message.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.
