Trial balance to Companies Act 2013 financials — Schedule III mapping validated and exported in under 30 seconds per period.
| Code | Ledger Name | Tally Group | Sch III Head | Dr (₹) | Cr (₹) |
|---|---|---|---|---|---|
| 1101 | Equity Share Capital | Capital Account | Equity & Liab → Share Capital | — | 50,00,000 |
| 2201 | Trade Payables — Domestic | Sundry Creditors | Equity & Liab → Trade Payables | 1,25,000 | — |
| 2205 | Payable — Acme Steels | Sundry Creditors | Equity & Liab → Trade Payables | — | 3,40,000 |
| 1450 | Crypto Holdings — BTC Wallet | Investments | (blank) | 8,50,000 | — |
Every Indian company under the Companies Act, 2013 must present annual financials in Schedule III format. For mid-market finance teams running 50–500 active ledgers in Schedule III mapping software or manual Excel, this classification exercise is the single largest bottleneck at year-end close.
A mid-market company with 150–300 active ledger codes in Tally Prime, SAP Business One, or Zoho Books must classify every code into a Schedule III head and sub-head before the Balance Sheet can be signed off. Done in Excel, this two-to-four-day exercise is sequential, error-prone, and the primary cause of delayed audit deliverables under Section 129 of the Companies Act, 2013.
New accounts created during the year — a crypto-asset wallet, a new class of borrowing, or an inter-company loan — have no Schedule III mapping and are silently omitted from the draft financials. The omission only surfaces when the statutory auditor reviews the pack, triggering a revision cycle that can push sign-off by one to three weeks.
A liability or equity ledger carrying a debit balance — typically a vendor overpayment — is arithmetically inconsistent with its Schedule III head. In Excel-based mapping sorted by classification rather than by expected sign, a debit figure in a creditors column is visually invisible, leading to a misstated Balance Sheet that reaches the auditor undetected. The Sign Consistency check catches this deterministically on every run.
The 2021 MCA amendment to Schedule III requires Trade Payables to be disaggregated between MSME enterprises (per Section 22 of the MSMED Act, 2006) and others, and related-party balances to be tagged under Ind AS 24 / AS 18. A manual mapping exercise has no systematic way to enforce these tags across hundreds of creditor ledgers — leaving the Notes to Accounts incomplete and the company exposed to qualification risk on MSME disclosures.
The typical elapsed time for a manual trial balance to Schedule III classification exercise at a mid-market company with 150–300 ledgers. One day to export and format the trial balance; one to two days to classify each ledger and build the Schedule III template in Excel; a final review cycle to resolve exceptions and tally the balance sheet. Under Section 129(2) of the Companies Act, 2013, financial statements that do not comply with Schedule III format are not considered to give a true and fair view — exposing the company and its directors to qualification risk from the statutory auditor.
Schedule III to the Companies Act, 2013 imposes five concurrent compliance obligations on every run: completeness, arithmetic integrity, sign consistency, MSME disclosure, and related-party tagging. Each obligation traces to a specific section or standard that the statutory auditor will verify.
Every Indian company must present its Balance Sheet (Part I) and Statement of Profit & Loss (Part II) in the Schedule III format. The 2021 MCA amendment introduced mandatory MSME ageing schedules, promoter shareholding disclosures, and CSR spending notes — items that cannot be generated without explicit ledger-level tagging at the trial balance stage.
Trade Payables in the Notes to Accounts must be separately disclosed as amounts due to Micro and Small Enterprises and amounts due to others, broken into an ageing schedule of less than one year, one to two years, two to three years, and more than three years. Non-disclosure or incorrect classification triggers regulatory exposure under the MSMED Act and potential qualification by the statutory auditor under ICAI SA 700.
Balances due from or to directors, key management personnel, subsidiaries, and associates must be identified and tagged for disclosure in the relevant Schedule III notes. Under Ind AS 24 (Related Party Disclosures) and AS 18, incomplete disclosure is a material misstatement risk that the auditor is required to escalate under SA 315 — Identifying and Assessing the Risks of Material Misstatement.
The statutory auditor requires a traceable chain from every balance sheet line item back to source ledger codes, mapping decisions, and any override or exception cleared by the preparer. ICAI SA 230 (Audit Documentation) mandates that this evidence be retained in sufficient detail for an experienced auditor to understand — a standard that a manually maintained Excel mapping log rarely satisfies without a separate, immutable audit trail.
When any one of these five checks fails silently, the downstream consequence is a Schedule III pack delivered to the statutory auditor with an untallied balance sheet, a missing MSME note, or an unmapped ledger buried in a suspense line. Under SA 210 (Terms of Audit Engagements) and SA 315, the auditor is required to escalate such gaps, which delays sign-off and triggers additional management representation requests.
Seven deterministic steps from raw trial balance to a print-ready Schedule III pack — in under 30 seconds per period on a trial balance of up to 500 ledger rows.
Accepts an Excel upload (sheet: "Trial Balance FY25") and parses every row — ledger_code, ledger_name, ledger_group, existing schedule_iii_head / schedule_iii_subhead if populated, debit_balance, and credit_balance — into a structured entry list. Handles Tally Prime exports, SAP S_ALR_87012277 reports, NetSuite Trial Balance, and Zoho Books with minor column relabelling.
Each ledger is matched against the full Schedule III taxonomy — Equity & Liabilities (Share Capital, Reserves & Surplus, Long-term Borrowings, Trade Payables, Short-term Provisions, and others) and Assets (PPE, CWIP, Intangibles, Trade Receivables, Cash & Cash Equivalents, Other Current Assets, and others). Ledgers with a blank schedule_iii_head are immediately flagged rather than silently omitted.
Any ledger with a blank Schedule III head or sub-head triggers a FAIL on the All Ledgers Mapped validation and is routed to the exception queue with an "Unmapped" badge. The export of the Schedule III pack is blocked until the controller manually assigns a head and sub-head, or records a disclosure note explaining the treatment — mirroring the requirement under AS 1 / Ind AS 1 that all material items be disclosed.
The workflow sums all asset-side ledgers and all equity-and-liability-side ledgers and compares the totals. Any non-zero difference is displayed as a numeric variance at the foot of the mapping inbox; export is blocked until the discrepancy is cleared or a suspense entry is recorded. This replaces the fragile manual total-row in an Excel sheet that a formula error can silently break.
Each ledger's normal balance is inferred from its Schedule III head: liability and equity ledgers are expected to carry credit balances; asset ledgers are expected to carry debit balances. A Trade Payables ledger showing a debit balance of ₹1,25,000 (code 2201) triggers a "Debit Balance in Liability Account" exception badge and is held in the exception queue pending controller review before the balance sheet can be exported.
Trade Payables ledgers are cross-checked for an MSME classification flag per Section 22 of the MSMED Act, 2006. Ledgers mapped to the Trade Payables sub-head without an explicit MSME tag receive an "MSME Untagged" warning, and the Excel export separates MSME and non-MSME payables in the Notes to Accounts, with the ageing schedule mandated by the 2021 MCA amendment pre-populated.
Once all FAIL-severity checks pass, the workflow produces a formatted Schedule III Balance Sheet (Part I) and Statement of Profit & Loss (Part II), an exception log, and a Notes to Accounts draft — all in a single Excel workbook downloadable from the inbox view. The Mapping Log tab records each ledger code, the original Tally group, the assigned head and sub-head, and the name of the preparer who resolved any exception, satisfying ICAI SA 230 documentation requirements.
Six synthetic test scenarios that exercise every failure mode observed in real-world trial balance data. Each produces a deterministic, auditor-verifiable outcome.
Four seeded trial balance files — each one engineered to exercise a specific failure mode. Three map cleanly or with resolvable warnings. One is deliberately misconfigured to prove the workflow surfaces every exception before export.
Ledger code 1101 — Equity Share Capital — passes all five validation checks: All Ledgers Mapped (mapped to Share Capital under Equity & Liabilities), Sign Consistency (credit balance confirmed on an equity ledger), and MSME Disclosure Tag and Related Party Tag (correctly marked not applicable). Export is unblocked immediately.
MSME Disclosure Tag check raises a WARNING. The Excel export separates MSME trade payables from non-MSME trade payables in the Notes to Accounts section, with the ageing schedule — per the 2021 MCA amendment — pre-populated with ₹3,40,000 in the <1 year bucket.
Sign Consistency FAIL raised. The sign-anomaly exception is the exception most frequently missed in manual Schedule III exercises because Excel sorts by classification rather than by expected sign — a debit figure in a creditors column is visually invisible. Cadel catches it deterministically on every run.
All Ledgers Mapped FAIL raised. The controller must assign code 1450 to "Other Non-Current Assets" with a disclosure note before the Schedule III pack can be exported. The export block ensures no ledger is silently omitted from the Balance Sheet.
A manual Schedule III mapping exercise for a mid-market company with 150–300 active ledgers typically consumes two to four working days. Cadel reduces that cycle to under 30 seconds of automated classification plus a controller review session of 15–30 minutes to clear exception-queue items. The five validation checks run simultaneously on every run, eliminating the version-control risk of sequential manual checks across separate spreadsheets.
The Sign Consistency check flags any liability or equity ledger carrying a debit balance — the exception most frequently missed in Excel-based mapping because the sort order conceals it. Catching it before the draft reaches the auditor eliminates a revision cycle that typically costs one to three working days and an additional management representation under ICAI SA 580.
The 2021 MCA amendment MSME ageing schedule and the Ind AS 24 related-party tagging requirements are validated on every run. The exported Notes to Accounts draft pre-populates both tables, so the preparer inserts confirmed amounts rather than reformatting from scratch — removing a disclosure gap that can delay statutory audit sign-off under ICAI SA 700.
The output workbook — Schedule III Balance Sheet, Statement of P&L, exception log, and Notes to Accounts draft — is structured to drop directly into the statutory audit file. The Mapping Log tab records every mapping decision, override, and validation result in an immutable, timestamped chain that satisfies ICAI SA 230 (Audit Documentation) without additional working paper preparation.
The questions finance controllers and statutory auditors ask most often before deploying Schedule III automation.
Upload one trial balance for the period as an .xlsx file. It should carry Ledger Code, Ledger Name, Tally Group, Schedule III Head, Schedule III Sub-Head, Debit (Rs) and Credit (Rs) columns. Cadel classifies and extracts every ledger row automatically. Trial balances from SAP (transaction S_ALR_87012277), NetSuite's Trial Balance report, or Zoho Books can be mapped to this template with a one-time column-relabelling step.
A Schedule III (Companies Act, 2013) financial statement per trial balance — a Balance Sheet split into Equity & Liabilities and Assets (Part I), plus a Statement of Profit & Loss (Part II) — generated as an Excel file you can open inline from the Schedule III Statements view and export. The workbook also includes an exception log and a pre-populated Notes to Accounts draft covering MSME ageing and related-party disclosures.
The workflow implements the Schedule III format as amended by MCA notification dated 24 March 2021, which applies to companies preparing financial statements under both the Accounting Standards (AS) framework and the Indian Accounting Standards (Ind AS) framework. The mapping templates include the additional disclosure requirements introduced in the 2021 amendment — MSME ageing, promoter shareholding, and CSR spending — and can be toggled between the AS and Ind AS column structures depending on the reporting entity's applicability threshold under the Companies (Ind AS) Rules, 2015.
The workflow runs five checks per trial balance: Balance Sheet Tallies (FAIL — total assets must equal total equity + liabilities), All Ledgers Mapped (FAIL — every ledger must have a Schedule III head and sub-head), Sign Consistency (FAIL — liability/equity ledgers must be credit, asset ledgers must be debit), MSME Disclosure Tag (WARNING — MSME vendors must be separately classified under Trade Payables), and Related Party Tag (WARNING — related-party balances must be tagged for AS-18 / Ind AS 24 disclosure). Anything that fails surfaces in the Exceptions view with the specific rule that tripped.
Any ledger whose schedule_iii_head and schedule_iii_subhead columns are blank triggers a FAIL on the All Ledgers Mapped validation and is routed to the exception queue with an "Unmapped" badge. The controller must either assign the ledger to the closest permissible Schedule III line item — for example, mapping crypto holdings to "Other Non-Current Assets" with a note — or record a disclosure note explaining the treatment before the workflow permits export. This mirrors the requirement under AS 1 / Ind AS 1 that financial statements present all material items with adequate disclosure.
MSME vendor payables must be separately disclosed under Trade Payables as amounts due to Micro and Small Enterprises under Section 22 of the Micro, Small and Medium Enterprises Development Act, 2006, read with the MCA Schedule III amendment of 2021, which requires an ageing schedule broken into outstanding periods of less than one year, one to two years, two to three years, and more than three years. Related-party balances must be tagged for disclosure in the Notes to Accounts under AS 18 (Related Party Disclosures) or Ind AS 24, as applicable. The workflow raises WARNING-level exceptions for both categories and generates pre-populated disclosure tables in the exported Schedule III pack.
The input is a structured Excel file with the six required columns — which matches the format of a Tally Prime trial balance export with minor column relabelling. Trial balances from SAP (transaction S_ALR_87012277), NetSuite's Trial Balance report, or Zoho Books can be mapped to this template using a one-time column-mapping step. No direct API connector is required; the workflow operates on the uploaded XLSX file regardless of source system.
Yes — once all trial balance ledgers are mapped, the workflow produces a Schedule III-format Balance Sheet (Part I) and a Statement of Profit & Loss (Part II) in a single Excel export, with each note numbered sequentially and cross-referenced to the face of the statements. Multi-entity consolidation — eliminating intercompany balances per Ind AS 110 / AS 21 — requires running the workflow separately for each subsidiary and then uploading the individual outputs to Cadel's Consolidation workflow. The Schedule III mapping workflow is scoped to a single legal entity trial balance per run.
