AOC-4 XBRL is not a filing route reserved only for listed companies. A private or unlisted company can also be pulled into XBRL because of its paid-up capital, turnover or Ind AS reporting position. The useful way to decide the form is therefore to test the company against the XBRL rules first, and only then prepare the annual filing package.
The statutory starting point is Rule 3 of the Companies (Filing of Documents and Forms in Extensible Business Reporting Language) Rules, 2015, as substituted in 2017. The MCA notification substituting Rule 3 sets out the applicability tests. If the MCA PDF is inconvenient to open, a readable text reproduction of the Gazette notification is also available as a secondary reference.
The four tests that make AOC-4 XBRL applicable
Rule 3 identifies four classes. A company should test each one independently because satisfying any one of them can bring the financial statements into the XBRL filing route:
- Listed-company test: companies listed with stock exchanges in India and their Indian subsidiaries.
- Paid-up capital test: companies having paid-up capital of ₹5 crore or above.
- Turnover test: companies having turnover of ₹100 crore or above.
- Ind AS test: all companies required to prepare their financial statements in accordance with the Companies (Indian Accounting Standards) Rules, 2015.
The fourth test is easy to overlook. A company does not become outside XBRL merely because its paid-up capital is below ₹5 crore and turnover is below ₹100 crore. If it is required to prepare financial statements under Ind AS, Rule 3 separately brings it within AOC-4 XBRL.
The exemption list should be read from the current Rule 3 text, not an old checklist
The 2017 substituted Rule 3 expressly exempts non-banking financial companies, housing finance companies, and companies engaged in the banking and insurance sectors from filing financial statements under these XBRL rules. That exemption is important because an entity may otherwise appear to satisfy one of the general triggers.
Older XBRL material can create another problem: some historical checklists still show a power-sector exemption. The substituted 2017 Rule 3 exemption proviso does not list the power sector. That does not mean every power company automatically files AOC-4 XBRL; the company must still satisfy an applicable Rule 3 trigger. It means a filing team should not carry an old power-sector exemption forward without checking the operative rule.
XBRL changes the filing format, not the underlying financial-statement responsibility
XBRL is a structured, machine-readable representation of the financial statements. It does not replace the company’s approved and signed financial statements. Rule 12 of the Companies (Accounts) Rules, 2014, as reflected in the ICSI Companies Act e-book on filing financial statements, requires the relevant AOC-4 filing and also addresses the XBRL route. The current text records that signed financial statements, including the Board’s report, auditor’s report and other required documents in PDF form, are also attached with XBRL forms.
That distinction matters in practice. The XBRL instance should be built from the final approved reporting set, not from an earlier trial balance or an unreconciled draft. A late adjustment to the signed financial statements should trigger a corresponding check of the tagged XBRL data before filing.
How the XBRL filing workflow fits together
The filing process is more than attaching an XML-style file to a form. The MCA’s XBRL workflow requires financial information to be mapped to the applicable taxonomy, converted into an instance document, validated and pre-scrutinised before the instance is attached to AOC-4 XBRL. MCA’s current portal notices also state that the V3 XBRL schema is the live schema route and that stakeholders should use the current MCA XBRL validation tool when filing AOC-4 XBRL. Because schema and utility versions can change, the current MCA portal notices should be checked immediately before a live filing.
A practical sequence is:
- Freeze the approved reporting set. Start from the financial statements and reports approved for the statutory filing process, not an earlier management-accounting version.
- Choose the correct taxonomy. The Rule 3 framework distinguishes the taxonomy used for companies preparing under Accounting Standards from the taxonomy used for Ind AS reporters.
- Map each disclosure carefully. Financial-statement line items, notes and required disclosures should be mapped to the appropriate taxonomy elements. A technically valid tag can still be a poor accounting mapping if it does not represent the underlying disclosure faithfully.
- Create and validate the instance document. Run the current MCA validation tool and resolve validation errors rather than treating them as a portal problem to be bypassed.
- Pre-scrutinise and perform a final comparison. Compare the rendered or human-readable output back to the signed financial statements, including totals, signs, units, comparative figures and note relationships.
- Attach the XBRL instance and required signed documents to the correct filing. Keep the instance document, signed PDFs and form data aligned to the same reporting period and approved numbers.
A simple applicability example
Hypothetical example: Assume an unlisted private company has paid-up capital of ₹3 crore and turnover of ₹72 crore. On those two numbers alone, it does not cross the ₹5 crore paid-up capital test or the ₹100 crore turnover test. If, however, the company is required to prepare its financial statements under Ind AS, the separate Ind AS limb of Rule 3 brings it into the XBRL filing class, subject to the sector exemptions in the rule.
Now change the facts: assume the company is not an Ind AS reporter, but its paid-up capital is ₹6 crore. The capital trigger is enough; it does not need to cross the turnover threshold as well. The Rule 3 tests are alternatives, not a cumulative scorecard.
Do not confuse XBRL applicability with the Section 137 filing clock
AOC-4 XBRL sits inside the broader financial-statement filing obligation under Section 137. The current Section 137 text in the ICSI Companies Act e-book states the general rule that duly adopted financial statements and the required accompanying documents are filed with the Registrar within 30 days of the annual general meeting. Section 137 also contains separate treatment where statements are not adopted at the AGM, where no AGM is held, and for One Person Companies.
The form decision and the deadline decision should therefore be documented separately. First identify whether the company is in the XBRL class; then calculate the statutory filing date from the facts that apply to that company. CA Samaaj’s separate company annual filing workflow explains the wider AOC-4 and annual-return cycle without duplicating the XBRL applicability analysis here.
What a defensible year-end file should show
Before the filing is signed off, the working papers should make it possible for another reviewer to understand why AOC-4 XBRL was or was not selected. A concise file can record:
- listing status and whether an Indian subsidiary relationship triggers the listed-company limb;
- paid-up capital and turnover used for the Rule 3 tests;
- whether the company is required to prepare financial statements under Ind AS;
- whether a specific Rule 3 sector exemption applies;
- the taxonomy selected for the reporting framework;
- evidence that the validated XBRL output reconciles to the signed financial statements; and
- the Section 137 trigger date and resulting filing due date.
The key control is to separate three questions that are often mixed together: Does XBRL apply? Which taxonomy and current MCA utility should be used? What is the Section 137 filing date? Answering them in that order prevents most form-selection errors and avoids relying on old exemption lists or stale utility instructions.
