Why RNG Data Gaps Are More Than a Recordkeeping Problem — They're a Compliance and Revenue Risk

RNG volumes under the Renewable Fuel Standard (RFS) are not “operational KPIs”; they are the quantitative basis for RIN generation, transfer, and downstream compliance, and EPA describes RINs as the “currency” of the program.
For biogas/RNG pathways, the regulations place reliable, continuous measurement (or approved alternatives), and auditable records at the center of eligibility and RIN integrity. This is where data historians fail often, creating gaps in the data and as such adds to headache, manpower, and cost to detect the gaps and apply the proper course of action to fill/substitute the data gap. As such it is important to have systems in place that provide proper monitoring and action. 

Regulatory basis

Continuous measurement and alternative measurement protocols

EPA’s sampling/testing/measurement rule for biogas and RNG establishes a clear default: except for specified exceptions, any party required to measure volume under Subpart E must continuously measure using compliant metering methods or have an EPA-accepted alternative measurement protocol (AMP).  The same rule sets conditions for EPA acceptance of an AMP, including demonstrating inability to continuously measure under the default methods and demonstrating that the alternative is at least as accurate and precise. 

For RNG RIN separators, §80.155 provides a distinct and operationally important option: the separator may measure using the standard metering approaches or use specified documentation (e.g., pipeline/utility statements, scale tickets, bills of lading) to establish volumes (in Btu LHV or converted as required). 

Invalid RINs, prohibited acts, QAPs, affirmative defense, and replacement

EPA defines invalid RINs to include RINs that are duplicates and RINs based on incorrect volumes (including volumes not standardized as required), among other defects.  The prohibited acts provision makes it unlawful to generate RINs for non-renewable fuel or for volumes not produced and to create or transfer an invalid RIN. 

For biogas/RNG pathways, Subpart E’s QAP provision requires QAP verification across the “chain” (including biogas and RNG facilities connected to a pipeline interconnect), and it requires auditors to verify that biogas and RNG were sampled/tested/measured as required under §80.155 and that PTDs meet requirements. 

Affirmative defense provisions apply only to invalidly generated RINs that were verified through a quality assurance audit under an EPA-approved QAP and apply to specified transfer/use violations—not as a general shield.  Replacement rules allocate responsibility: for Q-RINs, both the generator and the obligated party that owns the Q-RIN are required to replace invalidly generated Q-RINs with valid RINs under §80.1474 procedures. 

Finally, EPA explicitly addresses a core automation pitfall—double counting. Subpart E’s potentially invalid RIN provision states that if RINs are over-generated due to double counting of biogas or RNG volumes, the generator must follow the invalid RIN procedures under §80.1431. 

Why missing records create invalidity risk and commercial exposure

When meter records are missing, the compliance impact is direct: RNG batch volume (Btu LHV) is calculated from measured quantities under §80.155, and RIN generation is calculated from batch volume.  A data gap is therefore not merely “uncertain operations”; it can become “uncertain RIN math.”

 In practice, this creates a compliance exposure: incomplete feedstock evidence can translate into reduced eligible biogas energy. The commercial mechanism that converts these weaknesses into financial exposure is also explicit. EPA defines invalid RINs to include those based on incorrect volumes and duplicates.  It prohibits creation/transfer of invalid RINs.  And if RINs are invalidly generated—particularly Q-RINs—replacement obligations can attach to both the generator and the owning obligated party. 

Practical control design for evidence continuity

A defensible control environment for RNG under the RFS typically treats measurement data as controlled records. 

1. Use redundant historians and store-and-forward to reduce loss of evidentiary records.
2. Use PLC totalizers to strengthen defensibility by corroborating historian rollups and distinguishing instrument outages from communications/historian ingestion failures. 
3. Prevent double counting through de-duplication and reconciliation. The RFS framework explicitly connects duplicates and incorrect volumes to invalid RINs, and it directly references double counting of biogas/RNG volumes as a trigger for invalid-RIN procedures. 
4. Underwrite traceability with time synchronization, tag mapping, and unit normalization.
5. Establish a single software that serves as a data aggregator for points 1-4, instead of manually stitching up the data which opens higher risk of making a mistake, not to mention adding cost, resources, and time consuming. The software should have the ability to integrate data from your existing software(s), data historian(s), and documents (injection statements, utility bills, PTDs, affidavit).

Core software capabilities that materially reduce compliance exposure

A properly designed automation layer for RNG compliance includes:

1. Real-time gap detection across the full evidentiary chain, not just flow. This means monitoring meter streams in a regular and frequent cadence. 
2. Automatic recovery from redundant historian/buffer where equivalence controls are satisfied (time alignment, tag mapping, unit normalization).
3. Substitution paths aligned to the regulations. Substitution should be implemented based on the protocols of the regulation (e.g., LCFS, RFS, air permit, and others).
4. Automated audit package generation, including immutable data logs. Subpart E recordkeeping requires retention of underlying documentation, calculations, PTDs, and QAP-related documentation (where applicable), with five-year retention and the ability to make records available to EPA. 
5. Record human input of root-cause classification to distinguish instrument outages from human/historian failures. 
6. Alerts and approval workflows that prevent accidental RIN over-generation. This is especially important given prohibited acts related to creation/transfer of invalid RINs and the explicit treatment of double counting as a trigger for invalid-RIN procedures. 

‍