Audit Evidence Documentation for BRSR — Working Papers, Reconciliation Walks, and Management Representations

Last updated 7 May 2026 Reviewed 7 May 2026

How entity-side BRSR working files become audit-grade evidence: source-to-disclosure reconciliation, methodology documentation, testing trails, management reps.

Why audit evidence documentation matters

A reasonable-assurance opinion on BRSR Core KPIs is only as good as the evidence file behind it. If the entity’s working papers don’t walk each disclosed number from source documents through methodology to the final BRSR field, the assurance partner cannot conclude on reasonable assurance — irrespective of how accurate the underlying data may actually be. Audit evidence documentation is the bridge between “the entity has the data” and “the assurance partner can conclude on it”.

This guide walks through how entity-side BRSR working files become audit-grade evidence: the standards framework, the reconciliation discipline, the methodology documentation, the testing trails, the management representations, and the common evidence gaps that surface in BRSR Core engagements.

BRSR Core assurance depends on entity-side working papers that trace each disclosed KPI from source documents through methodology and reconciliation to the final value, with management representations supporting but not replacing source evidence.

The standards framework

SEBI’s BRSR Core circular (March 2023, with subsequent updates) requires reasonable assurance on the BRSR Core KPIs, with a phase-in by market-capitalisation rank — refer to the latest applicable SEBI circular for the exact phase-in dates and entity-cohort thresholds.

The applicable assurance standard should be disclosed in the assurance report and should be aligned to the SEBI framework and the engagement letter. Confirm the specific applicable standard for any given engagement with the assurance partner — the permissibility envelope is set by the latest SEBI circular and clarifications, not by any single source.

Standards commonly referenced as assurance-engagement standards in BRSR / sustainability assurance practice:

ICAI’s SSAE 3000 and IAASB’s ISAE 3000 — generic non-financial / sustainability assurance standards. These are the standards most commonly invoked for assurance over sustainability disclosures broadly.
ICAI’s SAE 3410 and IAASB’s ISAE 3410 — assurance engagements on greenhouse gas statements specifically. Apply to GHG-related disclosures (Scope 1 / 2 inventories, the BRSR Core GHG emission intensity attribute), not generalized to all BRSR Core KPIs. Note: IAASB has announced ISAE 3410 will be withdrawn in favour of ISSA 5000.

Disclosures outside the mandatory Core assurance scope — Section A general disclosures, Section B principle-wise indicators, BRSR Leadership disclosures — are not subject to the prescribed Core assurance mandate. Entities may engage extended-scope assurance over those disclosures voluntarily, subject to engagement scope and standard agreed with the assurance partner.

The five evidence layers

A complete BRSR audit evidence file commonly comprises five layers, each serving a distinct purpose in the assurance process. The list below describes common practice; the specific composition for any given engagement is set by the assurance partner’s procedures and the entity’s working file structure.

Layer 1 — Source documents

The underlying evidentiary records that the disclosed BRSR Core values draw on. The table below illustrates common assurance evidence patterns observed in BRSR Core engagements, not a SEBI-prescribed evidence list. Specific evidence examples (RBI location classification reference, wage-cost reconciliation, the composition of the Openness-of-business evidence set) are implementation choices the entity makes — SEBI prescribes the disclosure, not the working paper composition. Specific evidence requested in any given engagement is determined by the assurance partner’s procedures.

BRSR Core attribute area	Source-document examples commonly observed in practice
GHG emissions intensity	Utility bills (electricity, fuel); fuel consumption logs; refrigerant top-up registers; CEA grid emission factor reference; GHG Protocol calculation working
Water withdrawal intensity	Water meter readings; municipal supply bills; groundwater extraction logs (where applicable); water audit reports
Female wages disclosure	Payroll register; wage code mapping; employee category mapping table
Spend on wellbeing	Payroll register (wellbeing spend categories); HR system extracts; benefits administration records
Job creation in smaller towns	Payroll register with location data; the entity’s chosen location classification reference; the entity’s wage-cost reconciliation working
POSH complaints	POSH complaints register; ICC meeting minutes; resolution records
Openness of business (P1)	The entity’s working files for the relevant sub-indicators (commonly observed examples include board minutes, RPT register, whistle-blower register, and complaints registers across NGRBC Principles — the specific composition is an implementation choice)

The methodology page on Document Evidence Requirements for BRSR Metrics covers the per-KPI evidence list in greater depth.

Layer 2 — Reconciliation walks (source-to-disclosure)

For each BRSR Core attribute, a documented walk that ties the disclosed value back to the underlying source documents. The reconciliation walk typically includes:

