EHSSARAL RESEARCH

Environmental Compliance Is Not Environmental Accounting

The Missing Data Layer Between Indian Industrial Compliance and Sustainability Reporting

By Harshal T. Gajare

An Indian factory can meet its environmental obligations and still struggle to produce reliable BRSR, GRI or GHG data. This paper explains why environmental compliance and environmental accounting are structurally different-and proposes the missing data layer between them.

Previous Indian work has already documented weaknesses in the compilation and comparability of environmental data under BRSR. The Centre for Science and Environment's review of company disclosures, for example, found inconsistencies in environmental reporting and called for greater granularity and transparency. More recent research has attempted to cross-check BRSR environmental metrics against CPCB/SPCB and Form V information. These efforts demonstrate the problem. 

This paper asks a different question: What if the gap is not primarily in the reporting template, but in the absence of a persistent accounting layer between daily environmental compliance and corporate sustainability disclosure?

in This article - The term “environmental accounting” in this paper refers primarily to structured accounting of physical environmental flows and activities, rather than environmental cost accounting or natural-capital accounting.

Executive Summary

An industrial facility can hold a valid Consent to Operate, conduct prescribed environmental monitoring, maintain hazardous-waste records, file statutory returns and send waste only to authorised facilities-and still struggle to produce reliable sustainability data.

This apparent contradiction is not necessarily a failure of the EHS team.

It exists because environmental compliance and environmental accounting were designed to answer different questions.

Environmental compliance primarily asks:

Is the facility operating within applicable legal conditions, limits and obligations?

Environmental accounting asks:

What physically happened during the reporting period, how much occurred, how was the number derived, and can it be traced back to reliable evidence?

The first is largely a system of conditions, thresholds, permissions and evidence of compliance.

The second requires a ledger of environmental flows and activities.

Neither system is wrong.

The problem emerges when companies attempt to move directly from compliance records into BRSR, GRI, greenhouse-gas inventories, customer sustainability questionnaires or other disclosures-often by reconstructing the missing accounting layer through spreadsheets at the end of the year.

This paper argues that an important layer is missing between India's environmental-compliance infrastructure and modern sustainability reporting:

The Environmental Accounting Ledger

A useful architecture can be visualised as:

Layer 1 - Operational Environmental & Compliance Records

↓

Layer 2 - Environmental Accounting Ledger

↓

Layer 3 - Sustainability Disclosure, Assessment & Assurance

Many companies possess significant amounts of Layer 1 data.

They need Layer 3 outputs.

But Layer 2 often does not continuously exist.

It is reconstructed later.

That creates cost, inconsistency and what this paper calls sustainability data debt: the future reporting burden created when today's environmental activity is captured at insufficient granularity, context or evidence quality for tomorrow's legitimate reporting requirements.

The solution should not be another large environmental return.

Instead, environmental activity should increasingly be captured as structured, evidence-linked data capable of being reused.

A hazardous-waste dispatch, water-meter reading or fuel transaction should remain a traceable operational fact before it becomes an annual return, intensity ratio, emissions figure or sustainability disclosure.

This leads to the central architectural principle of this paper:

One underlying fact can have multiple legitimate uses.

The regulator can use the attributes required for environmental law.

The EHS team can use the same event for compliance management.

The sustainability function can apply an accounting methodology.

An assessment or assurance provider can examine the evidence lineage.

Different systems can therefore interpret the same physical event without requiring the event itself to be repeatedly reconstructed.

There is, however, an important trade-off.

Better environmental data creates greater accountability.

A transaction-level ledger may expose quantity mismatches, unexplained balances and historical inconsistencies that aggregated records may obscure. Any movement toward greater environmental traceability therefore has to address ownership, confidentiality, corrections, version history and appropriate access alongside interoperability and reporting efficiency.

The objective is not to turn State Pollution Control Boards into ESG agencies.

Nor is it to make environmental compliance responsible for every social, governance or value-chain disclosure.

The opportunity is narrower and more practical:

Create a reliable environmental data foundation from normal industrial operations.

If that foundation exists, regulatory reporting and sustainability reporting no longer need to begin from separate versions of the same physical reality.

India's next stage of environmental digitisation should therefore move beyond simply digitising forms.

It should begin digitising the environmental events beneath those forms.

Contents

Part I - The Structural Mismatch

1. The Industrial Paradox
2. Thresholds Versus Ledgers
3. Neither System Is Wrong

Part II - Where the Data Chain Breaks

4. Hazardous Waste
5. Water
6. Energy, Fuel and GHG Accounting
7. Continuous Monitoring Is Not Continuous Accounting
8. Sustainability Data Debt

Part III - The Missing Architecture

9. The Three-Layer Environmental Data Architecture
10. One Underlying Fact, Multiple Legitimate Uses
11. Measurements, Transactions and Derived Data
12. The Minimum Environmental Data Model
13. Environmental Balances, Uncertainty and Estimation
14. Capture Once, Preserve the Evidence, Calculate Many Times
15. What Does Not Belong in the Environmental Ledger

Part IV - Making the Architecture Work in India

16. BRSR and the Growing Importance of Data Lineage
17. This Is Not an Argument for More Compliance
18. MSMEs and Supply-Chain Data Pressure
19. Better Data Also Creates More Accountability
20. SPCBs Should Not Become ESG Agencies
21. How India's Environmental Data Architecture Could Evolve
22. What This Changes for EHS Professionals and Environmental Software
23. From Compliance-Ready to Sustainability-Data-Ready
24. Conclusion

