> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/material-management/material-management-module/mm-transactions/mm-transactions-store-month-closure.md).
# Store Month Closure
Steps to perform Store Month Closure
**Store Month Closure** is the process of officially closing inventory transactions for a particular month after completing the physical inventory verification and stock reconciliation.
## Steps to Perform Store Month Closure
Step 1: Navigate to **Transactions** in the **Inventory** module.
1. Select **Store Month Closure**.
* The Store Month Closure screen will be displayed.
Step 2: Click on the **Store** field.
1. Select the store that needs to be closed for the month.
* The system will automatically load the most recent open month available for closure.
Step 3: Review the month displayed by the system.
1. Ensure that all transactions for the selected month have been completed and verified.
2. Confirm that physical inventory reconciliation has been performed successfully.
Step 4: Click the **Close Month** button.
1. The system will process the month-end closure for the selected store.
---
# 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://help.rbsgo.com/material-management/material-management-module/mm-transactions/mm-transactions-store-month-closure.md?ask=&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.