Aggregation logic — how multiple source documents (e.g., monthly utility bills) aggregate into the annual reported value
Mapping logic — how source-system categories map to the BRSR taxonomy (e.g., payroll category mapping to BRSR employees / workers)
Adjustments — any adjustments applied (estimations, exclusions, restatements) with the basis documented
Recalculation reference — the working that the disclosed value can be recalculated from, end-to-end, by an independent reviewer

The reconciliation walk is the single most important entity-side working paper for the assurance engagement — without it, the assurance partner spends material engagement effort reconstructing the walk themselves, which delays the engagement and increases the risk of evidence gaps.

Layer 3 — Methodology documentation

For each BRSR Core attribute where the entity has made a methodology choice — scope boundary, calculation convention, materiality threshold, classification basis, year-on-year comparability adjustment — a documented methodology paper that records:

The methodology applied (the specific convention chosen)
The basis for the choice (why this convention, not an alternative)
The year-on-year consistency check (was this the same convention as the prior year; if not, the change disclosure)
The references applied (SEBI circular, GHG Protocol, Companies Act section, etc.)

Methodology documentation is the entity’s audit trail for judgement calls — the assurance partner reviews methodology documentation when challenging applicability, scoping, or calculation conventions on Core KPIs.

Layer 4 — Testing evidence

The working papers that document the assurance partner’s testing — sampling working, recalculation working, walk-throughs of process controls, confirmations from third parties (where applicable). This layer is the assurance partner’s working paper file, not the entity’s — but the entity’s working papers are the primary input the assurance partner draws from.

Common testing procedures observed in BRSR Core engagements:

Recalculation testing — independent recalculation of selected disclosed values from source documents
Sampling testing — sample-based testing of underlying transactions (e.g., sample of payroll entries, sample of utility bills)
Walk-through testing — process control testing for the entity’s data-collection and review controls
Analytical procedures — year-on-year and ratio-based analytical review
Third-party confirmation — where applicable (e.g., utility provider, auditor of consolidated subsidiary)

Layer 5 — Management representations

Written representations from management, signed by management in accordance with the engagement’s governance requirements, covering matters that supplement the procedures performed. Common matters covered in BRSR management representations include:

Completeness of the BRSR disclosures (no material disclosures omitted)
Accuracy of judgement calls made by management (materiality assessment, scoping decisions, methodology conventions)
Consistency of methodology applied year-on-year
Confirmation that source documents provided are the complete record
Disclosure of any subsequent events affecting the BRSR period
Management’s responsibility for the BRSR preparation

Management representations are corroborative evidence, not primary evidence — the assurance partner cannot conclude on reasonable assurance based solely on representations. Representations supplement the procedures performed against source documents and process controls; they do not substitute for source testing.

Common evidence gaps observed in BRSR Core engagements

These are common practice patterns observed in BRSR engagements — not SEBI-recognised categories of finding. Each is framed as an observation, not a categorical rule.

Gap 1 — Missing reconciliation walk for the largest-magnitude KPI

The single most common evidence gap. The entity has the source documents and the disclosed value, but the bridge between them — the reconciliation walk — is implicit rather than documented. Remediation: build the reconciliation walk as a structured working paper before engagement kick-off, not during the engagement.

Gap 2 — Methodology applied is undocumented or year-on-year inconsistent

Common for KPIs with judgement-heavy choices: scope boundary (which subsidiaries / value-chain partners), classification basis (e.g., “smaller towns” definition, employee vs worker mapping), calculation convention (spend-based vs activity-based for GHG, distance-based vs survey-based for commuting). When the methodology applied isn’t documented or has shifted year-on-year without disclosure, the assurance partner has to either reconstruct the methodology working themselves or modify the assurance opinion.

Gap 3 — Source-document completeness can’t be confirmed

For workforce / payroll / utility / CSR data, the entity provides the source documents — but cannot confirm completeness (“we believe this is the complete record” without a verifiable completeness check). Common remediation: independent reconciliation against a controllable total (e.g., payroll register against the audited financials’ employee benefit expense; utility bills against the annual energy consumption register).

Gap 4 — Subsidiary scope boundaries inconsistent across BRSR sections

A subsidiary included in Section A’s holding-subsidiary list is excluded from Section B’s workforce data, or vice versa. The boundary basis applied (operational control / financial control / equity-share) is itself an internal convention drawn from adjacent reporting frameworks (GHG Protocol, Ind AS 110), not SEBI-prescribed for BRSR — but consistency across BRSR sections is the assurance partner’s expectation. Remediation: a single boundary-basis register applied consistently, with the basis disclosed.

Gap 5 — Workforce mapping table is missing or inconsistent

