ASC 832 vs IAS 20: Government Grants Comparison After ASU 2025-10
For years, US GAAP left finance teams with no authoritative playbook for government grant accounting. The result was a patchwork of analogies: some companies borrowed from IAS 20, others from the not-for-profit contribution model under ASC 958-605, and a smaller group applied the contingent-gain model under ASC 450. On December 4, 2025, FASB ended that ambiguity with ASU 2025-10, amending ASC 832 to add a full recognition, measurement, and presentation framework deliberately modeled on IAS 20.
The result is substantial convergence. But "substantially converged" is not "identical," and the remaining gaps matter enormously for CFOs and controllers making accounting policy elections, assessing transition impact, and managing dual reporting obligations. This article goes beyond the side-by-side tables the Big 4 have already published and answers the questions those tables leave open.
Key takeaway: If your team has been applying IAS 20 by analogy under US GAAP, ASU 2025-10 will likely have limited practical impact on adoption. If you have been using ASC 450 or ASC 958-605, the change may be material. Either way, the accounting policy elections you make now will shape your EBITDA, leverage ratios, and asset values for the life of the grants.
What Changed in ASC 832 with ASU 2025-10
Before ASU 2025-10, ASC 832 contained only disclosure requirements. There was no US GAAP guidance on how to recognize, measure, or present government grants received by for-profit business entities. As BDO summarizes: "The lack of recognition, measurement, and presentation guidance in US GAAP led to diversity in practice in accounting for government grants received by businesses."
ASU 2025-10 fixes that by adding three things to ASC 832:
- Recognition criteria (when to record the grant)
- Measurement guidance (how to value it at inception and subsequently)
- Presentation requirements (where it goes on the income statement, balance sheet, and cash flow statement)
The FASB deliberately used IAS 20 as its foundation, with targeted improvements. As PwC notes: "Given the similarities between the guidance in ASU 2025-10 and IAS 20, adoption of ASU 2025-10 by companies currently applying IAS 20 by analogy will likely not have a significant impact."
The existing disclosure requirements in ASC 832 (added by ASU 2021-10 in November 2021) mostly carry forward, with certain modifications. Companies already complying with those disclosures are not starting from zero.
ASC 832 vs IAS 20: Where They Still Diverge
The top-ranking articles on this topic imply near-full convergence. That framing is too generous. Five areas of meaningful divergence remain.
1. Recognition Threshold: "Probable" vs. "Reasonable Assurance"
This is the most practically significant difference between the two standards.
- ASC 832: Recognition requires that it is probable the entity will comply with grant conditions and receive the grant, AND that the entity has incurred the related costs.
- IAS 20: Recognition requires reasonable assurance that conditions will be complied with and the grant received.
"Probable" under US GAAP is generally interpreted as "likely to occur," which most practitioners read as greater than 75%. "Reasonable assurance" under IFRS sits closer to "more likely than not" but carries a qualitative flavor that allows earlier recognition in some cases.
Consider a practical example: a manufacturer receives a conditional green-energy grant tied to achieving specific carbon reduction milestones over three years. Under IAS 20, if management has reasonable assurance the milestones will be met based on current trajectory, recognition can begin. Under ASC 832, the bar is higher: the entity must assess whether it is probable (not merely likely) that all conditions will be satisfied. For grants with complex or multi-year conditions, this threshold difference can delay US GAAP recognition by one or more reporting periods relative to IFRS.
ASC 832 also adds a third recognition condition absent from IAS 20: the entity must have incurred the costs and expenses associated with the grant before recognition. IAS 20 does not include this as a standalone criterion. This prevents front-loading of grant income under US GAAP even when the probability threshold is met.
2. Scope Differences
The two standards do not cover the same universe of transactions.
| Exclusion | ASC 832 | IAS 20 |
|---|---|---|
| Income taxes | ASC 740 transactions excluded | IAS 12 transactions excluded |
| Below-market interest rate loans | Excluded | Excluded |
| Government guarantees | Excluded | Excluded |
| Intangible asset grants / services | Excluded | Not explicitly excluded |
| Tax abatements | Excluded (reductions of liabilities) | Not explicitly excluded |
| Agriculture | No carve-out | IAS 41 transactions excluded |
| Not-for-profit entities | Excluded (use ASC 958-605) | No entity-type restriction |
| Employee benefit plans | Excluded | No entity-type restriction |
| Nongovernmental contributions in scope of ASC 958-605 | Excluded | N/A |
For dual reporters (companies filing under both US GAAP and IFRS), these scope differences create real complexity. A grant of an intangible asset, for example, falls within IAS 20's scope but is explicitly excluded from ASC 832. The entity must apply IAS 20 for IFRS reporting and identify an appropriate by-analogy framework for US GAAP. PwC confirms that a company may apply ASC 832 by analogy to out-of-scope transactions, as long as those transactions are not specifically subject to other US GAAP, consistent with ASC 105-10-05-02.
3. Nonmonetary Grant Measurement
Both standards permit the deferred income approach and the cost accumulation approach for grants related to assets. But they measure nonmonetary grants differently under the cost accumulation approach.
| Approach | ASC 832 (nonmonetary grant) | IAS 20 (nonmonetary grant) |
|---|---|---|
| Deferred income | Fair value | Fair value |
| Cost accumulation | Entity's cost (may be zero) | Fair value |
This divergence is subtle but real. If a state government transfers a parcel of land to a manufacturer as part of an economic development package, and the manufacturer incurred no cost to acquire it:
- Under ASC 832's cost accumulation approach, the land is recognized at zero (the entity's cost).
- Under IAS 20's cost accumulation approach, the land is recognized at fair value.
The result: the same economic event produces a materially different asset carrying value and a different depreciation (or amortization) base, depending on the standard applied. For companies receiving significant nonmonetary grants, this is not a rounding error.
4. Entity Type Restrictions
IAS 20 applies to all entity types without restriction. ASC 832 explicitly excludes not-for-profit entities (which continue to apply ASC 958-605) and employee benefit plans. This matters for dual reporters that include NFP or benefit plan structures in their group.
5. Agriculture Carve-Out
IAS 20 excludes transactions covered by IAS 41 (Agriculture). ASC 832 has no equivalent carve-out, though US agricultural entities may have other applicable guidance. This creates a potential scope mismatch for agribusiness dual reporters.
The Two Accounting Policy Elections: Which Should You Choose?
For grants related to assets, ASC 832 (like IAS 20) requires an entity-level accounting policy election between two approaches. This is not a grant-by-grant choice. Once made, it applies consistently across all asset-related grants.
Deferred Income Approach
Under this approach:
- The grant is recorded as a deferred income liability on the balance sheet.
- For a monetary grant, deferred income equals the cash received or expected.
- For a nonmonetary grant (e.g., equipment or land), deferred income is measured at fair value.
- The deferred income is recognized in earnings on a systematic and rational basis as the entity recognizes the related expenses (typically depreciation).
- For nondepreciable assets (e.g., land), the grant is recognized over the periods in which the entity incurs the costs to which the grant relates.
- The grant is presented in earnings either separately under a general heading (see the SEC nuance below) or as a reduction of the related expense.
Financial statement effects: Higher total assets (the asset is carried at full cost), a deferred income liability on the balance sheet, and grant income flowing through the income statement over the asset's useful life. EBITDA includes the grant amortization as income. Leverage ratios are affected by the deferred income liability.
Cost Accumulation Approach
Under this approach:
- The grant reduces the carrying amount of the asset directly.
- For a nonmonetary grant under ASC 832, the asset is recognized at the entity's cost, which may be zero.
- No separate deferred income liability appears on the balance sheet.
- Depreciation is calculated on the net carrying amount (cost less grant).
- No separate grant income line appears in earnings going forward.
Financial statement effects: Lower asset carrying value, lower depreciation expense over the asset's life, no deferred income liability, and no separate grant income line. EBITDA appears stronger because depreciation is lower, but there is no offsetting grant income credit. ROA and asset turnover metrics may look better.
Decision Framework
The right choice depends on your stakeholder priorities and capital structure. Ask:
- Debt covenants: Does a deferred income liability on the balance sheet trigger leverage covenant concerns? If so, the cost accumulation approach avoids that liability.
- EBITDA presentation: Do lenders or investors focus on EBITDA? The deferred income approach generates visible grant income that flows above the EBITDA line; the cost accumulation approach reduces depreciation instead, which also improves EBITDA but less visibly.
- Dual reporting: If you also report under IFRS, the deferred income approach aligns more closely with IAS 20 for nonmonetary grants (both use fair value). The cost accumulation approach creates a measurement divergence for nonmonetary grants.
- Audit simplicity: The cost accumulation approach is mechanically simpler; the deferred income approach requires ongoing tracking of the deferred income balance and its amortization schedule.
Key takeaway: Model both approaches against your actual grant portfolio before committing. The election is irrevocable on adoption and will affect your financial statements for the life of every asset-related grant.
The IRA and CHIPS Act Tax Credit Question
This is the live, high-stakes issue that most published guidance addresses only in passing.
Refundable and transferable tax credits under the Inflation Reduction Act (e.g., Section 48C advanced manufacturing credits) and the CHIPS and Science Act sit in a gray zone between ASC 740 (Income Taxes) and ASC 832.
The decision tree:
- Is the credit nonrefundable and nontransferable? It falls within ASC 740.
- Is the credit refundable (payable even without tax liability)? It is outside ASC 740 and falls within the definition of a government grant under ASC 832.
- Is the credit transferable (sellable to another taxpayer)? This is more nuanced. Nonrefundable but transferable credits may still be accounted for under ASC 740 by the original recipient. Any difference between the proceeds from selling the credit and its carrying value is recognized in the income tax provision.
PwC confirms that refundable tax credits not within the scope of ASC 740 fall within the definition of a government grant under ASC 832. Once ASU 2025-10 becomes effective, ASC 832 (rather than IAS 20 by analogy) will be the appropriate framework to apply by analogy to transferable tax credits that sit outside ASC 740.
For companies with significant IRA or CHIPS Act credit activity, this clarification matters now. The accounting policy you establish under the current by-analogy regime should be documented with ASU 2025-10 in mind, so the transition does not require a policy reversal. This intersects with the deferred tax analysis covered in our ASC 740 practitioner walkthrough.
The SEC Presentation Trap
Deloitte flags a nuance that neither BDO nor PwC explains in depth, and it is a real trap for SEC filers.
ASC 832 permits presenting a grant "separately under a general heading such as other income." The word "other income" here does not mean the same thing as "other income" in SEC Regulation S-X Rule 5-03, which represents income presented outside of operating income.
As Deloitte explains: "An entity may present this 'other income' as a component of income from operations if it is appropriate to do so on the basis of the entity's facts and circumstances."
In practice: a manufacturer that receives a grant reimbursing production costs may present that grant income within operating income, not below the operating income line. Presenting it below the line (as Reg S-X "other income") when the economics support an operating classification would misrepresent the company's operating performance and could attract an SEC comment letter.
The rule: follow the substance of the grant, not the label. If the grant compensates for operating costs, it belongs in operating income.
Cash Flow Presentation Under ASC 832
ASC 832 follows a "follow the underlying asset" logic for cash flow classification:
- Grants related to productive assets (e.g., PP&E): cash inflow presented as an investing activity.
- Grants related to operating assets (e.g., inventory): cash inflow presented as an operating activity.
- Grants related to income (e.g., wage subsidies, R&D reimbursements): cash inflow presented as an operating activity.
IAS 20 does not prescribe cash flow classification with the same specificity, leaving more judgment to the preparer. For dual reporters, this means the cash flow statement may look different under each standard for the same grant receipt.
Transition: Three Methods, One Right Answer for Most
ASU 2025-10 offers three transition methods. The choice affects comparative period financials and audit complexity.
| Method | What it means | Best for |
|---|---|---|
| Modified prospective | Apply to grants not yet fully recognized as of the beginning of the earliest period presented. No restatement of prior periods. | Entities with large, complex grant portfolios where retrospective restatement is impractical |
| Modified retrospective | Apply to all periods presented; record a cumulative-effect adjustment to opening retained earnings in the year of adoption. Comparatives are not restated. | Entities wanting cleaner comparatives without full restatement burden |
| Full retrospective | Restate all prior periods presented as if ASU 2025-10 had always been in effect. | Entities with simple grant portfolios and strong historical records; dual reporters wanting maximum IFRS alignment |
For most companies that were already applying IAS 20 by analogy, the modified prospective method is likely the path of least resistance. The accounting under the new ASC 832 will be substantially the same as what was already being done, so the cumulative-effect adjustment under modified retrospective may be immaterial anyway.
For companies that were using ASC 450 or ASC 958-605, the change may be material. These entities should model the cumulative-effect adjustment before choosing a transition method, because the full retrospective method could require significant restatement of prior-period financials and additional audit procedures.
Effective dates:
- Public business entities: annual periods beginning after December 15, 2028 (including interim periods within those annual periods).
- All other entities: annual periods beginning after December 15, 2029.
- Early adoption is permitted for any interim or annual period for which financial statements have not yet been issued.
For a company with a December 31 fiscal year, mandatory adoption falls in fiscal year 2029 (public) or 2030 (non-public). Early adoption is worth considering for companies with significant grant activity, dual reporters seeking IFRS alignment, or entities that want to resolve the IRA/CHIPS Act credit classification question under authoritative guidance rather than by analogy.
Disclosure Requirements: ASC 832 vs IAS 20
Both standards require disclosure of the nature, terms, and financial statement impact of government grants. The existing ASC 832 disclosures (from ASU 2021-10) mostly carry forward post-adoption, with modifications.
| Disclosure element | ASC 832 (post-ASU 2025-10) | IAS 20 |
|---|---|---|
| Accounting policy elected | Required | Required |
| Nature and significant terms/conditions | Required | Required |
| Balance sheet line items affected | Required | Required |
| Income statement line items affected | Required | Required |
| Unfulfilled conditions and contingencies | Required | Required |
| Grant repayment risk | Required | Required |
| Cash flow classification | Required | Encouraged, not mandated |
For SEC filers, the disclosure requirements under ASC 832 interact with Regulation S-X. The presentation of grant income within or outside operating income must be consistent with the disclosures and supportable based on the entity's facts and circumstances.
FAQ
Does ASU 2025-10 apply to my company if we already apply IAS 20 by analogy? Yes. Once ASU 2025-10 is effective, ASC 832 becomes the authoritative US GAAP framework for government grants received by business entities. You should assess whether your existing IAS 20 by-analogy policies need updating to comply, particularly around the "probable" recognition threshold, the third recognition condition (costs incurred), and the cost accumulation approach measurement of nonmonetary grants.
How do forgivable loans (e.g., PPP-style or green energy loans) fit under each standard? Under ASC 832, forgivable loan proceeds are in scope when it is probable the entity will meet the forgiveness terms. Under IAS 20, the threshold is reasonable assurance. The same threshold difference that applies to grants applies here. Document the basis for your probability assessment carefully, as auditors will scrutinize it.
We received a conditional grant but have not yet met all milestones. When do we recognize it? Under ASC 832, recognition requires both that it is probable you will comply with all conditions and receive the grant, AND that you have incurred the related costs. If either condition is not yet met, the grant is not recognized. Under IAS 20, the threshold is reasonable assurance rather than probable, which may permit earlier recognition in some fact patterns.
What happens if a grant becomes repayable after initial recognition? For grants related to assets: increase the asset's carrying amount (cost accumulation approach) or reduce the deferred income balance (deferred income approach), and immediately recognize in earnings any cumulative additional depreciation or change in prior gain, loss, or impairment that would have been recognized had the grant not been received. For grants related to income: apply the repayment against any remaining deferred income first; any excess is recognized immediately in earnings. IAS 20 follows the same general logic.
Can we apply ASC 832 to transactions explicitly excluded from its scope, like intangible asset grants? Yes, per ASC 105-10-05-02. As long as the transaction is not specifically subject to the scope of other US GAAP, a company may apply ASC 832 by analogy. PwC explicitly confirms this position for transferable tax credits and intangible asset grants.
How does this interact with ESG reporting? Government grants are increasingly conditioned on ESG commitments: green hydrogen subsidies, carbon capture grants, workforce diversity conditions. Under CSRD/ESRS and ISSB S2, companies may need to disclose the ESG conditions attached to material grants alongside their financial disclosures. The financial accounting treatment under ASC 832 or IAS 20 and the sustainability disclosure treatment are separate but should be coordinated. Finance and ESG teams should align on which grants carry material ESG conditions before the first CSRD reporting cycle.
For companies navigating the broader landscape of US GAAP versus IFRS convergence, our ASU 2023-09 vs IAS 12 income tax disclosures comparison covers a parallel convergence story in the tax disclosure space.







