Revenue Recognition

At contract inception, the Company assesses whether the collaboration arrangements are within the scope of ASC Topic 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 based on 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 arrangement are within the scope of ASC 808 and which elements are within the scope of ASC 606 (as described below). For elements of collaboration arrangements that are accounted for pursuant to ASC 808, an appropriate recognition method is determined and applied consistently, either by analogy to authoritative accounting literature or by applying a reasonable and rational policy election. To date, the Company has not entered into any arrangements within the scope of ASC 808.

The Company’s revenues were primarily generated through its license and collaboration agreements with Gilead. Refer to Note 3, “Collaboration Agreements” elsewhere in these notes to the Company's consolidated financial statements.

The Company recognizes revenue in accordance with ASC Topic 606, Revenue from Contracts with Customers. ASC 606 provides a five-step framework whereby revenue is recognized when control of promised goods or services is transferred to a customer at an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. To determine revenue recognition for arrangements that an entity determines are within the scope of ASC 606, the Company performs the following five steps: (i) identify the contract(s) with a customer; (ii) identify the performance obligations in the contract; (iii) determine the transaction price; (iv) allocate the transaction price to the performance obligations in the contract; and (v) recognize revenue when (or as) performance obligations are satisfied. The Company only applies this framework to contracts when it is likely that the entity will collect the 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 whether the goods or services promised within each contract are distinct and, therefore, represent a separate performance obligation. Goods and services that are determined not to be distinct are combined with other promised goods and services until a distinct bundle is identified. The Company then allocates the transaction price (that is, the amount of consideration the Company expects to be entitled to from a customer in exchange for the promised goods or services) to each performance obligation and recognizes the associated revenue when (or as) each performance obligation is satisfied. The Company’s estimate of the transaction price for each contract includes all variable consideration to which the Company expects to be entitled, subject to the constraint on variable consideration. Variable consideration is not constrained if the potential reversal of cumulative revenue recognized at the contract level is not significant.

In determining the appropriate amount of revenue to be recognized as the Company fulfills its obligations under active agreements, the Company must use its judgment to determine: (a) the number of performance obligations based on the determination under step (ii) above; (b) the transaction price under step (iii) above; (c) the stand-alone selling price for each performance obligation identified in the contract for the allocation of transaction price in step (iv) above; and (d) the contract term and pattern of satisfaction of the performance obligations under step (v) 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 the identified performance obligations 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 certain instances, the timing of satisfying these obligations can be difficult to estimate. Accordingly, the Company’s estimates may change in the future and those changes could be material. Such changes to estimates would result in a change in amounts of revenue recognized. If these estimates and judgments change over the course of these agreements, it may affect the timing and amount of revenue that the Company recognizes and records in future periods.

Amounts due to the Company for satisfying the revenue recognition criteria or that are contractually due based upon the terms of the collaboration agreements are recorded as accounts receivable in the Company’s consolidated balance sheet. Amounts received prior to satisfying the revenue recognition criteria are recorded as deferred revenue in the Company’s consolidated balance sheets. Amounts expected to be recognized as revenue within the one year following the balance sheet date are classified as current deferred revenue. Amounts not expected to be recognized as revenue within the one year following the balance sheet date are classified as deferred revenue, net of current portion. Amounts recognized as revenue, but not yet received or invoiced are generally recognized as contract assets.

Exclusive License Rights — If the license to the Company’s intellectual property 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 promises, whether the value of the license is dependent on the unsatisfied promises, whether there are other vendors that could provide the remaining promises and whether it is separately identifiable from the remaining promises. For licenses that are combined with other promises, the Company utilizes judgment to assess the nature of the combined performance obligation and whether the license is the predominant promise within 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. If the license is the predominant promise, and it is determined that the license represents functional intellectual property (“IP”), revenue is recognized at the point in time when control of the license is transferred. If it is determined that the license does not represent functional IP, revenue is recognized over time using an appropriate method of measuring progress.

Research and Development Services — The obligations under the Company’s collaboration agreements may include research and development services to be performed by the Company to benefit 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 and, if necessary, adjusts the measure of performance and related revenue recognition. The measure of progress, and thereby periods of which revenue should be recognized, are subject to estimates by management and may change over the course of the contract. 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 recorded as a reduction to research and development expense. No collaborative arrangements existed that would result in such reimbursements for the periods presented.

Customer Options — The Company’s arrangements may provide a collaborator with the right to acquire additional goods or services in the future. Under these agreements, fees may be due to the Company (i) upon the exercise of the customer option or (ii) in equal installment payments over an agreed upon period. If an arrangement is determined to contain customer options that allow the customer to acquire additional goods or services, the additional goods and services underlying the customer options are evaluated in order to determine if these additional goods or services are distinct from those included as a performance obligation at the outset of the arrangement. If the additional services are not determined to be distinct, the variable consideration pertaining to the customer option is added to the initial transaction price at the time in which the option exercise becomes probable, so long as a potential for reversal of cumulative revenue recognized at the contract level is not significant. Any such adjustments to the transaction price are recorded on a cumulative catch-up basis,

which would affect revenues and earnings in the period of adjustment. If the additional services are distinct, 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 an arrangement that includes development milestone payments, the Company evaluates whether the milestones are considered likely 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 reversal of cumulative revenue recognized would not occur, the associated milestone value is included in the transaction price. Milestone payments that are not within the control of the Company, 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, where 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 licensing agreements.

Historical Timeline

Fiscal YearFiled
2025Mar 5, 2026Showing above
2024Feb 27, 2025
2023Mar 18, 2024
2022Mar 27, 2023
2021Mar 28, 2022

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.