Company: IONQ
Filing Date: 2025-02-26
Form Type: 10-K
Source: 0000950170-25-027722
Chunk: 48

Company: IonQ, Inc.
Filing Date: 2025-02-26
Form: 10-K
Item: Item 6
Chunk 48
---
 or contain features that qualify as embedded derivatives in accordance with ASC Topic 815, “Derivatives and Hedging.” For derivative financial instruments that are accounted for as liabilities, the derivative instrument is initially recorded at its fair value on the grant date and is then re-valued upon exercise or at each reporting date for the unexercised warrants, with changes in the fair value reported in the consolidated statements of operations. The classification of derivative instruments, including whether such instruments should be recorded as liabilities or as equity, is evaluated at the end of each reporting period. The warrants of dMY assumed in the Business Combination are classified as liabilities and remeasured at each reporting period (as more fully described in Note 14). Derivative warrant liabilities are classified as non-current liabilities as their liquidation is not reasonably expected to require the use of current assets or require the creation of current liabilities. Revenue Recognition The Company derives revenue from the design, development, construction and sale of specialized quantum computing hardware together with related maintenance and support, from providing access to its quantum-computing-as-a-service (“QCaaS” or “Platform” services), and from consulting services related to co-developing algorithms on the quantum computing systems. The Company applies the provisions of the FASB Accounting Standards Update (“ASU”), Revenue from Contracts with Customers (“ASC 606”), and all related applicable guidance. The core principle of ASC 606 is that an entity shall recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. To support this core principle, the Company applies the following five step approach: 1.Identify the contract with the customer 2.Identify the performance obligations 3.Determine the transaction price 4.Allocate the transaction price to the performance obligations 5.Recognize revenue when (or as) the entity satisfies a performance obligation Certain of the Company’s contracts contain multiple performance obligations, most commonly in contracts for the sale of specialized quantum computing hardware together with related maintenance and support. Such contracts may also include access to the Company’s QCaaS. A contract’s transaction price is allocated to each distinct performance obligation and recognized as revenue when or as the performance obligation is satisfied. When there are multiple performance obligations in a contract, the Company allocates the transaction price to each performance obligation based on its standalone selling price when available. The Company determines standalone selling price based on the observable price of a product or service when it sells the products or