Filing of announcements in XBRL format

Filing of Announcements in XBRL Format

Listed companies on NSE and BSE must file most corporate announcements — board outcomes, dividend declarations, fund-raising events, and leadership changes — in XBRL format, alongside or before the PDF version. Under SEBI's Listing Obligations and Disclosure Requirements (LODR) Regulations, 2015, this obligation spans Regulation 30 (continuous disclosures), Regulation 33 (financial results), Regulation 27 (corporate governance), Regulation 31 (shareholding pattern), and several others. An incorrect taxonomy version, a missing mandatory tag, or a filing made even 90 minutes late can attract exchange fines, SEBI enforcement, and public naming as a defaulter. This guide walks you through the exact workflow, current regulatory timelines, common error patterns, and the real cost of non-compliance for FY 2026-27.

What XBRL Is — and Why Exchanges Now Insist on It

eXtensible Business Reporting Language (XBRL) is a structured, tag-based data format that makes every element of a corporate disclosure machine-readable. Instead of burying "dividend per share: ₹5" inside a PDF paragraph, XBRL wraps that value in a standardised tag drawn from a published taxonomy — say, in-sebi:DividendPerShare — so that SEBI surveillance systems, exchange analytics engines, analyst data terminals, and increasingly AI-based compliance tools can parse and cross-check the disclosure in milliseconds.

The business case for XBRL, from the exchange perspective, is simple: it eliminates manual data extraction, reduces errors, and makes structured comparison across thousands of companies possible. From the regulator's viewpoint, it enables near-real-time screening for disclosure gaps and market-sensitive information. From your perspective as a compliance officer, it means every tag you file is a permanent, structured record that SEBI can query during an inspection.

SEBI's progressive migration to XBRL-first filings began with Regulation 33 financial results and has since expanded to cover virtually every Regulation 30 event. In 2026, submitting only a PDF where XBRL is mandatory is not just rejected by the exchange portal — it is treated as a non-filing.

Where XBRL Filing Applies: A Regulation-by-Regulation Map

Understanding which regulations require XBRL prevents the most common first-level mistake — filing a well-tagged document under the wrong regulatory peg.

Regulation 30 — Continuous Disclosures (Schedule III Events) This is the highest-volume XBRL filing obligation. Every listed company must disclose events and information as categorised in Schedule III, Part A of the LODR Regulations. This includes board meeting outcomes, dividend declarations, fund-raising resolutions (rights issue, QIP, FCCB), mergers and acquisitions, changes in senior management, credit rating changes, commencement or cessation of business lines, and trading halts. All such announcements filed on NSE and BSE must be in the XBRL format prescribed by the respective exchange's disclosure taxonomy.

Regulation 30(11) — Market Rumour Response Inserted by the SEBI (LODR) (Third Amendment) Regulations, 2023, this provision requires a listed company to confirm, deny, or clarify any news report or market rumour that the exchange flags as potentially material. The response — and the XBRL filing of that response — must reach the exchange within 24 hours of receipt of the query. The XBRL taxonomy has separate fields for "confirmation," "denial," and "clarification" responses.

Regulation 33 — Financial Results Quarterly (standalone and consolidated) and annual financial results must be filed in the exchange-prescribed XBRL template — which follows SEBI's financial results taxonomy aligned with Indian Accounting Standards (Ind AS) or Indian GAAP, as applicable. The accompanying auditor's report and limited review report attach as linked documents.

Regulation 27 — Corporate Governance Report The quarterly corporate governance compliance report — covering board composition, committee structure, and compliance status — must be filed in XBRL on the exchange portal within 21 days from the close of each quarter.

Regulation 31 — Shareholding Pattern Shareholding pattern disclosures for each category of holder — promoter, public, non-institutional, institutional — require XBRL filing within 21 days from the end of each quarter, and within 10 days of a significant change exceeding two percentage points.

Regulation 7 / 13 — SAST and PIT Disclosures Reports of substantial acquisition (under SEBI Takeover Regulations) and trading-related disclosures under the Prohibition of Insider Trading (PIT) Regulations, where channelled through the exchange, incorporate XBRL fields for promoter identity, acquisition date, and quantum.

