EU RFNBO Certification Automation Reaches Industrial Scale: Lessons from 22 Completed Audits

Key Highlights

• Atmen (Munich), a Compliance Technology Provider for CertifHy EU RFNBO certification, published a 2026 audit operations report covering 31 certifiable entities and 22 completed audits through the CertifHy CTP pipeline.
• The report quantifies industrial-scale RFNBO complexity: approximately 70,000 data points per 10 MW electrolyser audit, more than 200 audit requirements spread across electricity, carbon intensity, mass balance, and logistics.
• Atmen claims a 94 percent workload reduction (485 to 30 FTE-days per audit) using platform automation, and approximately EUR 150,000 per year in cost savings for a 10 MW plant.
• The report identifies three structural compliance levers: electricity supply allocation, batch-level carbon intensity and mass balance, and multi-hop container tracking.
• A polling result from Atmen's April 2026 webinar indicates that 70 percent of attendees treat RFNBO certification as either top priority or important among competing workstreams.

What the Atmen Report Documents

Atmen's published report, RFNBO Certification in Practice, catalogues operational learnings from running EU RFNBO audits at industrial scale. The numbers are notable because they convert what has been an abstract regulatory burden into specific operational metrics:

• 70,000 data points per audit for a 10 MW electrolyser site. This includes meter readings, PPA records, Guarantee of Origin documentation, mass balance entries, and logistics records.
• 200+ requirements per audit, distributed across renewable electricity sourcing, carbon intensity calculation, mass balance, and transport.
• 485 FTE-days per audit without automation, reduced to approximately 30 FTE-days using platform-supported workflows. This is the workload reduction claim that drives the cost savings figure.
• EUR 150,000 per year in claimed cost savings for a 10 MW plant, framed as an enterprise SaaS value proposition.

Per Atmen's report, these numbers reflect the operational reality for projects post-COD that are running through the CertifHy Certification Technology Provider (CTP) pipeline. The 31 certifiable entities Atmen serves are all operational-stage projects, not pre-FID or pre-FEED.

Three Structural Compliance Levers

Atmen's report organises RFNBO operational compliance around three product pillars. Each lever is worth understanding independently because they correspond to distinct data flows and distinct audit risks.

Electricity supply and allocation

The first lever is how renewable electricity reaches the electrolyser and how that flow is documented for the auditor. Atmen identifies several layered compliance paths: PPAs (with additionality), low-price-hour grid sourcing, direct-line connections, and the more than 90 percent renewable grid exemption.

The report's emphasis is on what happens when these paths are combined. A single project may layer PPAs with grid sourcing in the same hour, may have unused PPA volume that rolls over, and may need to allocate scarce green power between the electrolyser stack and balance-of-plant equipment. Atmen claims that smart internal allocation can free up to 10 percent of green power volume.

The audit risk Atmen identifies is not in combining paths. It is in not being able to explain cleanly which megawatt-hour came from which source.

Carbon intensity and batch allocation

The second lever is mass balance. Carbon intensity and RFNBO percentage are calculated at every supply chain step. Off-taker constraints become hard allocation boundaries, since different customers may have different carbon-intensity ceilings. Energy for Transport and Distribution (ETD) emissions must be anticipated before delivery, not calculated after the fact.

Atmen's report makes a subtle but important operational point: RFNBO certificates are mass-balanced and not independently tradable. The certificate stays attached to the physical molecule. The same megawatt-hour of renewable electricity may produce hydrogen that passes for off-taker A and fails for off-taker B, depending on transport mode and ETD emissions.

Month-by-month batch optimisation under these constraints is the kind of work that does not scale by adding more spreadsheet hours.

Multi-hop logistics and container tracking

The third lever is supply chain visibility. Atmen issues Proof of Sustainability (PoS) per delivery before mass balances close, and tracks molecules across multi-actor supply chains (not just producer-to-offtaker flows). Container-level tracking covers every split, transfer, and relocation. The report admits this is harder when counterparties have varying digital maturity, since rigid systems break when downstream actors use paper records or basic spreadsheets.

Atmen's note is that averaging emissions across multi-hop chains inflates calculated carbon intensity and threatens compliance. The "black-box effect" between commercial flows and actual molecules is where audit failures hide.

What the Report Reveals About Market Maturity

The most consequential signal in the Atmen report is not any single statistic. It is that operational EU RFNBO certification has reached the scale where automation is a structural requirement, not a productivity enhancement.

Three readings of the data points support this:

1. Audit complexity is industrial, not bespoke. 70,000 data points and 200+ requirements per 10 MW audit are not numbers that survive Excel-based workflows. The 485 FTE-day baseline is the manual cost of compliance done at scale.
2. The certification market is consolidating around defined frameworks. CertifHy's CTP pipeline is the operational backbone, with Umweltbundesamt (Germany's federal environment agency) and the emerging Union Database as the destination registries. Atmen's report explicitly maps to these three reporting destinations.
3. The Union Database is becoming a real constraint. Atmen's mention of UDB as an emerging reporting layer signals that compliance work will need to be format-compatible with a registry that does not yet have fully published technical specifications.

The webinar poll embedded in Atmen's outreach quantifies stakeholder urgency: 37 percent of attendees rated RFNBO certification as top priority, 33 percent rated it important but competing with other workstreams. The combined 70 percent who treat certification as a high-priority workstream suggests broad consensus across the engaged developer community that this is operational work that needs to move now.

What the Report Does Not Cover

Atmen's report is candid about its scope, which is also worth noting. The 31 certifiable entities are EU-jurisdiction projects in operational stage. The report does not address:

• Pre-COD or pre-FID readiness assessment. The product assumes the project is built and producing.
• Non-EU certification frameworks like India's GHCI, Japan's GX-ETS / JCM, or Korea's CHPS.
• Tender-specific compliance preparation for programmes like H2Global, where bid-readiness is distinct from operational certification.
• Pre-FID contract-design questions like who owns the meter, PPA, GO, SCADA, transport, and offtaker delivery records that an auditor will eventually need to reconstruct.

These are not gaps in Atmen's product. They are scope boundaries. The full RFNBO compliance lifecycle has phases the operational platform does not address, and that part of the lifecycle is where pre-FID screening and tender readiness tools sit.

The Data-Rights Question Atmen Asks

The report closes with a question that has implications well beyond Atmen's own platform: where is certification data stored today, who owns it, and how much of it could survive an audit without reconstruction?

This is a contract-design question, not a software question. If a producer does not have contractual rights to export logistics records from a freight forwarder, or cannot retrieve hourly meter data from a counterparty's portal, the audit failure is structural, not operational. The lever to fix this is the PPA, the offtake contract, the EPC contract, and the logistics service agreement, all of which need data-rights clauses written before COD.

The implication is that audit survivability is partly determined years before the audit itself, by the contracts the developer signs and the records architecture put in place during construction.

HyGOAT Implications

Atmen's report substantiates the certification automation market with concrete operational metrics. For Indian producers pursuing dual GHCI plus RFNBO compliance, the report is useful as a calibration tool: it shows what operational RFNBO work looks like at industrial scale, and where automation has real leverage.

The complementary work that sits upstream of Atmen's scope, pre-FID screening, tender-specific readiness, contract-design diligence, is where most Indian developers are today. The right time to ask data-rights questions is during PPA negotiation, not during the year-end audit.

For projects that will eventually export to the EU, the most useful posture is to assume that the audit complexity Atmen documents will land at COD whether or not the developer prepared for it. The lower-cost path is to prepare for it during the pre-FID phase, while project parameters are still editable.