BRSR Data Quality - Filing Issues & How They Are Handled

Why BRSR ESG filings carry data-quality noise, the classes of issue found across the Nifty Total Market universe, the two-layer (algorithmic + printed-PDF) validation, and the bottom line: reliable for aggregates, verify specific company cells against the PDF.

Source data: VIGIL BRSR consistency checks + PDF validation over SEBI BRSR XBRL filings · Last updated: 2026-11-03 · Markdown version
Live tool

See the live BRSR data this quality register covers, with per-company drilldowns and downloads.

Every BRSR value is self-reported by the company in its SEBI XBRL filing. The XBRL format enforces structure, but individual numbers are not independently verified at source - so VIGIL runs a layered set of consistency checks and publishes the results openly. This page documents the data-quality framework and the classes of issue found; the full per-company registry (which changes with every data refresh) lives in the live BRSR Data Quality Explorer.

Open the live VIGIL BRSR Data Quality Explorer for the current per-company / per-cell flags.

Bottom line

At the May 2026 audit round the consistency checks had flagged 785 individual cell-level issues across 250 of the 712 filings then on file - roughly one in three Nifty Total Market BRSR filings carries at least one cell the algorithmic checks consider questionable, spanning 52 distinct fields (revenue/unit confusions, wage-format errors, complaint-count anomalies, turnover-rate format issues, POSH inconsistencies, workforce subtotal-tie failures, and more). The registry is now kept for every filing year. As at the 2 Nov 2026 data refresh it holds 906 open flags across 280 companies for FY 2025-26 (792 across 251 for FY 2024-25); the live counts sit on the Insights and Explorer sub-tabs of the app. Coverage is partial and a lower bound: not every taxonomy field has an algorithmic check yet, and each new check tends to surface another batch, so the share of filers with a flag is likely to rise above ~40%.

A companion PDF validation layer catches a different class - cells that pass every algorithmic check but are wrong when read against the printed BRSR PDF the filer signed (Adani Ports' wage table is the headline example: every cell is plausibly shaped but materially different from the PDF). Across both layers, the share of filers with at least one issue somewhere is likely approaching half the universe - meaningfully higher than in other regulated XBRL filings (quarterly results, prospectuses), which suggests the BRSR filing pipeline is worth fixing at the source.

Year on year: each check is re-run on each new filing year under the same rules. The first like-for-like reading, on the same companies, FY 2024-25 to FY 2025-26: wage figures that look filed in the wrong unit went from 376 to 352; impossible turnover rates from 19 to 30; parental-leave rates above 100% from 12 to 22; minimum-wage splits that do not add up to the workforce from 38 to 59. Three of the four moved the wrong way.

What this means: aggregate, sector and directional analysis remains highly reliable - 1-3% cell-level noise does not distort distribution shapes, year-on-year comparisons, or peer benchmarking. But for a specific company-level number used for a specific decision, validate it against the printed PDF first.

Classes of issue (and how each is handled)

Which year these describe: the issues below were first documented on the FY 2024-25 filings, and the companies and counts named in them come from that round. Every check is re-run on each new filing year; the current list for either year is in the Data Quality tab.

The source-filing-error registry

Companies whose XBRL contains nonsensical, impossible, or internally inconsistent values are catalogued in a data-quality registry (source errors in the filing, not extraction issues). Values are displayed as reported but flagged with a warning icon in chart drilldowns, and each entry records the company, section, type (unit mismatch / unit correction / unit acknowledged / nonsensical value / missing data / outlier), severity, description and detection date. Detection combines automated scans (e.g. wage F/M ratios over 5x) with manual investigation against the raw XBRL. The full, current registry is in the live Data Quality Explorer.

Open the live VIGIL BRSR Data Quality Explorer on TIGZIG, or see the BRSR methodology page and all VIGIL data sources.