Why an earnout clause could have quietly turned your loan into a derivative
Here's a scenario that catches founders and controllers off guard: your company takes on debt with an interest rate that steps down if you hit a greenhouse-gas reduction target, or you issue a warrant to a customer as part of a multi-year supply deal, or an acquisition agreement includes an earnout tied to the acquired company hitting a revenue milestone. None of these feel like exotic financial instruments — they feel like ordinary business terms. But under the accounting rules that existed until recently, some of these features could be swept into derivative accounting: split out, measured at fair value every reporting period, and run through earnings as a volatility-adding line item that has nothing to do with how the business actually performed.
FASB just narrowed that trap. In September 2025, the board issued ASU 2025-07, which adds a new scope exception for contracts whose payoff depends on "the operations or activities specific to one of the parties" — and separately clarifies how warrants and other equity instruments received from a customer should be accounted for. If your company has ESG-linked debt covenants, earnouts, milestone payments, or warrants tied to a customer relationship, this update is worth understanding well before its effective date.
A 30-second refresher on why this was a problem at all
Under ASC 815, a contract (or a feature embedded inside a larger contract, like a loan) can be classified as a derivative if it has an "underlying" — a variable that determines the payoff — along with a notional amount and little or no initial net investment. Once something is classified as a derivative, it typically has to be:
- Separated out from the host contract ("bifurcated") if it's embedded in something like a loan or a supply agreement
- Measured at fair value at each reporting date
- Run through the income statement as those fair-value changes occur — even though nothing about the underlying business changed
That treatment makes sense for financial instruments like interest rate swaps or foreign-currency forwards, where the whole point is hedging or speculating on a market variable. It makes a lot less sense when the "underlying" is something like "did this company get its product approved by a regulator" or "did this company's greenhouse gas emissions fall below a target." Those aren't market variables an outside speculator could trade on — they're operational milestones specific to one party. But the accounting literature didn't clearly exclude them, so practice was inconsistent: some companies bifurcated these features and ran quarterly fair-value swings through earnings that told investors almost nothing useful, while others didn't, creating exactly the kind of diversity in practice that FASB tries to stamp out.
What ASU 2025-07 actually changes
The update does two distinct things, bundled into one standard.
1. The new "own operations" scope exception
ASU 2025-07 adds a scope exception excluding non-exchange-traded contracts (or embedded features) whose underlying is based on the operations or activities specific to one of the contracting parties. "Operations" here includes financial operating results — or components of those results — and specific events tied to a party's business, such as:
- A change in control
- An initial public offering
- Obtaining regulatory approval
- Achieving a product development milestone
- Meeting a greenhouse gas emissions target
Critically, it doesn't matter whether the triggering event is within that party's control. Getting regulatory approval for a drug or a medical device, for example, isn't something the company can simply will into happening, but it still counts as an "own operations" underlying and can qualify for the exception.
2. What still falls outside the exception
The new exception is deliberately narrow. It does not apply to underlyings based on:
- A market rate, market price, or market index
- The price or performance (including default) of a financial asset or financial liability held by one of the parties
- An issuer's own equity (which is evaluated separately, under the existing equity-classification guidance in Subtopic 815-40)
- Call or put options on debt instruments
So an interest rate swap is still a derivative. A put option tied to a bond's price is still a derivative. But a step-down interest rate provision tied to your own company's emissions target, or a contingent earnout payment tied to the acquired business hitting an EBITDA threshold, can now plausibly sit outside derivative scope entirely.
3. Warrants and equity received from customers move to Topic 606
The second piece of the update addresses a narrower but common situation: a customer contract where the company receives share-based, noncash consideration from the customer — most often a warrant, as part of a strategic partnership or long-term supply arrangement. ASU 2025-07 clarifies that this revenue guidance in Topic 606 applies first, rather than derivative accounting, unless and until the company's right to receive or retain the instrument becomes unconditional. That removes a second source of the same problem: a contractual feature tied to a customer relationship being marked to fair value through earnings every quarter for reasons that have nothing to do with the underlying business relationship.
Real-world situations this is likely to touch
You don't need to be a Fortune 500 company with a derivatives desk for this to matter. The features most likely to be affected are common in growth-stage and middle-market businesses:
- ESG-linked or sustainability-linked debt. A growing number of credit facilities include interest rate step-ups or step-downs tied to the borrower hitting sustainability metrics — emissions reductions, diversity targets, renewable energy usage. Those provisions are a textbook example of an "own operations" underlying.
- M&A earnouts and contingent consideration. Post-acquisition payments tied to the acquired business hitting a revenue, EBITDA, or product milestone are exactly the kind of company-specific underlying the exception targets, provided they aren't also tied to a market index or the acquirer's own stock price.
- Change-of-control puts and calls. Debt or equity provisions that trigger on a change-of-control event — common in venture debt and mezzanine financing — can qualify, since the triggering event is specific to the company rather than a market variable.
- Milestone-based licensing and development payments. Biotech, medtech, and technology licensing agreements frequently include payments tied to a party achieving a development or regulatory milestone.
- Warrants issued to strategic customers or lenders. A warrant given to a customer as part of a long-term supply or partnership agreement is now squarely a Topic 606 question in the first instance, not an automatic derivative.
What doesn't change
It's worth being precise about the limits here, because this update is a scope narrowing, not a blanket exemption from derivative accounting. Anything tied to a market rate, a market index, the price of a financial instrument, or an issuer's own equity keeps going through the existing analysis. A convertible note with a conversion price tied to the company's own stock, for instance, still needs the existing equity-classification analysis under Subtopic 815-40 — this update doesn't touch that. And the exception only applies to contracts that aren't exchange-traded, so anything with a genuinely tradable market price is out of scope for this relief by definition.
Effective date and transition
ASU 2025-07 is effective for annual reporting periods beginning after December 15, 2026, and interim periods within those annual periods. Early adoption is permitted. Companies can apply the transition either prospectively or using a modified retrospective approach, with instrument-by-instrument elections available — meaning you don't have to apply the same transition method uniformly across every affected contract.
That flexibility is useful, but it also means the transition decision itself takes some analysis. A modified retrospective approach could remove accumulated fair-value volatility that's been sitting on your balance sheet or flowing through prior-period earnings for features that now qualify for the exception — which could meaningfully change reported equity and prior comparability, depending on how many affected contracts you carry.
What to do before this hits your financial statements
- Inventory contracts and embedded features with contingent, non-market underlyings. Pull together every ESG-linked debt covenant, earnout, change-of-control provision, milestone payment, and customer-issued warrant currently on your books, and note which ones are currently bifurcated and marked to fair value.
- Sort them against the exception's boundaries. For each one, ask whether the underlying is tied to your own operations (a candidate for the exception) or to a market rate, market index, financial instrument price, or your own equity (still in scope for the existing derivative analysis).
- Model the transition impact early. If reclassifying a feature out of derivative accounting will remove accumulated fair-value gains or losses from your balance sheet, understand that impact on equity and prior-period comparability before you have to explain it to a lender, investor, or auditor.
- Talk to your accountant about early adoption. If your company currently carries volatile, hard-to-explain fair-value swings from features that would now qualify for the exception, early adoption might simplify your financial statements sooner rather than waiting for the 2026 fiscal year effective date.
- Keep the underlying contract terms in clean, accessible records. This kind of scope analysis depends on having the actual contract language — interest rate step conditions, earnout thresholds, warrant vesting terms — readily available rather than buried in a deal folder from three years ago.
Keep Your Financial Records Ready for the Next Standard Change
Standards like ASU 2025-07 are a reminder that the contracts sitting in your deal files can have outsized effects on your financial statements years after signing. Beancount.io provides plain-text accounting that's transparent, version-controlled, and easy to hand to an auditor or accountant when a new standard requires you to revisit old instruments — no hunting through spreadsheets to reconstruct terms nobody remembers. Check out the documentation to see how a version-controlled ledger keeps your debt, equity, and contingent-consideration instruments organized and audit-ready.