XBRL Reporting Requirement

The skill tool isn't accessible in this environment, and the available Coupler.io skills relate to data-pipeline workflows — not XBRL compliance writing. Proceeding directly with the blog regeneration.

XBRL Reporting Requirement: A Complete Compliance Guide for FY 2026-27

For FY 2026-27, every Indian company that is listed, crosses Rs. 5 crore in paid-up capital, or exceeds Rs. 100 crore in turnover must file Form AOC-4 XBRL on the MCA V3 portal within 30 days of its Annual General Meeting. Listed entities carry an additional quarterly burden under SEBI's LODR Regulations, while banks, NBFCs, and insurers layer RBI and IRDAI XBRL obligations on top. A single late filing already costs Rs. 100 per day in MCA additional fees; combined penalties across portals can run to several lakhs. This guide maps every obligation, every deadline, and every common failure point for FY 2026-27.

What XBRL Is — and Why the Regulator Can Spot Your Errors Instantly

eXtensible Business Reporting Language (XBRL) converts a financial statement from a static document — a PDF a human must read — into structured data that a regulator's system can ingest, query and cross-reference in seconds. Each number and narrative disclosure is attached to a standardised taxonomy concept, making every tagged value directly comparable across companies, across years, and across filings made on different portals.

That last point is the one most finance teams underestimate. The MCA, SEBI, RBI and IRDAI now run analytics that cross-reference your filings. If the revenue figure in your AOC-4 XBRL on the MCA V3 portal differs from the revenue you reported in your BSE/NSE XBRL quarterly results, the discrepancy is flagged automatically. There is no inspector needed; the system does it at scale. Getting XBRL right the first time is not a matter of regulatory tidiness — it is a matter of avoiding queries and show-cause notices that cost far more to answer than the original filing cost to do properly.

Who Must File XBRL Under MCA Rules

The Companies (Filing of Documents and Forms in Extensible Business Reporting Language) Rules, 2015, as amended, specify six categories of companies that must submit their annual financial statements in XBRL format using Form AOC-4 XBRL:

• Listed companies and their Indian subsidiaries, regardless of size
• Companies with paid-up share capital of Rs. 5 crore or more
• Companies with turnover of Rs. 100 crore or more
• Companies mandated to prepare financial statements under Ind AS (Indian Accounting Standards)
• NBFCs above the asset-size threshold notified by the MCA / RBI
• Any additional class of company separately notified by the Central Government

If your company crosses any one threshold during FY 2026-27 — even for the first time — XBRL applies for that year's filings. New entrants cannot defer to the following year.

Which Taxonomy Applies?

The MCA maintains separate XBRL taxonomies. Filing with the wrong one triggers immediate validation rejection.

Always download the current taxonomy from the MCA V3 portal at the start of each filing cycle. Taxonomy versions are updated periodically, and filing with a prior-year version is one of the most common causes of avoidable rejection.

MCA Form AOC-4 XBRL: Process and FY 2026-27 Deadline

The Key Date

For a financial year ending 31 March 2027, the AGM must be held by 30 September 2027 (within six months of the financial year-end, under Section 96 of the Companies Act 2013). AOC-4 XBRL must be filed within 30 days of the AGM. If your AGM falls on 25 September 2027, your AOC-4 XBRL deadline is 25 October 2027.

Watch for any MCA general circular issued between July and October 2027 granting a blanket extension, as has occurred in several prior years. Extensions are not automatic; they require a formal circular.

Step-by-Step Filing Sequence

Follow this sequence every year — it is the single fastest way to eliminate last-minute surprises.

1. Finalise audited financial statements — profit and loss account, balance sheet, cash flow statement, notes — with Board approval and the auditor's signed report in hand. Do not begin tagging from a near-final draft; a last-minute audit adjustment will force a complete re-tag.
2. Confirm the current taxonomy version by checking the MCA portal notification. Note the version number and date in your working paper.
3. Load financial data into your XBRL tagging tool — options include Tally Prime's XBRL module, IRIS Carbon, Prowly, or the MCA's own free tagging utility available on the MCA V3 portal.
4. Map every line item to a taxonomy concept: each figure in the financial statements, each mandatory note (going concern, related party, segment reporting), and each identifier (CIN, DIN of directors, auditor registration number).
5. Tag identifiers: Corporate Identity Number (CIN), entity name, reporting period start and end, and digital identifier of the auditor.
6. Run the MCA pre-validation tool against the instance document. Resolve all errors before proceeding. Treat warnings seriously — many are mandatory elements the system will reject at submission stage.
7. Attach the validated `.xbrl` instance document to Form AOC-4 XBRL on the MCA V3 portal and complete the form fields.
8. Authenticate and submit using a valid Digital Signature Certificate (DSC) of an authorised director or company secretary.
9. Download and archive the SRN (Service Request Number) and payment challan as proof of timely filing.
10. Retain the source-to-tag working paper — a document mapping each financial statement line to its taxonomy concept and the tagged value — for a minimum of eight financial years, as required under the Rules.

SEBI LODR XBRL Submissions: The Full Listed-Entity Calendar

