Chart of Accounts
The Chart of Accounts (CoA) is the foundation of all financial activity in JobNext. It defines the hierarchical structure of account groups and ledgers that are used to record every financial transaction. Before any vouchers can be created, bills registered, or payments processed, the Chart of Accounts must be properly configured.
Access the Chart of Accounts from Finance > Chart of Accounts. The screen displays the full account hierarchy in a tree view, allowing you to expand groups and view their child ledgers.
Account Code Hierarchy
Hierarchical Structure
Accounts in JobNext are organized into a two-level hierarchy consisting of Groups and Ledgers. This structure ensures that accounts are logically categorized and easy to navigate, even in large organizations with hundreds of ledger accounts.
Groups
Groups are container nodes that serve as categories for organizing ledger accounts. They do not hold transactions directly; instead, they aggregate the balances of all ledgers beneath them. Groups can also contain other sub-groups, allowing for multi-level categorization.
Ledgers
Ledgers are the actual accounts where debit (DR) and credit (CR) transactions are recorded. Every voucher line item posts to a specific ledger. Ledgers cannot contain other accounts beneath them — they are always leaf nodes in the hierarchy.
Coding System
JobNext uses a structured coding system that encodes the parent-child relationship between groups and ledgers directly in the account code.
| Account Type | Code Length | Format | Example |
|---|---|---|---|
| Group | 4 characters | Alphanumeric abbreviation | ASST (Assets) |
| Ledger | 8 characters | Parent group code + 4-character suffix | ASSTBANK (Bank under Assets) |
The first 4 characters of any ledger code always correspond to its parent group code. For example, a ledger with code ASSTBANK automatically belongs to the group ASST. This naming convention makes it easy to identify which group a ledger belongs to simply by looking at its code.
Example Hierarchy
Consider the following example of how groups and ledgers are structured:
| Level | Code | Name | Type |
|---|---|---|---|
| 1 | ASST |
Assets | Group |
| 2 | ASSTBANK |
Bank Accounts | Ledger |
| 2 | ASSTCASH |
Cash on Hand | Ledger |
| 2 | ASSTFXAS |
Fixed Assets | Ledger |
| 1 | LIAB |
Liabilities | Group |
| 2 | LIABSCRD |
Sundry Creditors | Ledger |
| 2 | LIABPROV |
Provisions | Ledger |
Adding a New Group
To add a new account group to the Chart of Accounts:
- Navigate to Finance > Chart of Accounts
- Click the Add Group button
- Enter a 4-character group code (alphanumeric, unique across the CoA)
- Provide a descriptive group name
- Select the parent group if this is a sub-group, or leave at root level for a top-level group
- Specify the account nature (Assets, Liabilities, Income, or Expense)
- Click Save to create the group
Adding a New Ledger
To add a new ledger account:
- Navigate to Finance > Chart of Accounts
- Click the Add Ledger button
- Enter an 8-character ledger code where the first 4 characters match the parent group code
- Provide a descriptive ledger name
- The parent group is automatically determined from the first 4 characters of the code
- Configure additional properties such as tax applicability and reconciliation settings
- Click Save to create the ledger
Once a ledger code is assigned and transactions have been posted to it, the code cannot be changed. Plan your coding structure carefully before entering data. Ensure that the 4-character group codes you choose are meaningful and allow room for future expansion of ledger accounts.
Best Practices
- Plan your group codes — Use meaningful 4-character abbreviations that are easy to remember and clearly identify the category (e.g.,
ASSTfor Assets,EXPNfor Expenses) - Standardize ledger suffixes — Develop a consistent naming convention for the last 4 characters of ledger codes to make accounts predictable
- Create groups before ledgers — Always ensure the parent group exists before creating ledger accounts under it
- Review before going live — Verify the entire CoA structure before uploading opening balances or posting transactions, as restructuring later can be difficult
- Keep Tally in mind — If you plan to use the Tally Integration, ensure your CoA structure aligns with Tally's group hierarchy for smooth data export