Skip to content

Accounting Software | Chart of Accounts

One COA across entities. Schedule III, Ind-AS, IFRS layouts ready.

Master COA at the group level with per-entity inherit and override. Mapped to Schedule III note groupings, Ind-AS line items, IFRS and US-GAAP. Statutory mapping pre-built. Import from Tally Prime in one screen, with the duplicates merged before they hit the books.

Chart of Accounts imported from Tally Prime with 12 duplicates merged, multi-entity hierarchy mapped to Schedule III, Ind-AS and IFRS, with per-line links to Statement of Assets & Liabilities.

How it works

From Tally chaos to a master COA, with statutory mapping intact.

Step 01

Tally COA imported, deduplicated

Tally backups across companies are read; ledgers and groups merged into a single master COA. Duplicate ledgers (the three different "Travel Expenses" entries) are surfaced for one-click merge.

Step 02

Schedule III mapping pre-built

Each ledger is mapped to its Schedule III Division I, II or III line item. Mapping is editable per entity; the default ships with the standard Indian audit practice.

Step 03

Ind-AS and IFRS layouts ready

The same ledgers map to Ind-AS line items (financial assets, contract assets) and IFRS line items in parallel. Multi-GAAP per entity is supported with no parallel ledger.

Step 04

Per-entity inherit and override

New entities inherit the master COA. Local overrides (a UAE entity needing a VAT input account) sit on the entity without touching the group COA.

What the system does

Capability, input, output.

  • Master + entity COA

    Input
    Group ledgers + per-entity overrides
    Output
    Inherited COA per entity with local additions
  • Schedule III mapping

    Input
    Ledger + group classification
    Output
    Division I/II/III line item per ledger
  • Ind-AS / IFRS / US-GAAP layouts

    Input
    Same ledger
    Output
    Multi-GAAP line item assignment
  • Segment dimensions

    Input
    Cost-centre, project, product master
    Output
    Dimensional posting at JE level
  • Tally COA import

    Input
    Tally backup across companies
    Output
    Merged master COA with merge audit trail
  • GL controls

    Input
    Approval matrix per ledger
    Output
    Lock, deactivate, restrict-by-role per GL

Compliance + integrations

A COA your statutory auditor reads at first glance.

Schedule III out of the box. Ind-AS where the entity has crossed the threshold. IFRS for the foreign parent group view. Multi-GAAP per entity, no parallel ledger to maintain.

Regulations we work within

  • Companies Act, Schedule III

    Division I, II and III layouts ship pre-mapped per ledger.

  • Ind-AS

    Ind-AS 1 line items mapped where entity is on Ind-AS.

  • IFRS

    IFRS line items mapped for foreign-parent group consolidation.

  • Section 128, Companies Act

    COA changes captured in the audit trail with edit log.

Connects to

  • Tally Prime COA import + bidirectional sync
  • Zoho Books COA import
  • SAP Business One Native connector
  • NetSuite Native connector

Chart of Accounts FAQ

What buyers ask.

Our Tally has different COAs across our group's companies. Can we still consolidate?

Yes. The COA migration tooling reads each company's Tally COA, surfaces duplicate and inconsistent ledgers, and merges them into a master. Per-entity overrides are preserved. Once on a master COA, group consolidation runs without parallel mapping.

Does Schedule III auto-mapping really work?

For 80 to 90% of standard Indian B2B ledgers, the auto-mapping is correct out of the box. The remaining 10 to 20% (industry-specific or unusual ledgers) need a one-time review and override. The mapping is locked per FY once finalised, so the next FY's statements drop the day you close.

Can we have segment dimensions for cost-centre and project?

Yes. Segment dimensions (cost-centre, project, product, region) are first-class. Every JE carries the dimensions where applicable. Schedule III segment reporting is generated from these.

How does the COA handle an FY change in the law?

When the law changes (a new Schedule III amendment, a new Ind-AS standard), the master mapping is updated centrally and propagated. Per-entity overrides are preserved. Historic FYs retain their original mapping for comparability.

Bring your Tally COA. See the master, mapped, in 10 minutes.

Upload the Tally backup. The master COA, the duplicate-ledger merge list and the Schedule III mapping are all on one screen, free.