A listed company's XBRL obligations under SEBI's Listing Obligations and Disclosure Requirements (LODR) Regulations, 2015 run continuously throughout the year. There is no single annual event; there are at least fourteen submission points.

Quarterly Financial Results — Regulation 33

Financial results (standalone and, where applicable, consolidated) must be filed in XBRL format through the BSE and NSE XBRL utilities within:

• 45 days of the close of Q1, Q2, and Q3
• 60 days of the close of Q4 and the full financial year

The XBRL submission must be consistent with the simultaneously filed PDF. A mismatch between the two causes rejection and restart of the clock.

Shareholding Pattern — Regulation 31

File in XBRL within 21 days of each quarter-end:

• Q1: 21 July 2026 | Q2: 21 October 2026 | Q3: 21 January 2027 | Q4: 21 April 2027

Corporate Governance Compliance Report — Regulation 27(2)

Submit within 21 days of each quarter-end, on the same schedule as the shareholding pattern above.

Related-Party Transaction Disclosures — Regulation 23(9)

File within 30 days of the end of each half-year:

• H1 FY 2026-27 (April–September 2026): by 30 October 2026
• H2 FY 2026-27 (October 2026–March 2027): by 30 April 2027

How Exchange Submissions Work

Both BSE and NSE provide their own XBRL utilities. Prepare the tagged file, validate it within the exchange utility, and upload to both portals. Both exchanges must typically receive the filing simultaneously. Defective filings — where XBRL data does not match the PDF attachment — are rejected and must be refiled before the deadline.

RBI and IRDAI XBRL Returns for Regulated Entities

Scheduled Commercial Banks

Scheduled commercial banks file a wide range of prudential and statistical returns through the RBI's RADAR (Returns Analytical Data Warehouse) system, a significant portion of which are XBRL-based. Return cadence varies — monthly, quarterly, and annual — as prescribed in the RBI's Master Direction on Returns Filing. AD Category-I banks additionally file the Foreign Liabilities and Assets (FLA) return in XBRL format by 15 July each year for the preceding financial year. For FY 2026-27, the FLA XBRL deadline is 15 July 2027.

NBFCs

Non-Banking Financial Companies file supervisory returns including NBS-1 (balance sheet and profit and loss), NBS-2 (exposure to sensitive sectors), and NBS-7 (capital funds and risk-weighted assets ratio) through the RBI's COSMOS portal, with migration toward the RBI's SUPTECH XBRL platform ongoing. Systemically Important NBFCs (those with assets of Rs. 500 crore and above) carry more granular XBRL disclosure obligations. Exact return frequencies and deadlines are prescribed in the applicable RBI Master Circular for the current year — check the RBI website at the start of FY 2026-27 for the updated master circular.

Insurance Companies

IRDAI requires life insurers, general insurers, and standalone health insurers to file annual financial statements and regulatory returns in XBRL format using IRDAI's prescribed taxonomy. The annual filing window is linked to finalization of audited accounts, with the deadline typically falling by 30 September of the year following the financial year. Quarterly returns may carry additional XBRL requirements as notified by IRDAI.

Worked Example: What a Delayed Filing Actually Costs

Scenario: Acumen Infra Limited is a listed company on the NSE with paid-up capital of Rs. 18 crore. For FY 2026-27, an auditor change delays finalization. The Q4 financial results (XBRL deadline: 30 May 2027) are filed on 18 August 2027 — 80 days late. Form AOC-4 XBRL (deadline: 25 October 2027, assuming AGM held 25 September 2027) is filed on 26 January 2028 — 93 days late.

MCA late fee — Section 403 additional fee:

• AOC-4 XBRL: Rs. 100/day × 93 days = Rs. 9,300
• Form MGT-7 (Annual Return), also filed 93 days late: Rs. 100/day × 93 days = Rs. 9,300
• Combined MCA additional fees: Rs. 18,600

SEBI / Exchange penalty — delayed Q4 results: Stock exchanges levy fines for late XBRL submissions as prescribed in their circulars. Published fine schedules for delayed financial results filings have ranged from Rs. 1,000 per day for the initial period to higher slabs for prolonged delay (verify the exact rates against the current BSE/NSE circular). At a conservative Rs. 1,000 per day: 80 days × Rs. 1,000 = Rs. 80,000 in exchange fines alone. SEBI may separately initiate enforcement proceedings under Regulation 98 of the LODR Regulations for a persistent default, potentially adding adjudication penalties as notified.

Estimated combined exposure: Rs. 1,00,000 and above, before any legal response costs or director disqualification risk under Section 164 of the Companies Act 2013.

The practical lesson: what feels like a two-month delay in August 2027 translates into a six-figure compliance liability — from two separate regulators — by January 2028.

Common Pitfalls and How to Fix Them

Using a Superseded Taxonomy Version

What goes wrong: The finance team reuses the prior year's taxonomy file. The MCA pre-validation tool returns concept-not-found errors across dozens of elements, and the team loses three days diagnosing what should have been a thirty-second check.

Fix it: Create a standing checklist item at the start of every filing cycle: "Download current taxonomy from MCA V3 portal. Confirm version number against MCA notification dated [date]." Do this in July or August, not the week before submission.

