The thesis: a boundary that used to be a judgement call is now a dated event.
Companies get paid in equity more often than the accounting literature used to acknowledge. A supplier takes warrants alongside cash from a customer that would rather preserve runway. A platform takes shares in a partner in exchange for integration work. An early vendor to a private company negotiates an option grant as part of a supply agreement. Every one of those arrangements raises the same question on day one, which is whether the instrument you have been promised is an investment you hold now or a piece of the price of a contract you have not finished delivering.
FASB found that practice answered that question in more than one way, and ASU 2025-07 settles it. Share-based consideration from a customer stays inside the revenue standard until your right to receive or retain it becomes unconditional, and that happens when you have satisfied the performance obligations that release it. Only then does the instrument move to equity securities or derivatives accounting. The useful part for anyone who owns a finance system is what that rule depends on: a completion date for a specific set of performance obligations, which is a fact a revenue subledger computes continuously and currently sends to nobody.
What the Update does, and when it starts.
FASB issued Accounting Standards Update No. 2025-07 on September 29, 2025, under the full title Derivatives and Hedging (Topic 815) and Revenue from Contracts with Customers (Topic 606): Derivatives Scope Refinements and Scope Clarification for Share-Based Noncash Consideration from a Customer in a Revenue Contract. It carries two separate issues that share an effective date, and both of them come back to the same practical theme, which is where a commercial arrangement stops being a commercial arrangement and starts being a financial instrument.
The amendments are effective for all entities for annual reporting periods beginning after December 15, 2026, and interim reporting periods within those annual reporting periods. For a calendar-year company that is January 1, 2027. Early adoption is permitted in both interim and annual reporting periods for which financial statements have not yet been issued or made available for issuance, with one condition worth noting: an entity that early adopts one set of amendments has to early adopt the other at the same time. You cannot take the derivatives relief now and defer the revenue clarification.
Issue 1 addresses a complaint the Board heard through its 2021 Invitation to Comment on agenda consultation, which was that the definition of a derivative had grown broad enough to catch ordinary arrangements. Respondents pointed to bonds whose interest payments vary with environmental, social, and governance metrics, and to longstanding structures like research and development funding arrangements and litigation funding arrangements. Some noted that fair value measurement of those contracts was not producing decision-useful information, and that entities were structuring around the guidance to avoid derivative accounting. Issue 2 addresses the share-based consideration question directly.
How the revenue path actually runs.
New paragraph 606-10-15-3A says an entity applies Topic 606, including the noncash consideration guidance in paragraphs 606-10-32-21 through 32-24, to a contract with share-based noncash consideration from a customer for the transfer of goods or services. Guidance in other Topics, and the Update names Topic 815 on derivatives and Topic 321 on equity securities, does not apply unless and until the right to receive or retain that consideration is unconditional under Topic 606. Matching amendments were added at paragraphs 321-10-15-7, 815-10-25-16A, and 815-10-25-16B so the receiving standards point back the same way.
The test for unconditional is borrowed from familiar ground. It follows paragraph 606-10-45-4, under which a right to consideration is unconditional if only the passage of time is required before payment is due. What makes this workable in a system is the filter the Board put around it: in assessing whether the right is unconditional, only the contract terms that relate to your transfer of goods or services, or to a specific outcome of that transfer, are evaluated. A condition about a future financing round or an acquisition does not hold the instrument inside Topic 606, because it has nothing to do with whether you performed.
The Update added a worked example at paragraphs 606-10-55-250B through 55-250D that is worth walking through, because it shows how little of the mechanics is judgement once the data is in place. An entity contracts to deliver 5,000 units at $100 each in cash, plus 100 warrants with an estimated fair value of $100,000 at contract inception.
| Point in the contract | What is recorded | Why it matters for the data model |
|---|---|---|
| Contract inception | Transaction price is set at $600,000: 5,000 units at $100 cash, plus the $100,000 estimated fair value of 100 warrants. Allocated price per unit is $120. | The warrants are measured once, at inception, and become part of the transaction price. Nothing is recognised as an investment yet. |
| Year one, 3,000 units delivered | Revenue of $360,000 (3,000 units at $120), cash of $300,000, and a contract asset of $60,000, being the $100,000 inception fair value scaled by 3,000 of 5,000 units. | The contract asset carries the earned portion of the warrants. Changes in warrant fair value do not touch the transaction price, though the contract asset is assessed for impairment. |
| Year two, remaining 2,000 units delivered | Revenue of $240,000 (2,000 units at $120), cash of $200,000, and a further contract asset of $40,000 on the same inception measurement. | Still inside Topic 606. The warrants have not moved to investment accounting because performance is not yet complete. |
| All 5,000 units delivered | The right to receive or retain the 100 warrants is now unconditional under Topic 606. | The contract asset is derecognised and the warrants are accounted for under other Topics from that point. This is the handoff, and it has a date. |
Two details in that example carry most of the operational weight. The first is that the warrants are measured once, at contract inception, and the resulting amount stays in the transaction price. The example is explicit that the entity does not reflect changes in the fair value of the 100 warrants in the transaction price, though it does assess the related contract asset for impairment. That removes an entire class of remeasurement work, and it also removes the temptation to let revenue move with a customer’s share price. The second is that the contract asset accumulates in proportion to delivery, which means the balance is already derived from performance data your system holds.
The same clarification was added to Subtopic 610-20 at paragraph 610-20-15-3A, covering share-based consideration received from a counterparty for the transfer of nonfinancial assets or in substance nonfinancial assets. If your company takes equity as part of the price when it sells a building, a product line, or a similar asset, that transaction follows the same path, and the same register should cover it.
The second half, and why commercial finance should read it.
Issue 1 expands the scope exception at paragraph 815-10-15-59 for contracts that are not exchange-traded, adding a new item (e) for an underlying based on operations or activities specific to one of the parties to the contract. It covers underlyings based on the financial operating results, or components of those results, of one of the parties, and it covers underlyings based on the occurrence or nonoccurrence of an event specific to one party’s operations or activities. The examples the standard gives are obtaining regulatory approval, achieving a product development milestone, and achieving a greenhouse gas emissions reduction target. The Board added a helpful clarification for anyone applying this in practice: when evaluating whether operations or activities are specific to one of the parties, an entity does not need to consider whether the outcome is within its control.
| Treatment | Contract term | Basis in the Update |
|---|---|---|
| Inside the new scope exception | A payment that varies with the counterparty’s revenue, net income, or another component of its financial operating results. | Underlyings based on the financial operating results of one of the parties to the contract are covered by the expanded exception. |
| Inside the new scope exception | A milestone payment triggered by obtaining regulatory approval, achieving a product development milestone, or hitting a greenhouse gas emissions reduction target. | The exception reaches the occurrence or nonoccurrence of an event specific to the operations or activities of one of the parties. Whether the outcome is within your control does not need to be considered. |
| Outside the exception | A payment indexed to a market rate, market price, or market index. | Market-based underlyings are excluded from the exception by name, so the derivative analysis continues as before. |
| Outside the exception | A payment based on the price, performance, or default of a financial asset or financial liability of one of the parties, such as a default rate on a pool of loans one party holds. | Financial-instrument underlyings are excluded, including the occurrence of a credit event on a loan held by one of the parties. |
| Outside the exception | Contracts or features involving the entity’s own equity that fall under Subtopic 815-40, and call or put options on debt instruments. | Both are named exclusions, so the existing analysis for those instruments is unchanged. |
Two mechanical points sit alongside that list. Where a contract has more than one underlying and some but not all of them qualify for a scope exception, paragraph 815-10-15-60 keeps the existing predominant characteristics test, under which the contract stays inside Topic 815 if all its underlyings considered in combination behave in a way that is highly correlated with the variables that do not qualify. And solely for applying the new exception, the term party to the contract includes the parent, subsidiaries, and other entities consolidated by the parent, for both consolidated statements and the standalone statements of individual entities in the group. That second point matters for anyone maintaining a group structure in an ERP, because the entity whose operations drive the payment does not have to be the exact legal entity that signed.
The reason commercial finance should care is that the contracts affected are ordinary ones. Milestone fees, results-linked pricing, and earnout-shaped terms get drafted by people negotiating a deal, not by anyone consulting Topic 815. If those terms have been producing derivative accounting, some of them will stop, and the population has to be identified before the accounting can change. That is a contract review, and it is the same contract review that finds the share-based consideration for Issue 2.
The contract register worth building once.
Nothing about this requires new infrastructure. It requires a small number of fields attached to a small number of contracts, kept where the revenue records already live. The population is usually short enough to fit on one screen, which is exactly why it tends to be tracked informally until an auditor asks a precise question about it.
Contract identifier
The same identifier the revenue subledger uses, so a warrant or share right can be traced to the performance obligations that release it rather than to a signed PDF in a folder.
Consideration form
Cash, shares, share options, warrants, other equity instruments, or a mix, recorded as a field rather than inferred from a payment-terms free-text note.
Inception fair value
The measured fair value of the share-based consideration at contract inception, with the valuation method and inputs attached, because this is the number that stays in the transaction price for the life of the contract.
Releasing performance obligations
Which specific obligations have to be satisfied before the right becomes unconditional, since only terms relating to your own transfer of goods or services are evaluated for that question.
Non-performance conditions
Conditions unrelated to your performance, such as a financing round or a change of control, kept in a separate field so they are not accidentally treated as blocking the Topic 606 handoff.
Unconditional date
The date the right became unconditional, meaning only the passage of time remains before it is due. This is the single field that drives derecognition of the contract asset.
Receiving accounting treatment
Where the instrument goes after the handoff, whether that is equity securities under Topic 321 or derivatives under Topic 815, and who owns the record from that point.
Handoff owner
The named person responsible for moving the instrument between the revenue records and the investment records, so the event has an owner rather than being noticed at year-end.
Example register row for one contract with share-based consideration
{
"contract_id": "CTR-2026-04187",
"customer": "Series B platform customer, hardware supply agreement",
"consideration_form": ["cash", "warrants"],
"cash_component": { "units": 5000, "unit_price": 100, "currency": "USD" },
"share_based_component": {
"instrument": "warrants",
"quantity": 100,
"inception_fair_value": 100000,
"valuation_method": "black_scholes",
"measured_on": "2027-01-14"
},
"releasing_performance_obligations": ["PO-1 delivery of 5000 units"],
"non_performance_conditions": ["customer completes Series C"],
"unconditional_date": null,
"contract_asset_balance": 60000,
"receiving_treatment_on_handoff": "topic_321_equity_securities",
"handoff_owner": "Revenue accounting lead",
"transition_method": "prospective"
}The field doing the most work is the list of releasing performance obligations, because it converts an accounting judgement into a query. Once you can name which obligations release the right, the unconditional date stops being something a person remembers and becomes something the system can raise on the day it happens. The second most useful field is the separation of non-performance conditions, which is what stops a team from holding an instrument inside Topic 606 for a reason the standard does not recognise.
Implementation checklist.
Find the contracts first. Query the revenue and contract records for any arrangement whose consideration is not entirely cash, then check the commercial and legal files for warrants, share options, and equity grants agreed as part of a customer deal. In most companies this population is small, poorly labelled, and known to two people.
Record the inception fair value once, with its inputs, and stop revaluing it inside the transaction price. Under Topic 606 the share-based consideration is measured at contract inception, and later movements in the share price do not flow back into revenue.
Separate the conditions that relate to your performance from the ones that do not. Only contract terms tied to your transfer of goods or services, or a specific outcome of that transfer, are evaluated when deciding whether the right is unconditional.
Give the handoff an event and a date in the system, not a memo. When the releasing performance obligations are satisfied, the contract asset is derecognised and the instrument moves to Topic 321 or Topic 815. A revenue subledger already knows that date and can raise the event.
Decide the transition method deliberately and write down why. Prospective application covers new contracts entered into on or after adoption, including modified contracts treated as separate contracts under paragraph 606-10-25-12. Modified retrospective runs a cumulative-effect adjustment to opening retained earnings for contracts that exist at the start of the adoption period.
Plan the transition disclosure alongside the choice. Prospective adopters disclose the nature of and reason for the change. Modified retrospective adopters disclose that plus the cumulative effect on retained earnings or other equity components at the beginning of the adoption period.
Sweep commercial contracts for operations-linked payment terms while you are in there. Earnout-style clauses, milestone fees, and results-linked pricing are exactly the population the derivatives scope refinement moves, and the same contract review answers both questions.
Check whether any contract currently accounted for as a derivative comes out under the refinement. If you adopt on a modified retrospective basis there is a one-time instrument-by-instrument election to carry those contracts at fair value through earnings instead, and that election is irrevocable.
Extend the review to sales of nonfinancial assets. The same clarification was added to Subtopic 610-20, so share-based consideration received on a disposal of a nonfinancial asset follows the same path.
Sequence it by where the contracts are. Start with the commercial team’s record of non-cash deals, since those are the arrangements most likely to carry warrants or shares and least likely to be flagged in the revenue system. Work through open contracts with milestone or results-linked payment terms next, because that population answers the derivatives question. Historic contracts matter only if you choose modified retrospective transition, which is itself a reason to make the transition decision early rather than late.
Constructive failure modes to design around.
Booking the warrants as an investment on the day the contract is signed. That is one of the two treatments the Board found in practice, and after adoption the instrument stays inside Topic 606 until your performance makes the right unconditional.
Marking the share-based consideration to market through revenue as the customer’s share price moves. The measurement that sits in the transaction price is the one taken at contract inception, and the contract asset is tested for impairment rather than remeasured to fair value.
Treating a financing round, an IPO, or a change of control as a condition that holds the instrument inside Topic 606. Only terms relating to your own transfer of goods or services are evaluated for the unconditional assessment.
Leaving the handoff to a spreadsheet owned by one person. The event is driven by performance obligation completion, which the revenue system computes continuously, so a manual quarterly sweep will find it late in the quarter it happens.
Assuming the derivatives refinement only matters to treasury. The contracts it moves are ordinary commercial arrangements with milestone and results-linked terms, and they are drafted by commercial teams rather than by anyone who reads Topic 815.
Adopting one half of the Update early. Early adoption of the share-based noncash consideration amendments requires simultaneous early adoption of the derivatives amendments, and the same holds in reverse.
Reading the scope exception as narrower than it is because a milestone feels outside your control. The standard says explicitly that an entity does not need to consider whether the outcome is within its control when evaluating whether operations or activities are specific to one of the parties.
The pattern running through most of these is the same. The accounting is settled and fairly simple to state, and the risk sits in whether the right facts reach the right system on the right date. That is a solvable problem, and it is solvable with fields rather than with judgement.
What to ask ERP and revenue vendors now.
Can the revenue module hold noncash consideration as a first-class field on the contract, with its inception fair value and valuation inputs, rather than forcing it into a cash-denominated transaction price?
Does it raise an event when the specific performance obligations that release a share-based right are satisfied, so the handoff to investment accounting is triggered by the system rather than by a calendar reminder?
Can a contract asset be tagged to the instrument it represents, so derecognition on the handoff date is traceable to the obligations that caused it?
Does the contract record distinguish conditions tied to your performance from conditions tied to outside events, given that only the first group affects the unconditional assessment?
Can it report the full population of contracts with noncash or operations-linked consideration for a period, which is the population both halves of this Update turn on?
Does it support running the prospective and modified retrospective transition methods side by side long enough to compare the outcome before the method is chosen?
A platform that can hold noncash consideration as structured data, tie a contract asset to the instrument behind it, and raise an event when the releasing obligations complete has already built what this Update rewards. The judgements that remain, which instruments are in scope and how the receiving standard treats them, stay with the technical accounting team, which is where they belong.
Practical takeaway.
ASU 2025-07 is a clarification rather than an upheaval, and that is what makes it a good piece of work to do early. There is a known effective date of January 1, 2027 for calendar-year companies, a short and findable population of contracts, and a rule that reduces to one dated event: the moment your performance makes the right unconditional. Companies that spend a few weeks this autumn finding those contracts and giving them proper fields will adopt quietly. Companies that wait will spend the same effort in December on a population they are discovering for the first time, with a transition election to make at the same moment.
Sources.
- FASB: Accounting Standards Update No. 2025-07, Derivatives and Hedging (Topic 815) and Revenue from Contracts with Customers (Topic 606), full text (September 2025)
- AICPA and CIMA: ASU 2025-07, Changing Scope of Derivatives Accounting and Clarifying Accounting for Share-Based Noncash Consideration
- KPMG Financial Reporting View: FASB issues ASU on derivative scope refinements
- RSM US: FASB issues ASU on derivatives scope refinements
- BDO: Derivatives Scope Refinements and Scope Clarification for a Share-Based Noncash Consideration
- Deloitte: FASB Releases ASU to Amend Guidance on Derivatives Scope Refinements and Make Revenue-Related Scope Clarification
- Grant Thornton Snapshot 2025-12: Derivative scope refinements
- Moss Adams: Derivatives Scope Refinements and Clarifications to Share-Based Consideration
- Accounting Today: FASB releases standard on derivatives scope refinements
Targeted searches for public X and Twitter commentary on ASU 2025-07, the derivatives scope refinements, and share-based noncash consideration from a customer returned standard-setter accounts and trade-press links without a credible set of on-topic posts from a regulator or an independent practitioner. Ordinary citations are used instead, and nothing here is fabricated. Figures and paragraph references come from the text of the Update itself.