RIN / RFS

Renewable Identification Numbers

RIN inventory managed as an asset class, not a spreadsheet tab.

What the instrument is

Renewable Identification Numbers are generated with renewable fuel production, travel attached to physical volume, and separate from that volume at defined points in the supply chain. That combination — a unit that is simultaneously a production record, a tradable instrument, and a compliance currency — is precisely what general-purpose inventory and trading systems handle poorly.

Why it is hard to control

A RIN’s eligibility depends on attributes captured at generation: the D-code, the vintage year, the generating facility, and the fuel pathway. If those attributes are incomplete when the RIN enters the books, every downstream decision — which obligation it can satisfy, what it is worth, whether it can be sold — requires reconstruction from source records. Organizations frequently discover this only during an audit or a position review under deadline.

Asset model

Attributes carried on every unit

AttributeWhy it matters

D-codeDetermines which renewable fuel category the unit represents and which obligations it may be applied against.

Vintage yearGoverns the compliance year the RIN may be used for and any carry-forward treatment permitted by policy.

Separation statusDistinguishes assigned RINs travelling with physical volume from separated RINs available to trade or retire.

Generating facility and pathwaySupports facility-level attribution and the eligibility basis recorded on the asset.

Legal entityDetermines the obligated party attribution and the accounting entity for any posting.

Acquisition basisFor purchased RINs, the recorded cost that establishes book value and retirement cost.

Lifecycle

States a unit moves through

01GENERATED

A production event has been validated and RIN inventory created with its full attribute set.

02ASSIGNED

The unit remains attached to the physical volume it was generated with.

03SEPARATED

The unit has been separated from physical volume and is available to trade or apply.

04AVAILABLE

Held in inventory, unencumbered, and included in the available compliance position.

05RESERVED

Committed to a pending retirement or sale and excluded from the available position.

06RETIRED

Surrendered against an obligation, with registry confirmation recorded.

Obligations

How the compliance position is derived

Obligation derivation

The renewable volume obligation is tracked as a liability with its compliance year, entity, and outstanding quantity, updated as retirements are confirmed rather than maintained by hand.

Category eligibility

Program rules govern which D-codes may satisfy which portions of the obligation. Eligibility is evaluated by the rules engine and recorded on the asset so the reasoning survives later review.

Forward position

Expected generation, contracted purchases, planned sales, and known obligations combine into a forward view that surfaces a surplus or deficit before the compliance deadline rather than at it.

Reconciliation

What gets compared

Registry RIN balance compared to platform inventory by D-code, vintage, and entity
Separated versus assigned quantities agreed against registry state
Platform book value compared to the general ledger balance for the corresponding accounts
Retirement submissions compared to registry confirmations, with unconfirmed items aged
Trade settlements compared to inventory movements and posted accounting events

Accounting

Valuation and treatment

Purchased RINs carry a recorded acquisition basis at the inventory-layer level.
Internally generated RINs receive the treatment the organization’s policy specifies, applied consistently.
Retirement cost is derived from the recorded basis of the specific layers applied.
Market valuation uses loaded prices by D-code and vintage, with source and effective date retained.
Accounting events are generated from recorded activity and carry the returned ledger document reference.