Treating XBRL as a Vendor Activity Disconnected from Finance

What goes wrong: The file is outsourced entirely to a software vendor who has no visibility into the notes to accounts. The vendor tags the face-of-financial-statements figures but misses the going-concern note, the segment-reporting table, and the related-party schedule. MCA analytics flag missing mandatory elements post-submission, triggering a deficient-filing notice.

Fix it: Assign one finance-team member as XBRL Owner — the person who sits with the vendor during tagging, reconciles the instance document against the signed financial statements line by line, and signs off on the source-to-tag working paper before the DSC is applied.

Inconsistency Between MCA and Exchange XBRL Data

What goes wrong: A listed company's Q4 results XBRL (filed in May) shows standalone revenue of Rs. 48.12 crore. The AOC-4 XBRL filed in October shows Rs. 48.00 crore — because the exchange XBRL was prepared from a near-final draft and a rounding correction was made after the auditor's sign-off. Regulators' cross-referencing tools surface the Rs. 12-lakh discrepancy. The company must now respond to an exchange query and potentially file a revision.

Fix it: Maintain a single master working paper that is the authoritative source for both exchange XBRL and MCA XBRL. Lock figures only after Board approval and auditor sign-off. Never update one portal submission without simultaneously updating the other from the same source.

No Internal Buffer Before the Regulatory Deadline

What goes wrong: Tagging is completed on deadline evening. The MCA V3 portal is under high load; alternatively, the DSC token driver has expired or the director authorised to sign is travelling. The filing is missed, and Rs. 100 per day begins running from the following morning.

Fix it: Set an internal deadline five working days before every regulatory deadline. Build this into the compliance calendar explicitly — not as a courtesy but as a mandatory gate. A portal outage on day five still leaves four days to resolve.

Overlooking Subsidiary-Level Obligations

What goes wrong: The holding company's AOC-4 XBRL is filed on time. Three Indian subsidiaries — all with paid-up capital above Rs. 5 crore — are not tracked in the compliance register. Each attracts its own late-filing fee and, if delayed beyond six months, risks a show-cause for strike-off.

Fix it: Maintain a group-level XBRL compliance register listing every entity, its CIN, the threshold that triggers XBRL for that entity, its AGM date, and its individual AOC-4 XBRL deadline. Review this register when any group entity raises fresh capital or grows its turnover.

Building Your XBRL Compliance Calendar for FY 2026-27

A complete calendar for a listed NBFC — which faces MCA, SEBI, and RBI obligations simultaneously — looks like this:

*Assumes AGM held 25 September 2027. Shift both dates if your AGM is earlier or later.

For RBI/COSMOS NBFC returns and IRDAI returns, extract the exact schedule from the applicable Master Circular and add those items to the same calendar. Every row must carry three fields: regulatory deadline, internal deadline (five working days earlier), and named owner.

Why XBRL Data Quality Is Now an Investor-Relations Risk

One angle that finance teams consistently underestimate: XBRL-tagged filings are consumed not just by regulators but by Bloomberg, Refinitiv, CMIE, and a range of ESG-data vendors through automated feeds. A depreciation figure incorrectly tagged under "Other Expenses" in your AOC-4 XBRL taxonomy will appear that way in investor databases for years, because third-party platforms cache and re-serve MCA filings. Correcting a tagging error requires filing a revised AOC-4 XBRL, which itself signals a disclosure problem and draws attention.

The single most effective safeguard against this is the reconciliation working paper: a three-column document showing (i) the financial-statement line as signed by the auditor, (ii) the XBRL taxonomy concept it is tagged to, and (iii) the tagged value. This working paper is both your internal control and your defence in any regulatory query about a disclosure. It also makes next year's XBRL faster, because the concept mapping from the prior year is your starting point.

Key Takeaways

• XBRL compliance is year-round, not annual: a listed company has at least fourteen XBRL submission points in FY 2026-27 spread across MCA V3, the BSE/NSE exchange utilities, and (for regulated entities) the RBI and IRDAI portals.
• Threshold triggers are one-way gates: once your company crosses Rs. 5 crore paid-up capital or Rs. 100 crore turnover, XBRL applies from that year onwards — there is no reversion threshold.
• Late MCA fees accumulate at Rs. 100 per day per form: a 93-day delay on AOC-4 XBRL alone costs Rs. 9,300; add MGT-7 and exchange fines, and total exposure for a single delayed cycle can exceed Rs. 1 lakh.
• Taxonomy version must be confirmed each year: download the current version from the MCA V3 portal at the start of the tagging cycle — do not reuse last year's file.
• One named XBRL Owner in the finance team is non-negotiable: XBRL accuracy cannot be delegated entirely to a vendor without context; the working paper sign-off must sit with your team.
• Set every internal deadline five working days ahead of the regulatory deadline to absorb portal outages, DSC renewal issues, and last-minute queries from the auditor.
• MCA V3 and exchange XBRL must show identical figures: regulators' analytics tools cross-reference both portals automatically; a discrepancy as small as a rounding difference will generate a query.