> 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/closing-the-billing-cycle.md).

# Close the billing cycle

This topic describes two methods for closing the billing cycle for AR accounts. You must close the billing cycle before you print or email statements.

Store Manager does not automatically close the billing cycle on the closing date. Instead, you have to manually close the billing cycle for your AR accounts on or after the closing date.

1. Click **Customer**.
2. Click **Close Billing Cycle**.
3. Select the **Closing Date**.

{% hint style="info" %}
If you select the 26th of the month, Store Manager will include all ledger entries up to and including the 25th. If you select the 1st of the month, Store Manager will include all ledger entries up to and including the 30th/31st of the previous month.
{% endhint %}

4. Enter a **Reference**, if desired.
5. From **Filter**, select **Standard** or **Advanced**.
6. Click **Next**.
7. From **Selection Type**, select one of the following:

* **ACCGROUP:** Close the billing cycle for the selected account groups. Select the account groups from the list.
* **Advanced Filter:** Use the filter to close the billing cycle for filtered AR accounts. Click **Define** to display the **Filter** dialog.

8. Cick **Finish**. Click **OK** to confirm the billing cycle has been closed for the selected AR accounts.


---

# 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/closing-the-billing-cycle.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.
