Form ADT-4 Mechanics Under Section 143(12): The 60-Day Clock That Ends Careers
In the NFRA enforcement orders tracker, one failure pattern shows up disproportionately: the auditor identified or suspected fraud, audit work was substantially complete, the underlying conclusions were defensible — but the Form ADT-4 filing was late or never made. Section 143(12) of the Companies Act 2013 prescribes both the substantive obligation and the timeline, and the timeline has teeth.
The Religare Finvest order (January 2025), the Zee Entertainment order against Deloitte Haskins & Sells LLP (December 2024), and earlier orders against Reliance Capital and RHFL all cite Section 143(12) delay or omission as a primary finding. This post breaks down the mechanics of ADT-4 — the 2-day / 45-day / 15-day breakdown — and what an auditor must do the moment a fraud red flag appears.
What Section 143(12) actually says
Section 143(12) of the Companies Act 2013:
"Notwithstanding anything contained in this section, if an auditor of a company in the course of the performance of his duties as auditor, has reason to believe that an offence of fraud involving such amount or amounts as may be prescribed, is being or has been committed in the company by its officers or employees, the auditor shall report the matter to the Central Government within such time and in such manner as may be prescribed."
Rule 13 of the Companies (Audit and Auditors) Rules 2014 prescribes:
- Threshold for Central Government reporting: ₹1 crore or more.
- Form: ADT-4 (electronic filing via MCA21 portal).
- Timeline: 60 days from the date of "knowledge" of the suspected fraud.
- Sub-threshold (below ₹1 crore): Report to Audit Committee (or Board if no AC) within 2 days. Disclosure in Board's Report under Section 134(3)(ca).
The 60-day timeline is not a single block. It breaks into a specific sequence the Rule prescribes:
- Days 1-2 — Auditor writes to the Board / Audit Committee describing the suspected fraud, asking for reply within 45 days.
- Days 3-47 — Board / AC has 45 days to respond.
- Days 48-60 — Auditor, having received (or not received) the reply, files Form ADT-4 with the Central Government via MCA21 portal. Includes the auditor's report on the matter and the management's reply (if received).
So the 60-day clock starts on the date the auditor has reason to believe an offence of fraud has been committed. That date is the most-contested factual question in NFRA enforcement orders.
"Reason to believe" — when does the clock start?
The phrase "reason to believe" is the trigger. NFRA orders interpret this as the date the auditor has objective, demonstrable basis to suspect fraud — not the date of final confirmation. This is a lower threshold than "knowledge of fraud beyond reasonable doubt."
In the Religare Finvest order (CA Neeraj Bansal, January 2025), NFRA found that the auditor had access to information about a ₹2,036 crore corporate-loan-book fraud well before he filed ADT-4. Specifically, NFRA cited:
- Previous-auditor's resignation letter flagging the fraud
- Internal SFIO report shared with the auditor
- Corporate Affairs Ministry communications
Once any of these inputs is on the auditor's desk, the 60-day clock starts.
In the Reliance Capital order (Pathak H.D. & Associates, April 2024), NFRA cited that the auditor had access to Price Waterhouse's reported suspected fraud of ~₹12,571 crore in loans to group companies — yet failed to act on the information. The penalty: ₹3 crore on the firm + ₹1 crore on the engagement partner + 10-year debarment for the EP.
The implication for auditors: the moment a fraud red flag arrives (resignation letter from prior auditor, regulator communication, internal whistleblower, significant unexplained transaction), document it with a timestamp. The clock has started.
The "2 days" — most underestimated step
The first action under Section 143(12) is to write to the Board / Audit Committee within 2 days. This is not a casual email. The communication must:
- Describe the suspected fraud with specific facts — amount involved, nature of transaction, persons implicated (if known).
- Request a reply within 45 days in writing.
- State the auditor's intention to report to Central Government if no satisfactory reply is received within 45 days.
- Be issued on firm letterhead with proper signature and dispatch record.
A common error: the auditor raises the fraud informally in a meeting, gets verbal assurances from management, and treats that as the "communication." NFRA does not. The formal letter on firm letterhead is the documentary anchor — without it, the 60-day calendar arguments don't hold.
Where to find the model letter format: ICAI's Implementation Guide on Reporting on Fraud under Section 143(12) provides a sample template. The Form ADT-4 template on CORAA's templates library includes the precursor communication letter to the Audit Committee.
The 45-day reply — what counts as "satisfactory"
Rule 13(2)(c) — the auditor must consider the Board / Audit Committee's reply on its merits. A satisfactory reply typically:
- Confirms or refutes the auditor's suspicion with specific factual basis
- If confirms — describes the management's remedial actions, internal investigation report, recovery / restitution steps
- If refutes — explains why the auditor's belief is mistaken, with documentary support
- Is signed by an authorised person (Chairman of Audit Committee or Company Secretary on Board's behalf)
A reply that says "we are investigating and will revert" is NOT satisfactory. Neither is a reply that disputes the auditor's belief without contrary evidence. NFRA's interpretation has been strict — if the auditor accepts a thin reply and skips filing ADT-4, NFRA treats that as the auditor's failure, not management's.
If no reply arrives by day 47, the auditor proceeds to file ADT-4 within the remaining 13 days.
The Form ADT-4 itself — what to file
Form ADT-4 is filed via the MCA21 portal under "Auditor's Reports". Required content:
- Particulars of the company (CIN, name, registered office)
- Particulars of the auditor (firm name, FRN, signing partner's membership number)
- Details of the fraud: nature, amount, period, persons involved (if known)
- Audit procedures performed that led to the suspicion
- Management's reply (attached as enclosure) — or noted "no reply received"
- Auditor's conclusion on the suspected fraud
- Date of first knowledge / first reasonable belief
- Communication trail with Board / AC (attached)
The Form is reviewed by the Ministry of Corporate Affairs and may be referred to SFIO (Serious Fraud Investigation Office) for formal investigation. The auditor's report becomes the basis of the SFIO mandate.
For the auditor, filing ADT-4 closes the Section 143(12) obligation. It does NOT make the auditor a defendant in any subsequent proceeding — the auditor is the reporter, not the accused. (Unless the auditor was complicit, in which case NFRA / ICAI / CBI proceed separately.)
The penalty for failure
Failure to file ADT-4 within 60 days, where filing was required, has been the explicit basis of NFRA enforcement orders:
- Religare Finvest (Bansal, January 2025) — ₹5 lakh penalty + 5-year debarment. Primary basis: delay in Section 143(12) reporting of ₹2,036 cr Corporate Loan Book fraud.
- Zee Entertainment (Deloitte HSL, December 2024) — ₹2 crore on firm + 5-year debarment for engagement partner. Citations included failure to report suspected fraud on ₹200 cr pledged FD.
Beyond the NFRA penalty, Section 143(15) provides for ICAI Council to take cognisance — leading to professional misconduct proceedings and possible removal from the Register of Members. And under Section 147(5), the company itself can recover damages from the auditor for losses caused by the auditor's failure to discharge Section 143(12).
What about below the ₹1 crore threshold?
For fraud below ₹1 crore, Section 143(12) read with Rule 13 requires:
- Report to the Audit Committee (or Board if no AC) within 2 days of identification
- Description with circumstances, amount involved
- Disclosure in the Board's Report under Section 134(3)(ca) — categorised by nature of fraud
The auditor does NOT file ADT-4 for sub-₹1cr items. But this is not a free pass — the disclosure in the Board's Report is itself a public document and subject to peer review / NFRA scrutiny.
A common audit error: identifying a ₹40 lakh employee embezzlement, reporting to AC, but failing to ensure the disclosure makes it into the Board's Report. The auditor must verify the disclosure landed correctly in the Director's Report — and if not, modify the audit report accordingly.
How CORAA helps
The Section 143(12) workflow is not just about the filing — it's about the audit trail that leads to the filing. CORAA's Scrutiny module flags transactions that meet fraud red-flag patterns (round-number journal entries at year-end, unusual related-party transactions, suspense routing, post-period adjustments) across 100% of ledger entries. Each flag is timestamped immutably — establishing the "date of first reasonable belief" with cryptographic certainty.
For the audit team, this matters in two ways:
-
Earlier detection — flags surface during audit fieldwork, not during management's response. The 60-day clock starts earlier and there's adequate time for the 2-day + 45-day + 15-day sequence.
-
Defensible documentation — if NFRA later asks "when did the auditor first have reason to believe?", the CORAA flag timestamp is the answer.
The SA 240 Journal Entry Risk Scorer helps score individual JEs against the 16 red-flag criteria. The going concern indicator scorer covers SA 570 considerations that often pair with fraud (cash-flow deterioration is a leading fraud indicator).
A practical timeline — example
A junior team member spots an unexplained ₹1.2 cr inter-company transfer dated 28 February with no documentation. Date of identification: 5 March (after team review).
| Day | Date | Action |
|---|---|---|
| 1 | 5 March | Team identifies transaction. Engagement partner reviews. Reasonable belief formed. |
| 2 | 6 March | Letter dispatched to Audit Committee on firm letterhead. Substantive description, request for reply within 45 days. |
| 3-47 | 7 Mar - 20 Apr | Wait for reply. Continue other audit procedures. Document any further evidence. |
| 47 | 20 April | Reply received: "The transfer was a temporary loan; will be reversed by 31 March." No supporting documentation. Auditor judges reply unsatisfactory. |
| 48-60 | 21 April - 4 May | Prepare Form ADT-4 with all attachments. Get partner sign-off. File via MCA21. |
| 60 | 4 May | Form ADT-4 filed. Section 143(12) closed for this matter. |
If the reply at day 47 had been: "The transfer was an erroneous accounting entry; original entry attached; reversed entry attached; revised ledger attached," that would have closed the suspicion. The auditor would document the satisfactory reply and not file ADT-4.
The judgement on "satisfactory" is the auditor's. NFRA second-guesses it after the fact. Document the reasoning.
Bottom line
Section 143(12) is one of the most strictly-enforced auditor obligations in Indian audit law. The 60-day clock is non-negotiable. The 2-day initial communication is the documentary anchor. A weak "we'll investigate" reply does not close the obligation. NFRA enforcement orders consistently cite delay or omission as the primary failure — even where the audit work was substantially complete.
For audit firms, build the workflow:
- Train every audit team member to recognise fraud red flags and escalate within 24 hours.
- Maintain a fraud-suspicion register at the engagement level — every flag with timestamp.
- Have a partner-level review every flag within 48 hours.
- Document the date of "reasonable belief" with the basis.
- Issue the 2-day letter on firm letterhead with proper dispatch record.
- Track the 45-day reply window in your project management system.
- File ADT-4 by day 60 — no exceptions.
The Form ADT-4 template on CORAA's templates library includes the precursor communication letter, the ADT-4 form, and the SA 230 documentation index for the entire workflow.
See CORAA → Built to surface fraud red flags during fieldwork, not after. India-hosted, audit-grade evidence trail. Talk to us or see Scrutiny module.