Fuel Accounting and Compliance — CI Tracking, Feedstocks, Anomaly Alerts and Multi-Program Allocation

Renewable fuel programs are introducing stricter requirements, requiring operational data to be collected from multiple parties and systems. Teams need CI scores they can defend, a clear line from feedstock to fuel, and a way to allocate production across programs without double-counting.

Mangrove’s new suite of fuel accounting and compliance capabilities is built for exactly that. Today we’re launching CI score generation using the models registries expect, feedstock tracking, data gap and anomaly alerts with substitution rules, and multi-program allocation so one production stream can feed ISCC, CFR, LCFS, RFS, 45Z, and voluntary pathways from a single source.

‍

Generate carbon intensity scores

CI scores determine eligibility and credit issuances. Mangrove generates and tracks CI scores using the same models that registries and auditors expect: CA GREET 4, Argonne GREET, GHGenius, 45Z GREET, and other frameworks regulators accept. Operational inputs—feedstock mix, energy use, process data—flow into these models so reported CI matches program rules.

Projects can export a copy of the populated Excel model for each CI calculation. Auditors and counterparties get a reproducible record; the project spends less time on verification back-and-forth.

Where this applies:

• LCFS pathway applications: Generate pathway-specific CI with the required model version and attach the populated file to reporting.
• 45Z and voluntary deals: Archive model outputs for each reporting period so buyers and verifiers see exactly how each score was calculated.

‍

Feedstock tracking and accounting

Credits and compliance depend on knowing which feedstocks went into which production. Mangrove’s feedstock tracking traces production back to specific feedstocks and categorizes them by program-defined types (e.g. Fats, Oils & Greases; agricultural residues; manure) so project data matches what gets reported to LCFS, RFS, and other frameworks.

Feedstocks are defined at the project level and linked to events and production accounting. Projects can partition calculations by feedstock type, run separate carbon accounting for each stream, and filter events and batches by feedstock.

Where this applies:

• Multi-feedstock RNG or biomethane: Attribute daily production to specific sources and tag them with official program categories for pathway and RIN eligibility.
• Audit and verification: Show verifiers a direct line from feedstock receipts and blend records to production batches and CI scores.

‍

Data Rules

Missing or bad data delays reporting, triggers questions from verifiers, or forces last-minute substitutions. Mangrove's data rules help producers catch problems early. Configure rules so that when a primary data source has gaps or fails a quality check like having data that does not match evidence, the system applies defined fallbacks (such as default factors) and preserves the change for future review.

Rules are aligned with the program’s methodology—which data parameters need to pass, under what checks, and how failed checks are resolved. The result: fewer delays, clearer documentation when substitutions happen, and consistent handling across projects.

Where this applies:

• Sensor outages: Fuel producers can define substitution rules so production or energy data can be estimated when a meter is down in accordance to the program.
• Gap filling according to CDR methodologies: For CCS projects, align checks with registry rule sets so that substitution for flow meter data gaps only happens when appropriate, and the resolutions are documented for verification.

‍

Multi-value stream allocation and reporting

Fuel producers often monetize the same physical production across multiple value streams—LCFS, RFS, 45Z, voluntary—each with its own reporting cadence, methodology and evidence requirements. Mangrove lets projects split a single stream of ongoing production across programs, with allocation logic and program-specific reports.

Split production by feedstock, and the platform tracks allocated quantities, CI, and supporting data per program. One operational source, no separate spreadsheets, no double-counting risk.

Where this applies:

• LCFS + RFS + 45Z: Allocate RNG or biodiesel production to LCFS credits, RINs, and 45Z tax credits, with separate reporting packages for each.
• Voluntary and compliance: Reserve a portion of production for voluntary offtake and the rest for compliance, with reports tailored to each buyer or program.

‍

Built for commercialization and reporting teams

Spend less time reconciling inventory and mass balance spreadsheets, and more time closing offtakes and reporting on time. Mangrove also handles mass balance for co-mingled feedstocks, data integration, direct registry connections, and audit trails.

Reach out to your Mangrove representative or get in touch to see how fuel compliance can be configured for your project.