PART I - THE STRUCTURAL MISMATCH

1. The Industrial Paradox

Consider a manufacturing facility at the end of a financial year.

Its environmental team has worked throughout the year.

The Consent to Operate is valid.

Environmental monitoring has been conducted.

Effluent-treatment records have been maintained.

Hazardous-waste records are available.

Waste movements have been documented.

Laboratory reports have been filed.

Annual environmental returns have been prepared.

Electricity bills exist.

Fuel purchase records exist.

Water meter readings exist.

Production data exists somewhere else in the organisation.

From a conventional environmental-compliance perspective, the facility may be reasonably well managed.

Then the corporate sustainability team sends a request.

It asks for:

• water withdrawal by source;
• water consumption;
• water recycled and reused;
• total energy consumed;
• renewable and non-renewable energy;
• Scope 1 emissions;
• Scope 2 emissions;
• GHG intensity;
• hazardous and non-hazardous waste generated;
• waste diverted from disposal;
• waste directed to disposal;
• production-normalised environmental intensity;
• year-on-year variation;
• calculation methodology;
• supporting evidence.

Suddenly, hundreds of existing environmental records do not automatically become answers.

The EHS manager opens Excel.

Accounts is asked for invoices.

Production is asked for output.

Stores provides diesel information.

Waste manifests are reconciled.

Different units are converted.

Old meter records are checked.

Missing periods are investigated.

Assumptions are made.

Evidence is searched across folders and emails.

A reporting process begins that looks less like disclosure and more like reconstruction.

This is often called an ESG reporting problem.

But the reporting template is merely where the weakness becomes visible.

The deeper problem occurred earlier.

The environmental activity was captured for one immediate purpose but was not preserved with enough structure to support another legitimate use later.

2. Thresholds Versus Ledgers

The mechanical difference can be reduced to two questions.

Environmental compliance frequently asks:

Did the facility stay within the required boundary?

Environmental accounting asks:

What moved through the system during the period?

Environmental regulation necessarily deals with questions such as:

• permitted quantities;
• concentration standards;
• operating conditions;
• authorised activities;
• monitoring frequencies;
• storage requirements;
• waste classifications;
• approved receivers;
• statutory documentation;
• reporting deadlines.

An effluent result may therefore be compared with a prescribed concentration.

A stack-monitoring result may be compared with the applicable standard or Consent condition.

A hazardous-waste activity may be checked against authorised waste categories and quantities.

A movement may be checked for appropriate documentation and an authorised destination.

These are critical environmental controls.

Environmental accounting has another task.

It must accumulate physical activity.

How much water entered the facility?

From which sources?

Where was it used?

How much was recycled?

How much left the boundary?

How much was consumed?

How much fuel was burned?

In which assets?

How much electricity was used?

How much waste was generated?

What happened to it?

How much production occurred?

Which methodology transformed these underlying facts into a disclosed environmental metric?

The difference can be represented as follows:

This distinction is not absolute.

Indian environmental regulation already requires substantial quantities of numerical data.

Online monitoring can produce high-frequency measurements.

Hazardous-waste registers contain transactional information.

Environmental Statements contain material, water and pollution-related information.

Likewise, sustainability frameworks contain qualitative disclosures, policies and regulatory information.

But the design centre is different.

One system principally protects environmental and regulatory boundaries.

The other attempts to account for environmental performance across time.

That distinction explains much of today's reporting friction.

3. Neither System Is Wrong

It would be easy to conclude from this argument that Indian environmental compliance collects the "wrong" information.

That would be inaccurate.

Pollution-control legislation, Consent mechanisms, hazardous-waste rules and associated monitoring systems were developed to regulate environmental impacts and determine whether facilities were meeting legal obligations.

A hazardous-waste manifest is not deficient because it does not contain every field required by every sustainability reporting framework.

A Consent to Operate is not deficient because it does not calculate Scope 2 emissions.

A laboratory report is not deficient because it does not automatically generate a corporate water footprint.

They were designed for different purposes.

Similarly, sustainability reporting cannot replace pollution-control regulation.

A company may report improving water intensity while violating an effluent standard.

A facility may reduce GHG emissions while storing hazardous waste improperly.

An organisation may achieve a strong sustainability rating and still breach a Consent condition.

Environmental performance and environmental legality overlap, but they are not identical concepts.

The objective should therefore not be:

Turn environmental compliance into ESG reporting.

It should be:

Preserve the underlying environmental facts well enough that different legitimate systems can use them.

That distinction is fundamental.

PART II - WHERE THE DATA CHAIN BREAKS

4. Hazardous Waste: Compliance Data That Almost Becomes a Ledger

Hazardous-waste management provides one of the clearest examples.

Indian industrial facilities handling hazardous waste may maintain records under the Hazardous and Other Wastes (Management and Transboundary Movement) Rules, 2016 and applicable amendments.

The practical information chain can include:

Generation

↓

Form 3 records

↓

Storage

↓

Dispatch

↓

Manifest / movement documentation

↓

Weighment

↓

Recycler / co-processor / TSDF

↓

Acknowledgement or other evidence

↓

Annual return

From a data-architecture perspective, this is already surprisingly close to a transaction ledger.

It contains physical movement.

It contains quantities.

It contains categories.

It contains destinations.

It contains evidence.

But the purpose of these records remains hazardous-waste regulation.

A downstream sustainability framework may classify the same physical activity according to another taxonomy.

