XML 32 R21.htm IDEA: XBRL DOCUMENT v3.24.3
Summary of Significant Accounting Policies (Policies)
9 Months Ended
Sep. 30, 2024
Accounting Policies [Abstract]  
Segment Reporting
Segment Reporting
Operating segments are identified as components of an enterprise about which discrete financial information is available for evaluation by the chief operating decision-maker ("CODM") in making decisions regarding resource allocation and assessing performance. The Company views its operations and manages its business in one operating segment.
Basis of Presentation
Basis of Presentation
The accompanying unaudited condensed consolidated financial statements have been prepared in accordance with accounting principles generally accepted in the United States (“GAAP”) for interim financial information and with the instructions of the Securities and Exchange Commission (“SEC”) on Form 10-Q and Rule 10-01 of Regulation S-X. Accordingly, they do not include all of the information and disclosures required by GAAP for complete financial statements. In the opinion of management, the unaudited condensed consolidated financial statements include all adjustments necessary, which are of a normal and recurring nature, for the fair presentation of the Company’s financial position and of the results of operations and cash flows for the periods presented. These unaudited condensed consolidated financial statements should be read in conjunction with the audited consolidated financial statements and notes thereto for the year ended December 31, 2023 included in the Company’s Annual Report on Form 10-K filed with the SEC on March 5, 2024. The results of operations for the interim period shown in this report are not necessarily indicative of the results that may be expected for any other interim period or for the full year. The balance sheet at December 31, 2023, has been derived from the audited consolidated financial statements at that date.
Use of Estimates
Use of Estimates
The preparation of condensed consolidated financial statements in conformity with GAAP requires management to make estimates and assumptions that affect the reported amounts of assets, liabilities, revenues, expenses and related disclosures. These estimates and assumptions are based on current facts, historical experience and various other factors believed to be reasonable under the circumstances, the results of which form the basis for making judgments about the carrying values of
assets and liabilities and the recording of expenses that are not readily apparent from other sources. Actual results could differ from those estimates.
Collaborative Arrangements
Collaborative Arrangements
The Company assesses whether its licensing and other agreements are collaborative arrangements based on whether they involve joint operating activities and whether both parties have active participation in the arrangement and are exposed to significant risks and rewards. For arrangements that the Company determines are collaborations, it identifies each unit of account, and then determines whether a customer relationship exists for that unit of account. If the Company determines a performance obligation within the collaborative arrangement to be with a customer, it applies its revenue recognition accounting policy. If a portion of a distinct bundle of goods or services within the collaborative arrangement is not with a customer, the Company applies recognition and measurement based on an analogy to authoritative accounting literature or, if there is no appropriate analogy, a reasonable, rational and consistently applied accounting policy election. To the extent the arrangement is within the scope of ASC 808, the Company assesses whether aspects of the arrangement between the Company and the collaboration partner are within the scope of other accounting literature. If the Company concludes that some or all aspects of the arrangement represent a transaction with a customer, the Company accounts for those aspects of the arrangement within the scope of ASC Topic 606, Revenue from Contracts with Customers (ASC 606). See Note 10, "Significant Agreements and Contracts," for more information.
Revenue Recognition
Revenue Recognition
The Company recognizes revenue when a customer obtains control of promised goods or services in a contract for an amount that reflects the consideration the Company expects to receive in exchange for those goods or services. For contracts with customers, 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) the Company satisfies each performance obligation. The Company only applies the five-step model to contracts when it is probable that the Company will collect the consideration it is entitled to in exchange for the goods or services it transfers to the customer. As part of the accounting for contracts with customers, the Company develops assumptions that require judgment to determine the standalone selling price of each performance obligation identified in the contract. In addition, variable consideration such as milestone payments are evaluated to determine if they are constrained and, therefore, excluded from the transaction price. The Company then allocates the total transaction price proportionally to each performance obligation based on their estimated standalone selling prices, unless an allocation exception applies. 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.
In a contract with multiple performance obligations, the Company must develop estimates and assumptions that require judgment to determine the underlying standalone selling price for each performance obligation, which determines how the transaction price is allocated among the performance obligations. The estimation of the stand-alone selling price(s) may include estimates regarding forecasted revenues or costs, development timelines, discount rates, and probabilities of technical and regulatory success. The Company evaluates each performance obligation to determine if it can be satisfied at a point in time or over time. Any change made to estimated progress towards completion of a performance obligation and, therefore, revenue recognized will be recorded as a change in estimate. In addition, variable consideration must be evaluated to determine if it is constrained and, therefore, excluded from the transaction price.
If a license to the Company’s intellectual property is determined to be distinct from the other performance obligations identified in a contract, the Company recognizes revenues from the transaction price allocated to the license when the license is transferred to the licensee and the licensee is able to use and benefit from the license. For licenses that are bundled 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 from the allocated transaction price. The Company evaluates the measure of progress at each reporting period and, if necessary, adjusts the measure of performance and related revenue or expense recognition as a change in estimate.
At the inception of each arrangement that includes milestone payments, the Company evaluates whether the milestones are considered probable of being reached. 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 Company’s or a collaboration partner’s control, such as regulatory approvals, are generally not considered probable of being achieved until those approvals are received. At the end of each reporting period, the Company re-evaluates the probability of achievement of milestones that are within its or a collaboration partner’s control, such as operational developmental milestones and any related constraint, and,
if necessary, adjusts its estimate of the overall transaction price. Any such adjustments are recorded on a cumulative catch-up basis, which will affect revenue from sale of licenses and revenue from contracts with collaborators in the period of adjustment. Revisions to the Company’s estimate of the transaction price may also result in negative revenue from sale of licenses and revenue from contracts with collaborators in the period of adjustment.
For arrangements that include sales-based royalties, including commercial milestone payments based on the level of sales, and a license is deemed to be the predominant item to which the royalties relate, the Company will recognize 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 from collaborative arrangements.
Recently Issued Accounting Pronouncements Not Yet Adopted
Recently Issued Accounting Pronouncements Not Yet Adopted
In November 2023, the FASB issued ASU 2023-07, Segment Reporting (Topic 280) Improvements to Reportable Segment Disclosures (“Topic 280”), which modifies the disclosure and presentation requirements of reportable segments. The amendments in the update require the disclosure of significant segment expenses that are regularly provided to the CODM and included within each reported measure of segment profit and loss. The amendments also require disclosure of all other segment items by reportable segment and a description of its composition. Additionally, the amendments require disclosure of the title and position of the CODM and an explanation of how the CODM uses the reported measure(s) of segment profit or loss in assessing segment performance and deciding how to allocate resources. Lastly, the amendment requires that a public entity that has a single reportable segment provide all the disclosures required by ASU 2023-07 and all existing segment disclosures in Topic 280. This update is effective for annual periods beginning after December 15, 2023, and interim periods within fiscal years beginning after December 15, 2024. Early adoption is permitted. The Company is currently evaluating the impact that this guidance will have on the presentation of its condensed consolidated financial statements and accompanying notes.
In December 2023, the FASB issued ASU 2023-09 "Income Taxes (Topics 740): Improvements to Income Tax Disclosures" to expand the disclosure requirements for income taxes, specifically related to the rate reconciliation and income taxes paid. ASU 2023-09 is effective for our annual periods beginning January 1, 2025, with early adoption permitted. The Company is currently evaluating the potential effect that the updated standard will have on its financial statement disclosures.
Net Loss Per Share
Net Loss Per Share
The Company follows the guidance in FASB ASC 260, Earnings per Share, or ASC 260, which establishes standards regarding the computation of earnings per share, or EPS, by companies that have issued securities other than common stock that contractually entitle the holder to participate in dividends and earnings of a company. The guidance requires earnings to be hypothetically allocated between the common, preferred, and other participating stockholders based on their respective rights to receive non-forfeitable dividends, whether or not declared.
Basic and diluted net loss per share of common stock is computed by dividing net loss attributable to common stockholders by the weighted-average number of common shares outstanding for the period. In loss periods, basic net loss per share and diluted net loss per share are identical because the otherwise dilutive potential common shares become anti-dilutive and are therefore excluded.