Glossary · Accounting & Bookkeeping
Ledger Mapping Schema
Definition
A ledger mapping schema is a documented table that matches each ledger in an old accounting system to the right account in a new one. It is built before a software migration and drives the data import. Without it, balances land in the wrong accounts and the new books open wrong.
At a glance
- Category
- Accounting & Bookkeeping
- In this entry
- What it means for Indian businesses How it works · Example
In practice
01 What it means for Indian businesses
Two accounting systems rarely share the same chart of accounts. When a business moves from Tally to Zoho Books or Odoo, each Tally ledger must be given a destination: Sundry Debtors to Accounts Receivable, each expense head to its new account, and GST ledgers to the right tax accounts. The schema also records what merges (duplicate ledgers) and what splits.
A chart of accounts and a mapping schema are different. The chart of accounts is the permanent list of accounts a system posts to. The mapping schema is the translation between two charts, used whenever two systems or two entities must agree.
GST ledgers need special care. Keep separate input and output ledgers for CGST, SGST, IGST and cess, because input tax credit is set off in a fixed legal order and must reconcile with the electronic credit ledger and GSTR-3B. Under sections 49, 49A and 49B and rule 88A, IGST credit is used first, and CGST credit can never pay SGST or UTGST, or the other way round.
How it works
02 How it works
- Extract the source chart
Every ledger and group from the old system, usually with its trial balance.
- Design the destination chart
So each source ledger has a target.
- Map each ledger
To one target account; merge duplicates and fix wrong groups.
- Validate
No ledger may be left unmapped. An unmapped ledger should stop the import, not fall into suspense.
- Import
Using the schema.
- Reconcile
Tie the new trial balance back to the old one before go-live.
Import tools only follow the map. A wrong map produces a clean import of wrong data.
Worked example
03 Example
An example, not advice on your facts.
A services company moves from Tally to Zoho Books.
| Tally ledger | Balance (₹) | Mapped to |
|---|---|---|
| Sundry Debtors | 12,00,000 | Accounts Receivable |
| Sundry Creditors | 8,00,000 | Accounts Payable |
| Two duplicate expense ledgers | 3,50,000 (total) | One expense account |
Because every ledger has a destination, the migrated trial balance agrees with Tally, and the new books open clean.
Watch out
04 Common mistakes
- Leaving a ledger unmapped, which drops its balance.
- Mapping by name only, so a liability lands in an income group.
- Carrying duplicate ledgers into the new chart.
- Going live without tying the new trial balance to the old one.
- Merging all GST into one ledger.
Need help with a ledger mapping schema? See our Migration: Tally to Zoho Books or Migration: Tally to Odoo. You can also see our Chart of Accounts Setup Services.
Review and sources
Sources: CBIC Tax Information Portal, CGST Act s.49, 49A, 49B; rule 88A: official copy 1, official copy 2
