> 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-masters/fiscal-year-closing-selective-ledger.md).
# Fiscal Year Closing- Selective Ledger
The **Fiscal Year Closing – Selective Ledger** option allows users to close and carry forward only specific ledger accounts during the fiscal year-end process, while leaving other ledger accounts open.
## Steps to Process Fiscal Year Closing for a Selective Ledger
Step 1: Navigate to the **General Ledger** module.
1. Click **Masters 1** from the menu.
2. Select the **Fiscal Year Closing -Selective Ledger** option.
* The Fiscal Year Closing - Selective ledger screen will be displayed.
Step 2: Select the required **Group** from the drop-down list.
* The system will display the ledgers associated with the selected group.
Step 3: Click the **Search** icon and select the **Ledger Account** that needs to be closed.
Step 4: Enter a **Narration** describing the purpose of the selective ledger closing.
Step 5: Review the selected group, ledger, and narration.
1. Click the **Proceed** button.
* The system will process the closing for the selected ledger.
---
# 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-masters/fiscal-year-closing-selective-ledger.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.
.png?alt=media)
