DIGIT Urban
PlatformDomainsAcademyDesign SystemFeedback
v2.0
v2.0
  • What Is DIGIT Urban?
  • DIGIT Urban Architecture
  • Product & Modules
    • Brochures
    • User Manuals
      • Logging Into DIGIT
      • mCollect
        • Citizen User Manual
        • Employee User Manual
      • Trade License
        • Citizen User Manual
        • Employee User Manual
      • Public Grievance & Redressal
        • Citizen User Manual
        • Employee User Manual
        • Complaint Types List
      • Property Tax
        • Citizen User Manual
        • Employee User Manual
    • Services Overview
      • Core Services
        • Workflow Services
        • Location Services
        • User Services
        • Access Control Services
        • PDF Generation Service
        • MDMS (Master Data Management Service)
        • Payment Gateway Service
      • Business Service
      • Municipal Service
        • PGR Services
        • Trade-License Service
      • Utilities
    • Release Notes DIGIT 2.0
      • BPA Release Notes
      • Trade License Release Notes
      • Property Tax Release Notes
      • PGR Release Notes
      • Water & Sewerage Release Notes
      • Advance Payments Release Notes
      • Configuration Changes
    • DIGIT Roadmap
    • Product FAQs
    • Quality Assurance
  • Configure DIGIT
    • Git Repos
    • Setting up DIGIT
      • Configuring InfraOps
      • Setting up DIGIT Environment
      • Email And SMS Setup
      • FileStore Setup
      • Setting Up SSL Certificate
      • Periodic Log Cleanup
    • Setting up Master Data
      • MDMS Overview
      • Configuring Master Data
      • Adding New Master
      • Configuring Tenants
      • State Level Vs City Level Master
    • Master Data Collection Templates
      • Environment Setup
        • State Level Setup
          • Tenants Information
          • SMS Account Configuration
          • Email Account Configuration
          • Google Play Store Account
          • Payment Gateway Configuration
          • POS Integration Configuration
          • Domain Name Configuration
          • SSL Configuration
          • ULB Departments
          • ULB Designations
          • Localization
          • Google Map Configuration
        • ULB Level Setup
          • Boundary Hierarchies
          • Boundary Data
          • Cross Hierarchy Mapping
          • ULB Bank Accounts
      • Module Setup
        • Trade Licenses Templates
          • Trade Category
          • Trade Type
          • Trade Sub Type
          • Trade License Fee
          • Trade License Documents Attachment
          • Structure Type
          • Structure Sub Type
        • Property Tax Data Templates
          • Road Type
          • Construction Type
          • Property Type
          • Property Sub Type
          • Usage Category Major
          • Usage Category Minor
          • Usage Category Sub Minor
          • Usage Category Detail
          • Ownership Category
          • Ownership Sub Category
          • Owner Special Category
          • Special Category Documents
          • Unit Rates
          • Tax Rates
          • Interest Rates
          • Penalty Rates
          • Rebate Rates
          • Mutation Fee
        • PGR Data Templates
          • Grievance Type
          • Grievance Sub Type
          • Routing Matrix
          • Escalation Matrix
        • Fire NOC Data Templates
          • Building Usage Type
          • Building Sub Usage Type
          • Fire Station Master
          • Areas Served Master
          • Fire Station Mapping
          • Fire NOC Fee
        • mCollect Data Templates
          • Service Category
          • Service Sub Category
          • Service Sub Category GL Code Mapping
        • Web Portals Templates
          • State Portal
          • ULB Portal
        • OBPAS Data Templates
          • List Of Services
          • Service-Wise Documents
          • Building Occupancy
          • Building Sub Occupancy
          • Building Usage
          • Inspection Checklist
          • Stakeholders Type
          • Town Planning Schemes
          • NOC Departments
          • Fee Structure
          • eDCR Drawing
        • HRMS Data Templates
          • User Roles
          • System Users
        • Finance Data Templates
          • Chart Of Accounts
          • Funds
          • Functions
          • Contractors
          • Suppliers
          • Schemes
          • Sub Schemes
          • Bank
          • Bank Branch
          • Bank Account
          • Deductions
          • Opening Balances
          • Sub Ledger Category
          • Sub Ledger Master
        • Water Charges Data Templates
          • Pipe Size Types
          • Water Source Types
          • Water Rates (Metered)
          • Water Rates (Non-Metered)
          • Water Penalty Rates
          • Water Interest Rates
        • Sewerage Charges Data Templates
          • Sewerage Rates
          • Sewerage Penalty Rates
          • Sewerage Interest Rates
        • Billing And Payments Data Templates
          • Tax Heads
          • Receipt Format
          • Demand Bill Format
        • DSS Data Templates
          • KPI Acceptance
        • Workflow Data Templates
          • Workflow Actions
          • Workflow Levels
          • Workflow Process
          • Workflow Notifications
        • Common Configuration Details
          • Standard Document List
          • Service Document Mapping
          • Checklist
          • Configuring Data FAQs
    • Configuring Workflows
      • Setting Up Workflows
      • Configuring Workflows For An Entity
    • Configuring Services
      • API Dos and Don'ts
      • Setting Up Service Locally
      • Configuring New Reports
        • Types Of Reports Used In Report Service
      • Customizing PDF Notices And Certificates
    • Setting up a Language
      • Adding New Language
      • Setting Up Default Language For SMS & Emails
    • Configuring Localization
      • Setup Base Product Localization
      • Configure SMS and Email
    • Setting Up SMS Gateway
      • Using The Generic GET & POST SMS Gateway Interface
    • Configuration FAQs
    • Setting Up eDCR Service
    • Adding Roles To System
    • Mapping Roles With APIs
    • Setting Up Finance Service
    • Adding New APIs For Access
  • Customize DIGIT
    • Frontend/UI
    • DIGIT Customization
      • API Do's & Don'ts
      • Writing A New Customer
    • Services
      • Core Services
      • Business Services
      • Municipal Services
      • Infra Services
    • Master & Configuration data load kit
    • Data Migration
      • Data Migration Principles
      • Data Templates
      • Data Migration Kit
  • Deployment Tools
    • Setup DIGIT
      • Infra Requirements
      • Why Kubernetes for DIGIT
      • Supported Clouds
        • Google Cloud
        • Azure
        • AWS
        • VSphere
        • SDC
        • NIC
      • Infra Sizing
      • Infra Best Practices
      • Deployment Architecture
      • Deploy DIGIT
        • Routing Traffic
        • Backbone Deployment
    • Skills Needed
    • Resource Requests & Limits
    • Readiness & Liveness
    • Troubleshooting
      • Distributed Tracing
      • Logging
      • Monitoring & Alerts
    • CI/CD
    • Security Practices
  • DIGIT Training Materials
    • Training Calendar
    • Training Videos
  • DIGIT Support
    • eGov Enablement Support for DIGIT
    • Troubleshooting Guides
