Revenue Recognition: Product Revenues Product revenues consist of commercial sales of XERMELO in the United States and sales of bulk tablets of XERMELO to Ipsen Pharma SAS (Ipsen). Product revenues are recognized when the customer obtains control of the Companys product, which occurs upon delivery to the customer. The Company recognizes product revenue net of applicable reserves for variable consideration, including allowances for customer credits, estimated rebates, chargebacks, discounts, returns, distribution service fees, and government rebates, such as Medicare Part D coverage gap reimbursements in the U.S. These estimates are based on the most likely amount method for relevant factors such as current contractual and statutory requirements, industry data and forecasted customer buying and payment patterns. The Companys net product revenues reflect the Companys best estimates of the amounts of consideration to which it is entitled based on the terms of the respective underlying contracts. Product shipping and handling costs are considered a fulfillment activity when control transfers to the Companys customers and such costs are included in cost of sales. Collaborative Agreements Revenues under collaborative agreements include both license revenue and contract research revenue. The Company performs the following five steps in determining the amount of revenue to recognize as it fulfills its performance obligations under each of its agreements: (i) identify the contract(s) with a customer; (ii) identify the performance obligation in the contract; (iii) determine the transaction price; (iv) allocate the transaction price to the performance obligation in the contract, and (v) recognize revenue when (or as) the Company satisfies the performance obligation. The Company applies this 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. At contract inception, the Company assesses the goods or services promised within each contract and determines those that are performance obligations, and assesses whether each promised good or service is distinct. 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. The Company develops assumptions that require judgment to determine the stand-alone selling price for each performance obligation identified in the contract. At contract inception, the Company evaluates whether development 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 will not occur, the associated development milestone value is included in the transaction price. Development milestones that are not within the control of the Company or the licensee, including those requiring regulatory approval, are not considered probable of being achieved until those approvals are received. The transaction price is allocated to each performance obligation on a relative stand-alone selling price basis, for which the Company recognizes revenue when (or as) the performance obligation is satisfied. At the end of each reporting period, the Company re-evaluates the probability of achievement of the development milestones and any related constraint, and if necessary, adjusts its estimates of the overall transaction price. Any such adjustments are recorded on a cumulative catch-up basis, which would affect collaboration revenues in the period of adjustment. In agreements in which a license to the Companys intellectual property is determined distinct from other performance obligations identified in the agreement, the Company recognizes revenue when the license is transferred to the licensee and the licensee is able to use and benefit from the license. For agreements that include sales-based royalties, including milestones based on a level of sales, 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). The Company may receive payments from its licensees based on billing schedules established in each contract. Up-front payments and fees are recorded as deferred revenue upon receipt or when due, and may require deferral of revenue recognition to a future period until the Company performs its obligations under these agreements. Amounts are recorded as accounts receivable when the Companys right to consideration is unconditional.