Postal Ballot and AGM Voting Results Scrutiniser reports, e-voting outcomes, and postal ballot results must be filed in XBRL within 48 hours of the conclusion of the voting period.

The XBRL Filing Workflow: Step-by-Step

Step 1 — Identify the Triggering Event and the Applicable Regulation

Before you open any portal, pin down the exact regulation and Schedule III paragraph. A board meeting that approves a dividend and a rights issue simultaneously produces two XBRL filings: one under Para A (dividend) and one under Para A (fund-raising). Filing them as a single miscellaneous announcement is a tagging error.

Step 2 — Access the Exchange Utility

• NSE: Log in to the NSE Listing Portal (earlier known as NEAPS — NSE Electronic Application Processing System) at the NSE Listing Module. Your company's compliance officer login credentials are separate from the investor login.
• BSE: Log in to the BSE Listing Centre at corp.bseindia.com. BSE provides an offline XBRL utility for Regulation 33 filings that can be downloaded, tagged offline, and then uploaded.

Both portals require dual-exchange filing. Do not assume a successful NSE submission is simultaneously pushed to BSE — they are separate systems, and a discrepancy between the two is itself a compliance flag.

Step 3 — Select the Template and Map Fields to the Taxonomy

Each portal presents a structured form corresponding to the type of announcement. Select the correct announcement sub-type (e.g., Dividend — Final Dividend, not Dividend — General). The form pre-loads the mandatory taxonomy tags for that event type. For each field:

• Enter values exactly as they appear in the board resolution — ₹5.00 per share, not "five rupees" or "5."
• Date fields must follow DD/MM/YYYY or YYYY-MM-DD as the portal specifies — mixing formats causes validator failure.
• For free-text fields (e.g., "reason for scheme of arrangement"), do not paste formatted text with special characters; strip formatting first.

Step 4 — Validate the Instance Document

Before uploading, run the portal's inline validator (or the offline utility's validator for BSE Reg 33 filings). The validator checks:

• Mandatory tags have non-null, correctly typed values
• Date ranges are internally consistent
• Numeric fields fall within expected ranges (negative revenue triggers a warning, for instance)
• The taxonomy version matches the exchange's current published version

Zero errors is the target. Warnings may be accepted, but every warning must be reviewed — several "warning" classifications were reclassified as "errors" in recent taxonomy updates.

Step 5 — Dual Upload and Obtain Acknowledgements

Upload to NSE first, then BSE, within the same session. Note the system-generated acknowledgement number and timestamp for both. The timestamp is your proof of compliance with the Regulation 30 timeline — not the time you sent the email to your vendor, not the time the board meeting ended.

Step 6 — Archive the Complete Filing Set

Maintain the following for a minimum of eight years from the date of filing:

• The XBRL instance document (.xml file)
• The PDF/HTML version of the announcement
• The exchange validator report
• The NSE and BSE acknowledgement receipts
• The board resolution or authority document that triggered the disclosure

This archive is your primary defence in any SEBI inspection or forensic audit.

Regulation 30 Disclosure Timelines You Must Know in 2026

The LODR Regulations, as amended, specify two primary timelines under Regulation 30(6):

The 30-minute rule for Para A events is unforgiving. If your board meeting runs from 2:00 PM to 4:45 PM and approves a dividend, the XBRL filing and the PDF announcement must both be live on both exchanges by 5:15 PM. This means your XBRL draft must be built in parallel with the board meeting itself — not after.

Worked Example: A Dividend Declaration and the Cost of Getting It Wrong

Scenario: The board of Lakshman Textiles Limited meets on September 30, 2026. The meeting concludes at 4:00 PM. The board approves a final dividend of ₹8 per equity share for FY 2026-27 (record date: October 20, 2026). The company's compliance officer files the XBRL announcement on NSE at 5:45 PM (105 minutes after the meeting) and on BSE at 6:10 PM (130 minutes after). Both filings are thus outside the 30-minute Para A deadline.

Exchange action (illustrative under NSE/BSE SOP): Both exchanges flag the filing as late. Under the exchanges' Standard Operating Procedure for non-compliance with LODR Regulations, a late filing of a Regulation 30 Para A event attracts a fine. The fine quantum is notified periodically by each exchange under their respective Listing Agreements and SOP circulars — check the current schedule on the NSE/BSE website before each filing cycle. As a reference, under earlier SOP circulars, fines for delayed Regulation 30 filings have been levied in the range of ₹1,000 to ₹5,000 per instance per exchange, escalating for repeat defaults within a financial year.

