Menu
Engineering
07/10/2025
SAF Credits Are Only as Valuable as the Trail Behind Them
Sustainable Aviation Fuel is increasingly central to how aviation operators think about decarbonization — and increasingly, it’s a commercial opportunity, not just a compliance cost. Virtual SAF credit sales let operators monetize sustainability efforts, offer clients verifiable green options, and participate in a market that’s growing in both volume and regulatory scrutiny. That last part […]
decoration

Sustainable Aviation Fuel is increasingly central to how aviation operators think about decarbonization — and increasingly, it's a commercial opportunity, not just a compliance cost. Virtual SAF credit sales let operators monetize sustainability efforts, offer clients verifiable green options, and participate in a market that's growing in both volume and regulatory scrutiny.

That last part matters. The RSB (Roundtable on Sustainable Biomaterials) framework that governs SAF certification isn't optional overhead — it's the foundation of trust in the market. A SAF credit is only worth something if it's traceable, non-duplicated, and audit-ready from the moment fuel enters the supply chain to the moment a certificate is issued.

This is where many SAF programs hit a wall they didn't anticipate.

The spreadsheet ceiling

In the early stages of a SAF program, spreadsheet-based tracking is workable. Volume is low. One or two people manage the records. Everyone knows where things are.

As volume grows, the model starts to crack. Multiple people update records in parallel. Allocation decisions happen simultaneously. Reconciliation becomes a periodic event rather than a continuous state. And then a question comes up that the spreadsheet can't confidently answer: has this quantity of SAF credit already been allocated? Is this batch's remaining availability reflected correctly across all records?

The uncomfortable honest answer is usually: probably. In most operational contexts, "probably" is an acceptable level of confidence. In RSB-compliant SAF tracking, it isn't. Double-counting isn't a technical error that can be corrected in the next version — it's a credibility problem that can undermine the entire program, and the commercial relationships built on it.

What traceability actually requires

The RSB framework mandates what's called mass-balance accounting: the ability to demonstrate, for any given certificate, that the claimed quantity of SAF can be traced back through every step from intake to issuance, without gaps and without overlap.

This sounds straightforward. It isn't, once operations reach any meaningful scale.

SAF doesn't flow through a single pipeline. It enters at different times, in different quantities, from different suppliers. It's stored across warehouses, tanks, batches. Contingents are created from batches. Allocations are made from contingents. Certificates are issued against allocations. Each step has to be recorded, and the records have to be consistent — not just at a point in time, but across the entire history of every movement.

When this is managed in spreadsheets, consistency is enforced by human attention. Someone checks before allocating. Someone reconciles after each period. This works until volume makes it impractical, or until two allocations happen close enough together that the checks don't catch the overlap.

Reliable mass-balance accounting requires systems where consistency is enforced structurally — where an allocation that would exceed available quantities isn't just flagged for review, but prevented. Where every movement is logged in a way that can't be retroactively adjusted. Where the chain from intake to certificate is reconstructable at any point, without a manual audit.

The commercial dimension

It's worth being direct about why this matters beyond compliance: the infrastructure for a SAF program is part of the product being sold.

Buyers of SAF credits — particularly corporate clients with their own sustainability reporting obligations — are increasingly sophisticated about what they're buying. A certificate that comes with a clear, auditable trail from intake to issuance is a different product than one that comes with an assurance that the records are probably accurate.

As voluntary carbon and SAF markets mature, this distinction will become more pronounced. The market is moving toward higher verification standards, not lower. SAF programs that can demonstrate rigorous traceability will have a durable advantage over those that rely on goodwill and manual reconciliation.

This isn't just about passing audits. It's about the credibility of the commercial offer.

What reliable SAF infrastructure enables

Beyond compliance, the practical operational benefits are significant.

When intake, storage, allocation, and issuance are tracked in a single system with enforced consistency, scaling throughput doesn't require scaling the administrative burden in parallel. Coordinators can process more volume without a corresponding increase in reconciliation time. New batches can be onboarded and allocated without a manual audit cycle after each step.

Role clarity becomes easier to enforce. The people managing intake see what they need to see. The people managing client allocations see what they need. Certificate issuance can be delegated with confidence because the system enforces the checks, not the individual.

And when an auditor or a client asks for traceability — for the complete record of a specific credit from the moment it entered the supply chain — the answer is a report, not a search through historical files.

Why this tends to get underinvested

The pressure to launch a SAF program is often stronger than the pressure to build the infrastructure correctly. Volume is low at the start, spreadsheets work at low volume, and the compliance risk feels abstract until it isn't.

The investment in proper infrastructure gets deferred — usually until one of three things happens: volume grows to the point where the spreadsheet model breaks under its own complexity; an audit surfaces a gap in the mass-balance record; or a client asks a traceability question that can't be answered cleanly.

The teams that avoid this tend to treat the registry as a first-class concern from the start — not as something to be addressed once the program proves out commercially. The program proves out commercially in part because the registry is credible. These things aren't sequential.