ASU 2026-02 Adoption Guide: Five Decisions Your Team Must Make Before 2028

FASB issued ASU 2026-02, Environmental Credits and Environmental Credit Obligations (Topic 818) on May 19, 2026. For calendar-year public companies, mandatory adoption begins January 1, 2028, including all interim periods within that year. The Big-4 summaries cover the mechanics well. What they do not provide is a sequential decision framework that walks a CFO or technical accounting team through every judgment call in the right order. This guide does that.

Key takeaway: ASU 2026-02 creates ASC 818, the first authoritative US GAAP framework for environmental credits. Before this standard, entities analogized to ASC 330, ASC 350-30, or ASC 450, producing significant diversity in practice. That diversity ends at adoption.

For the full overview of what ASC 818 requires and what it means for your SEC filings, see our ASU 2026-02 accounting standard overview and our SEC disclosure guide. This article focuses on the five sequential decisions every entity must work through before adoption.

Decision 1: Does ASU 2026-02 Apply to You?

ASC 818 applies to all entities, public and private, for-profit and not-for-profit, that hold, generate, or carry a regulatory obligation settleable with environmental credits. The scope is broader than most teams initially assume.

An item qualifies as an environmental credit under ASC 818 only if it meets all four of the following criteria, per the ASU full text:

1. It lacks physical substance and is not a financial asset under US GAAP.
2. It is represented to prevent, control, reduce, or remove emissions or other pollution.
3. It is, or previously was, separately transferable in an exchange transaction (or, if no longer transferable, can be used to satisfy an ECO). Note: an active market is not required to meet this criterion.
4. It is not an income tax credit that may be used to settle an entity's income tax liability.

In-scope credits include cap-and-trade emissions allowances, Renewable Identification Numbers (RINs) from the US Renewable Fuel Standard, Renewable Energy Certificates (RECs) from state Renewable Portfolio Standards, carbon offsets, California LCFS credits, and ZEV credits earned by automobile manufacturers under CAFE or state programs. Credits received from related parties, including intercompany REC transfers within a corporate group, are explicitly in scope.

Three explicit carve-outs to know:

• Income tax credits, including renewable energy tax credits under the Inflation Reduction Act, remain in scope of ASC 740. They are not environmental credits under ASC 818, regardless of whether the entity has a tax liability or intends to use them for that purpose.
• Environmental remediation liabilities within the scope of ASC 410-30 are not ECOs under ASC 818.
• Freestanding forward contracts to buy or sell environmental credits in the future may still be derivatives under ASC 815, even though ECOs themselves are excluded from ASC 815 embedded derivative analysis. This is a live question for energy, utilities, and manufacturing companies that use forwards to lock in credit prices for future compliance periods.

IRA credit bifurcation watch: Many renewable energy projects generate both RECs (in scope of ASC 818) and production or investment tax credits (excluded, governed by ASC 740). As EY notes, entities must bifurcate these at the project level. The two credit types follow entirely different accounting models and cannot be blended.

Decision 2: How Do You Classify Each Credit You Hold?

Classification drives the entire subsequent measurement model, so it must be made at the reporting date for every credit in the portfolio, and documented.

ASC 818 uses an intent-based recognition model. A credit is recognized as an asset only if it is probable, collectively, that the entity will:

• Use it to settle an environmental credit obligation (ECO),
• Transfer it in an exchange transaction, or
• Use it in a nonreciprocal transfer.

Credits that do not meet this threshold, including those held solely for voluntary net-zero or carbon-neutral purposes, are expensed as incurred, including nonrefundable deposits. As EY summarizes: "Entities are required to capitalize or expense an environmental credit based on its planned use."

For credits that do qualify as assets, the classification splits into two categories:

What happens when intent changes? This is the scenario the Big-4 summaries flag but do not work through. If an entity initially classifies a credit as a compliance credit (capitalizes at cost, no remeasurement) and subsequently decides to sell it instead, the credit is reclassified to noncompliance status. The carrying amount at the date of reclassification becomes the new cost basis for impairment testing. Critically, Deloitte notes that the entity must disclose the financial statement impact of any change in intent. That disclosure obligation is live from day one of adoption.

Also note: a voluntary net-zero commitment or similar statement of intent does not constitute an ECO under ASC 818. Only regulatory compliance obligations arising from existing or enacted laws, statutes, or ordinances qualify as ECOs.

What does "probable" mean here? The standard uses the probability threshold for asset recognition but does not define it in the ASC 818 context. Most practitioners are treating it consistently with the ASC 450 "probable" standard, meaning the outcome is likely to occur. Auditors are still developing views on this, so robust contemporaneous documentation of intent at acquisition and at each reporting date is essential.

Decision 3: Which Measurement Elections Will You Make?

ASC 818 offers three accounting policy elections that must be made at adoption. None has a default, and some are irrevocable at the class level.

Costing method election

Entities must elect one of three costing methods for measuring environmental credit assets: FIFO, average cost, or specific identification. Per Deloitte's Heads Up, the ASU does not specify a default. The choice has real audit and disclosure implications:

