Your external auditors are going to ask for your REC records. Not a summary. The actual records: what you held, how each certificate was classified, who approved every allocation decision, and whether any of those designations changed between reporting periods. FASB’s ASU 2026-02, issued this spring, made that a GAAP requirement.
That’s a new standard for infrastructure that was mostly built for program management, not financial reporting.
The line that matters in ASU 2026-02
The standard creates Topic 818 from scratch and draws one distinction that determines almost everything about compliance burden: whether a credit is being used to settle a regulatory obligation or not.
Compliance credits (RECs designated for RPS compliance) are recognized at cost, carried indefinitely with no impairment testing, and subject to a documentation and disclosure requirement. The burden is largely administrative: know what you have, how it’s designated, and be able to show that.
Noncompliance credits (RECs backing green tariff customers, bilateral deals, or held as excess inventory) face a heavier requirement. They require impairment testing at each reporting date, based on fair value by type, vintage, and geography. REC markets aren’t uniformly liquid, which means this is an active data sourcing effort every period, not a once-a-year spot check. A fair value option is available for eligible credits by class, which adds another layer of accounting judgment.
Most utilities hold both types. That means both sets of requirements apply simultaneously to what is often a single overlapping certificate inventory.
Self-generated RECs are worth flagging separately. They carry a book value of $0, which leads most teams to assume the disclosure obligation disappears with it. It doesn’t. Quantities, movements, and usage still require full disclosure every period.
The allocation decision is also an accounting decision
For utilities with green tariffs or bilateral customer deals, the question of which RECs back which customer contract determines two things at once: what gets disclosed in the financial statements, and what gets reported to the customer for their Scope 2 disclosures and CFE attestations.
Under ASU 2026-02, designating a REC to a specific customer account rather than RPS compliance shifts it from a compliance credit to a noncompliance credit, triggering impairment testing. That designation needs an approval trail auditors can verify. The moment of reclassification is the moment of allocation, and that moment needs to be documented.
Here’s what that looks like in practice. A utility runs a voluntary customer program. At the start of the year, the program management team allocates RECs across 60 enrolled customers. Mid-year, four customers restructure their contracts: two reduce their load share, one exits the program, one upgrades to a higher CFE percentage. The spreadsheet tracking the program captures the updated allocation. It doesn’t capture who approved each change, when the decision was made, or whether the certificate vintage and facility still match what was contractually promised. Auditors need the first two answers to verify the balance sheet. Customers need the last two for their own downstream reporting.
The same decision, the same record. Two different audiences, both of whom will ask for it.
What auditors will ask under ASU 2026-02
The standard takes effect for public business entities in fiscal years beginning after December 15, 2027. Calendar-year companies adopt January 1, 2028. All other entities follow a year later. Early adoption is permitted.
When that clock runs out, auditors will want to know what RECs the utility holds, how each is classified, what the basis for each classification is, who approved the allocation decisions that drove those classifications, and whether any reclassification between reporting periods is documented. For utilities using LIFO-equivalent costing methods, there’s also a cumulative-effect adjustment to opening retained earnings upon transition. No restatement of prior periods, but the calculation needs to be documented and auditable.
What ASU 2026-02 requires from your REC records
The gap the standard exposes isn’t in technical accounting treatment. Most utilities will work through that with their auditors. The gap is in the underlying records: the approval trail behind each allocation, the classification history for each certificate, the documentation that connects program decisions to balance sheet line items.
Closing that gap means the allocation decision and the audit trail need to be the same thing, not separate processes. Impairment testing needs records built to support it, not records built for customer reporting that have to be retrofitted every quarter. REC quantities and usage need to be tracked as they happen, not reconciled from program exports.
When auditors ask for the approval trail and it isn’t there, the problem isn’t a missing document. It’s that the decision was never recorded in a system designed to record it. The utilities furthest behind on this are the ones where program operations and financial reporting were never connected by design, and for years that didn’t matter. Starting in 2028, it will.
Singularity Energy helps utilities and grid operators manage clean energy programs: program administration, compliance tracking, customer reporting, and the auditable record that supports all three. If you’re working through what ASU 2026-02 means for your program infrastructure, we’d be glad to talk through it.