For example, GRI 306 distinguishes waste diverted from disposal from waste directed to disposal and further differentiates particular recovery and disposal operations.[1]

A regulatory record may therefore contain enough information to demonstrate authorised movement without necessarily containing every semantic attribute required to map the same event automatically into another disclosure framework.

This distinction is subtle but important.

The conclusion should not be:

Form 4 does not contain enough ESG data.

The conclusion should be:

The waste transaction contains more potential information than any one regulatory form needs.

A better architecture therefore preserves the underlying movement.

A structured waste transaction might include:

• facility ID;
• generating process;
• waste name;
• statutory category/code;
• hazardous or non-hazardous classification;
• date or reporting period;
• quantity;
• unit;
• storage location;
• dispatch date;
• transporter;
• receiver;
• receiver authorisation details;
• regulatory destination category;
• actual treatment/recovery/disposal route where known;
• manifest reference;
• weighment evidence;
• receiver acknowledgement;
• source documents;
• responsible person;
• revision history.

Then different systems can consume different attributes.

The regulatory return sees one view.

The internal waste reconciliation sees another.

GRI mapping can use another.

An auditor can use the evidence chain.

The transaction itself does not need to be recreated.

5. Water: A Compliant Outlet Is Not a Water Ledger

Water makes the same distinction even more visible.

A factory's regulatory attention may reasonably focus on:

• permitted water use;
• wastewater generation;
• ETP/STP operation;
• discharge conditions;
• reuse requirements;
• ZLD requirements where applicable;
• effluent-quality limits;
• required monitoring.

All are important.

But sustainability water accounting asks a broader physical-flow question.

A simplified system might look like:

Source

↓

Withdrawal

↓

Process / utility use

↓

Wastewater generation

↓

Treatment

↓

Recycle / reuse

↓

Discharge

↓

Consumption

GRI 303 separately addresses water withdrawal, discharge and consumption and recognises that water consumption may, where direct measurement is unavailable, be calculated using withdrawal and discharge data.[2]

That is fundamentally a balance.

An ETP sample demonstrating that BOD, COD or TSS meets a prescribed limit does not answer:

• how much water entered the factory during the year;
• which sources supplied it;
• how much was internally reused;
• how much left through permitted discharge;
• how much was lost through evaporation;
• how much was incorporated into product;
• how much remained in storage where relevant;
• how the reported water-consumption figure was derived.

The monitoring report is not weak.

It is answering another question.

The same issue applies to Zero Liquid Discharge.

A ZLD condition describes an important pollution-control outcome.

But "zero liquid discharge" does not, by itself, constitute a complete water account.

A sustainability system may still need to understand:

withdrawal → internal circulation → recycle → evaporation/loss → consumption

This yields a useful distinction:

A compliant water system is not automatically an accounted water system.

6. Energy, Fuel and GHG Accounting

Carbon accounting exposes the organisational fragmentation particularly clearly.

Suppose a factory uses diesel.

Different departments may hold different parts of the underlying fact.

Accounts

holds invoices and expenditure.

Stores

holds fuel receipts and inventory.

Maintenance

holds DG runtime.

EHS

holds emissions-monitoring records.

Production

holds activity information.

Sustainability

needs GHG emissions.

The organisation possesses data.

But it does not necessarily possess a continuous environmental accounting ledger.

Compare:

August HSD consumed: 25,000 litres

with:

14 August
Plant A
DG-02
HSD issued: 1,200 litres
source document: stores issue record
equipment activity reference available
reporting boundary identified

The first preserves the total.

The second preserves the event and its lineage.

GHG Protocol approaches use activity data together with appropriate emission factors to derive emissions, and its Scope 2 guidance likewise discusses electricity activity data and applicable emission-factor approaches.[3][4]

If the detailed operational attributes have already been collapsed into a single monthly figure, later analysts may have to rely on allocations or assumptions that did not exist at the time of the activity.

Sometimes estimates are entirely legitimate.

The architectural problem arises when estimation is necessary only because useful source context was discarded.

7. Continuous Monitoring Is Not Continuous Accounting

India already has important examples of environmental digitisation.

Online Continuous Emission and Effluent Monitoring Systems are one of them.

CPCB's OCEMS protocols cover technology, installation, operation, calibration and electronic submission of online monitoring data.[5]

This demonstrates an important point:

Indian environmental regulation is already capable of working with machine-generated environmental information.

But monitoring and accounting remain different functions.

An online monitoring system may answer:

What concentration was recorded?

Was a parameter exceeding a prescribed level?

What was the trend?

An environmental account may ask:

What cumulative mass was emitted during the reporting period?

Depending on the pollutant and calculation methodology, that may additionally require information such as:

• volumetric flow;
• operating duration;
• equipment status;
• process activity;
• fuel consumption;
• production;
• calculation factors.

The implication is not that continuous monitoring is inadequate.

It is that:

Continuous monitoring is not automatically continuous accounting.

Telemetry is an input.

Accounting is an interpretation of physical activity over a defined boundary and period.

Connecting the two is an architectural problem.

8. Sustainability Data Debt

The current approach creates a hidden liability.

This paper calls it:

Sustainability Data Debt

Sustainability data debt is:

The future reporting and verification burden created when today's environmental activity is captured at insufficient granularity, context or evidence quality for tomorrow's legitimate requirements.

Consider a company that retains only:

Diesel consumed in August: 25,000 litres.

Six months later, it wants to understand how much was used by different sources.

If that allocation was never recorded, software cannot recreate the historical fact with certainty.