• FIFO works well for entities with relatively homogeneous credit pools where older vintages are consumed first. It produces a predictable cost flow but can create book-to-market gaps in rising-price environments.
• Average cost suits entities with high-volume, frequently replenished credit portfolios (common in RIN-heavy refining or blending operations). It smooths price volatility but requires robust tracking of weighted-average cost at each purchase.
• Specific identification is appropriate where credits are individually tracked and material differences exist between vintages or programs (e.g., a utility holding both California Carbon Allowances and voluntary offsets from distinct projects). It maximizes precision but demands the most granular record-keeping.

This election is an accounting policy choice. Changing it later requires a preferability assessment under ASC 250.

Fair value election for noncompliance credits

For eligible classes of noncompliance credits, entities may make a class-wide policy election to measure those credits at fair value on an ongoing basis, with changes recognized in net income. In active markets like California Carbon Allowances or EU ETS allowances, fair value swings can be material quarter to quarter. Weigh this election carefully against your hedging strategy and earnings guidance practices before adoption.

Internally generated or regulator-granted credits

For credits the entity internally generates or receives as a grant from a regulator, an entity-wide election is available to measure those credits at transaction costs incurred (which may be zero for regulator grants), regardless of intended use classification. This simplifies measurement for entities in cap-and-trade programs that receive free allowances.

Decision 4: How Do You Measure the ECO Liability?

The ECO liability model is the most operationally complex part of ASC 818. It bifurcates the liability into a funded portion and an unfunded portion, and the sequencing of measurement is mandatory.

Key takeaway: Per Deloitte, the funded ECO liability must be measured after the environmental credit asset has been recognized and measured, including any intent-change reassessment. Get the sequencing wrong and the funded liability will not tie to the asset.

The ECO liability reflects the number of credits needed to settle the obligation if the reporting date were the end of the compliance period. It is a current-period measure, not a cumulative or run-rate figure.

Funded portion

The funded portion covers the ECO for which the entity holds compliance credits it intends to use for settlement. It is measured at the carrying amount of those compliance credits, directly linking the liability to the asset. This is why the sequencing rule matters: you must first confirm which credits on hand you actually intend to use before you can measure the funded ECO.

Unfunded portion: three measurement paths

The unfunded portion covers the remaining ECO not covered by credits on hand. The measurement path depends on the entity's situation, per Deloitte's Heads Up:

Gross presentation is required throughout. Environmental credit assets and ECO liabilities may not be netted on the balance sheet, regardless of whether the same credits will be used to settle the same obligation.

The ASC 820 interaction for the remaining unfunded ECO is a meaningful complexity. For illiquid credits with no observable market price, entities will need to develop Level 3 fair value inputs. This requires coordination between the technical accounting team and whoever manages credit procurement, and auditors will scrutinize the inputs. For more on ASC 820 fair value measurement mechanics, see our ASC 820 fair value disclosure guide.

Decision 5: How Do You Execute the Transition?

ASU 2026-02 uses a modified retrospective transition method. Entities recognize a cumulative-effect adjustment to beginning retained earnings at the date of initial application. Prior periods are not recast, so comparative financial statements will not reflect ASC 818 treatment.

Transition measurement rules for credits on hand at adoption

The measurement of credits held at the adoption date depends on their classification, per Deloitte:

The practical challenge here is reconstruction. Credits previously expensed under an analogy to ASC 450 (contingencies) will not have a carrying amount on the books. Entities must determine whether those credits, if still on hand, would qualify as assets under ASC 818 and, if so, establish a cost basis. That reconstruction exercise requires going back to original purchase records and, in some cases, to regulator grant documentation.

Effective dates at a glance

A calendar-year PBE that has not yet adopted must begin Q1 2028 interim disclosures under ASC 818. That means the Q1 2028 Form 10-Q, not just the 2028 annual report, will carry the new presentation and disclosure requirements.

XBRL taxonomy gap for early adopters

The GAAP Taxonomy improvements for ASU 2026-02 are incorporated into the 2027 Development Taxonomy but are not part of the 2026 Annual Taxonomy Release pending SEC acceptance. Early adopters filing under the 2026 taxonomy must use extensions based on Development Taxonomy elements until the 2027 Annual Release is accepted by the SEC. If your team is considering early adoption for fiscal year 2026, coordinate with your XBRL preparer now to build the required extensions.

SAB 74 Disclosures: What You Must Say Right Now

SAB 74 requires SEC registrants to disclose the expected impact of recently issued but not yet adopted accounting standards in every 10-K and 10-Q filed before adoption. That obligation is live today, before the 2028 mandatory date.

Commercial Metals Company (CMC), a large accelerated filer, included one of the earliest real-world SAB 74 disclosures of ASU 2026-02 in its Form 10-Q for the period ended May 31, 2026, describing the standard as improving "the financial accounting for and disclosure of environmental credit obligations by creating a comprehensive framework to apply to all entities."

A compliant SAB 74 disclosure for ASU 2026-02 should cover:

