CARO Report Using Gen Bal Software

CARO Report Using Gen Bal Software

The Companies (Auditor's Report) Order, 2020 (CARO 2020) requires statutory auditors to comment on 21 specific clauses — from fixed asset verification to fraud reporting to statutory dues ageing. For FY 2026-27 audits, with NFRA inspections intensifying and MCA enforcement focused on clause-level documentation, manually drafting CARO reports is no longer viable for most CA firms. Gen Bal (Genius Balance Sheet) by SAG Infotech automates clause-by-clause generation, links responses to working papers and exports compliant Word and PDF output — significantly reducing drafting time while improving consistency across the engagement team.

What CARO 2020 Requires — and Who Must Comply

The Companies (Auditor's Report) Order, 2020, issued by the Ministry of Corporate Affairs (MCA) under Section 143(11) of the Companies Act 2013, applies to financial years commencing on or after 1 April 2021. For the FY 2026-27 audit cycle, CARO 2020 is fully operative and no further deferment or amendment is anticipated before that cycle closes.

*CARO 2020 is mandatory for all companies except the following exempt categories:*

• One Person Companies (OPCs) as defined under Section 2(62) of the Companies Act 2013
• Small companies satisfying both conditions: paid-up share capital not exceeding Rs. 4 crore and turnover not exceeding Rs. 40 crore (thresholds as revised effective 1 April 2021)
• Private companies that simultaneously satisfy all three conditions: (a) paid-up share capital plus reserves and surplus not exceeding Rs. 1 crore at the balance sheet date; (b) total borrowings from banks or financial institutions not exceeding Rs. 1 crore at any point during the year; and (c) total revenue not exceeding Rs. 10 crore during the year — and are not a subsidiary or holding company of a public company
• Banking companies, insurance companies and Section 8 companies (not-for-profit)

Two points that trip up auditors in practice. First, a private company that breaches any one of the three financial thresholds mid-year — say its bank borrowings cross Rs. 1 crore in Q3 — loses the exemption for the entire year, not just from the breach date. Second, the small company thresholds (Rs. 4 crore / Rs. 40 crore) under Section 2(85) are distinct from the private company CARO exemption thresholds (Rs. 1 crore / Rs. 1 crore / Rs. 10 crore). These are separate tests. Document your applicability determination in the engagement planning file before fieldwork begins.

The 21 CARO 2020 Clauses — and the Five That Attract Regulator Scrutiny in 2026

CARO 2020 requires the auditor to comment on 21 specific matters in prescribed sequence. The full landscape:

For FY 2026-27, five clauses attract the sharpest regulator attention:

1. Clause (vii) — statutory dues, particularly GST arrears correlated with GSTR-9, TDS defaults identified via TRACES and EPF/ESI outstanding beyond six months
2. Clause (iii) — interest-free or below-market loans to group entities, flagged by MCA as indicators of fund diversion
3. Clause (xi) — fraud reporting under Section 143(12); post-IL&FS, NFRA expects documented evidence of enquiry, not a routine nil statement
4. Clause (xiii) — related-party disclosures are correlated by SEBI and MCA against XBRL data; inconsistencies between CARO and note disclosures are a red flag
5. Audit trail under Rule 11(g) — this is not a CARO clause; it is reported in the main auditor's report under Rule 11(g) of the Companies (Audit and Auditors) Rules 2014, but Gen Bal handles it in the same engagement workflow and it belongs in every audit file discussion

A common error in practice is referring to audit trail as "CARO clause (xvii)." Clause (xvii) covers cash losses, not audit trail. Audit trail is a standalone requirement in the main auditor's report. Keep the terminology precise, especially in NFRA inspection files.

Why CA Firms Use Gen Bal for CARO Report Generation

Gen Bal — formally Genius Balance Sheet by SAG Infotech, Jaipur — is one of India's most widely deployed balance sheet and statutory audit reporting platforms. Its CARO 2020 module addresses the core problems with manual drafting:

• Pre-loaded clause templates aligned with current CARO 2020 wording; SAG Infotech issues annual updates tracking MCA circulars and ICAI guidance
• Trial balance linkage — import directly from TallyPrime, Tally.ERP 9 or Excel; key figures (gross block, borrowed funds, statutory dues ledgers) populate the relevant clauses automatically rather than requiring manual transcription
• Structured remarks library — a curated set of satisfactory, qualified and adverse remarks for each clause; you select and customise rather than draft from scratch, reducing routine drafting time by 60–70% on standard engagements
• Built-in consistency checks — the software flags contradictions, such as PPE gross block stated in clause (i) differing from the balance sheet schedule, before you export
• Clause-level attachment module — scan and attach fixed asset registers, physical verification reports, statutory dues challans and management representations directly against the clause they support
• Multi-company, multi-user management — a firm handling 80+ statutory audits can assign each engagement to a team member, track completion status across clauses and log the engagement partner's sign-off with date and digital credential
• Export to Word and PDF — output format is compatible with MCA V3 portal submissions as part of e-Form AOC-4 or AOC-4 XBRL

A firm recovering four to six hours per CARO engagement across a portfolio of eighty audits saves 320–480 partner and senior hours per year — time better invested on judgement-intensive clauses and quality review rather than mechanical formatting.

Step-by-Step: Generating a CARO 2020 Report in Gen Bal

This sequence applies to an FY 2026-27 engagement (audit of accounts for the year ending 31 March 2027). AOC-4 filing is typically due by late October 2027 (within thirty days of the AGM, which must be held by 30 September 2027 for a March year-end company under Section 96 of the Companies Act).

Step 1 — Set Up the Company Master

Open Gen Bal and navigate to Company Master. Confirm: company type (public/private/OPC/Section 8), CIN, registered address, auditor details and the financial year (1 April 2026 to 31 March 2027). Set the CARO applicability flag based on the exemption check above. Record the applicability determination as a working paper — this is an NFRA inspection point.

Step 2 — Import the Trial Balance

Use File → Import Trial Balance. Gen Bal accepts Tally XML, standard Excel templates and CSV. Map debit/credit heads to the software's chart of accounts. Run the auto-balance check; the imported trial balance must tally to zero before you proceed to the CARO module. Any suspense balance indicates a mapping error — resolve it before fieldwork figures are locked.

Step 3 — Open the CARO 2020 Module

Navigate to Audit Reports → CARO 2020. All 21 clauses are displayed. Each clause carries: a status flag (Not Applicable / Satisfactory / Qualified / Adverse), a text field for the remark and an attachment icon. Do not leave any clause status blank — a blank status triggers an incomplete CARO warning at export and is itself a quality deficiency.

Step 4 — Work Through Clauses Sequentially

For each clause: (a) read the statutory requirement shown in the left panel, (b) select the correct status, (c) choose a standard remark from the library or draft a bespoke one, and (d) attach the supporting working paper. Treat clauses (xii) and (xvi) as genuinely Not Applicable for most non-Nidhi, non-NBFC clients and mark them as such with a brief note. "Not Applicable" is a valid and complete response; blank is not.

Step 5 — Build Clause-Specific Schedules for High-Risk Clauses

For clauses (vii), (iii), (ix) and (xiii), build a supporting Excel schedule outside the software: reconcile figures to the trial balance, document source documents and cross-reference dates. Then import the schedule as a PDF attachment in Gen Bal and transcribe the key numbers — amounts, due dates, outstanding periods — into the remark text. This two-step discipline ensures the numbers in the CARO report match the underlying working paper exactly.

Step 6 — Partner Review and Sign-off

Generate the draft CARO report via File → Print Preview → CARO 2020. Circulate to the engagement partner for clause-by-clause review. Gen Bal's sign-off module records the reviewer's name, date and digital signature. Backdated sign-offs are among the most heavily penalised findings in NFRA inspection reports — log the actual review date.

Step 7 — Finalise and Export

After partner sign-off, export to Word for any final wording adjustments and PDF for archival. The finalised CARO report is appended to the main auditor's report and submitted to the ROC via the MCA V3 portal as part of e-Form AOC-4 (or AOC-4 XBRL for listed companies and certain large unlisted public companies).

Worked Example: Clause (vii) — Statutory Dues Reconciliation in Practice

Company: Meridian Components Pvt Ltd — private company, revenue Rs. 38 crore for FY 2026-27, bank borrowings Rs. 3 crore. CARO 2020 applicable (revenue exceeds Rs. 10 crore threshold).

Statutory dues position as at 31 March 2027:

How each line affects the CARO report:

• March 2027 TDS of Rs. 4,20,000 — due date is 30 April 2027, after the balance sheet date. Not an arrear at 31 March 2027. No clause (vii) disclosure required, though the subsequent payment should be noted in the audit file.

• February 2027 EPF of Rs. 96,000 — paid 24 days late. EPFO levies damages under Section 14B of the Employees' Provident Funds and Miscellaneous Provisions Act 1952 at 5% for delays up to two months: Rs. 96,000 × 5% = Rs. 4,800. Disclose the late payment; the damages amount is a contingent or actual liability depending on whether EPFO has raised a demand.

• January 2027 GSTR-3B of Rs. 2,80,000 — paid 36 days late. Interest under Section 50 of the CGST Act 2017 accrues at 18% per annum: Rs. 2,80,000 × 18% × 36/365 = Rs. 4,975 (approximate). Late, but paid before year-end; disclose as "statutory dues were not regularly deposited" with amounts and dates.

• September 2026 TDS of Rs. 1,10,000 — outstanding for 176 days at 31 March 2027, well past the six-month threshold. This must be explicitly named in clause (vii)(b) with the amount, the authority (Income Tax Department), the nature (TDS on contractor payments, Section 194C) and the due date. Failure to identify this is a qualified or adverse CARO observation.

Late interest on the TDS arrear under Section 201(1A) of the Income-tax Act 1961 at 1.5% per month from the date of deduction (assume 30 September 2026) to the date of actual payment: for six months — Rs. 1,10,000 × 1.5% × 6 = Rs. 9,900 — also reportable as a contingent liability in the notes to accounts.

In Gen Bal, populate clause (vii)(b) with: "Undisputed dues of Income Tax (TDS — Section 194C) amounting to Rs. 1,10,000 have been outstanding for more than six months from the date they became payable, as at 31 March 2027. The amount was due on 7 October 2026."

Attach the TDS ledger printout and the TRACES default summary to the clause (vii) attachment slot before partner sign-off.

Audit Trail Reporting Under Rule 11(g) — The 2026 Pressure Point

Audit trail is not a CARO clause. It is reported in the statutory auditor's main report under Rule 11(g) of the Companies (Audit and Auditors) Rules 2014, inserted by the Companies (Audit and Auditors) Amendment Rules, 2021, and fully operative from FY 2023-24 onwards. For FY 2026-27 audits, there is no deferred applicability — every company within scope must be reported on.

The auditor must state:

• Whether the accounting software used by the company has a feature of recording an audit trail (edit log) for every transaction
• Whether the audit trail was enabled throughout the year and not tampered with
• Whether the audit trail has been preserved as required under record-retention provisions of the Companies Act (minimum eight years)

Three scenarios that require careful handling in 2026:

1. Company on TallyPrime Release 4.0 or higher — the audit trail feature exists. But was it enabled from 1 April 2026? Obtain a configuration report or vendor confirmation of the enablement date. If enabled from, say, 1 July 2026, the auditor must qualify the remark for the period 1 April to 30 June 2026.

1. Custom ERP or in-house software without audit trail capability — the feature is absent entirely. The remark must state this plainly and qualify the report. Do not soften the language with phrases like "audit trail feature is under implementation."

1. Third-party payroll or manufacturing software — even if the main accounting system has audit trail, payroll entries may originate in an external application without edit log capability. Scope the remark to cover all accounting software used, not just the primary ledger system.

Gen Bal integrates a dedicated Rule 11(g) checklist in the auditor's report module (separate from the CARO 2020 module). You document: name and version of accounting software, enablement date, evidence of enablement, whether the audit trail covers period-end adjustments and journal entries, and back-up frequency and storage location. The remark auto-populates into the auditor's report. Maintain the evidence — screenshots, vendor certificates, IT management representations — as a separate working paper.

Common Mistakes and Pitfalls to Avoid

These errors appear repeatedly in NFRA inspection findings and ICAI Quality Review Board reports.

1. Copying prior-year CARO remarks verbatim Reusing last year's output without updating dates, amounts and facts is the single most common and most damaging error. If your FY 2025-26 report stated "physical verification was conducted in November 2025," that phrase cannot appear in the FY 2026-27 CARO. Gen Bal's year-forward rollover carries remarks forward for efficiency — treat every rolled-over remark as a draft requiring verification, not a finished response.

2. Missing the six-month threshold for clause (vii) arrears Auditors frequently state "all statutory dues are regularly deposited" without running a due-date-versus-payment-date reconciliation. For TDS, compare challan BSR codes and dates in TRACES against the TDS payable ledger. For GST, reconcile GSTR-3B payment dates against the liability ledger. For EPF, check Electronic Challan-cum-Return (ECR) receipt dates against wage month due dates.

3. Treating clause (iii) interest-free loans to group companies as routine Under clause (iii), the auditor must comment whether terms of loans and advances are prejudicial to the company's interest. An interest-free loan of Rs. 50 lakh to a wholly-owned subsidiary at a time when the parent is itself servicing bank borrowings at 10% per annum is materially prejudicial. Document your assessment and, where applicable, qualify — do not wave it through as "per management representation."

4. Leaving genuinely inapplicable clauses blank rather than marking them "Not Applicable" Clause (xii) on Nidhi companies and clause (xvi) on RBI registration are inapplicable to the vast majority of companies. Mark them Not Applicable with a one-line reason (e.g., "The company is not a Nidhi company as defined under Section 406 of the Companies Act 2013"). A blank field in the exported report looks like an incomplete audit — because it is one.

5. Not correlating clause (ix) with banker's documentation Clause (ix) asks whether the company has defaulted on repayment of loans or borrowings to banks, financial institutions or debenture holders. Management will almost always say no. Independently obtain loan account statements or banker's certificates and verify that every instalment due during the year was paid on or before the scheduled date. Regularisation before the year-end does not eliminate the disclosure obligation — a default that occurred and was subsequently cured must still be reported.

6. Audit trail qualification scope too narrow Many firms qualify the audit trail remark only for the main accounting system. If payroll runs through a separate HR platform, manufacturing data feeds into a production module and expense claims are processed via an app — each of these is a sub-system. The Rule 11(g) remark covers all software used in the preparation of the financial statements. Scope it comprehensively.

NFRA Scrutiny and the 2026 Audit Quality Baseline

The National Financial Reporting Authority (NFRA), established under Section 132 of the Companies Act 2013, has published inspection reports citing deficient CARO documentation as a top-three finding across both large and mid-tier audit firms. The ICAI Quality Review Board reaches similar conclusions for smaller practices.

What regulators look for in a CARO audit file:

• One working paper per clause — not a general audit memorandum that "covers the CARO requirements." Clause-level documentation.
• Source documents in the file — signed physical verification reports for clause (i), challan printouts for clause (vii), bank certificates for clause (ix), management confirmation for clauses (xi) and (xix).
• Documented partner-level review before the audit report date — not a casual verbal review, not a sign-off backdated after filing.
• Numerical consistency — every figure stated in a CARO clause must trace exactly to the audited financial statements. Rounding differences and amounts from draft financials that changed before finalisation are a common source of inconsistency.
• Evidence of professional scepticism — at minimum, a documented discussion of management representations before accepting them for clauses covering fraud, going concern and related parties.

Gen Bal's attachment module and partner sign-off functionality directly support these requirements. But the software organises; the auditor exercises judgement. Regulators are inspecting both.

Choosing Between CARO Generation Tools

For context, here is how the main tools in the Indian market compare for CA firms doing statutory audit work in 2026:

The primary reason professional firms standardise on a single tool across their practice is output consistency. When an NFRA inspector or peer reviewer opens any audit file in your practice, encountering the same CARO structure, the same attachment protocol and the same partner sign-off format across every engagement is itself an indicator of quality discipline — regardless of which tool generates it.

Key Takeaways

• CARO 2020 is mandatory for FY 2026-27 for all companies except those meeting the small company thresholds or the private company exemption (all three conditions: paid-up capital + reserves ≤ Rs. 1 crore, borrowings ≤ Rs. 1 crore, revenue ≤ Rs. 10 crore). Verify applicability at engagement planning stage and document it.
• Gen Bal reduces CARO drafting time by 60–70% on standard engagements through pre-loaded templates, trial balance linkage and a clause-level attachment module — but every software-generated remark must be backed by a working paper before partner sign-off.
• Clause (vii) is the highest-risk clause for most operating companies: run a due-date-versus-payment-date reconciliation across TDS (via TRACES), GST (via GSTR-9 and payment history), EPF (via ECR receipts) and ESI — amounts outstanding beyond six months must be explicitly named with authority, amount and due date.
• Audit trail is reported under Rule 11(g) of the Companies (Audit and Auditors) Rules 2014, not as a CARO clause. Clause (xvii) covers cash losses. Keep the terminology correct, especially in files subject to NFRA inspection.
• The six most consequential mistakes are: rolling forward prior-year remarks without verification, missing six-month arrear disclosures in clause (vii), leaving inapplicable clauses blank, failing to correlate clause (ix) with independent bank documentation, scoping audit trail remarks too narrowly to the primary accounting system, and backdating partner sign-off.
• NFRA and the ICAI Quality Review Board inspect clause-level documentation, not just the face of the CARO report. Treat Gen Bal's attachment feature as a compliance asset — a file without clause-level evidence is a regulatory liability, not an audit file.
• A software-generated, working-paper-backed, partner-reviewed CARO 2020 report is the professional baseline for FY 2026-27. Anything less is a disciplinary exposure waiting for the next inspection cycle.