Or imagine a water meter was replaced during the year but the old meter identification and closing reading were not preserved.

The annual total may still be estimated.

But the lineage has weakened.

Or imagine an environmental transaction was documented sufficiently for a regulatory purpose, while a downstream treatment attribute required by a later sustainability classification was never captured.

That information may no longer exist.

The problem is deeper than "bad Excel."

Environmental information that was never captured cannot always be reconstructed later.

Companies frequently attempt to service this debt through:

• retrospective reconciliation;
• employee memory;
• proportional allocation;
• email searches;
• invoice reconstruction;
• consultant calculations;
• year-end assumptions.

Environmental accounting will always contain legitimate estimation and professional judgement.

But there is a meaningful difference between:

estimating something that could not reasonably be directly measured

and

estimating something because the underlying operational information was discarded.

A mature environmental data architecture should reduce the second category.

PART III - THE MISSING ARCHITECTURE

9. The Three-Layer Environmental Data Architecture

The problem can now be visualised more clearly.

LAYER 3 - SUSTAINABILITY DISCLOSURE, ASSESSMENT & ASSURANCE

BRSR / BRSR Core
GRI
GHG inventories
customer sustainability questionnaires
ESG-related disclosures
assessment / assurance

↑

classification
aggregation
boundary rules
methodology
calculation

↑

LAYER 2 - ENVIRONMENTAL ACCOUNTING LEDGER

Water balance
Energy balance
Waste flows
Material flows
GHG activity data
Environmental intensities
Methodologies
Evidence lineage
Revision history

↑

structured records
transactions
measurements
telemetry
documents

↑

LAYER 1 - OPERATIONAL ENVIRONMENTAL & COMPLIANCE RECORDS

Consent conditions
Meters
Form 3
manifest records
annual returns
Environmental Statement
laboratory reports
OCEMS
ETP logs
fuel records
utility bills
production data
waste certificates

The central problem is:

Many companies attempt to jump directly from Layer 1 to Layer 3.

Excel becomes the temporary bridge.

At reporting time, pieces of Layer 1 are gathered.

A temporary environmental account is created.

Metrics are calculated.

The disclosure is submitted.

The workbook is archived.

The next reporting period begins.

The company therefore repeatedly rebuilds the missing middle layer.

This is inefficient because Layer 2 should be a continuing operational asset, not an annual reporting project.

10. One Underlying Fact, Multiple Legitimate Uses

This leads to one of the paper's most important principles:

Standardise the facts before trying to standardise every report.

Reporting frameworks change.

Regulatory requirements change.

Emission factors change.

Boundaries change.

Companies enter different supply chains.

Customers ask different questions.

New reporting regimes emerge.

Attempting to create one permanent final "ESG number" is therefore fragile.

Instead, preserve the underlying event.

For example:

24 August
720 litres HSD
Plant A
DG-02
stores issue reference
invoice/batch reference
responsible function
timestamp

The regulator may need only a subset.

The EHS team may use it for fuel reconciliation.

The energy manager may calculate equipment performance.

The sustainability team may use it in a GHG inventory.

An assessment or assurance provider may examine the evidence.

The physical event remains unchanged.

This is the difference between:

storing reports

and

storing environmental events.

11. Measurements, Transactions and Derived Data

A mature environmental system should also distinguish between three different classes of data.

11.1 Observed or Measured Data

This is directly observed from an instrument, test or physical measurement.

Examples:

Water meter reading: 842 m³

Stack PM concentration: X mg/Nm³

Weighbridge quantity: 4,510 kg

Measured data should ideally preserve attributes such as:

• instrument;
• unit;
• timestamp;
• calibration status where relevant;
• sampling/measurement method;
• source location;
• evidence.

11.2 Transaction Data

A transaction describes an environmental event.

For example:

4.5 tonnes of hazardous waste dispatched from Plant A to Recycler B on 18 September.

The quantity may itself originate from a measurement, but the transaction adds:

• sender;
• destination;
• date;
• regulatory category;
• transporter;
• documentation;
• purpose or treatment route.

Transactions describe movement or activity.

11.3 Derived Data

Derived data is produced by calculation.

For example:

Annual Scope 1 emissions = X tCO₂e

or:

Water intensity = X m³ per tonne of product.

Derived metrics depend on:

underlying activity

calculation method

assumptions/factors

boundary

The architecture should therefore preserve the lineage:

Measurement / Transaction → Calculation → Disclosure

This is important because methodologies can change without changing historical physical activity.

If an emission factor is updated, the underlying fuel activity remains valid.

If a reporting framework changes a classification, the historical waste transaction does not need to be reinvented.

If an intensity denominator changes, the source environmental data remains intact.

This separation between fact and interpretation is fundamental to a resilient environmental ledger.

12. The Minimum Environmental Data Model

If sustainability-data-readiness is to emerge from daily operations, what should the environmental ledger actually preserve?

This paper proposes a conceptual:

Minimum Environmental Data Model - MEDM

The MEDM is not proposed as another statutory form.

It is a design framework describing the minimum kinds of structured information necessary to preserve environmental events and their lineage.

12.1 Facility and Boundary

Every environmental event must belong to a clearly identified source.

Useful fields include:

• legal entity;
• facility/site ID;
• site location;
• operating unit;
• process;
• equipment/source ID where relevant;
• regulatory jurisdiction;
• reporting period;
• operating status;
• applicable production unit.

Without stable identifiers, multi-site aggregation quickly becomes unreliable.

12.2 Production and Activity