The HRIS rarely uses BRSR employee / worker categorisation natively. Without an explicit mapping table from payroll categories to BRSR fields, the workforce-related KPIs (Female Wages Disclosure, Spend on Wellbeing) can’t be cleanly traced from source. The mapping table is itself a reviewable workpaper and should be retained as part of the BRSR working file.

Gap 6 — Year-on-year restatement undisclosed

When the entity changes a methodology mid-cycle (refining Cat 1 spend factors to activity-based, switching the workforce mapping table, restating prior-year figures), the year-on-year restatement should be disclosed alongside the disclosed value. Undisclosed restatements show up as analytical-procedure exceptions in the assurance work and need management explanation.

Gap 7 — Management representations not aligned with disclosures

The representation letter signed by management asserts completeness / accuracy at a level that the underlying working papers don’t support. Common remediation: align the representation letter wording to what the working papers can substantiate, and obtain additional procedure work where the representation is broader than the evidence.

A practical working paper file structure

The below describes a commonly observed working paper file structure for a BRSR Core engagement. The exact structure varies by entity size, partner CA firm methodology, and the specific Core KPIs in scope.

BRSR Working File / FY [year]
  /00 Engagement memorandum
    - Engagement letter (entity ↔ partner CA firm)
    - Scope inclusion / exclusion register
    - Materiality benchmark working
  /01 Section A General Disclosures
    - Section A working paper (per the Section A pre-fill workflow)
    - MCA21 master data extract
    - Section 135 CSR Annual Report
    - Complaints aggregation working
  /02 Section B NGRBC Principle-wise
    - Per-Principle working papers
  /03 BRSR Core attributes (one folder per attribute)
    /03a GHG intensity per revenue
      - Source documents
      - Reconciliation walk
      - Methodology documentation
      - Recalculation working
    /03b Water withdrawal intensity
      - [same structure]
    /03c Female wages disclosure
      - [same structure]
    [...one folder per Core attribute]
  /04 Methodology decisions
    - Scope boundary register
    - Materiality assessment working
    - Workforce mapping table (employees / workers)
    - Year-on-year comparability log
  /05 Management representations
    - Final representation letter
  /06 Final BRSR submission
    - Final BRSR PDF
    - Final BRSR XBRL
    - Signed assurance certificate from partner CA firm
    - Stock exchange filing acknowledgements

The structure mirrors the BRSR Format itself (Section A / B / C) so the working papers map cleanly to the assurance partner’s review path.

Where Batchwise fits (service description — separate from the regulatory workflow above)

The sections above describe the regulatory and assurance-evidence discipline for BRSR — the working paper layers, reconciliation walks, methodology documentation, and management representations that any entity preparing for BRSR Core assurance would assemble regardless of tooling.

The section below describes Batchwise’s service in this discipline. The two are deliberately kept separate so readers can distinguish what audit evidence documentation is from what Batchwise does.

Batchwise is a workflow and data-preparation service layered over the BRSR audit evidence discipline — not part of the assurance framework itself. The entity remains responsible for the BRSR submission and sign-off; the partner CA firm remains responsible for the assurance procedures, the assurance file, and the assurance opinion.

In practice, Batchwise’s role in the audit-evidence layer covers:

Helping structure the entity-side working file under management’s responsibility — supporting the assembly of source documents, reconciliation walks, and methodology documentation per the file structure described above. Management retains responsibility for the data, the working papers, and the representation letter content; Batchwise structures the workflow.
Source-to-disclosure traceability — supporting traceability from each disclosed BRSR Core value back to the underlying source documents, with audit-trail
Methodology documentation templates — pre-structured methodology documentation templates for each Core KPI’s common judgement calls (scope, classification, calculation convention), for the entity to populate and sign off
Pre-engagement evidence-gap diagnostic — flag-listing common evidence gaps before the assurance engagement starts, so remediation happens during data preparation rather than during the assurance window
Management representation drafting support — drafting support for the representation letter aligned to the assembled working papers; management reviews, edits, and signs

The signed assurance opinion is always the partner CA firm’s, on the partner CA firm’s letterhead, under the partner CA firm’s signing partner’s DSC. Batchwise’s role is workflow and data-preparation support under management’s responsibility; the assurance procedures, assurance file, and assurance opinion remain entirely with the partner CA firm.

What this guide captures and what it doesn’t

Captures:

The standards framework around BRSR Core assurance (SEBI’s permissibility framework, ICAI / IAASB standards commonly referenced)
The five evidence layers (source documents, reconciliation walks, methodology documentation, testing evidence, management representations)
Common evidence gaps observed in practice
A practical working paper file structure
How Batchwise’s data-preparation service sits relative to the assurance discipline