Powered by GitBook

​All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page
  • Introduction
  • Data Table
  • Procedure
  • Data Definition
  • Steps to fill data
  • Checklist
  • Common Checklist
  • Entity Specific Checklist
  • Attachments

Was this helpful?

Edit on Git
Export as PDF
  1. Configure DIGIT
  2. Master Data Collection Templates
  3. Module Setup
  4. Finance Data Templates

Chart Of Accounts

PreviousFinance Data TemplatesNextFunds

Last updated 4 years ago

Was this helpful?

Introduction

A chart of Accounts (COA) is a listing of the Ledger codes that a State or ULB’s has identified and made available for recording transactions in its general ledger. COA is a standard data which need to be set up as per the National Municipal Accounting Manual or Respective State-wise manual. Click for NMAM manual. The COA definition can consist of 3 or 4 levels of hierarchy. Ex: Major->Minor->Detailed (3 levels) or Major->Minor->Sub Minor->Detailed (4 Levels). It is up to the state to define the levels required depending on the reporting needs. Detailed code is the node or the level at which the transaction is done.

Data Table

Sr. No*

Major Code*

Major head Description*

Minor Code*

Minor Head Description*

SubMinor Code

SubMinor Head Description

Detailed Heads (Ledgers)*

Ledger Code*

Type