Environmental intensity requires context.

Relevant data may include:

• product;
• production quantity;
• unit;
• line/process;
• operating hours;
• relevant throughput;
• shutdown periods.

The objective is not to reproduce the entire production ERP inside an environmental system.

It is to preserve enough activity information to interpret environmental performance.

12.3 Water

A structured water record may contain:

• withdrawal source;
• meter/source ID;
• quantity;
• unit;
• timestamp or period;
• process destination;
• treatment quantity;
• recycle quantity;
• reuse quantity;
• discharge quantity;
• discharge destination;
• water-quality evidence where relevant;
• meter calibration status;
• measured/calculated/estimated status;
• methodology;
• evidence.

This allows systems to distinguish a regulatory water limit from a physical water balance.

12.4 Energy and Fuel

Useful attributes include:

• energy/fuel type;
• quantity;
• unit;
• date;
• facility;
• consuming equipment/process where reasonably available;
• electricity meter;
• supplier/source;
• invoice;
• renewable/non-renewable attribute where relevant;
• calculation metadata;
• evidence.

The primary objective is to preserve activity before it becomes a downstream metric.

12.5 Waste

A structured waste event may contain:

• waste stream;
• statutory category/code;
• hazardous/non-hazardous classification;
• generating process;
• generation period;
• quantity;
• unit;
• storage location;
• opening inventory;
• dispatch quantity;
• closing inventory;
• transporter;
• receiver;
• receiver authorisation;
• regulatory destination category;
• recovery/treatment/disposal route where known;
• manifest;
• weighment;
• acknowledgement;
• evidence.

This allows one transaction chain to support multiple legitimate classifications later.

12.6 Air and Emissions

Relevant attributes can include:

• source;
• stack/source ID;
• process/fuel;
• pollutant;
• measured concentration;
• unit;
• flow where relevant;
• operating duration;
• sampling/monitoring method;
• date/time;
• laboratory;
• OCEMS record where applicable;
• production/activity context;
• applicable limit;
• evidence.

The compliance view and the accounting view can then coexist.

12.7 Wastewater

A structured wastewater flow could include:

• generating process;
• influent quantity;
• treatment system;
• treated quantity;
• recycle/reuse;
• discharge quantity;
• discharge location;
• monitored quality;
• sampling date;
• meter/instrument;
• laboratory report;
• evidence.

A quality test and a quantity flow are not interchangeable.

A complete system needs both where relevant.

12.8 Evidence

Every material environmental number should ideally have a path back to its source.

Possible evidence includes:

• meter reading;
• utility bill;
• fuel invoice;
• stores record;
• weighbridge slip;
• manifest;
• recycler acknowledgement;
• TSDF record;
• laboratory report;
• calibration certificate;
• production record;
• telemetry;
• calculation workbook;
• responsible-person approval.

The essential concept is:

A number should know where it came from.

12.9 Methodology and Revision

Environmental accounting involves judgement.

The ledger should therefore preserve:

• measured/calculated/estimated status;
• data source;
• calculation formula;
• conversion factor;
• emission factor;
• factor source/version;
• assumption;
• reporting boundary;
• responsible person;
• approval;
• correction;
• reason for correction;
• timestamp;
• previous value.

This converts a mutable spreadsheet number into a governed environmental record.

13. Environmental Balances, Uncertainty and Estimation

Calling this an "environmental ledger" does not mean physical environmental balances should be treated as financial double-entry accounting.

Physical systems contain uncertainty.

A water balance may contain:

• meter accuracy limitations;
• unmetered minor uses;
• evaporative loss;
• blowdown;
• moisture;
• storage changes;
• instrument drift;
• estimated flows.

Waste quantities may vary because of:

• moisture;
• weighing equipment accuracy;
• tare;
• sampling;
• material condition.

Emissions measurements also have method and instrument uncertainty.

Therefore, a credible environmental ledger should not force an artificial:

100.000% closure

where the physical system does not support it.

Instead, it should preserve:

measurement

uncertainty

estimation

methodology

residual

explanation

For example, a water balance closing at 97% may be more credible than a manually adjusted spreadsheet claiming 100% closure without explaining how the remaining 3% was resolved.

This principle matters greatly for assurance.

Transparency about uncertainty is stronger than false numerical precision.

The objective of an environmental ledger is therefore not mathematical perfection.

It is traceable environmental reasoning.

14. Capture Once, Preserve the Evidence, Calculate Many Times

A popular digitisation idea is:

Enter once, report everywhere.

That is attractive but too simplistic.

Different frameworks legitimately:

• define boundaries differently;
• classify activities differently;
• use different denominators;
• apply different methodologies;
• require different factors.

The better principle is:

Capture the physical event once.

Preserve its evidence.

Calculate it many times.

Suppose electricity consumption is captured correctly.

That underlying activity may later support:

• energy management;
• environmental intensity;
• BRSR;
• Scope 2 calculation;
• production benchmarking;
• ISO 50001-related analysis.

The original kWh does not need to be recreated for each one.

But the calculations built upon it may legitimately differ.

Likewise, a waste movement is recorded once.

Its regulatory classification and sustainability classification may then be separately mapped.

This architecture is more resilient than building separate databases for every reporting framework.

15. What Does Not Belong in the Environmental Ledger

This proposal needs boundaries.

It is not arguing that environmental compliance should become the complete ESG information system of a company.

Many sustainability topics properly belong elsewhere.

Examples include:

