> 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/general-ledger/general-ledger-module/gl-transaction/fiscal-period-closing.md).
# Fiscal Period Closing
**Period Closing** is a control mechanism used to close a specific accounting period (month) and prevent further transactions from being entered, modified, or deleted for that period.
Once a period is closed, users cannot create, edit, or post transactions within the selected month. This helps maintain the integrity of financial records and ensures that finalised accounting data remains unchanged.
## Steps for Period Closing
Step 1: Navigate to the General Ledger module.
1. Click Transaction from the menu.
2. Select **Period Closing** option.
* The Period Closing screen is displayed
Step 2: Click the **Open** button.
* Review the list of available months displayed on the screen.
Step 3: Select the month that need to be closed.
* Carefully review the selected month(s) before closing, as this action restricts transaction processing for the chosen period.
Step 4: Click the **Save** button.
* The selected month(s) are successfully closed.
---
# 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/general-ledger/general-ledger-module/gl-transaction/fiscal-period-closing.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.
