Form 3CD in an Afternoon: All 44 Clauses, JSON-Ready for the Portal
"Are all the clauses available, or are you still working on it?" is a question we hear in nearly every Form 3CD-related conversation, and it's a fair one — Form 3CD, the Statement of Particulars under Rule 6G(2) read with Section 44AB, is 44 clauses covering everything from books-of-account identification to TDS/TCS compliance tables to related-party transaction disclosures. A tool that handles the easy clauses and quietly stops at the hard ones isn't really automating the tax audit, it's automating the parts that were never the bottleneck.
Not all 44 clauses are the same kind of problem
The honest starting point is that Form 3CD's clauses split into genuinely different categories of work, and treating them identically is where automation claims usually overreach.
Identity and structural clauses (1-7) — legal name, address, registration details, nature of business — are the kind of thing that should pull automatically from authoritative sources like the MCA21 database by CIN, with the auditor confirming rather than re-keying.
Computational and factual clauses — depreciation (Clause 18), Section 43B statutory dues (Clause 26), TDS/TCS compliance tables (Clause 34), Section 43CA/50C property transaction checks (Clause 17) — are where structured extraction from the ledger genuinely works well, because the answer is derivable from the books themselves.
Judgement clauses are the ones that shouldn't be silently auto-concluded, and any tool that claims to "complete" them without auditor input should be treated with real suspicion. Clause 8A (whether the assessee has opted for the Section 115BAC regime) and Clauses 13/14 (ICDS adjustments under Section 145A) turn on interpretation the ledger doesn't settle by itself. Clause 36A (deemed dividend under Section 2(22)(e)) depends on accumulated profits and shareholding structure the trial balance doesn't state. The honest approach is to draft these as candidates, citing the specific section and the specific fact pattern that triggered the draft, and leave the conclusion to the auditor — never present a drafted position as a concluded one.
What actually gets you to "an afternoon"
The time saving isn't from skipping the judgement clauses — it's from not manually re-deriving the ~30 clauses that genuinely are computable from data you already have. On CORAA, the Form 3CD module composes all 44 clauses with reconciliation embedded directly into the relevant ones — TDS/TCS compliance cross-checked against 26AS in Clause 34, Section 43B statutory dues traced to payment evidence in Clause 26 — so the clauses that are fundamentally a data-extraction-and-cross-check exercise are handled as exactly that, freeing the afternoon for the handful of clauses that actually need a partner's judgement.
The JSON output matters for a separate, practical reason: the income tax portal, and filing software like Genius or Winman, expect a specific structured format, and manually transcribing 44 clauses' worth of figures into that format is its own source of transcription error, independent of whether the underlying figures were right. Portal-ready JSON output removes that second failure mode entirely.
What this season's Form 3CD is up against
Worth flagging for anyone reading this closer to a transition: the Income Tax Act 2025 consolidates Forms 3CA, 3CB, and 3CD into a single 53-clause Form 26 under Section 63, effective from Tax Year 2026-27 onwards (first due 30 September 2027) — but the AY 2026-27 audit, due 30 September 2026, still runs entirely on the current 44-clause Form 3CD structure. It's genuinely the last season for the form as it exists today, which is exactly the kind of transition detail worth having right rather than assumed.
What to check before trusting a "complete" Form 3CD tool
Ask specifically which clauses draft automatically from ledger data versus which are presented as candidates requiring your conclusion — a tool that can't articulate that distinction is either overclaiming or hasn't actually thought about where the line belongs. And check the reconciliation: does Clause 34's TDS table actually cross-reference 26AS, or is it just a formatted restatement of what's in the ledger with no independent check against the return data.
Frequently Asked Questions
How many clauses does Form 3CD have, and does automation cover all of them?
44 clauses under Rule 6G(2). Identity clauses (1-7) and computational/factual clauses (like depreciation, Section 43B dues, TDS/TCS tables) are well-suited to automated drafting from ledger data. Judgement clauses (8A, 13/14, 36A) are drafted as candidates with the relevant section cited — never auto-concluded.
What does "JSON-ready for the portal" actually save?
It removes the manual-transcription failure mode — the income tax portal and filing software like Genius/Winman expect a specific structured format, and hand-transcribing 44 clauses into that format is a separate error source from whatever's in the underlying figures.
Is this the last season for the current 44-clause Form 3CD?
Yes for most filers — the Income Tax Act 2025 replaces Forms 3CA/3CB/3CD with a single 53-clause Form 26 from Tax Year 2026-27 onwards (first due 30 September 2027). The AY 2026-27 audit, due 30 September 2026, still uses the current 44-clause structure.
Does the tool decide Clause 8A or Clause 36A for me?
No — these are judgement clauses that depend on facts and interpretation the ledger doesn't fully capture (the Section 115BAC election, or shareholding and accumulated-profits detail for deemed dividend under Sec 2(22)(e)). They draft as candidates with the governing section cited, not as concluded positions.
Related: Form 3CD module · Start a free trial