XML 33 R18.htm IDEA: XBRL DOCUMENT
v3.22.2.2

Description of Business and Summary of Significant Accounting Policies (Policies) | 9 Months Ended
--- | ---
Sep. 30, 2022
Organization, Consolidation and Presentation of Financial Statements [Abstract] |
Revenue Recognition for Contracts with Customers | Revenue Recognition for Contracts with Customers The Company’s revenues are generated primarily through collaborative research, license, development and commercialization agreements. Accounting standards codification (“ASC”) 606, Revenue from Contracts with Customers (“ASC 606”) applies to all contracts with customers, except for contracts that are within the scope of other standards. Under ASC 606, an entity 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 revenue recognition for arrangements that an entity determines are within the scope of ASC 606, the entity 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 entity satisfies a performance obligation. At contract inception, once the contract is determined to be within the scope of ASC 606, the Company evaluates the performance obligations promised in the contract that are based on goods and services that will be transferred to the customer and determines whether those obligations are both (i) capable of being distinct and (ii) distinct in the context of the contract. Goods or services that meet these criteria are considered distinct performance obligations. If both these criteria are not met, the goods and services are combined into a single performance obligation. 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. Arrangements that include rights to additional goods or services that are exercisable at a customer’s discretion are generally considered options. The Company assesses if these options provide a material right to the customer and if so, these options are considered performance obligations. The exercise of a material right is accounted for as a contract modification for accounting purposes. The Company recognizes as revenue the amount of the transaction price that is allocated to the respective performance obligation when (or as) each performance obligation is satisfied at a point in time or over time, and if over time this is based on the use of an output or input method. For the nine months ended September 30, 2022, the Company recorded cumulative catch up adjustments on its contracts with customers that decreased revenue by $5.1 million; the cumulative catch-up adjustments resulted from changes in total estimated effort required to satisfy performance obligations. Invoices issued as stipulated in contracts prior to revenue recognition are recorded as deferred revenue. Amounts expected to be recognized as revenue within the 12 months following the balance sheet date are classified as deferred revenue within current liabilities in the accompanying condensed consolidated balance sheets. Amounts not expected to be recognized as revenue within the 12 months following the balance sheet date are classified as noncurrent deferred revenue. Amounts recognized as revenue, but not yet invoiced are generally recognized as contract assets in the other current assets line item in the accompanying condensed consolidated balance sheets. During the nine months ended September 30, 2022, the Company recorded $10.8 million in revenue that was included in deferred revenue as of December 31, 2021. Milestone Payments – If an arrangement includes development and regulatory milestone payments, the Company evaluates whether the milestones are considered probable of being reached 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 Company’s or the licensee’s control, such as regulatory approvals, are not considered probable of being achieved until those approvals are received and therefore revenue recognized is constrained as management is unable to assert that a reversal of revenue would not be probable. The transaction price is then allocated to each performance obligation on a relative standalone selling price basis, for which the Company recognizes revenue as or when the performance obligations under the contract are satisfied. At the end of each subsequent reporting period, the Company re-evaluates the probability of achievement of such development 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 would affect collaboration revenues and earnings in the period of adjustment. Royalties – For arrangements that include sales-based royalties, including milestone payments based on a level of sales, which are the result of a customer-vendor relationship and for which 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 linked to some or all of the royalty has been satisfied or partially satisfied. To date, the Company has not recognized any royalty revenue resulting from any of its licensing arrangements. Significant Financing Component – In determining the transaction price, the Company adjusts consideration for the effects of the time value of money if the timing of payments provides the Company with a significant benefit of financing. The Company does not assess whether a contract has a significant financing component if the expectation at contract inception is such that the period between payment by the licensees and the transfer of the promised goods or services to the licensees will be one year or less. The Company assessed each of its revenue arrangements in order to determine whether a significant financing component exists and concluded that a significant financing component does not exist in any of its arrangements. Collaborative Arrangements – The Company has entered into collaboration agreements, which are within the scope of ASC 606, to discover, develop, manufacture and commercialize product candidates. The terms of these agreements typically contain multiple promises or obligations, which may include: (1) licenses, or options to obtain licenses, to use the Company’s technology, (2) research and development activities to be performed on behalf of the collaboration partner, and (3) in certain cases, services in connection with the manufacturing of preclinical and clinical material. Payments the Company receives under these arrangements typically include one or more of the following: non-refundable, upfront license fees; option exercise fees; funding of research and/or development efforts; clinical and development, regulatory, and sales milestone payments; and royalties on future product sales. The Company analyzes its collaboration arrangements to assess whether the collaboration agreements are within the scope of ASC 808, Collaborative Arrangements (“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, are within the scope of ASC 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 ASC 606. For those elements of the arrangement that are accounted for pursuant to ASC 606, the Company applies the five-step model described above. For additional discussion of accounting for collaboration revenues, see Note 9, “Collaboration and License Agreements.”

X
- References No definition available. + Details
Name: | us-gaap_OrganizationConsolidationAndPresentationOfFinancialStatementsAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for revenue from contract with customer. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 17 -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130561-203045 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 20 -Subparagraph (d) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130566-203045 Reference 3: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 18 -Subparagraph (b) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130563-203045 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI https://asc.fasb.org/topic&trid=49130388 Reference 5: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 20 -Subparagraph (c) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130566-203045 Reference 6: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 18 -Subparagraph (a) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130563-203045 Reference 7: http://www.xbrl.org/2003/role/exampleRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 4 -Subparagraph (e) -URI https://asc.fasb.org/extlink&oid=126899994&loc=d3e18823-107790 Reference 8: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 20 -Subparagraph (b) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130566-203045 Reference 9: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 19 -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130564-203045 Reference 10: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 20 -Subparagraph (a) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130566-203045 + Details
Name: | us-gaap_RevenueFromContractWithCustomerPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration