> 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/faq-on-material/how-to-finalize-your-physical-inventory-reconciliation-and-open-up-the-system-for-next-months.md).

# How to finalize your physical inventory reconciliation and open up the system for next month's ?

To perform a Store Month Closure after completing your Physical Inventory Reconciliation, follow these steps:

1. Navigate to Transaction > Store Month Closure.
2. Select the Store. *(The last month will load automatically.)*
3. Click the Close Month button.

Important Details:

* Purpose: This process confirms your final closing stock on the last day of the month and finalizes operations for that period.
* Unlocking Next Month: Completing the Store Month Close is necessary based on your system settings to start recording transactions for the upcoming month.
* Applicability: Based on system settings, this closure applies to all store types, including perishables, circulating, and stock-able items


---

# 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/faq-on-material/how-to-finalize-your-physical-inventory-reconciliation-and-open-up-the-system-for-next-months.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.