Revenue Recognition

Under ASC 606, Topic 606, Revenue from Contracts with Customers, or ASC 606, the Company recognizes revenue when its customer obtains control of promised goods or services, in an amount that reflects the consideration which the entity expects to receive in exchange for those goods or services. To determine the appropriate amount of revenue to be recognized for arrangements determined to be within the scope of ASC 606, the Company performs the following five steps: (i) identification of the contract(s) with the customer; (ii) identification of the promised goods or services in the contract and determination of whether the promised goods or services are performance obligations; (iii) measurement of the transaction price; (iv) allocation of the transaction price to the performance obligations; and (v) recognition of revenue when (or as) the Company satisfies each performance obligation. The Company only applies the five-step model to contracts when it is probable that the entity will collect consideration it is entitled to in exchange for the goods or services it transfers to the customer. At contract inception, once the contract is determined to be within the scope of ASC 606, the Company assesses the goods or services promised within each contract and determines those that are performance obligations and assesses whether each promised good or service is distinct. The Company then recognizes as revenue the amount of the transaction price that is allocated to the respective performance obligation when (or as) the performance obligation is satisfied.

As part of the accounting for these arrangements, the Company must use significant judgment to determine: a) the number of performance obligations based on the determination under step (ii) above and whether those performance obligations are distinct from other performance obligations in the contract; b) the transaction price under step (iii) above; and c) the standalone selling price for each performance obligation identified in the contract for the allocation of transaction price in step (iv) above. The Company uses judgment to determine whether milestones or other variable consideration, except for royalties, should be included in the transaction price as described further below. The transaction price is allocated to each performance obligation on a relative stand-alone selling price basis, for which the Company recognizes revenue as or when the performance obligations under the contract are satisfied. In determining the stand-alone selling price of a license to the Company’s proprietary technology or a material right provided by a customer option, the Company considers market conditions as well as entity-specific factors, including those factors contemplated in negotiating the agreements as well as internally developed estimates that include assumptions related to the market opportunity, estimated development costs, probability of success and the time needed to commercialize a product candidate pursuant to the license. In validating its estimated stand-alone selling prices, the Company evaluates whether changes in the key assumptions used to determine its estimated stand-alone selling prices will have a significant effect on the allocation of arrangement consideration between performance obligations.

The Company estimates the transaction price based on the amount of consideration the Company expects to receive for transferring the promised goods or services in the contract. The consideration may include both fixed consideration and variable consideration. At the inception of each arrangement that includes variable consideration, the Company evaluates the amount of the potential payments and the likelihood that the payments will be received. The Company utilizes either the most likely amount method or expected value method to estimate the transaction price based on which method better predicts the amount of consideration expected to be received. If it is probable that a significant revenue reversal would not occur, the variable consideration is included in the transaction price.

Performance obligations are promised goods or services in a contract to transfer a distinct good or service to the customer. Promised goods or services are considered distinct when: (i) the customer can benefit from the good or service on its own or together with other readily available resources and (ii) the promised good or service is separately identifiable from other promises in the contract. In assessing whether promised goods or services are distinct, the Company considers factors such as the stage of development of the underlying intellectual property, the capabilities of the customer to develop the intellectual property on their own and whether the required expertise is readily available.

For performance obligations which consist of licenses and other promises, the Company utilizes judgment to assess the nature of the combined performance obligation in order to determine whether the combined performance obligation is satisfied over time or at a point in time. The Company receives payments from customers based on billing schedules established in each contract. Up-front payments and fees are recorded as deferred revenue upon receipt or when due until the Company performs its obligations under these arrangements. Amounts expected to be recognized as revenue within the 12 months following the balance sheet date are classified as current portion of deferred revenue in the accompanying consolidated balance sheets. Amounts not expected to be recognized as revenue within the 12 months following the balance sheet date are classified as deferred revenue, net of current portion. Amounts are recorded as accounts receivable when the Company’s right to consideration is unconditional. Amounts recognized as revenue, but not yet received or invoiced are generally recognized as contract assets.

Exclusive Licenses—If the license granted in the arrangement is determined to be distinct from the other promises or performance obligations identified in the arrangement, which generally include research and development services, the Company recognizes revenue from non-refundable, upfront fees allocated to the license when the license is transferred to the customer and the customer is able to use and benefit from the license. In assessing whether a license is distinct from the other promises, the Company considers relevant facts and circumstances of each arrangement, including the research and development capabilities of the collaboration partner and the availability of the associated expertise in the general marketplace. In addition, the Company considers whether the collaboration partner can benefit from the license for its intended purpose without the receipt of the remaining promise, whether the value of the license is dependent on the unsatisfied promise, whether there are other vendors that could provide the remaining promise, and whether it is separately identifiable from the remaining promise. For licenses that are combined with other promises, the Company utilizes judgment to assess the nature of the combined performance obligation to determine whether the combined performance obligation is satisfied over time or at a point in time and, if over time, the appropriate method of measuring progress for purposes of recognizing revenue. The Company evaluates the measure of progress each reporting period and, if necessary, adjusts the measure of performance and related revenue recognition based on estimated remaining research and development costs. The calculation of the total remaining estimated research and development costs includes forecasted costs associated with internal employee efforts, materials costs, and third-party contract costs, as well as the assumed timing and duration of these activities. The recognition of revenue pursuant to collaboration arrangements is subject to these judgments made and estimates developed by management and is sensitive to changes in these assumptions. Therefore, the measure of progress, and thereby periods over which revenue should be recognized, are subject to estimates by management and may change over the course of the arrangement.

