Skip to main content

Company law · MCA filings

XBRL filing: who must file, and how tagging actually works.

A practical walkthrough for practising CAs and CA-Final students — applicability, the tagging-to-filing process, and the mistakes that get instance documents rejected.

  • Reviewed July 2026
  • 7 min read
  • CA Anil Agarwal & the TatvaBooks team

What is XBRL filing?

XBRL (eXtensible Business Reporting Language) is a structured data format for financial statements. Instead of filing a PDF or scanned copy of the balance sheet and profit & loss account, a company "tags" every line item, note and disclosure to a standard element defined in an MCA-notified taxonomy — so a regulator's system can read and compare the data programmatically across thousands of companies, rather than a human reading each filing individually.

In India, this is done through Form AOC-4 XBRL, filed with the Ministry of Corporate Affairs (MCA) as part of annual filing, in place of the standard Form AOC-4. The underlying financial statements are the same, audited, AGM-approved numbers — XBRL only changes how they are represented for filing.

Which companies must file in XBRL?

XBRL applicability is defined by notified rules under the Companies Act, and the specific thresholds have been revised more than once since XBRL filing was introduced. The framework below reflects the commonly understood applicability classes — treat the exact figures as a starting point, not a citation, and confirm current thresholds on the MCA portal before advising a client.

Category Note
All listed companies And their Indian subsidiaries, regardless of size.
Companies with paid-up capital ≥ ₹5 crore Threshold as generally understood — verify the current figure on the MCA portal before relying on it.
Companies with turnover ≥ ₹100 crore Same caveat — thresholds have moved before and can move again.
Companies already filing in XBRL Once covered, a company generally continues filing in XBRL in subsequent years even if it later falls below the threshold — check the current carry-forward rule.
Specifically exempted classes MCA has, from time to time, exempted banking, insurance, power and NBFC companies from the standard XBRL taxonomy (they may have sector-specific taxonomies instead) — confirm your company's classification.

Verify on the MCA portal before relying on any of these thresholds — paid-up capital and turnover limits, the list of exempted sectors, and the "once covered, always covered" carry-forward rule have all been amended over time, and getting this wrong means either an unnecessary XBRL exercise or a missed mandatory filing.

The XBRL filing process, step by step

Tagging is a distinct exercise from preparing the financial statements — it happens after the numbers are final and approved, not instead of the usual finalisation and audit process.

