> 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/bill-passing/material-gl-posting/product-subgroup-cost-center-gl-link.md).
# Product SubGroup Cost Center GL Link
**Product SubGroup Cost Center GL Link** is a configuration that maps each product sub-group to a specific **Cost Center** and corresponding **General Ledger (GL) accounts**. This ensures that all transactions related to the product sub-group are posted correctly to the assigned cost center and GL accounts, enabling accurate financial tracking, cost allocation, and reporting.
## Steps to Configure Product SubGroup Cost Center GL Link
Step 1: Navigate to the **Material GL Posting** menu in the **Bill Passing** module.
1. Click on **Product Sub Group Cost Center GL Link**.
* The configuration screen will be displayed.
Step 2: Click the **Open** button.
1. Select the required product sub-group from the list.
* Once the product sub-group is selected, the system will display the assigned **Cost Center** and linked **General Ledger (GL) accounts.**
Step 3: After confirming the ledger linking details, verify that all information is correct.
1. Click the **Save** button.
* The Product SubGroup will be successfully linked with the selected Cost Center and GL accounts.
---
# 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/bill-passing/material-gl-posting/product-subgroup-cost-center-gl-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.
