> 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/analysis-code.md).
# Analysis Code
An **Analysis Code** is a predefined classification used in an accounting or financial system to categorise transactions for detailed tracking, reporting, and analysis beyond the standard general ledger structure.It allows organisations to analyse financial data based on specific business dimensions such as department, project, cost center, location, activity and Business Unit.
## Steps to Create an Analysis Code
Step 1: Navigate to the **General Ledger** module.
1. Click **Masters 1** from the menu.
2. Select **Analysis Code** from the list.
* The Analysis Code screen will be displayed.
Step 2: Click the **Open** button.
* The system will display the list of analysis codes.
Step 3: Click the **Add** button available on the screen.
Provide the required information:
1. **Code -** Enter a unique code that will identify the analysis category.
2. **Description -** Enter a meaningful description that clearly defines the purpose of the analysis code.
Step 4: Verify that the code and description are correct.
1. Click the **Save** button.
* The Analysis Code will be created and made available for use within the system.
---
# 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/analysis-code.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.
