By Shawn Elliott, CFO | High Rock Accounting
So here’s the scenario I see more than I’d like to. A biotech company closes a partnership deal with a large pharma. Big moment. Years of work. The term sheet includes a $15 million upfront payment, clinical development milestones totaling another $80 million if certain Phase II and FDA approval events hit, and royalties on net sales down the road. And then everyone goes off to celebrate, and the finance team is left trying to figure out how to actually book all of it.
I’ll be honest, that’s where things can go sideways in a hurry if you don’t have a clear framework for how ASC 606 applies to these kinds of deals. And it’s not a simple framework. These agreements are some of the most complex revenue recognition situations I come across in the healthcare and biotech space, and the judgment calls involved are real and consequential. Getting them wrong doesn’t just create a messy close, it can create restatement risk and investor confusion at exactly the wrong moment.
So let me walk you through how the standard applies to each piece of a typical pharma licensing deal, because upfront payments, milestones, and royalties all get treated differently, and each one has its own set of rules that you need to understand before you touch the books.
Step One: The Five-Step Model Still Applies: But Pharma Contracts Make Every Step Harder
ASC 606 is built around a five-step model that applies to any contract with a customer. *1 You identify the contract, you identify the performance obligations inside it, you determine the transaction price, you allocate that price across the obligations, and you recognize revenue when each obligation is satisfied. That framework is not optional, even in pharma. But what makes these licensing deals tricky is that almost every step of the model requires more judgment here than it does in a typical product sale or service contract.
Step two is usually where the real complexity starts. In a pharma licensing deal, you often have multiple distinct promises bundled into one agreement: the IP license itself, ongoing R&D services, manufacturing commitments, regulatory support obligations, and sometimes options to acquire additional rights. The question under ASC 606 is which of those are separate performance obligations and which are bundled together. *2 A performance obligation has to be capable of being distinct and distinct within the context of the contract. That is a judgment, and it requires you to actually read the contract carefully and understand the substance of what each party is promising.
This matters a lot because how you define your performance obligations determines how you split up the transaction price, and how you split the transaction price determines when revenue hits the income statement. If you bundle obligations that should be separate, you’ll defer revenue that you could be recognizing. If you separate things that should be bundled, you might be pulling revenue forward before you’ve earned it. Neither one is a good look with an auditor.
The Upfront Payment: Point in Time or Over Time?
This is probably the question I get most often, and the answer is: it depends on the nature of the IP license.
Under ASC 606, IP licenses fall into two categories: functional IP and symbolic IP. *3 Functional IP has significant standalone functionality, meaning a drug compound or a patented formulation that the licensee can use as it exists on the day it’s transferred. Symbolic IP is something more like a brand or logo, where the value depends on the licensor’s ongoing activities to maintain it.
In pharma, drug compounds and formulations are generally functional IP. And for functional IP, the default under ASC 606 is point-in-time recognition, meaning you’d recognize the upfront license fee on the day control of the license transfers to the partner. *4 That’s a straightforward read, and it’s a meaningful departure from legacy GAAP, where many companies deferred upfront payments ratably over the contract term essentially out of habit.
But here’s the catch. If that license is not a separate, distinct performance obligation, because it’s bundled with significant ongoing R&D services that are intertwined with the license, then you can’t recognize it at point in time. You have to recognize revenue over the period you’re performing those combined obligations. *5 So if your deal includes continuing development responsibilities that meaningfully affect the IP itself, and the licensee’s ability to benefit from it depends on your ongoing work, the upfront payment may need to be deferred. That’s not a technicality. That’s a material impact on reported revenue.
The practical question to answer is: does the licensor still have substantive obligations that change the utility of the IP after day one? If the answer is yes and the licensee is contractually or practically required to use the updated IP once available, you’re looking at over-time recognition, not point in time. *3
Milestone Payments: Variable Consideration and the Constraint
Milestones are where the variable consideration guidance kicks in, and this is one of the trickier areas of the standard.
Under ASC 606, milestone payments are variable consideration because they depend on future events. The standard requires you to estimate variable consideration and include it in the transaction price, but it also applies a constraint: you can only include an amount if it’s probable that recognizing it won’t result in a significant revenue reversal later. *6 For early-stage milestones that are highly uncertain, like a Phase I completion payment where the trial hasn’t started yet, the constraint typically means you include zero in the transaction price until the outcome is no longer highly uncertain.
The standard gives you two estimation methods: expected value and most likely amount. *7 For milestone payments that are binary in nature, meaning either the FDA approves or it doesn’t, the most likely amount method is generally more appropriate. You identify which outcome is more likely and use that amount. You don’t average it. And you re-evaluate that estimate at every reporting period.
So in practice, what does this look like? A regulatory approval milestone of $10 million should generally stay off your income statement until approval becomes probable. That could mean you don’t touch that revenue until very late in the clinical process, sometimes not until the approval actually occurs. That’s not conservative accounting for its own sake. That’s what the standard requires to avoid a significant reversal, and it’s what auditors will push on if your judgment doesn’t hold up.
One nuance worth flagging: the variable consideration constraint applies to milestones, but the royalty exception is different, and I’ll get to that in a moment.
Royalties: The Sales-Based Royalty Exception
Royalties on licensed IP have their own rule under ASC 606, and it’s a genuine exception to the general variable consideration guidance. Under ASC 606-10-55-65, if you have a royalty that is sales-based or usage-based and relates to a license of intellectual property, you do not estimate and constrain it at contract inception. You recognize that royalty revenue only when the underlying sale or usage actually occurs, or when the performance obligation to which it relates is fully or partially satisfied, whichever is later. *8
In pharma terms, this means you do not try to estimate what future royalty revenue might be and include it in your transaction price. You wait. You recognize royalty revenue when your licensing partner reports sales to you, because that’s when the uncertainty resolves and the event triggering the payment has happened.
This exception exists because the FASB recognized that estimating usage-based royalties involves so much uncertainty that requiring companies to estimate and constrain them at contract inception would produce unreliable and potentially misleading revenue numbers. So the standard just says wait for the actual data.
The practical implication is that your royalty revenue stream will look lumpy, especially in the early commercial years of a product when sales data comes in on a lag. That’s expected and appropriate. What you don’t want to do is try to smooth it by accruing estimated royalties before the sales reports arrive, unless you have highly reliable data to support a very tight estimate. Most audit teams will push back hard on premature royalty accruals.
Allocating the Transaction Price Across Multiple Obligations
Once you’ve identified your performance obligations and estimated the transaction price including any milestone amounts you’ve determined are probable, you have to allocate that price across the obligations in proportion to their standalone selling prices. *1
In pharma licensing, standalone selling prices are often not observable, meaning you don’t have direct market data for what a specific IP license or R&D service arrangement would sell for on its own. That means you have to estimate them using methods like adjusted market assessment, expected cost plus a margin, or residual approach when one element’s price is highly variable. This is another area where judgment is required and where documentation of your methodology becomes critical.
Whatever allocation methodology you use, you need to apply it consistently across similar contracts and be able to defend it when your auditor asks. In my experience working through these kinds of deals, the documentation of the standalone selling price estimation is often the piece that’s most underdeveloped. The calculation gets done, but the rationale behind the method doesn’t get captured in writing in a way that would survive scrutiny six months later. That’s worth fixing before you close the deal’s first reporting period.
What Your Books and Your Disclosures Need to Reflect
The accounting treatment matters, but so does the disclosure. ASC 606 requires companies to provide detailed qualitative and quantitative disclosures about their revenue recognition policies, including the nature of their performance obligations, the methods and significant judgments used to recognize revenue, and any variable consideration constraints applied. *9
For pharma companies with licensing deals, this means your footnotes should clearly explain how you’re treating each payment type and why. Investors and analysts want to understand the revenue recognition timeline for milestone payments in particular, because those are often the events that drive significant step-changes in reported revenue. If your disclosures are thin or boilerplate, that’s where investor questions, and sometimes SEC comment letters, tend to come from.
On the books themselves, make sure your chart of accounts and your ERP system can handle deferred revenue in a way that traces back cleanly to the individual performance obligations. In Sage Intacct, for example, you can set up contract-based revenue schedules that automate the release of deferred revenue as obligations are satisfied, which removes a lot of the manual journal entry risk that tends to create errors in these complex multi-element deals. The mechanistic pieces of the close are a lot cleaner when the system is doing the heavy lifting.
The Mistakes I See Most Often
Just to give you a practical sense of where things go wrong:
- Treating upfront license fees as automatically recognizable at signing without first analyzing whether the license is distinct and whether it’s truly functional IP with no continuing performance obligations attached.
- Including milestone payments in the transaction price before it’s probable they won’t reverse, essentially pulling revenue forward in a way that may need to be reversed in a future period.
- Estimating and accruing royalty revenue before sales data has been received, which violates the sales-based royalty exception and creates reversal risk.
- Failing to update variable consideration estimates each reporting period, treating the initial estimate as fixed when the standard requires ongoing re-evaluation.
- Thin or missing documentation of standalone selling price assumptions, leaving the allocation methodology difficult to defend during audit or diligence. *6
In that type of scenario, any of those mistakes can create a material issue. And when you’re at the Series B or C stage and have a big pharma deal on the books that investors are watching closely, a revenue restatement or a qualification from your auditor on accounting methodology is the kind of thing that creates real turbulence at exactly the wrong time.
Getting This Right Before It Becomes a Problem
ASC 606 for pharma licensing deals is not the kind of thing you want to figure out on the fly in the middle of a close cycle. The judgment calls are substantial, the audit exposure is real, and the downstream impacts on investor reporting are significant enough that it’s worth getting a sanity check before you finalize the treatment.
If you’ve got a licensing deal in the works or have recently closed one and aren’t fully confident the books are squeaky clean on the revenue recognition side, that’s exactly the kind of thing my team at High Rock can dig into with you. We work in Sage Intacct, we know the standard, and we’ve been through this enough times to know where the landmines tend to be.
Come find us on a Hawaiian Shirt Friday at our Ask an Accountant Hour, every Friday at 10 AM PT. It’s open office hours, no agenda required, and it’s a good place to bring exactly this kind of question. You can join here:
Or if you’d rather grab some dedicated time to talk through your specific deal structure, book a 30-minute call here:
https://meetings-na2.hubspot.com/shawn-elliott/30-minute-meeting
Either way, we’re just a Slack message away. Happy to partner along the way and make sure the revenue side of your books is on solid ground before things get complicated.
Sources
*1 FASB ASC 606-10: Revenue from Contracts with Customers, Five-Step Model Overview. houseblend.io
*2 Common ASC 606 Issues: Life Sciences Entities : performance obligation identification in pharma licensing. revenuehub.org
*3 Licenses for Intellectual Property : functional vs. symbolic IP, point-in-time vs over-time recognition. revenuehub.org
*4 ASC 606 for Pharmaceuticals: Revenue Recognition Guide : upfront license treatment and the departure from legacy GAAP. houseblend.io
*5 EY Technical Line: How the New Revenue Standard Affects Life Sciences Entities : bundled obligations and deferral requirements. ey.com
*6 Variable Consideration Under ASC 606: How to Apply the Constraint : estimation methods and re-evaluation requirements. billingplatform.com
*7 ASC 606 & Life Sciences Revenue : most likely amount method for binary milestone payments. scrubbed.net
*8 Revenue Recognition in the Life Sciences Industry, RSM : the sales-based royalty exception under ASC 606-10-55-65. rsmus.com
*9 Pharmaceutical Licensing Agreements : disclosure obligations and standalone selling price methodology. drugpatentwatch.com
Enjoyed this article? Consider Sharing
Author