• The name and nature of the standard (ASU 2026-02, ASC 818, environmental credits and ECOs).
• The mandatory effective date for your filer category.
• Whether you intend to early adopt.
• The transition method (modified retrospective, cumulative-effect adjustment to retained earnings).
• A qualitative description of the expected impact on your financial statements, or a statement that the assessment is in progress.
• Quantification of the expected impact once it is reasonably estimable. The SEC expects this to become more specific as the adoption date approaches.

For a full SAB 74 execution framework, including the progressive disclosure ratchet the SEC expects as adoption approaches, see our SAB 74 disclosure requirements guide.

Annual Disclosure Requirements Under ASC 818

Once adopted, ASU 2026-02 requires robust annual disclosures. Per Deloitte's Heads Up, the required disclosures include:

• How credits were obtained (acquired, granted, internally generated, nonreciprocal transfer).
• Intended use of credits and current/noncurrent classification, by line item on the balance sheet.
• The costing method elected (FIFO, average cost, or specific identification).
• ASC 820 fair value disclosures for any fair value measurements.
• Description of activities or events giving rise to ECO liabilities.
• Nature and timing of settlement provisions.
• Accounting policies for ECOs.
• How the unfunded ECO liability is measured.
• Significant estimates and judgments.
• The financial statement impact of any changes in intent for credits held.

This last point deserves emphasis. If a credit is reclassified from compliance to noncompliance (or vice versa) during the year, that change and its financial statement impact must be disclosed. Build the disclosure process into your close calendar from day one of adoption.

Building Your Adoption Roadmap

With 18 months until the mandatory PBE effective date, the sequencing of pre-adoption work matters. A practical timeline:

1. Now through Q3 2026: Complete the scope assessment. Inventory every credit type held, generated, or subject to an ECO. Confirm which are in scope of ASC 818 and which fall under ASC 740 (IRA credits) or ASC 410-30 (remediation).
2. Q4 2026: Make the accounting policy elections: costing method, fair value election for noncompliance credits, and internally generated/regulator-granted credit measurement. Document the rationale for each.
3. Q1 2027: Build or update systems and internal controls to track intent classification at the credit level, cost basis by costing method, and fair value inputs for the unfunded ECO. The close-process sequencing requirement (asset before funded ECO liability) must be embedded in the month-end workflow.
4. Q2 2027: Draft the opening retained earnings adjustment. Reconstruct cost bases for credits previously expensed. Engage auditors on the "probable" threshold and Level 3 fair value inputs for illiquid credits.
5. Q3 2027: Finalize SAB 74 disclosures with quantified impact estimates for the 2027 annual report. Coordinate with XBRL preparers on taxonomy extensions if early adopting.
6. January 1, 2028: Mandatory adoption for calendar-year PBEs. Q1 2028 Form 10-Q carries the first interim disclosures under ASC 818.

For multinational preparers who also report under IFRS, the treatment of the same credits differs materially under IAS 38 and IAS 37. A side-by-side comparison is in our ASC 818 vs. IFRS guide.

As FASB Chair Richard Jones stated when the ASU was issued: "It responds to stakeholders who expressed the need for increased understandability and comparability in this emerging area." The 2028 mandatory date is close enough that the work starts now.

FAQ

Do IRA renewable energy tax credits fall inside ASC 818? No. Income tax credits, including all renewable energy tax credits associated with the Inflation Reduction Act, are explicitly excluded from the definition of an environmental credit under ASC 818. They continue to be governed by ASC 740. Entities with projects that generate both RECs (in scope of ASC 818) and production or investment tax credits (ASC 740) must bifurcate accounting at the project level.

Can we net environmental credit assets against ECO liabilities on the balance sheet? No. Gross presentation is required under ASC 818. Environmental credit assets and ECO liabilities must be presented separately on the balance sheet and may not be offset, even when the same credits will be used to settle the same obligation.

What if we hold credits for both compliance and voluntary purposes? Classification is based on intent at the reporting date, not the credit's legal characteristics. A credit held for both purposes must be classified based on the primary intended use that meets the "probable" threshold. If the entity cannot establish that it is probable the credit will be used for compliance, transfer, or nonreciprocal distribution, it is expensed as incurred. Robust documentation of intent at acquisition and at each subsequent reporting date is essential.

When must a calendar-year private company adopt ASU 2026-02? Private companies and not-for-profit entities must adopt for annual periods beginning after December 15, 2028, meaning January 1, 2029 for calendar-year entities. Early adoption is permitted as of the beginning of any annual period. Private companies have no SAB 74 obligation, but should still assess impact and make accounting policy elections well in advance of the mandatory date.

How do forward contracts to purchase environmental credits interact with ASC 818? ECOs themselves are excluded from ASC 815 embedded derivative analysis. However, as PwC notes, a freestanding contract to obtain or sell an environmental credit in the future may still be subject to derivative accounting under the overall requirements of ASC 815. Entities using forward contracts to hedge credit price risk for future compliance periods should assess whether those contracts are derivatives and, if so, whether hedge accounting is available under ASC 815.