Doesn’t capture:

Per-KPI evidence detail — see Document Evidence Requirements for BRSR Metrics
The assurance partner’s internal methodology and quality-control procedures — these vary by firm and are subject to ICAI / IAASB Quality Control Standards
Reasonable-assurance vs limited-assurance procedure depth in detail — refer to the applicable assurance standard text
ISSA 5000 transition specifics — see related ISSB / IFRS Foundation publications

Document Evidence Requirements for BRSR Metrics — per-KPI evidence list (utility bills, payroll, CSR Annual Report, etc.)
BRSR Section A Pre-fill Workflow — Section A working paper assembly
DSC Signing for BRSR Reports — the filing event after the assurance opinion is signed
Materiality Assessment Walkthrough — the materiality framework that anchors several Core KPIs’ applicability calls
Scope 3 Emissions for Service Companies — Leadership Scope 3 evidence considerations (where extended-scope assurance applies)
BRSR Core Assurance Service — Batchwise’s BRSR Core engagement scope
Standalone GHG / ISAE 3410 Service — GHG inventory assurance under the IAASB / ICAI standards

Frequently asked questions

What level of evidence does reasonable assurance over BRSR Core actually require?

Per the assurance standards commonly applied (SEBI's BRSR Core circular permits ICAI standards including SSAE 3000 / SAE 3410, and IAASB's ISAE 3000 / ISAE 3410, with the standard applied disclosed in the assurance report — refer to the latest applicable SEBI circular for current permissibility), reasonable assurance over BRSR Core KPIs requires evidence at a level analogous to a financial-statement audit: testing of the entity's processes and controls over the underlying sustainability data, recalculation testing of the disclosed numbers, traceability from disclosed value back to source data, and written representations from management. The assurance opinion concludes that the BRSR Core information is prepared, in all material respects, in accordance with the criteria. Limited assurance, by contrast, requires materially less procedure depth and concludes negatively (nothing has come to attention).

What's the difference between source documents, working papers, and the assurance file?

Source documents are the underlying evidentiary records — utility bills, payroll registers, CSR Annual Report, Section 135 working, GST returns, MCA21 master data extracts, audited financials. Working papers are the entity's internal documentation that walks each disclosed BRSR number from the source documents to the BRSR field — including calculation working, methodology choices, scoping decisions, and reconciliation walks. The assurance file is the partner CA firm's own working paper file documenting the procedures they performed, the evidence obtained, the conclusions drawn, and the management representations received. The entity prepares working papers; the assurance partner prepares the assurance file; the source documents are the underlying records that both rely on. ESG data collection templates are commonly treated like audit working papers — methodology documented, version-controlled, signed off.

Does the entity have to retain audit evidence after the BRSR is filed?

Yes — for the duration prescribed by the entity's record-retention policy and applicable law. The audit evidence underlying assured BRSR Core disclosures should be retained alongside the corresponding source records, with the period determined by the entity's records-retention policy and the applicable statutory and regulatory framework. The assurance partner's file is retained per the partner CA firm's own retention policy under applicable ICAI / IAASB Quality Control Standards. Refer to the entity's policy, the Companies Act / SEBI provisions applicable to the specific document type, and the partner CA firm's policy for the specific retention period.

What happens when the assurance partner identifies an evidence gap?

Evidence gaps are an assurance-risk management matter, not a fixed SEBI rule. Where the entity's working papers don't trace cleanly from source to disclosed value, or where the methodology applied isn't documented, or where source documents are missing, the assurance partner manages the gap as part of the engagement's risk procedures. The common sequence observed in practice: the assurance partner raises the gap with management; management addresses it (by retrieving source documents, documenting the methodology applied, restating the disclosed value, or providing supporting evidence); the assurance partner re-tests. Where the gap can't be remediated within the engagement timeline, the assurance partner exercises professional judgement on the engagement-level response per the applicable assurance standard. Most evidence gaps that surface in BRSR Core engagements are remediable with effort; the cost of remediation rises sharply close to the filing deadline.

Are management representations alone enough evidence for any BRSR disclosure?

No — management representations are corroborative evidence, not primary evidence. Per the assurance standards, the assurance partner cannot conclude on reasonable assurance based solely on management representations; representations supplement the procedures performed against source documents and process controls. Common practice patterns: management representations cover (a) completeness of the BRSR disclosures (no material disclosures omitted), (b) accuracy of judgement calls made by management (materiality assessment, scoping decisions), (c) consistency of methodology applied year-on-year, (d) confirmation that source documents provided are the complete record. Representations are commonly obtained near the end of the engagement and signed by the relevant authorised signatory.