> 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/store-day-closure.md).

# Store Day Closure

**Store Day Closure** is the process of closing and finalising all inventory transactions for a specific day. This procedure ensures that all stock movements, receipts, issues, transfers, and adjustments for the day have been recorded and verified before the next business day begins.

## Steps to Perform Store Day Closure

Step 1: Navigate to **Transactions** in the **Inventory** module.

1. Select **Store Day Closure**.

* The Store Day Closure screen will be displayed.

Step 2: Select the date for which the day closure needs to be performed.

1. Verify that the selected date is correct and that all transactions for that day have been completed.

Step 3: Click the **Save** button.

* The system will process the day-end closure and finalise all inventory transactions for the selected date.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-7989dbfba656de2171ca27be11d141a465caab27%2Fb5%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/store-day-closure.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.
