Filing & audit tools · on-device
Get your BRSR XBRL accepted the first time
A rupee-scale converter plus the recurring data-entry mistakes that get a BRSR XBRL filing bounced by the exchange utility. Fix them before you upload.
- Convert Lakhs or Crores to the absolute rupees the taxonomy expects
- Clear the 7 errors that most often fail validation, each cited
- No taxonomy software needed, nothing leaves your browser
For the consultant preparing the instance document, right before the BSE / NSE upload. Not a full taxonomy validator; it catches the common human errors.
Rupee-scale converter
Enter this in the numeric XBRL cell
Type an amount to see the absolute-rupee value.
The 7 checks before you upload
Clear each of these before generating the instance document. They are the mistakes that most often trip the validation, ordered by how frequently they appear.
Why it fails: Most quantitative BRSR fields ask for the current and previous financial year. The XBRL utility rejects or flags a numeric context that is left empty when a prior-year value exists in last year's filing.
Fix: Enter the previous-year figure for every quantitative row. If the company genuinely did not report the metric last year, use the utility's designated not-reported handling rather than leaving the numeric cell blank.
Source: SEBI BRSR Format, Section C quantitative tables (current FY / previous FY columns)
Why it fails: A numeric XBRL element only accepts a number. Typing N/A, NA, Not Applicable, dash, or NIL into a numeric field is the single most common cause of a validation error.
Fix: Enter 0 where the true value is zero. Where a metric does not apply, use the boolean/flag or the narrative field the taxonomy provides for it, never free text in a numeric element.
Source: SEBI/exchange BRSR XBRL taxonomy, numeric element data types
Why it fails: The taxonomy expects monetary values in absolute rupees. Entering a figure in Lakhs or Crores under-states the number by a factor of 100,000 or 10,000,000 and either fails a range check or files a wrong number.
Fix: Convert every monetary figure to absolute INR before entry (use the converter above). A turnover of 500 Crore is 5,00,00,00,000, not 500.
Source: SEBI/exchange BRSR XBRL taxonomy, monetary unit and scale
Why it fails: Section A identity/registration fields, and several Section C essential indicators, are mandatory. The utility will not generate a valid instance while any mandatory element is missing.
Fix: Run the utility's own completeness/validation pass and clear every mandatory-field error before generating the instance document. CIN, registered address, financials, and the essential P-indicators are the usual gaps.
Source: SEBI BRSR Format, Section A (mandatory disclosures) + Section C essential indicators
Why it fails: If the company marks a KPI or the BRSR Core as reasonably assured, the taxonomy expects the assurance provider's name and the type/scope of assurance. Marking assured without the provider block fails validation.
Fix: For every assured item, fill the assurance-provider name and assurance type. Keep it consistent with the assurance statement your ICAI-registered assurer issued.
Source: SEBI BRSR Core (circular 12 Jul 2023), reasonable-assurance disclosure fields
Why it fails: Energy, water and emissions elements each carry a fixed unit (for example energy in joules/GJ, not kWh; emissions in metric tonnes CO2e). A value entered against the wrong unit reference is rejected or silently mis-scaled.
Fix: Match each quantitative value to the unit the taxonomy declares for that element. Convert kWh to GJ for energy fields, and report GHG in tCO2e, before entry.
Source: SEBI BRSR Format, Principle 6 quantitative disclosures (energy, water, emissions units)
Why it fails: Where the format breaks a total into components (energy by source, water by source, waste by stream, employees by category and gender), the utility and the assurer both check that the parts sum to the stated total.
Fix: Reconcile every breakdown before filing: source components must add up to the total, and the male/female/other split must equal the headcount total. Fix the underlying number, not the total.
Source: SEBI BRSR Format, Section C component-vs-total tables (P3, P6)
XBRL utility validations change with each taxonomy release. Confirm against the current BSE/NSE BRSR XBRL manual and the utility's own validation messages before filing.
For the full 108-field gap analysis on your client, run the free readiness report.
What XBRL is, and why the exchange cares
Most rejections aren't about the ESG content, they're about the format. A quick grasp of what XBRL is and the one convention it enforces prevents almost all of them.
A machine-readable filing
XBRL tags every number in your BRSR with a taxonomy label, so software reads 'total energy consumed' the same way across every company. The exchange stores structured data, not a PDF a human has to retype.
Why SEBI mandates it
Structured filings let SEBI, investors and rating agencies compare thousands of companies automatically and screen for outliers. That's only possible if everyone tags to the same taxonomy, which is why validation is strict.
The units convention
Company accounts are kept in Lakhs or Crores, but the numeric XBRL cells expect absolute rupees. Entering 500 where 5,00,00,000 was meant is the single most common bounce. Convert first, every time.