Financial Reporting
Customer Warrants and ASU 2025-04: When Equity Paid to a Buyer Becomes Negative Revenue
ASU 2025-04 rewrites how warrants paid to a customer hit revenue: purchase-based vesting is a performance condition, and forfeitures must be estimated.
By 409.AI Team - 2026-08-13
Somewhere in your commercial contracts there is probably a sentence that quietly rewrites your income statement. It usually reads something like this: "Upon Customer's cumulative purchases exceeding $2,000,000, Customer shall receive a warrant for 25,000 shares of Common Stock." Sales negotiated it to close the logo. Legal papered it. Nobody in finance priced it.
FASB has now spelled out how to price it. Accounting Standards Update 2025-04, issued on May 15, 2025, cleans up the accounting for share-based consideration payable to a customer. It takes effect for annual reporting periods beginning after December 15, 2026, including interim periods within those years, so a calendar-year company adopts it on January 1, 2027. That leaves this year to find every deal of this kind and decide what to do about it.
Equity paid to a customer is not marketing spend
Start with the part that trips people up before any new guidance applies.
Under ASC 606, consideration payable to a customer is accounted for as a reduction of the transaction price, and therefore of revenue, unless the payment is in exchange for a distinct good or service the customer transfers to you (ASC 606-10-32-25 and 606-10-32-26). "Payment" is not limited to cash. A warrant, an option, or a share grant handed to a customer is consideration payable to that customer.
So it does not sit in sales and marketing next to your conference budget. It comes off the top line. Companies that use customer warrants at scale report it exactly that way. Plug Power carries a line called "provision for common stock warrants" as a reduction of revenue in its [SEC filings](https://www.sec.gov/Archives/edgar/data/1093691/000155837025002049/plug-20241231x10k.htm), tied to warrants issued to Amazon and Walmart that vest as those customers buy. A Darden case study on the arrangement is titled "A Case of Negative Revenue," which is the most honest three-word description of the mechanic anyone has published.
The measurement side has been settled since ASU 2019-08: you measure share-based consideration payable to a customer under ASC 718, the same standard that governs [how you expense stock options](https://409.ai/articles/asc-718-stock-based-compensation-startup-guide), rather than remeasuring it to vesting-date value. What ASU 2019-08 did not settle was how the vesting conditions interact with revenue, and that is where practice diverged for six years.
The four things ASU 2025-04 changed
Purchase-based vesting is a performance condition. The master glossary definition of "performance condition" now explicitly covers conditions based on the volume or monetary amount of a customer's purchases or potential purchases, including targets tied to purchases by others in the distribution chain, such as your customer's customers. If you sell through channel partners and the warrant vests on sell-through rather than sell-in, this is the sentence that governs you.
The forfeiture policy election is gone for customer awards. GAAP has long let a company choose between estimating forfeitures up front and recognising them only as they happen. That choice survives for awards to employees and to vendors. It does not survive for share-based consideration payable to a customer with a service condition, where you now have to estimate the forfeitures you expect.
The ASC 606 variable consideration constraint does not apply. This was the live debate. Some companies had been running these awards through the constraint, including consideration only to the extent a significant revenue reversal was not probable. FASB closed that door: the constraint does not apply to share-based consideration payable to a customer measured under Topic 718, and it does not apply regardless of whether the award's grant date has occurred.
Topic 718 governs before and after grant date. If grant date has not yet happened, the award is still measured under ASC 718 at fair value, updated at each reporting date. Once grant date occurs, that fair value is fixed, and later swings in your share price do not move the transaction price. Vesting conditions keep driving recognition, so only the consideration you expect to be earned reduces revenue.
FASB's own summary of the project sits on the [Share-Based Consideration Payable to a Customer page](https://www.fasb.org/page/PageContent?pageId=%2Fprojects%2Frecently-completed-projects%2Fshare-based-consideration-payable-to-a-customer.html), and [Grant Thornton](https://www.grantthornton.com/content/dam/grantthornton/website/assets/content-page-files/audit/pdfs/snapshot/snapshot-2025-08-fasb-clarifies-accounting-for-share-based-consideration-payable-to-a-customer.pdf) and [Crowe](https://www.crowe.com/insights/take-into-account/fasb-asu-addresses-share-based-payments-to-customers) have both published readable walkthroughs of the amendments.
Working the numbers
Take a Series B infrastructure company. To land an anchor customer it grants a warrant over 100,000 shares of common stock at a $1.00 exercise price, vesting in four tranches of 25,000 shares as cumulative purchases pass $2M, $4M, $6M and $8M. An appraiser prices the warrant at $1.20 per underlying share at grant date, so the whole instrument is worth $120,000.
The company does not book $120,000 anywhere on day one. It asks which tranches are probable of vesting. Sales forecasts and the customer's own procurement plan support roughly $6M of purchases over the contract term, so three tranches are probable: 75,000 shares at $1.20, or $90,000 of consideration. That $90,000 comes off revenue as the related purchases are recorded, not as a lump sum and not as an operating expense.
Two quarters later the customer expands into a second business unit and the fourth tranche becomes probable. The company trues up, adding the remaining 25,000 shares at $1.20, another $30,000 against revenue. If the customer instead stalls at $3M and the third tranche stops being probable, the estimate reverses in the other direction.
That true-up rhythm is the practical difference from running these awards through the ASC 606 constraint. The constraint sets a high bar, admitting a variable amount only to the extent a significant revenue reversal is not probable, which led some companies to hold off on the hit until the customer's purchases were close to certain. The performance-condition model asks a simpler question, whether achievement is probable, books accordingly, and adjusts when the answer changes. Same contract, different revenue line, different quarterly story for your board.
The valuation is the part people underestimate
Every number above starts with a fair value, and for a private company that fair value is not sitting in a market data feed.
Valuing a warrant over private common stock takes two layers. First the current price of the underlying share, which is the same common stock fair value your option strike prices run on, built by allocating enterprise value across the capital structure through [an OPM, a PWERM or a backsolve](https://409.ai/articles/409a-allocation-methods-opm-pwerm-backsolve) and then discounting for illiquidity. Then an option pricing model on top of it, with expected term, risk-free rate, and volatility drawn from guideline public companies.
There is a useful shortcut here for private companies. ASU 2021-07 gave nonpublic entities a practical expedient for determining that current price input on equity-classified awards: a valuation performed under the reasonable application of a reasonable valuation method, the same standard the Treasury regulations use for Section 409A, satisfies the ASC 718 requirement. In plain terms, one defensible valuation can serve both the tax side and the reporting side. It applies to awards granted to employees and to nonemployees, and it is not available for liability-classified awards, so classification matters before you rely on it.
Timing matters too. If your award has not reached grant date, you are remeasuring at every reporting date, which means a single annual valuation may not carry you through the year. This is the same discipline that governs [how often you refresh a 409A](https://409.ai/articles/409a-valuation-frequency-how-often-should-you-get-one) when material events keep landing. And if an IPO is anywhere on your horizon, remember that underwriters and the SEC apply hindsight to the fair values you used in the run-up. The [cheap stock analysis](https://409.ai/articles/cheap-stock-pre-ipo-409a-sec-option-grants) that second-guesses your option grants will look just as hard at the warrant you handed your largest customer, because that one moved reported revenue.
Companies reporting under IFRS rather than US GAAP are outside the scope of this ASU entirely and continue under IFRS 2 and IFRS 15. If you run dual books, our comparison of [IFRS 2 and ASC 718](https://409.ai/articles/ifrs-2-vs-asc-718-share-based-payment) covers where the two share-based payment models already diverge.
What to do before the standard bites
The work this year is discovery, not adoption. Pull every commercial agreement where a customer, reseller, or channel partner can earn equity: warrants in master service agreements, options in partnership deals, share grants in pilot conversions, anything a business development team signed that a controller never saw. In a lot of companies these live in the contract repository and nowhere in the accounting close.
For each one, read the vesting trigger and label it. Purchase volume or purchase value, from that customer or from anyone downstream, is now a performance condition. Time or continued relationship is a service condition, and those are the ones that lost the forfeiture election.
Then pick a transition method. ASU 2025-04 allows either a modified retrospective approach, which puts a cumulative-effect adjustment into opening retained earnings in the period of adoption without recasting prior periods, or a full retrospective approach, which recasts comparatives and uses the actual outcome of vesting conditions where it is already known. Early adoption is permitted for financial statements not yet issued, which is worth considering if you have an audit coming and would rather change once than twice.
The awkward version of this project is the one that starts when your auditor asks the question in early 2027 and you discover that the answer requires valuing an instrument as of a date eighteen months in the past. Retroactive valuations are doable, and they are more expensive and less comfortable than current ones.
The takeaway
Go find the vesting sentence. Not the deal summary, not the term sheet, the operative sentence in the executed contract that says what the customer has to do to earn the shares. Whether that sentence describes purchases or the passage of time now determines which model you apply, when the charge hits, and how much judgment your auditor gets to test. Everything else in ASU 2025-04 follows from reading it correctly.
If you have customer or partner equity on the books, 409.ai produces the ASC 718 and 409A valuations that feed these numbers, including the option pricing work behind warrants over private common stock.
*This article is educational and is not accounting or tax advice. Confirm the current text of ASU 2025-04 against FASB's published standard and speak with your auditor before applying it.*