XBRL-specific complication: The compliance officer also enters the record date as 20-10-2026 instead of 20/10/2026 (date format mismatch). This creates a validator error. The corrected re-filing is treated as a revision, which itself requires a written explanation to the exchange. The company now faces: (a) a late filing fine, (b) a revision notice requiring documentation, and (c) the disclosure appearing in the exchange's monthly non-compliance report.

Lesson: A format error that takes four seconds to fix causes a paper trail that takes four hours to resolve. Build a pre-meeting XBRL draft checklist — record date, dividend per share, payment date, tax rate if applicable — so the only step on filing day is entering the confirmed numbers and uploading.

Common Mistakes That Trigger Rejections and SEBI Notices

1. Using an outdated taxonomy version SEBI and the exchanges update the XBRL taxonomy when Ind AS amendments take effect or when new regulatory requirements are added (such as the Reg 30(11) rumour-confirmation fields added in 2023). Filing with a taxonomy version that was valid six months ago will result in an outright rejection. Always download the taxonomy from the exchange portal the day of filing, not from your archive.

2. Mismatched PDF and XBRL values The exchange's surveillance system cross-checks numeric values between your XBRL instance document and the accompanying PDF. A ₹500 crore revenue figure in the PDF and ₹5,00,00,000 (typed without abbreviation handling) in the XBRL triggers an automated mismatch flag. This is one of the most frequent causes of SEBI scrutiny letters.

3. Mandatory tags filled with placeholders Fields marked mandatory in the taxonomy cannot be left blank or populated with "NA," "N/A," or "NIL" when an actual value exists. For example, if you file a board meeting outcome that includes both a dividend and a fund-raise, the BoardMeetingPurpose tag cannot be tagged as "Others" — the taxonomy provides specific permitted values.

4. Wrong announcement sub-type selected Selecting Scheme of Arrangement — Amalgamation when the board actually approved a demerger means the taxonomy-mandated fields for the two transaction types do not align. This is not caught by the validator (since technically the fields are populated) but will be caught in any regulatory review.

5. Failing to file on both exchanges Regulation 30 requires simultaneous disclosure to all exchanges where the company's securities are listed. A company listed on both NSE and BSE that files only on NSE is non-compliant for BSE. The timestamps must be within the permitted window for both.

6. Ignoring the materiality policy obligation Under LODR Regulation 30(4), every listed company must frame and file a materiality determination policy with the exchange. This policy itself must be in XBRL. Companies that have not filed or updated their materiality policy cannot rely on the "immaterial event" exemption in any enforcement proceeding.

Penalties and Enforcement Consequences

Non-compliance with XBRL filing obligations exposes a listed company and its officers to action on multiple fronts:

Exchange-level fines: NSE and BSE each maintain a Standard Operating Procedure (SOP) for LODR non-compliances. Fines for delayed or defective Regulation 30 filings are imposed per instance and escalate for repeat defaults within the same financial year. Defaulting companies are also listed in the exchanges' monthly non-compliance reports, which are public documents and frequently picked up by financial media.

SEBI enforcement: Under Section 15A of the SEBI Act, 1992, failure to file information or documents as required by securities law can attract a penalty of up to ₹1 lakh per day of default, subject to a maximum of ₹1 crore. For wilful or persistent non-disclosure, SEBI can also initiate adjudication proceedings, issue show-cause notices, and in serious cases, refer the matter for prosecution under Section 24.

Market and reputational risk: A delay in disclosing a dividend or a material event does not just carry regulatory risk — it creates an information asymmetry window during which informed parties may trade, potentially triggering an insider trading inquiry. The indirect costs of that inquiry — legal fees, management distraction, reputational damage — are many times the exchange fine.

Directors' liability: Officers in default under the LODR Regulations include the company secretary (who typically signs off on exchange filings), the CFO, and the managing director. Personal penalties can be imposed alongside the company-level fine.

Building a Dual-Track XBRL Workflow In-House