• board composition;
• corporate governance;
• employee diversity;
• human rights;
• labour matters;
• financial ESG information;
• community programmes;
• several supply-chain datasets;
• many Scope 3 categories originating outside plant-level environmental operations.

Those should remain in appropriate corporate systems.

This paper concerns the physical environmental layer:

Materials • Energy • Water • Waste • Emissions • Evidence

That boundary prevents the environmental accounting ledger from becoming an ESG catch-all.

PART IV - MAKING THE ARCHITECTURE WORK IN INDIA

16. BRSR and the Growing Importance of Data Lineage

India's sustainability-disclosure system is itself evolving.

SEBI's BRSR Core framework identifies a defined set of sustainability KPIs and has established a phased applicability structure.

The original 2023 framework set a glide path covering the top 150 listed entities in FY 2023-24, top 250 in FY 2024-25, top 500 in FY 2025-26 and top 1,000 in FY 2026-27.[6]

SEBI subsequently introduced the concept of assessment or assurance and modified aspects of the framework, including value-chain disclosures, through its March 28, 2025 circular.[7]

For the present argument, the important point is not whether a particular organisation uses one assessment or assurance approach.

It is more fundamental:

A sustainability number needs a defensible origin.

Suppose a reported annual waste number is 482.6 tonnes.

A reviewer may ask:

Which transactions produced that total?

Suppose annual water consumption is reported.

The next question is:

Which withdrawal and discharge data produced it?

Suppose Scope 1 emissions are calculated.

The question becomes:

Which fuel/activity records and factors produced the figure?

An aggregated spreadsheet is an output.

A credible system should preserve what lies underneath.

BRSR therefore reinforces a question EHS professionals already understand from inspections and audits:

Where did this number come from?

17. This Is Not an Argument for More Compliance

The most obvious objection to this proposal is:

Indian industry already maintains enough environmental records. Why create another requirement?

That objection is valid if MEDM is interpreted as another regulatory return.

It should not be.

The objective is the opposite.

Do not repeatedly collect the same physical fact.

If a hazardous-waste movement already exists as a transaction, its quantity should not need to be independently reconstructed for:

• a daily register;
• monthly Excel;
• annual return;
• Environmental Statement;
• BRSR workbook;
• GRI workbook;
• customer questionnaire.

Different outputs may require different calculations or classifications.

But they should increasingly reference the same underlying event.

The future should therefore involve:

less duplicate data entry

not

more environmental bureaucracy.

18. MSMEs and Supply-Chain Data Pressure

A proposed environmental ledger has to work for Indian MSMEs.

A complex enterprise platform requiring hundreds of mandatory fields for every activity would fail.

The architecture must be proportionate.

But there is another reality.

A small or medium industrial supplier may never independently publish a BRSR.

It can nevertheless receive environmental-data requests from:

• listed customers;
• multinational buyers;
• ESG programmes;
• banks;
• investors;
• supply-chain assessments;
• customer audits.

SEBI's 2025 changes made BRSR Core value-chain ESG disclosures voluntary and modified the value-chain framework.[7]

That should prevent the argument from being overstated as a universal regulatory supplier mandate.

But the commercial pass-through of environmental information requirements remains important.

A supplier can therefore find itself answering different customers with different spreadsheets containing variations of the same questions:

electricity?

diesel?

renewable energy?

water?

waste?

emissions?

recycling?

The best response to this problem is not an enterprise-scale ESG bureaucracy for every MSME.

It is lightweight, structured operational data that can be reused.

For smaller facilities, this means designing systems around:

• minimum fields;
• mobile entry;
• document upload;
• simple meters;
• evidence capture;
• guided classifications;
• standard export formats;
• proportional requirements.

Digital environmental management should reduce administrative burden.

It should not turn EHS officers into data-entry operators.

19. Better Data Also Creates More Accountability

There is a harder side to this proposal.

Granular environmental information does not merely make reporting easier.

It can reveal things organisations would prefer not to discover.

Imagine a hazardous-waste ledger showing:

Opening stock: 5 MT

Generation: 95 MT

−

Dispatch: 87 MT

=

Expected closing stock: 13 MT

But physical stock is:

8 MT

The system now exposes:

5 MT unexplained.

A collection of loosely connected annual documents may hide that inconsistency longer.

A structured ledger surfaces it.

Likewise:

• water balances may reveal unexplained consumption;
• fuel records may expose reconciliation gaps;
• waste movements may reveal missing acknowledgements;
• revisions may show that a reported value was altered;
• cross-year comparisons may reveal anomalies.

Companies therefore have legitimate concerns around:

• data ownership;
• confidentiality;
• commercial sensitivity;
• legal discoverability;
• regulatory access;
• historical inconsistencies;
• corrections;
• employee accountability;
• misuse of data;
• retention.

These concerns should not be dismissed as resistance to transparency.

They are legitimate data-governance questions.

Any serious environmental data architecture needs rules for:

ownership

role-based access

purpose limitation

correction

version history

retention

confidentiality

regulatory access

Better data creates better management.

It also creates more accountability.

Both are features of the architecture, not accidental consequences.

20. SPCBs Should Not Become ESG Agencies

No.

State Pollution Control Boards and Pollution Control Committees have environmental-regulatory mandates.

Those responsibilities should not be blurred by requiring them to operate every corporate sustainability framework.

An SPCB does not need to determine every Scope 2 methodology.

It does not need corporate-governance data.

It does not need to own every ESG calculation.

Interoperability does not require common ownership.

A better principle is:

Common environmental facts. Different authorised consumers.

The regulator uses the attributes required for environmental law.

The company uses the information operationally.

The sustainability function applies appropriate methodologies.

Assessment or assurance providers examine permitted evidence.

Customers receive agreed disclosures.

The same environmental event can serve multiple purposes while institutional roles remain separate.

21. How India's Environmental Data Architecture Could Evolve

India does not need to build this architecture from zero.

Important components already exist.

OCEMS demonstrates machine-generated environmental telemetry.

Regulatory portals demonstrate digital filing.

Electronic Consent systems demonstrate digital regulatory workflows.

Hazardous-waste movements already use structured documentation.

Environmental laboratories increasingly generate digital reports.

BRSR has increased the structure of sustainability reporting.

The next question is therefore not:

Should Indian environmental compliance become digital?

Much of the transition has already begun.

The more interesting question is:

Can environmental digitisation move from digital documents to structured environmental events?

That progression can be understood in stages.

Stage 1 - Paper

Environmental activity is recorded physically.

↓

Stage 2 - Digital Document

Paper becomes PDF, image or spreadsheet.

↓

Stage 3 - Digital Submission

The document or values move into a portal.

↓

Stage 4 - Structured Environmental Event

The underlying activity receives structured attributes, IDs and evidence.

↓

Stage 5 - Connected Environmental Ledger

Water, waste, energy, emissions, production and evidence can be reconciled.

↓

Stage 6 - Multiple Outputs

Different regulatory and sustainability calculations use the governed underlying data.

The critical observation is:

Digitising a form is not the same as digitising the environmental event represented by the form.

A practical evolution path does not require a massive central database.

It can begin with:

• stable facility identifiers;
• standard units;
• standard waste/source identifiers;
• structured data schemas;
• evidence links;
• machine-readable exports;
• APIs where justified;
• instrument integration where practical;
• revision history;
• calculation metadata.

Different systems can then remain separate while becoming interoperable.

22. What This Changes for EHS Professionals and Environmental Software

This architecture has consequences for both people and technology.

The EHS Professional

A significant part of traditional environmental-compliance work involves:

• maintaining registers;
• storing reports;
• tracking deadlines;
• filing returns;
• collecting manifests;
• preparing evidence.

Those tasks remain necessary.

But environmental professionals are increasingly likely to own questions such as:

• Does the water balance reconcile?
• Why did hazardous-waste intensity rise?
• Which fuel records produced the GHG number?
• Is this value measured or estimated?
• Which meter supplied it?
• Was the instrument calibrated?
• Can the number be reproduced?
• Why was last month's value changed?

The profession therefore moves gradually from:

Document Custodian

toward:

Environmental Data Steward

That requires a powerful combination of skills:

regulatory interpretation

environmental engineering

mass-balance thinking

data-quality management

assurance awareness

This is likely to become an increasingly important capability inside industrial EHS functions.

Environmental Software

Software faces a similar choice.

One approach is to digitise every form individually.

That is useful.

But it risks creating:

digital silos instead of paper silos.

The deeper architecture models the events underneath those forms.

In that model:

Form 3 is not the database.

Form 4 is not the database.

Form V is not the database.

BRSR is not the database.

GRI is not the database.

The environmental activity ledger is the database.

Forms become views.

Reports become aggregations.

Disclosures become calculations.

Evidence remains attached to the underlying operational activity.

This is a fundamentally different philosophy.

It means building environmental software around:

events rather than forms

lineage rather than final totals

relationships rather than folders

reconciliation rather than year-end reconstruction

23. From Compliance-Ready to Sustainability-Data-Ready

Historically, an environmentally compliance-ready facility might have meant:

Required documents can be produced when requested.

Digitisation improved that definition:

Required documents can be produced electronically.

The next stage could be:

Environmental numbers, calculations and evidence can be reconciled continuously.

That changes readiness from:

document availability

to:

data integrity.

A facility can therefore become:

inspection-ready

and increasingly:

sustainability-data-ready

and:

assessment/assurance-ready by design

This does not mean:

• automatically GRI compliant;
• automatically BRSR compliant;
• automatically certified;
• automatically eligible for carbon credits;
• automatically successful in an ESG rating.

Those outcomes involve separate rules, methodologies and judgements.

The environmental ledger provides something more basic.

It provides a trustworthy starting point.

24. Conclusion

Environmental regulation and sustainability reporting emerged from different histories and were created for different purposes.

Environmental compliance focuses strongly on:

• legality;
• standards;
• authorisations;
• conditions;
• monitoring;
• pollution control;
• waste management;
• regulatory evidence.

Environmental accounting increasingly requires:

• physical flows;
• accumulated activity;
• boundaries;
• calculations;
• methodologies;
• intensities;
• evidence lineage.

When a company attempts to move directly from the first system into the second, the missing transformation often appears as an annual spreadsheet exercise.

That is why a facility can be environmentally compliant and still be sustainability-data-unready.

The problem should not be solved by demanding another return.

It should be solved by improving the underlying environmental data architecture.

A litre of fuel should remain a traceable activity before becoming tonnes of CO₂e.

A cubic metre of water should remain part of a physical flow before becoming an intensity metric.

A tonne of waste should retain its generation, storage, movement and destination history before becoming an annual sustainability disclosure.

A monitoring result should remain connected to its source, method and evidence before becoming a compliance conclusion.

This is the transition from:

reporting environmental numbers

to:

maintaining the environmental facts beneath those numbers.

The goal is not numerical perfection.