Research and Development Services—The promises under the Company’s collaboration and license agreements generally include research and development services to be performed by the Company on behalf of the collaboration partner. For performance obligations that include research and development services, the Company generally recognizes revenue allocated to such performance obligations based on an appropriate measure of progress. The Company utilizes judgment to determine the appropriate method of measuring progress for purposes of recognizing revenue, which is generally an input measure, such as costs incurred. The Company evaluates the measure of progress each reporting period as described under Exclusive Licenses above. Reimbursements from the partner that are the result of a collaborative relationship with the partner, instead of a customer relationship, such as co-development activities, are generally recorded as a reduction to research and development expense.

Customer Options—The Company’s arrangements may provide a collaborator with the right to certain optional purchases, such as the right to license a target either at the inception of the arrangement or within a pre-defined option period. Under these agreements, fees may be due to the Company at the inception of the arrangement as an upfront fee or payment or upon the exercise of an option to acquire a license. If an arrangement is determined to contain customer options that allow the customer to acquire additional goods or services, the goods and services underlying the customer options are not considered to be performance obligations at the outset of the arrangement, as they are contingent upon option exercise. The Company evaluates the customer options for material rights, or options to acquire additional goods or services for free or at a discount. If the customer options are determined to represent a material right, the material right is recognized as a separate performance obligation at the inception of the arrangement. The Company allocates the transaction price to material rights based on the relative stand-alone selling price, which is determined based on the identified discount, and the probability that the customer will exercise the option. Amounts allocated to a material right are not recognized as revenue until, at the earliest, the option is exercised or expires.

Milestone Payments—At the inception of each arrangement that includes milestone payments based on certain events, the Company evaluates whether the milestones are considered probable of being achieved and estimates the amount to be included in the transaction price using the most likely amount method. If it is probable that a significant revenue reversal would not occur, the associated milestone value is included in the transaction price. Milestone payments that are not within the control of the Company or the licensee, such as regulatory approvals, are not considered probable of being achieved until those approvals are received. The Company evaluates factors such as the scientific, clinical, regulatory, commercial, and other risks that must be overcome to achieve the particular milestone in making this assessment. There is considerable judgment involved in determining whether it is probable that a significant revenue reversal would not occur. At the end of each subsequent reporting period, the Company reevaluates the probability of achievement of all milestones subject to constraint and, if necessary, adjusts its estimate of the overall transaction price. Any such adjustments are recorded on a cumulative catch-up basis, which would affect revenues and earnings in the period of adjustment. If a milestone or other variable consideration relates specifically to the Company’s efforts to satisfy a single performance obligation or to a specific outcome from satisfying the performance obligation, the Company generally allocates the milestone amount entirely to that performance obligation once it is probable that a significant revenue reversal would not occur.

Royalties—For arrangements that include sales-based royalties, including milestone payments based on a level of sales, and the license is deemed to be the predominant item to which the royalties relate, the Company recognizes revenue at the later of (i) when the related sales occur or (ii) when the performance obligation to which some or all of the royalty has been allocated has been satisfied (or partially satisfied). To date, the Company has not recognized any royalty revenue resulting from any of its licensing arrangements.

Collaboration revenue—The Company analyzes its collaboration arrangements to assess whether they are within the scope of ASC 808, Collaborative Arrangements, or ASC 808, to determine whether such arrangements involve joint operating activities performed by parties that are both active participants in the activities and exposed to significant risks and rewards dependent on the commercial success of such activities. This assessment is performed throughout the life of the arrangement based on changes in the responsibilities of all parties in the arrangement. For collaboration arrangements within the scope of ASC 808 that contain multiple elements, the Company first determines which elements of the collaboration are deemed to be within the scope of ASC 808 and those that are more reflective of a vendor-customer relationship and therefore within the scope of Topic 606. For elements of collaboration arrangements that are accounted for pursuant to ASC 808, an appropriate recognition method is determined and applied consistently, generally by analogy to Topic 606. For those elements of the arrangement that are accounted for pursuant to Topic 606, the Company applies the five-step model described above.

About Revenue Disclosures

Revenue disclosures under ASC 606 explain how a company identifies performance obligations, allocates transaction prices, and determines when revenue is recognized. This section is essential for understanding whether reported revenue reflects genuine economic activity or aggressive accounting choices. Analysts examine the mix of point-in-time versus over-time recognition, which directly affects revenue timing and comparability.

Key signals: rising contract liabilities (deferred revenue) suggest strong future revenue visibility, while declining contract assets may indicate slowing project milestones. Watch for variable consideration estimates — rebates, returns, and performance bonuses that require management judgment. Significant changes in disaggregated revenue by geography or product line can reveal shifting business mix before it appears in headline numbers. Compare revenue growth against contract liability growth to assess sustainability, and scrutinize any changes in the timing of recognition that coincide with earnings pressure.