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

# Customer Statements

See [Customer Statements ](/setup/configuration/statements.md)

<details>

<summary>Media</summary>

<img src="/files/J287xL4U1ozzJwqiLpzE" alt="" data-size="line">[Customer Statements](https://salesorder.wistia.com/medias/25tf5s1cp5)

</details>

### Customer Statement - need to know

Customer statements detail the Accounts Receivable (Sales Ledger) transactions in a period. You can bulk email Statements.

### Generating Customer Statements <a href="#w7m87dwbqw6" id="w7m87dwbqw6"></a>

You can generate individual Customer statements from:

* the Customer master Actions
* in bulk from the Customers List Actions.

In both cases there are two actions:

#### ‘Generate Statement(s)’ <a href="#l4xxkhqx3dkh" id="l4xxkhqx3dkh"></a>

This action produces statements that include all open invoices, all open credit notes, all unallocated funds (ie. unused payment), ordered by date with the oldest transaction first.

On the Customer Master, <mark style="color:orange;">Actions>Create Statement</mark>

On the Customer List, <mark style="color:orange;">Actions>Create Statement</mark>

#### ‘Generate Statement(s) for Period’ <a href="#id-9fu77iuu9hst" id="id-9fu77iuu9hst"></a>

This action allows the user to generate statements for a date range as per the existing functionality (ie. will include all transactions within the selected period).

On the Customer Master, <mark style="color:orange;">Actions>Create Statement for Period</mark>

On the Customer List, <mark style="color:orange;">Actions>Create Statement for Period</mark>

#### Find Customers and their respective Documents to include in statements <a href="#id-4cz53yokix06" id="id-4cz53yokix06"></a>

<mark style="color:orange;">Customers>Find</mark>

* with overdue invoices
* with unused payments
* With non-zero balance

OR

<mark style="color:orange;">Customers>Advanced Search tab</mark>

Now select the Customers you want to generate statements for, then use the relevant Action.

### Email Customer Statements <a href="#id-4f03b33rkxer" id="id-4f03b33rkxer"></a>

<mark style="color:orange;">Customers></mark>

Generate, Find or Search the Customer statement(s) you want to email.

Now select the Customers you want to generate statements for.

### Setup Customer Statement template <a href="#id-5yxscsfdzikr" id="id-5yxscsfdzikr"></a>

<mark style="color:orange;">Setup>Configuration>Sales>Customer Statement</mark>

### Print Customer Statements <a href="#pvel6tk3o4ho" id="pvel6tk3o4ho"></a>

<mark style="color:orange;">Customers></mark>

Generate, Find or Search the Customer statement(s) you want to print.

### Download Customer Statements as a .xlsx file <a href="#obv7uwhxbmsf" id="obv7uwhxbmsf"></a>

<mark style="color:orange;">Customers></mark>

Generate, Find or Search the Customer statement(s) you want to download.


---

# 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://helpwith.salesorder.com/sales/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.