For mid-size and large listed companies, the recommended architecture is:

1. Pre-board XBRL draft: The compliance team builds the XBRL shell — pre-populated with all standing data — before every board meeting. Only the confirmed values (dividend amount, resolution date, scheme details) need to be entered post-meeting.
2. Four-eye review: Preparer → Company Secretary → Independent reviewer. Each reviewer signs off on the tag mapping, the taxonomy version, and the PDF-XBRL reconciliation before upload.
3. Simultaneous dual upload: NSE and BSE filings should be initiated back-to-back within the same five-minute window. Use two browser tabs or two sessions where permitted.
4. Post-filing reconciliation: Within two hours of filing, compare the exchange's published announcement display against your XBRL source data. If the display shows a formatting anomaly, raise a revision immediately rather than waiting for an exchange notice.
5. Taxonomy monitoring: Subscribe to the SEBI alerts mailing list and the NSE/BSE circular notification service. New taxonomy versions are typically announced 30–60 days before the effective date, giving you time to update templates and train staff.

Smaller listed companies that outsource XBRL tagging to vendors must remember: accountability cannot be outsourced. The compliance officer who uploads the filing is the officer in default if it is wrong. Institute a sign-off protocol where the vendor delivers a tagged file, and your internal team validates it independently before uploading.

2026 SEBI Updates You Must Factor In

Reg 30(11) market rumour framework: Introduced in 2023 and now embedded in standard operating practice, this provision requires that when an exchange queries a company about a news report, the company's response — even a "we do not comment on market speculation" response — must be XBRL-tagged and filed. The taxonomy includes distinct fields for Response Type, EventDescription, and NatureOfDevelopment.

Materiality policy documentation in XBRL: SEBI's circulars now require that the board-approved materiality determination framework — including the quantitative thresholds (typically 2% of turnover or ₹50 crore, whichever is lower, as a guide) — be filed in structured form.

Tightened scrutiny of financial results XBRL: SEBI's integrated surveillance function now runs automated consistency checks between Regulation 33 XBRL data and Regulation 30 announcements. A Regulation 30 announcement about a project completion must be consistent with asset capitalisation data in the Regulation 33 filing. Discrepancies trigger automated alerts for further review.

ESG and BRSR: The Emerging XBRL Frontier

The Business Responsibility and Sustainability Report (BRSR) has been mandatory for the top 1,000 listed companies since FY 2022-23. For FY 2026-27, BRSR Core — the assured metrics subset covering energy intensity, water consumption, waste management, and social indicators — applies to the top 250 companies (and is being progressively expanded). SEBI is developing XBRL taxonomy extensions to capture BRSR Core metrics in machine-readable form.

This means the same four-eye review process you apply to financial XBRL today will need to extend to sustainability data. Scope 1 and Scope 2 emissions figures, employee injury rates, and community investment spending will become XBRL-tagged fields on the exchange portal. Companies that wait until the taxonomy is finalised to begin data collection will scramble. Begin now: identify your data owners for each BRSR Core indicator, establish a quarterly data pull process, and map existing GRI/TCFD reporting fields to the anticipated XBRL taxonomy structure.

Key Takeaways

• XBRL is mandatory, not optional, for Regulation 30, 33, 27, 31, and related exchange filings on both NSE and BSE — a PDF-only submission is treated as a non-filing.
• Para A events must be filed within 30 minutes of conclusion of the board meeting; Para B events within 24 hours; Regulation 30(11) rumour responses within 24 hours of the exchange query.
• Always use the current taxonomy version — outdated versions cause outright rejection and the effective filing date is your upload timestamp, not your preparation date.
• The PDF and XBRL values must match exactly — automated cross-checks between them are a primary source of SEBI scrutiny letters.
• Build the XBRL shell before the board meeting, not after, so the only step post-meeting is entering confirmed values and uploading within the 30-minute window.
• Penalties compound across both exchanges: a single late Regulation 30 filing triggers separate fines from NSE and BSE, plus personal liability for officers in default under Section 15A of the SEBI Act, 1992.
• BRSR Core metrics are the next XBRL obligation — companies should establish sustainability data collection pipelines now so they are not caught building from scratch when the taxonomy goes live.