Account Detail Type

Function Required

Budget Required

1

110

Tax Revenue

110-01

Property Tax

110-01-01

Property Tax - General Tax

Property Tax - General Tax - Residential

110-01-01-01

Income

Yes/No

Yes/No

2

210

Establishment Expenses

210-10

Salaries and Wages

Basic Pay

210-10-01

Expenses

Yes/No

Yes/No

3

350

Other Liabilities

350-11

Employee Liabilities

Salaries Unpaid

350-11-01

Liabilities

Drawing Officer

Yes/No

Yes/No

4

410

Fixed Assets

410-20

Buildings

Office Building

410-20-02

Assets

Yes/No

Yes/No

Data given in the table is a sample data.

Procedure

Data Definition

Sr No

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

1

Major Code

Alphanumeric

50

Yes

The Major Code can be any number of digits, (though NMAM suggest the first 3 digits) of the GL Code to be the Major code, this will help in collating the reports at the Nation level

2

Major head Description

Text

250

Yes

The short name given to the Major code to easily identify the Account Name for individual code

3

Minor Code

Alphanumeric

50

Yes

The Minor Code can be any number of digits, the digits are configurable. The Minor code will help in collating the reports at the State level. Also, the State has the flexibility to define the minor codes

4

Minor Head Description

Text

250

Yes

The short name given to the Minor code to easily identify the Account Name for individual code

5

SubMinor Code

Alphanumeric

50

No

The SubMinor Code can be optional, State/ULB can set up a sub minor level code based on their requirement, this would help in facilitating the additional level of reporting and also detail transaction-level information (The SubMinor code is not listed in NMAM manual)

6

SubMinor Head Description

Text

250

No

The short name given to the SubMinor code to easily identify the Account Name for individual code

7

Detailed Heads (Ledgers)

Text

250

Yes

The short name for the Ledger Code, wherein users use this account head name while posting the transactions into the system

8

Ledger Code

Alphanumeric

50

Yes

A General Ledger Code (GL Code) is a string of 7 to 9 digit numeric characters assigned to each financial entry in a State/ULB ledger. A GL Code can be assigned to different debit or credit entries to make accounting transactions

9

Type

Text

250

No

The Type indicates the Income, Expenses, Liabilities and Assets which are mapped to each individual GL code. User can easily identify the GL code by this mapping

10

Account Detail Type

Text

250

No

The account details type is the subsidiary ledger, The Suppliers, Contractors and Employees are standard subsidiary ledger. This will help the user to identify the subsidiary ledger details while processing any bill transaction in the system

11

Function Required

Text

250

No

A GL Code can be linked for the validation of the Function, the user while posting a transaction can select a particular function to which transaction will be linked and this will facilitate easy Function wise reporting

12

Budget Required

Text

250

No

A GL Code can be linked for the validation of a Budget. User can have a validation check while posting a transaction into the system, this will facilitate to track the amount usage

Steps to fill data

  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. 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.

  5. Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.

Checklist

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

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

Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

Sr. No.

Checklist Parameter

Example

1

The Major, Minor and Sub minor Description Name should not contain any special characters

Tax Revenue : [Allowed]

#Tax Revenue! : [Not allowed]

2

The Ledger Codes that are defined by the state team should be alphanumeric and Unique

110-01-01-01

Attachments

here
Checklist
31KB
configuration-data-template-chart-of-account.xlsx
Configuration Data Template
25KB
sample-confugration-data-chart-of-account.xlsx
Sample Data