Step What happens
1. Confirm applicability & taxonomy Check whether the company falls within the notified class for the relevant financial year, and which taxonomy version applies (Ind AS or Companies (Accounts) taxonomy) — this is revised periodically by MCA.
2. Prepare financials in the standard format Financial statements must be finalised and adopted (AGM-approved) in the Schedule III format before tagging begins — XBRL is a re-presentation of approved financials, not a shortcut to skip approval.
3. Map and tag each line item Every line item, note and disclosure is mapped to an element in the notified taxonomy using XBRL-enabled software (in-house tool, Tally add-on, or a filing agent's tool). This is the most error-prone step.
4. Validate against MCA's tool Run the instance document through the MCA-prescribed validation tool to catch tagging errors, negative values entered as positive (or vice versa), unit mismatches and missing mandatory tags.
5. Pre-scrutiny and review Pre-scrutinise the validated file, then have the signing director/CFO and the CA/CS reviewing the filing tie the tagged figures back to the audited financials line by line.
6. File on the MCA portal Upload the instance document with Form AOC-4 XBRL within the statutory timeline from the AGM — verify the current due date and any late-filing fee structure on the MCA portal before the filing window.

The taxonomy — the standard dictionary of tags a filer can use — is issued and periodically revised by MCA. A company must tag against the taxonomy version applicable for the relevant financial year, not simply whatever version the software defaults to. Always confirm the applicable taxonomy version on the MCA portal before starting tagging for a new filing season.

Common XBRL filing mistakes

These are the errors that most often cause a validation failure, a rejected filing, or — worse — a filing that's accepted but doesn't actually match the audited financials:

  • Sign errors. Tagging a deduction, provision or negative adjustment with the wrong sign, so the tagged figure doesn't match the reported figure even though the label is correct.
  • Wrong element mapping. Forcing a line item into the "closest" available taxonomy element instead of the correct one — common with company-specific note headings that don't map cleanly to standard tags.
  • Using the wrong taxonomy version. Tagging against last year's taxonomy when MCA has notified an updated one for the current filing year.
  • Unit and scale mismatches. Mixing absolute rupees with figures reported in lakhs or crores within the same instance document.
  • Tagging before the financials are finalised. Starting the XBRL exercise on a draft P&L or balance sheet that changes after AGM approval, so the instance document and the adopted financials diverge.
  • Skipping the validation and pre-scrutiny step. Uploading straight to the MCA portal without running the prescribed validation tool first, which surfaces most tagging errors before they become a rejected or defective filing.
  • Missing mandatory notes and disclosures. Related-party disclosures, contingent liabilities and accounting-policy notes are easy to leave untagged when tagging is treated as a mechanical, line-item-only exercise.

The practical safeguard for a CA firm: always reconcile the validated XBRL output back to the signed financial statements, line by line, before filing — not just a validation-tool "pass".

A note for practice

XBRL is a filing-format exercise, not an accounting exercise — the numbers should never change because of tagging. If a client's XBRL figures don't tie out to the AGM-approved financials, that's a tagging bug to fix, not a reason to revisit the underlying accounts. Keeping tagging and finalisation as separate, sequential steps — and building a line-by-line reconciliation into your review checklist — is the single biggest reducer of XBRL rejections we see in practice.

If your firm tracks annual filing deadlines (AOC-4, AOC-4 XBRL, MGT-7) for multiple clients, a compliance calendar with per-client due dates removes the manual tracking. See what that looks like on our TatvaBooks for CAs page, or go straight to pricing.

Frequently asked questions

Which companies are required to file financial statements in XBRL?
As a framework: all listed companies and their Indian subsidiaries, plus unlisted companies crossing prescribed paid-up capital and turnover thresholds, must file in XBRL. Certain sectors (banking, insurance, power, NBFCs) have historically had separate taxonomies or exemptions. The exact thresholds and exempted classes are notified by the MCA and have changed over the years — always verify current applicability on the MCA portal or in the latest Companies (Accounts) Rules before advising a client either way.
Once a company starts filing in XBRL, can it go back to normal filing?
Generally no — once a company falls within the notified class and files in XBRL, the common understanding is that it continues to do so in subsequent years even if it later drops below the threshold. This carry-forward principle has held across amendments, but confirm the current rule on the MCA portal before advising a client to stop XBRL filing.
What is the difference between XBRL tagging errors and a wrong financial statement?
They are legally distinct. A tagging error is a mismatch between the approved financial statements and how they were represented in the XBRL instance document — for example, tagging a provision under the wrong element, or a sign error. The underlying AGM-approved financials remain correct; only the XBRL representation needs to be corrected and refiled. Tagging errors are still a compliance risk because MCA validation and manual scrutiny can flag them, and refiling has its own procedure and timeline.
Do XBRL financials need to be signed and certified again?
The XBRL filing (Form AOC-4 XBRL) itself needs to be authenticated by a director/CFO/company secretary and, where applicable, certified by a practising professional (CA/CS/CMA), similar to a normal e-form filing — it isn't a re-audit of the financials, but it is a fresh certification that the tagged data faithfully represents the AGM-approved statements. Confirm the current certification requirement on the MCA portal for the specific form version in use.
Can a CA firm do XBRL tagging in-house, or does it need a specialist vendor?
Either is workable. Firms with recurring XBRL clients often invest in an XBRL-enabled tool (a standalone converter, or a module inside their accounting/tax software) and do tagging in-house once the team is trained on the taxonomy. For occasional or first-time filers, using a specialist XBRL vendor to prepare the instance document — while the CA firm reviews and certifies it against the audited financials — is common and reduces tagging-error risk.

Built for CA practices

Run your practice's compliance calendar in one place.

Track annual filing, GST and tax deadlines across every client — TatvaBooks Practice plan keeps your team ahead of due dates.