XBRL filing of AOC-4 is mandatory for listed companies, for companies with paid-up capital of ₹5 crore or more, and for companies with turnover of ₹100 crore or more, under the Companies (Filing of Documents and Forms in XBRL) Rules, 2015. The ₹5 crore figure applies to paid-up capital, not turnover — the most common confusion around this rule. Companies outside these thresholds file AOC-4 in non-XBRL (PDF) format, and XBRL filers must validate their instance document on the MCA portal before submission.
Since MCA21 V3 (June 2025): AOC-4 XBRL is filed in iXBRL format on the V3 portal, with portal-side validation before submission. The XBRL trigger thresholds — listed, paid-up capital ₹5 crore or more, turnover ₹100 crore or more — are unchanged by the portal migration.
What the law actually requires
The Companies (Filing of Documents and Forms in XBRL) Rules, 2015 (as amended) prescribe who must file financial statements in XBRL — eXtensible Business Reporting Language, a tagged electronic format that lets the MCA read every line item of the balance sheet and P&L as data rather than text.
⚠️ — the Rules have been amended over time and the current trigger list should be confirmed against the latest MCA notification. Confirm whether your company (including subsidiaries and companies required to prepare consolidated financial statements) is in scope before the audit closes.
Why the turnover figure causes so much confusion
The brief version of this rule travels as "₹5 crore turnover." That is wrong on the turnover limb — the turnover threshold is ₹100 crore, while the ₹5 crore figure is the paid-up-capital threshold. A company with ₹8 crore of turnover but ₹10 crore of paid-up capital must file XBRL; a company with ₹200 crore of turnover but ₹1 crore of paid-up capital must also file XBRL; a company with ₹3 crore turnover and ₹2 crore paid-up capital need not. The two limbs are tested independently.
The iXBRL format on MCA21 V3
Filing on the MCA21 Version 3 portal is done in iXBRL (inline XBRL) — the human-readable financial statements with the XBRL tags embedded in the same document. This differs from older XBRL filings that separated the instance document from the rendered view. Practically, the accounting/audit software generates the iXBRL file, and it must pass the portal's validation before the form can be attached and submitted.
Worked example: two companies, two formats
Kite Finance is the trap. Its founders assumed "we're too small" because turnover is only ₹3 crore — but the paid-up capital limb (₹5 crore) is triggered by its capital structure, and AOC-4 must be filed in XBRL. Getting this wrong means the form is rejected or treated as defective, and the Section 137 clock keeps running.
What the tagging covers
An XBRL AOC-4 requires every line item of the balance sheet, profit and loss account, statement of changes in equity, and the accompanying schedules to be tagged against the MCA taxonomy — assets, liabilities, equity, revenue, expense heads, contingent liabilities, and the notes. The tagging must reconcile exactly with the figures in the signed financial statements; a mismatch between the audited PDF and the XBRL figures is a red flag on MCA21 v3.
Practical implications
- Confirm scope before the audit closes, not after. XBRL preparation is a separate workstream from drafting the financials. Confirm whether the company crosses either limb before the audit is signed, so the same closing figures feed the XBRL generation.
- The accounting software must support XBRL. The iXBRL output has to match the MCA taxonomy for the relevant year. Confirm the software's taxonomy version is current for the filing year before the balance-sheet date passes.
- Validate on the portal before submission. MCA21 v3 runs validation on upload — errors in tags, entity identifiers (CIN), or the accounting standards applied will bounce the form. A bounced form does not stop the Section 403 late-fee clock.
- Reconciliation is now data-driven. Because the MCA reads XBRL as data, the numbers are cross-checkable against the ITR and GST returns. A material mismatch between AOC-4 XBRL figures and the company's ITR-6 is exactly the kind of inconsistency the MCA21 v3 data-matching layer flags.
Step-by-step: preparing an XBRL AOC-4
- Confirm scope before the audit closes. Check all three limbs — listed status, paid-up capital ₹5 crore or more, turnover ₹100 crore or more — against the company and its subsidiaries. Include companies required to prepare consolidated financial statements where the Rules require it. on the current trigger list.
- Prepare the financial statements in XBRL-enabled software. The balance sheet, P&L, statement of changes in equity and notes must be generated against the MCA taxonomy for the relevant year — not last year's taxonomy version.
- Map every line item to the taxonomy tag. The tagging must capture each line exactly as it appears in the signed statements. A note disclosed in the PDF but missing a tag is a validation failure.
- Validate the instance document on the MCA portal. The portal's validation tool checks entity identifiers, tags and the accounting standards applied. Bounce the errors here, before submission.
- Generate the iXBRL file — the human-readable statements with the tags embedded, as required by MCA21 V3.
- Attach and pre-scrutinise the form, then file with the DSC within 30 days of the AGM.
- Reconcile the XBRL figures with the ITR. Because the MCA reads XBRL as data, a material divergence between AOC-4 XBRL and the company's ITR-6 is exactly what the MCA21 data-matching layer flags.
FAQ
Is AOC-4 XBRL mandatory at ₹5 crore turnover?
No. The ₹5 crore threshold is for paid-up capital. The turnover threshold is ₹100 crore. Both limbs are tested independently.
Which companies must file AOC-4 in XBRL?
Listed companies (and their Indian subsidiaries), companies with paid-up capital of ₹5 crore or more, and companies with turnover of ₹100 crore or more, under the Companies (Filing of Documents and Forms in XBRL) Rules 2015.
What format is used on MCA21 V3?
iXBRL (inline XBRL) — the XBRL tags are embedded in the human-readable financial statements, and the file must pass the portal's validation before the form is submitted.
What if our company is below all thresholds?
File AOC-4 in the normal non-XBRL (PDF) format. The non-XBRL route does not waive the 30-day-from-AGM deadline.
Can a bounced XBRL file extend our deadline?
No. A rejected or defective form does not stop the Section 403 late-fee clock. The 30-day deadline applies regardless of how many validation attempts you need.
Does XBRL change the audit requirement?
No. The financial statements must still be audited and signed before filing; XBRL is the electronic format of the same audited figures, and the tagged amounts must match the signed statements.
Sources
- Companies (Filing of Documents and Forms in XBRL) Rules, 2015 (as amended)
- Section 137, Companies Act 2013 (filing of financial statements); Section 403 (late fee)
- MCA21 Version 3 portal (iXBRL validation and filing)
Use the ROC compliance calendar to time XBRL preparation ahead of the AOC-4 deadline. For a ROC annual-filing compliance audit of your company, visit pvtltd.co.
---
See Also
Ready to incorporate or sort your compliance?
Our team handles every filing. You focus on building.