Physical systems contain uncertainty.

The goal is transparent, reproducible environmental reasoning.

The goal is not a single database for regulators, sustainability teams and customers.

The goal is interoperability.

The goal is not to turn SPCBs into ESG agencies.

The goal is for the underlying physical event to remain usable by different legitimate systems.

The goal is not another ESG layer that sits above fragmented factory records.

The missing layer needs to exist underneath reporting.

That layer is the:

Environmental Accounting Ledger.

If Indian industry moves in this direction, a factory should no longer require a sustainability-data rescue exercise at the end of every year.

Normal environmental operations should continuously create the foundation from which regulatory reports, environmental accounts, sustainability metrics and evidence packs can later be produced.

The proposition is therefore simple:

The future of Indian environmental compliance should not be more forms.

It should be better underlying environmental data.

And the design principle behind that future should be:

Capture once. Preserve the evidence. Calculate many times.

When that becomes normal, sustainability-data-readiness will no longer need to be created once a year.

It will become a natural consequence of how environmental activity is managed every day.

References and Research Notes

[1] Global Reporting Initiative - GRI 306: Waste 2020.
Particularly Disclosures 306-3, 306-4 and 306-5 covering waste generated, waste diverted from disposal and waste directed to disposal, including recovery and disposal classifications.

[2] Global Reporting Initiative - GRI 303: Water and Effluents 2018.
The Standard separately addresses water withdrawal, water discharge and water consumption and provides guidance on calculation and contextual methodology.

[3] Greenhouse Gas Protocol - Corporate Value Chain (Scope 3) Accounting and Reporting Standard.
Used in this paper for the general relationship between activity data, emission factors and resulting GHG emissions.

[4] Greenhouse Gas Protocol - Scope 2 Guidance.
Provides guidance concerning electricity activity data and approaches to Scope 2 emissions accounting.

[5] Central Pollution Control Board - Protocols for Online Continuous Effluent & Emission Monitoring Systems (OCEMS), 2018.
Covers system installation, operation, calibration and electronic data submission for online continuous monitoring.

[6] Securities and Exchange Board of India - BRSR Core framework, Circular dated 12 July 2023.
Established the original phased BRSR Core applicability path: top 150 listed entities for FY 2023-24; top 250 for FY 2024-25; top 500 for FY 2025-26; and top 1,000 for FY 2026-27.

[7] Securities and Exchange Board of India - Circular dated 28 March 2025, “Measures to facilitate ease of doing business with respect to framework for assurance or assessment, ESG disclosures for value chain, and introduction of voluntary disclosure on green credits.”
Relevant to the paper's references to assessment or assurance and the revised treatment of value-chain ESG disclosures.

[8] Ministry of Environment, Forest and Climate Change - Hazardous and Other Wastes (Management and Transboundary Movement) Rules, 2016, as amended.
Primary Indian legal framework referred to in discussion of hazardous-waste records, movement and annual reporting.

Scope and Limitations of This Paper

This paper deliberately distinguishes statutory environmental compliance from sustainability accounting.

It does not suggest that BRSR, GRI, GHG accounting or sustainability-reporting frameworks replace obligations under Indian environmental law.

It does not claim that maintaining the proposed environmental ledger automatically makes an organisation compliant with any disclosure framework, certification standard or carbon-market methodology.

The Minimum Environmental Data Model (MEDM) presented in this paper is a conceptual framework proposed by the author to stimulate discussion around environmental data architecture. It is not an existing Indian regulatory standard.

The examples are intended to demonstrate information architecture and should not be interpreted as universal regulatory requirements for every facility or industry.

About the Author

Harshal T. Gajare works at the intersection of industrial environmental compliance, environmental data and digital systems.

Through EHSSaral, his work explores how Indian industries can move beyond fragmented registers, spreadsheets, reports and annual reconstruction toward structured, traceable and evidence-linked environmental information.

His focus is on a practical question:

How can the environmental work industries already perform every day create a more reliable data foundation for compliance, audits and future sustainability requirements?

About EHSSaral Research

EHSSaral Research examines structural and practical challenges in Indian environmental compliance.

Its work focuses on the intersection of environmental regulation, industrial operations, environmental data and technology-with particular attention to how environmental information is generated, reconciled and used in real factories.

The objective is not merely to explain existing regulations, but to examine how environmental-compliance systems may need to evolve as Indian industry becomes increasingly digital, accountable and data-intensive.

FAQ

1. What is the difference between environmental compliance and environmental accounting?

Environmental compliance focuses on meeting legal conditions, limits, authorisations and reporting obligations. Environmental accounting tracks physical environmental activity-such as water, energy, waste and emissions-across a defined reporting boundary and period.

2. Does environmental compliance data automatically make a company BRSR-ready?

No. Compliance records may provide important source data, but BRSR reporting can require aggregation, classifications, boundaries, intensities, methodologies and evidence lineage that are not automatically created by regulatory records.

3. What is an environmental accounting ledger?

An environmental accounting ledger is a structured record of environmental measurements, transactions, calculations, methodologies and evidence across areas such as water, energy, emissions and waste.

4. What is sustainability data debt?

Sustainability data debt is the future reporting and verification burden created when environmental activity is not captured with enough granularity, context or evidence when it occurs.

5. Should SPCBs collect all ESG data?

No. Pollution-control regulators and sustainability-reporting systems serve different purposes. The opportunity is to make underlying environmental data more structured and interoperable, not turn SPCBs into ESG reporting agencies.