Revenue recognition The Company accounts for contracts with customers in accordance with Accounting Standards Codification (ASC), Topic 606, Revenue from Contracts with Customers (Topic 606), including all amendments thereto. This standard applies to all contracts with customers, except for contracts that are within the scope of other standards, such as collaborative arrangements and leases. The Companys disclosure within the below sections or elsewhere within these consolidated financial statements reflects the Companys accounting policies in compliance with this new standard. Under Topic 606, an entity recognizes revenue when or as its customer obtains control of promised goods or services, in an amount that reflects the consideration that the entity expects to receive in exchange for those goods or services. To recognize revenue for arrangements that an entity determines are within the scope of Topic 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, including variable consideration, if any; (iv) allocate the transaction price to the performance obligations in the contract; and (v) recognize revenue when (or as) the entity satisfies its performance obligations. The Company only applies the five-step model to contracts when it is probable that the entity will collect substantially all of the consideration to which it will be entitled in exchange for the goods or services it transfers to the customer. Once a contract is determined to be within the scope of Topic 606, the Company assesses the goods or services promised within each contract and identifies as a performance obligation each promise to transfer to the customer either (a) a good or service (or bundle of goods and services) that is distinct, or (b) a series of distinct goods and services that are substantially the same and have been the same pattern of transfer to the customer. The Company assesses whether each promised good or service is distinct for the purpose of identifying the performance obligations in the contract. This assessment involves subjective determinations and requires management to make judgments about the individual promised goods or services and whether such are separable from the other aspects of the contractual relationship. Promised goods and services are considered distinct provided that: (i) the customer can benefit from the good or service either on its own or together with other resources that are readily available to the customer (that is, the good or service is capable of being distinct) and (ii) the entitys promise to transfer the good or service to the customer is separately identifiable from other promises in the contract (that is, the promise to transfer the good or service is distinct within the context of the contract). In assessing whether a promised good or service is distinct, the Company considers factors such as the research, manufacturing and commercialization capabilities of the collaboration partner (the customer in this type of arrangement) and the availability of the associated expertise in the general marketplace. The Company also considers the intended benefit of the contract in assessing whether a promised good or service is separately identifiable from other promises in the contract. If a promised good or service is not distinct, an entity is required to combine that good or service with other promised goods or services until it identifies a bundle of goods or services that is distinct. For each arrangement that results in revenues, the Company identifies all performance obligations, which may include, for example, a license to IP and know-how, research and development activities, and/or manufacturing services. In addition to any upfront payment, if the consideration promised in a contract includes a variable amount, the Company estimates the amount of consideration to which it will be entitled in exchange for transferring the promised goods or services to a customer. The Company determines the amount of variable consideration by using the expected value method or the most likely amount method. The Company includes the estimated variable consideration in the transaction price to the extent it is probable that a significant reversal of cumulative revenue recognized will not occur. At the end of each subsequent reporting period, the Company re-evaluates the estimated variable consideration included in the transaction price 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 in the period of adjustment. 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. There is considerable judgment involved in determining whether it is probable that a significant revenue reversal would not occur. If it is probable that a significant revenue reversal will not occur, the associated milestone value is included in the transaction price. Milestone payments that are not within the control of the Company or of the licensee such as regulatory approvals, are generally not considered probable of being achieved until those approvals are received. At the end of each subsequent reporting period, the Company re-evaluates 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. For contracts that include sales-based royalties (including milestone payments based on the level of sales) promised in the exchange for licenses of intellectual property, and the license is deemed to be the predominant item to which the royalties relate, the Company recognizes royalty revenue and sales-based milestone payments 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. In determining the transaction price, the Company adjusts the promised amount of consideration for the effects of the time value of money if the timing of payments provides the Company or the Companys customer with a significant benefit of financing the transfer of goods and services. 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 assesses each of its revenue generating arrangements in order to determine whether a significant financing component exists. 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, either at a point in time or over time. For performance obligations satisfied over time, the Company measures progress toward completion of its performance obligations using an input method based on the Companys efforts and inputs to satisfy its performance obligations relative to total expected inputs to the satisfaction of that performance obligation. Amounts received from a customer prior to revenue recognition are recorded as deferred revenue. Amounts received from a customer that are expected to be recognized as revenue within the 12 months following the balance sheet date are classified as a current liability in the accompanying consolidated balance sheets.