> 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/masters-2/revenue-group-analysis-code-link.md).
# Revenue Group-Analysis Code Link
The **Revenue Group – Analysis Code Link** module is used to define and manage the relationship between a revenue group and its corresponding analysis codes.
This linkage enables structured classification of revenue transactions, ensuring accurate financial reporting and detailed analysis across different dimensions such as department, project, cost center, or business activity.
## Steps to Configure Revenue Group – Analysis Code Link
Step 1: Navigate to the **General Ledger** module.
1. Click **Masters 2** from the menu.
2. Select the **Revenue Group-Analysis Code Link** option.
* The Revenue Group-Analysis Code Link screen will be displayed.
Step 2: Choose the required **Revenue Main Group** from the list.
* The selected revenue group will be displayed for mapping.
Step 3: After selecting the revenue group, the available **Analysis Codes** will be displayed.
* Select the required analysis code(s) that need to be linked with the revenue group.
Step 4: Review the selected revenue group and linked analysis codes.
1. Click the **Save** button.
* The system will save the linkage between the revenue group and the analysis code.
---
# 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/masters-2/revenue-group-analysis-code-link.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.
