Trial balance + movement schedule in, validated AS-3 / Ind AS 7 statement out — cash flow statement software in under 60 seconds.
| Acct Code | Account Name | Sch III Head | CFS Class | CY Balance | PY Balance |
|---|---|---|---|---|---|
| 1010 | Property, Plant & Equipment | Fixed Assets | I | 4,85,00,000 | 4,20,00,000 |
| 1310 | Bank — Current Account | Cash & Equivalents | Cash | 62,20,000 | 38,00,000 |
| 2100 | Trade Receivables | Current Assets | O | 1,18,00,000 | 95,00,000 |
| 3200 | Long-term Borrowings | Non-Current Liabilities | F | 2,40,00,000 | 2,80,00,000 |
| 4000 | Profit Before Tax | P&L | O | 3,85,00,000 | 3,10,00,000 |
| 5100 | Trade Payables | Current Liabilities | O | 78,50,000 | 64,20,000 |
Mid-market controllers spend two to three full days per close hand-building the cash flow statement from a trial balance, PPE schedule, borrowing register and P&L — then both direct and indirect methods must reconcile to each other and to closing cash on the balance sheet. That sequence is not merely slow; it is structurally error-prone in ways that surface in audit.
The statement sits at the junction of three primary financial statements. Any mis-classification, PBT carry-forward error, or closing-cash discrepancy propagates into the Schedule III presentation, triggering auditor queries that delay sign-off. For companies under Ind AS, the indirect method must also reconcile to the direct method — doubling the verification burden. Beyond 50 movement lines, the manual process becomes arithmetically unreliable.
The human cost is also material: two to three days of controller time, per entity, per period. For groups preparing consolidated statements across five to ten subsidiaries, that multiplies to 10-30 person-days every quarter — almost entirely spent on classification, arithmetic, and cross-referencing rather than analysis.
Pulling CY and PY balances for every GL account, building a non-cash movement schedule, writing the statement line by line, then formatting to Schedule III heads takes 2–3 days — and the same file must support both the direct and indirect method under Ind AS 7 para 18–20.
Across 30–50 movement lines, disposal proceeds get tagged Operating instead of Investing, or a borrowing repayment is omitted from Financing — a Schedule III departure that surfaces in audit as a reportable item under Companies Act 2013, Section 134.
A draft P&L figure carried into the indirect method while a revised figure sits in the trial balance leaves the indirect CFO subtotal arithmetically unreliable — often by a small, easy-to-miss amount. The Rs 75,000 gap in our sample data illustrates exactly this failure mode.
Opening cash plus net change must equal closing cash on the balance sheet. A break of even Rs 1.2 lakh forces the auditor to trace the variance figure by figure before signing — extending the statutory close and delaying the board submission required under Companies Act 2013, Section 121.
of senior controller time per close period, per entity, go into building and cross-checking the statement — a task that AS-3 (Revised) and Ind AS 7 make mandatory for every company filing under the Companies Act 2013, regardless of size.
AS-3 and Ind AS 7 fix five reconciliation anchors for every cash flow statement; Schedule III prescribes the exact presentation heads auditors verify line by line. Non-compliance is not a formatting issue — it is a statutory departure with disclosure consequences.
The ICAI’s Accounting Standard 3 requires every company not yet on Ind AS to present a Cash Flow Statement as a primary financial statement, with all cash flows classified into Operating, Investing and Financing activities. Omission or misclassification constitutes a departure from Indian GAAP that auditors are required to qualify under SA 705.
Ind AS 7 permits either the direct method (gross receipts and payments) or the indirect method (para 20 — reconciliation from Profit Before Tax) for operating cash flows. This workflow builds and ties out both, ensuring the indirect-method CFO subtotal agrees with the direct-method CFO total before export.
Schedule III fixes the exact heads — Operating, Investing and Financing activities — and auditors verify each classification individually. Treating asset-disposal proceeds as an operating inflow, or a dividend payment as an operating outflow, is a reportable departure that requires an explanatory note under Section 134(5) directors’ responsibility statement.
SA 230 requires auditors to document sufficient evidence to support their conclusions. The workflow’s export — a classified statement, CY/PY working paper and validation log with PASS/FAIL per check — provides a traceable path from closing cash to every adjustment line, dropping straight into the audit file without a separate bridging schedule.
Seven deterministic passes from two Excel inputs to a signed-off Schedule III / Ind AS 7 statement — in under 60 seconds per period. Each pass produces an auditable intermediate result: no black boxes, no silent rounding.
Reads and auto-classifies the two required inputs: a Trial Balance (Account Code, Account Name, Sch III Head, CFS Classification, CY/PY balances) and a Movement Schedule (Account Code, Line Item, Activity O/I/F, Inflow/Outflow, Amount, Note Ref). File order does not matter — the worker identifies each from its column structure.
Uses the cfs_classification column in the trial balance to route each GL account to Operating, Investing or Financing, and isolates accounts tagged Cash to establish opening and closing cash & equivalents. Any account without a tag triggers the All Lines Classified exception before building activity sub-totals.
Starts from Profit Before Tax (account 4000), adds back non-cash charges such as depreciation per Note 12 — PPE Schedule, and adjusts for working-capital movements derived from the CY-minus-PY deltas for trade receivables, inventories, payables and other current items. The PBT sourced here is cross-checked to the movement schedule on the next pass.
Aggregates gross cash receipts and payments from all movement-schedule lines tagged Operating, producing a direct-method operating cash flow presentation alongside the indirect build. Both presentations are required for a complete Ind AS 7 disclosure package when your auditor requests the supplementary direct-method schedule.
Compares direct CFO to indirect CFO and raises a Direct Indirect CFO Agree warning on any arithmetic divergence, so the two presentations always agree before export. This check is the deterministic guard that prevents the common scenario of an indirect-method PBT revision not propagating to the direct-method build.
Closing Cash Ties (opening + net change = closing balance sheet cash), PBT Matches PNL (trial balance PBT = movement schedule PBT opening line), All Lines Classified (no untagged O/I/F rows), Working Capital Ties BS (every working-capital delta ties to a balance-sheet movement), and Direct Indirect CFO Agree — each deterministic, each surfaced in the exception queue on failure with the exact figure and account code.
Produces a multi-tab Excel working paper: one tab per activity section (CFO, CFI, CFF), a validation log with PASS/FAIL and a plain-English comment per check, and a one-page Schedule III statement ready to drop into the audit file or the board pack. The package traces every figure to its source account code and note reference, aligned with ICAI SA 230 documentation expectations.
The sample pair embeds four real failure modes as rows in a single trial balance and movement schedule for Acme Industries Pvt Ltd (FY ended 31-Mar-2026). Each produces a deterministic, named exception an auditor can verify in seconds — no fuzzy scoring, no thresholds.
cfs_classification column in the trial balance governs: the workflow applies it consistently to both the current and prior year, and any period-on-period reclassification surfaces in the exception log rather than silently changing the comparatives.Two consolidated Excel files for one entity and one period — both share Account Codes so the movement lines tie back to trial-balance GL balance movements. Cadel auto-classifies each file from its column structure; no manual labelling required at upload.
38 Schedule III–mapped GL accounts with CFS Classification and CY/PY balances. Carries the authoritative PBT (Rs 3,85,00,000, account 4000) and the planted Rs 1,20,000 bank overstatement (account 1310). The CFS Classification column drives the O/I/F routing throughout the workflow.
33 movement lines — depreciation (Note 12–PPE), interest, tax paid, dividends, asset additions and borrowing moves — each carrying the Account Code of the trial-balance GL it derives from. Embeds the PBT gap (Rs 3,84,25,000 vs trial-balance Rs 3,85,00,000), the untagged disposal line (account 1010), and the unmatched working-capital line (account 9999).
Run against the consolidated pair, the clean rows all pass: each movement line ties to a trial-balance Account Code via shared key, depreciation from Note 12 — PPE Schedule is added back in the indirect method, and the direct and indirect CFO totals agree at Rs 2,26,75,000. The four planted exception rows each trigger exactly one named check.
Closing Cash Ties fails on the Rs 1,20,000 bank overstatement in account 1310 — the variance is isolated to that account and closing cash is quantified as Rs 62,20,000 on the trial balance against Rs 61,00,000 computed from the movement schedule. PBT Matches PNL fails on the Rs 75,000 gap: the trial balance PBT of Rs 3,85,00,000 (account 4000) versus the movement schedule opening line of Rs 3,84,25,000 makes the indirect CFO subtotal unreliable until corrected.
All Lines Classified fails on the plant-disposal proceeds (account 1010, Note 12 — Disposals): direction Inflow, Amount Rs 12,00,000, Activity column blank. The line is excluded from every activity sub-total and listed in the exception queue by name and amount until it is tagged Investing. Working Capital Ties BS fails on the "Decrease in Security Deposits" line (account 9999): a target-only exception, because the movement schedule carries a Rs 4,50,000 Inflow under Operating that has no counterpart in the 38-account trial balance.
The validation log exports with each check in a separate row: check name, PASS/FAIL, the exact figure and account code that tripped it, and a plain-English comment the audit team can copy directly into the audit working paper notes under ICAI SA 230.
A two-to-three-day spreadsheet build becomes a sub-minute run with deterministic validation results and an audit-ready export. The efficiency gain is not a matter of speed alone — it is a structural shift from error-prone manual classification to a rule-driven engine that applies the same O/I/F logic to every account, every period, without drift.
Closing-cash breaks, PBT divergence between P&L and the indirect method, untagged movement lines that silently drop from activity totals, and working-capital movements that do not tie to balance-sheet deltas are each caught by a named, deterministic check before export — reducing the error classes that currently extend statutory close timelines and generate auditor queries under SA 315 risk assessment procedures.
The same O/I/F logic is applied to every line in both inputs across all periods, so activity-tagging error falls from the human baseline of two to five misclassified lines per statement to zero wherever the cfs_classification field is populated. Period-on-period reclassifications surface in the exception log rather than silently altering the comparatives, preserving consistency under Ind AS 1 para 38.
The export bundles the Schedule III statement, a CY/PY working paper with source account codes, and a validation log with PASS/FAIL and a plain-English comment per check — a traceable path from closing cash to every adjustment, aligned with ICAI SA 230 — Audit Documentation, with no separate bridging schedule and no manual annotation required.
Questions finance controllers and statutory auditors ask before deploying this workflow in their close process.
Two Excel files for one period: a Schedule III trial balance (Account Code, Account Name, Sch III Head, CFS Classification, CY and PY balances) and a non-cash movement schedule (Account Code, Line Item, Activity O/I/F, Inflow/Outflow, Amount, Source/Note Ref). Drop both together — Cadel classifies each file automatically from its column structure, so order does not matter.
Both AS-3 (Cash Flow Statements) issued by the ICAI for companies not yet on Ind AS, and Ind AS 7 (Statement of Cash Flows) for companies applying Ind AS. Both require cash flows classified into Operating, Investing and Financing activities and permit the direct or indirect method for operating activities — the workflow builds and reconciles both. For IFRS reporters, Ind AS 7 is substantially converged with IAS 7, so the output is structurally compatible with IAS 7 requirements as well.
The indirect build starts from Profit Before Tax. The workflow reads PBT from the trial balance (account 4000) and compares it to the PBT opening line in the movement schedule. Any difference — even Rs 1 — fails the PBT Matches PNL check, so a draft P&L figure carried into the CFS is caught before the indirect CFO subtotal is trusted. The sample data embeds a Rs 75,000 gap to demonstrate this check in action.
Opening cash plus the net change computed from the movement schedule must equal the closing cash and equivalents on the trial balance. If they diverge, the Closing Cash Ties check fails and the variance is isolated to the rupee — the exact account code and amount are shown — so you can trace it before signing off the statement. This check corresponds to the reconciliation required by Ind AS 7 para 28–30.
Every movement-schedule line must carry an Operating, Investing or Financing tag. A row left blank — for example, asset-disposal proceeds with no O/I/F tag — fails the All Lines Classified check and is listed by name and amount. An untagged line would silently drop out of the activity sub-totals and break the Schedule III presentation, making the CFO, CFI and CFF sub-totals arithmetically inconsistent.
The workflow computes the CY-minus-PY delta for each working-capital head (trade receivables, inventories, trade payables, other current assets/liabilities) from the trial balance and compares it to the matching movement-schedule line via the shared Account Code. A movement line with no trial-balance counterpart, or a delta that does not tie, fails the Working Capital Ties BS check — preventing the silent inclusion of a phantom working-capital adjustment in CFO.
A finished Schedule III / Ind AS 7 cash flow statement. The worker classifies every movement line into Operating, Investing or Financing, derives CFO under the indirect method from Profit Before Tax, and posts the statement to the Cash Flow Statements view as a downloadable Excel showing CFO, CFI, CFF and the net change in cash — with any unclassified line listed separately so it never silently drops out of the activity sub-totals.
Yes, by file. Export the trial balance and movement schedule from Tally Prime, Zoho Books, QuickBooks, NetSuite or SAP B1 — no connector or API is required. You add or confirm the CFS Classification and Sch III Head columns once; a saved mapping makes subsequent periods near-instant. The mapping is stored per entity, so multi-subsidiary runs reuse the same column mappings without re-setup.
Yes. Export the classified statement, the CY/PY working paper and the validation log (each check with PASS/FAIL and a plain-English comment) to Excel from the Inbox toolbar. The package traces every figure to its source document and note reference, aligned with ICAI SA 230 — Audit Documentation expectations, and provides the evidence trail an auditor requires to agree closing cash without a separate bridging schedule.