Five distinct CARO clauses carry GST-specific obligations. Each triggers a different audit response — from clean report to ADT-4 fraud filing to MCA central government report.
Senior practitioner clarity: "CARO Para 13" is informal shorthand often used to describe the broader GST-related reporting requirement. The formal numbering is Clauses 3(vi), 3(vii), 3(viii), 3(xi), and 3(xiii) of the Companies (Auditor's Report) Order, 2020. Understanding which clause fires for which GST scenario determines whether the auditor issues a qualification, an emphasis of matter, or files ADT-4 with the Central Government.
3(vii)
GST dues — undisputed (>6 months) and disputed dues at every forum
3(viii)
Off-books transactions surrendered or disclosed in IT assessments
ADT-4
Mandatory fraud report to Central Govt when GST gap ≥ ₹1 Cr = fraud
Clause
What it covers — GST dimension
Audit outcome
The three-layer GST-CARO reporting obligation
Layer 1 — Statutory dues
CARO 3(vii)(a): Is the company regular in depositing GST? Undisputed GST outstanding >6 months at year-end must be quantified and reported with period and due date.
Key source: GSTN Electronic Liability Register + Electronic Cash Ledger. Not just the books entry — portal data is independent evidence.
Layer 2 — Disputed dues
CARO 3(vii)(b): All disputed GST demands must be listed with forum (ASMT/First Appeal/Tribunal/HC/SC), nature, and amount. Each pending notice is a separate line.
Key source: GST portal case status + litigation tracker + management representation letter.
Layer 3 — Off-books transactions
CARO 3(viii): If GST return data reveals supplies not in books — are they income surrendered in IT assessments? Have they now been recorded? Most under-reported aspect.
Key source: GSTR-1 vs P&L + E-way bill vs dispatch records + AIS/26AS vs booked income.
Why this matters more than ever — Project Saksham integration
The three-database triangulation (FY 2021-22 onwards)
CBDT and CBIC data-sharing under Project Saksham means: GSTR-3B turnover is now uploaded to Form 26AS (Part F). MCA RoC filings are cross-referenced with GSTR-9C. AIS shows GSTR-1 invoice values alongside banking credits. The auditor, the GST department, and the income tax department are now looking at the same three numbers simultaneously. Any company whose P&L revenue, GST turnover, and AIS banking credits do not broadly align — is automatically flagged on all three systems at once.
For the auditor: This integration creates a professional obligation beyond CARO. If the auditor signs off on FS showing ₹50 Cr revenue while the client's GSTR-1 shows ₹65 Cr turnover — without an explanation in the Notes — the auditor's own professional credibility is on the line when the ASMT notice inevitably arrives.
Module 02 — The Core Problem
How GST returns show more than the books
Four scenarios — from legitimate timing differences to fraud. The auditor's job is to classify each gap correctly and report accordingly.
The decision matrix — what each gap means
Gap classification framework
Before deciding on CARO reporting, every GSTR-1 vs P&L gap must be classified into one of four buckets. Only one bucket requires adverse reporting.
BUCKET A — LEGITIMATE (No CARO issue)
Inter-GSTIN branch transfers (Schedule I)
Advance GST paid before Ind AS 115 revenue recognition
Post-year-end credit note timing difference
Export turnover cut-off timing
Action: Explain in GSTR-9C Part II + FS notes
BUCKET B — ACCOUNTING ERROR (CARO 3(vii))
GST on free samples not recognised in GSTR-1 (overclaim by officer)
Rate classification error — wrong HSN applied
Double-counting due to GSTR-1 amendment not reversed in books
Action: Correct in books + disclose + CARO 3(vii) if tax short-paid
BUCKET C — SUPPRESSION (CARO 3(viii))
Cash sales in GSTR-3B not booked in P&L
Surrendered income in IT assessment — not recorded in books
E-way bill value with no matching invoice or booking
Action: CARO 3(viii) adverse + require management to record + management letter
BUCKET D — FRAUD (ADT-4 mandatory if ≥ ₹1 Cr)
Systematic GST paid on sales but sales not booked — structured scheme
Fake ITC claims using non-existent supplier invoices
Circular transactions through group entities to inflate ITC
Action: ADT-4 to Central Govt + CARO 3(xi) qualification + possible police report
Module 03 — Audit Execution
Step-by-step procedure — GST-books reconciliation under CARO
Seven audit steps — from portal data extraction to management representation. Each step is a working paper requirement under SA 230 (Documentation).
Key data sources — what the auditor obtains independently
From GST portal (independent access)
GSTR-1 summary — all 12 months + amendments
GSTR-3B summary — tax paid, ITC claimed
GSTR-9 draft — annual return data
Electronic Liability Register — all liabilities raised
Electronic Cash Ledger — all tax payments
Electronic Credit Ledger — ITC balance
GSTR-2B — vendor-wise ITC available
E-way bill summary — from NIC EWB portal
From IT portal / AIS (cross-verification)
Annual Information Statement — Part F (GSTR-3B data)
Form 26AS — banking credits, TDS, TCS data
ITR filing — turnover per Schedule BP / P&L
IT assessment orders — additions, surrenders
Form 3CD — Clause 44 expense breakup by GST
Search/survey statements (if any)
Vivad Se Vishwas / settlement disclosures
SA 240 — When fraud risk procedures apply
SA 240 (The Auditor's Responsibilities Relating to Fraud) requires the auditor to assess fraud risk factors at planning stage. In a GST context, fraud risk indicators include:
Significant unexplained gap between GSTR-1 turnover and P&L revenue where management is evasive
Multiple GSTINs for same PAN with no clear business rationale — possible circular invoicing
Large ITC claims from suppliers who are newly registered, have low turnover, or are untraceable
Cash sales constituting a disproportionate share of GSTR-3B B2C turnover vs industry norms
Management refuses to provide portal access or relies only on management-prepared reconciliation
When fraud risk indicators are present: extend audit procedures, obtain independent confirmations from key customers (SA 505), and document all enquiries and management responses. If fraud confirmed at ≥ ₹1 Cr — ADT-4 is mandatory regardless of management's preference.
Module 04 — Specimen Language
Ready-to-use CARO report language — GST clauses
Six specimen paragraphs covering every outcome — clean, qualified, emphasis of matter, and ADT-4 scenarios. Click to copy any specimen.
Module 05 — Mandatory Disclosures
Schedule III 2021 amendment — GST disclosures in FS notes
MCA notification dated 24 March 2021 made these GST disclosures mandatory for all companies from FY 2021-22. The auditor must verify each is present and accurate.
What the 2021 amendment requires
The amendment inserted specific GST-related disclosure requirements across the Balance Sheet, Profit and Loss Account, and Notes to Accounts in Schedule III. These are mandatory — not best practice or voluntary. An auditor who clears a FS without these notes has technically cleared an incomplete set of financial statements.
The ICAI Technical Guide on GSTR-9C (December 2025 edition) specifically addresses how the Schedule III disclosures must reconcile with GSTR-9C Part II and III — creating a continuous chain of accountability from FS → GSTR-9C → GST portal → AIS.
Schedule III GST disclosure checklist0/0 verified
Module 06 — Fraud Reporting
ADT-4 — when the GST gap is fraud, not a timing difference
Section 143(12) Companies Act 2013 + Rule 13, Companies (Audit and Auditors) Rules 2014. Non-filing is itself an offence with criminal liability for the auditor.
Critical: ADT-4 is NOT optional once the threshold is met. The auditor does not get to exercise judgment on whether to file. Section 143(12) uses the word "shall" — it is a mandatory obligation. An auditor who detects fraud of ≥ ₹1 crore and does not file ADT-4 is personally liable for prosecution under Sec 143(15) of the Companies Act — imprisonment up to 1 year and/or fine up to ₹25 lakh.
ADT-4 procedure — timeline and steps
GST scenarios that mandate ADT-4
Systematic cash sales in GSTR-3B not booked in accounts — structured suppression scheme
Fake ITC claims using invoices of non-existent or shell suppliers
Circular transactions through group entities to generate fraudulent ITC
Directors/management using company GSTIN to claim ITC on personal purchases
E-way bills for goods movement to unknown parties — possible diversion + suppression
GSTR-1 filed with fabricated invoice data inflating turnover for loan purposes
GST scenarios that do NOT mandate ADT-4
Legitimate timing differences — advance GST, Ind AS 115 recognition
Inadvertent error in HSN classification or rate application
Inter-GSTIN branch transfers correctly explained in GSTR-9C
ITC reversal under Rule 42 not done (procedural lapse, not fraud)
GSTR-1 amendment filed but books not updated — accounting error
RCM liability missed — negligence but no intent to defraud
CARO 3(xi)Specimen — fraud report language when GST-related fraud detected
(xi) During the year, we have detected/reported a fraud on/by the Company in the following matter:
During the course of our audit, we have reason to believe that fraud has been committed by [officers of the Company / the Company itself] involving an amount of approximately ₹X crores. The fraud pertains to [describe: e.g., non-recording of cash sales in books of account while reflecting the same in Goods and Services Tax returns filed under the Central Goods and Services Tax Act, 2017, thereby resulting in understated revenue from operations in the statement of profit and loss for the year ended 31st March 20XX].
A report in this regard has been filed with the Central Government in Form ADT-4 pursuant to Section 143(12) of the Companies Act, 2013 read with Rule 13 of the Companies (Audit and Auditors) Rules, 2014. The Board of Directors / Audit Committee was informed of this matter on [date], and their reply was received on [date].[Note: Include details of the fraud — nature, period, amount, officers involved, and whether police report has been filed. The CARO report must reference the ADT-4 filing.]
Module 07 — Management Response
The CFO's playbook — turn CARO from threat to clean report
Five qualification scenarios and how to prevent each. The auditor who receives a clean, documented reconciliation on Day 1 of fieldwork verifies — not investigates.
The fundamental principle
The auditor will run the GSTR-books reconciliation regardless. Management's only protection is having a pre-prepared, documented reconciliation that explains every line item before the auditor asks. A CFO who hands the auditor a clean, signed reconciliation worksheet on Day 1 of fieldwork changes the entire dynamic — the auditor verifies, not investigates. A CFO who scrambles to explain during fieldwork loses control of the narrative, the timeline, and the final outcome.
Pre-audit documentation — what management must prepare
Primary reconciliation documents
GSTR-9C reconciliation worksheet (CFO-signed): P&L revenue → GSTR-1 turnover. Every adjusting line with amount, nature, and ledger reference
Branch transfer schedule: All inter-GSTIN transfers during year, value, rate, GSTR-1 invoice numbers
Credit note log: All credit notes, original invoice cross-referenced, GSTR-1 amendment month
E-way bill reconciliation: Every e-way bill → invoice or job work challan or sample dispatch or purchase return
Supporting compliance documents
ITC reversal register: Rule 37, Rule 42, Sec 17(5) — month-wise with reasons and amounts
Dispute register: All ASMT/SCN/DRC-01/Appeal orders — current status, amount, provision vs contingent note classification
GST interest provision: Sec 50 computation at 18% p.a. on all identified late payments
IT assessment summary: All IT orders completed during year — additions, surrenders, and corresponding FS treatment
MSME payables list: Payables to MSME suppliers with payment dates — Sec 43B(h) IT + Sec 16(2) GST dual compliance
The five most common CARO qualifications — and how to prevent each
The closing message for the boardroom
CARO 2020 transformed the statutory auditor into an involuntary GST compliance verifier. The auditor who once said "I audit accounts, not tax returns" now must reconcile GSTR-1 to P&L, verify e-way bills against dispatch records, check ITC reversals against Rule 42 computations, and evaluate whether a GST-books gap is a timing difference or a fraud. The CFO who builds a clean reconciliation trail before fieldwork begins turns a potential qualification into a clean report in three days. The one who does not turns a ₹50 lakh gap into a ₹5 crore qualified opinion, an ASMT investigation, and a boardroom explanation.