> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/v2.8/products/modules/mcollect-mcs/mcollect-master-data-templates/service-sub-category-gl-code-mapping.md).

# Service Sub Category GL Code Mapping

## Introduction <a href="#introduction" id="introduction"></a>

Service Subcategory is mapped to relevant GL code to help capture the accounting-related parameters for each service subcategory. The same is used to pass the accounting vouchers into the accounting and finance system.

## Data Table <a href="#data-table" id="data-table"></a>

| Sr.No | Service Subcategory Code\* | Service Subcategory (English)\* | Service Subcategory (Local Language)\* | GLCODE\* | ULB CODE | DEPT CODE | FUND Code |
| ----- | -------------------------- | ------------------------------- | -------------------------------------- | -------- | -------- | --------- | --------- |
| 1     | PEF0478                    | Parks Entry Fee                 | पार्क प्रवेश शुल्क                     | 1404007  | 1001     | DEPT\_1   | 01        |
| 2     | SANT0045                   | Sanitation Tax                  | स्वच्छता कर                            | 1405010  | 1002     | DEPT\_2   | 01        |

The data given in the table above is sample data.

## Procedure <a href="#procedure" id="procedure"></a>

### Data Definition <a href="#data-definition" id="data-definition"></a>

| Sr. No. | Column Name                          | Data Type    | Data Size | Is Mandatory? | Definition/ Description                                                                                                                                                                                                                                                                                                               |
| ------- | ------------------------------------ | ------------ | --------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1       | Service Category                     | Text         | 250       | Yes           | The type of category which is to be mapped with the relevant service subcategory. Click[ here](/local-governance/v2.8/products/modules/mcollect-mcs/mcollect-master-data-templates/service-category.md) for Service category reference                                                                                                |
| 2       | Service Subcategory (English)        | Text         | 250       | Yes           | Name of “Service Sub-category” in English. This will help the user to select the Subcategory name while doing the collection. Click[ here](/local-governance/v2.8/products/modules/mcollect-mcs/mcollect-master-data-templates/service-sub-category.md) for Service Subcategory reference                                             |
| 3       | Service Subcategory (local Language) | Text         | 250       | Yes           | Name of “Service Sub-category” in Local Language. This will help the user to select the Subcategory name while doing the collection                                                                                                                                                                                                   |
| 4       | GLCODE                               | Alphanumeric | 50        | Yes           | General Ledger Code (GL Code) is a string of alphanumeric characters assigned to each Service. Click [here](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/finance-data/sub-ledger-category) for the General Ledger Code Reference                                                             |
| 5       | ULB CODE                             | Alphanumeric | 50        | No            | The CODE which is specified and assigned to each ULB. It refers to the [department](https://docs.digit.org/configure-digit/configuring-master-data-templates/environment-setup/state-level-setup/ulb-departments)​                                                                                                                    |
| 6       | DEPT CODE                            | Alphanumeric | 50        | No            | The Master Department Code linked to the“Service Category” at the State Level. The Department Code can be ascertained from the ULB Departments master. Click [here](https://docs.digit.org/configure-digit/configuring-master-data-templates/environment-setup/state-level-setup/ulb-departments) to learn more about ULB Departments |
| 7       | FUND Code                            | Text         | 250       | No            | The type of fund allocated/associated with the respective service subcategory. Click[ here](/local-governance/v2.8/products/modules/finance/finance-master-data-templates/funds.md) for Fund reference                                                                                                                                |

### Steps to Fill Data <a href="#steps-to-fill-data" id="steps-to-fill-data"></a>

1. Download the data template attached to this page.
2. Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.
3. Make sure all the headers, its data type, field size and its definition/ description is understood properly. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
4. Identify all different types of service subcategory GL code on the basis of ULB’s functions.
5. Start filling the data starting from serial no. and complete a record at once. repeat this exercise until the entire data is filled into a template.
6. Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.

## Checklist <a href="#checklist" id="checklist"></a>

The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.

### Common Checklist <a href="#common-checklist" id="common-checklist"></a>

This checklist covers all the activities which are common across the entities.

| Sr. No | Checklist Parameter                                                               | Example                                                                                                                      |
| ------ | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| 1      | Make sure that each and every point in this reference list has been taken care of | ​[Checklist](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist)​ |

### Entity Specific Checklist <a href="#entity-specific-checklist" id="entity-specific-checklist"></a>

This checklist covers the activities which are specific to the entity. There is no entity-specific checklist activity applicable.

## Attachments <a href="#attachments" id="attachments"></a>

{% file src="/files/J83hNGrgPGEeXy3A12Zr" %}

{% file src="/files/N9mZmQqn1TDUYZ9ZX3XF" %}

[![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)](http://creativecommons.org/licenses/by/4.0/)All content on this page by [eGov Foundation ](https://egov.org.in/)is licensed under a [Creative Commons Attribution 4.0 International License](http://creativecommons.org/licenses/by/4.0/).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.digit.org/local-governance/v2.8/products/modules/mcollect-mcs/mcollect-master-data-templates/service-sub-category-gl-code-mapping.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
