Significant Accounting Policies | Significant Accounting Policies There have been no changes to the significant accounting policies disclosed in the Company’s most recent Annual Report on Form 10-K, except as required by recently adopted accounting pronouncements, as discussed below. Revenue Recognition Effective January 1, 2018, the Company adopted the provisions of Accounting Standards Codification (“ASC”) 606, Revenue from Contracts with Customers using the modified retrospective method for all contracts not completed as of the date of adoption. The reported results for 2018 reflect the application of ASC 606 guidance, while the reported results for 2017 were prepared under the guidance of ASC 605, Revenue Recognition (ASC 605). Under ASC 606, the Company recognizes revenue when its customer obtains control of promised goods or services, in an amount that reflects the consideration which the Company expects to receive in exchange for those goods or services. To determine revenue recognition for arrangements that are within the scope of ASC 606, the Company performs the following five steps: 1. Identify the contract with the customer. A contract with a customer exists when (i) the Company enters into an enforceable contract with a customer that defines each party’s rights regarding the goods or services to be transferred and identifies the related payment terms, (ii) the contract has commercial substance, and (iii) the Company determines that collection of substantially all consideration for goods and services that are transferred is probable based on the customer’s intent and ability to pay the promised consideration. The Company applies judgment in determining the customer’s intent and ability to pay, which is based on a variety of factors including the customer’s historical payment experience, or in the case of a new customer, published credit and financial information pertaining to the customer. 2. Identify the performance obligations in the contract. Performance obligations promised in a contract are identified based on the goods and services that will be transferred to the customer that are both capable of being distinct, whereby the customer can benefit from the good or service either on its own or together with other available resources, and are distinct in the context of the contract, whereby the transfer of the good or service is separately identifiable from other promises in the contract. To the extent a contract includes multiple promised goods and services, the Company must apply judgment to determine whether promised goods and services are both capable of being distinct and distinct in the context of the contract. If these criteria are not met, the promised goods and services are accounted for as a combined performance obligation. 3. Determine the transaction price. The transaction price is determined based on the consideration to which the Company will be entitled in exchange for transferring goods and services to the customer. To the extent the transaction price includes variable consideration, the Company estimates the amount of variable consideration that should be included in the transaction price utilizing either the expected value method or the most likely amount method, depending on the nature of the variable consideration. Variable consideration is included in the transaction price if, in the Company’s judgment, it is probable that a significant future reversal of cumulative revenue under the contract will not occur. Any estimates, including the effect of the constraint on variable consideration, are evaluated at each reporting period for any changes. Determining the transaction price requires significant judgment. 4. Allocate the transaction price to performance obligations in the contract. If the contract contains a single performance obligation, the entire transaction price is allocated to the single performance obligation. However, if a series of distinct services that are substantially the same qualifies as a single performance obligation in a contract with variable consideration, the Company must determine if the variable consideration is attributable to the entire contract or to a specific part of the contract. Contracts that contain multiple performance obligations require an allocation of the transaction price to each performance obligation on a relative standalone selling price basis unless the transaction price is variable and meets the criteria to be allocated entirely to a performance obligation or to a distinct service that forms part of a single performance obligation. The consideration to be received is allocated among the separate performance obligations based on relative standalone selling prices. 5. Recognize revenue when or as the Company satisfies a performance obligation. The Company satisfies performance obligations either over time or at a point in time. Revenue is recognized over time if either (i) the customer simultaneously receives and consumes the benefits provided by the entity’s performance, (ii) the entity’s performance creates or enhances an asset that the customer controls as the asset is created or enhanced, or (iii) the entity’s performance does not create an asset with an alternative use to the entity and the entity has an enforceable right to payment for performance completed to date. If the entity does not satisfy a performance obligation over time, the related performance obligation is satisfied at a point in time by transferring the control of a promised good or service to a customer. Examples of control are using the asset to produce goods or services, enhance the value of other assets, or settle liabilities, and holding or selling the asset. Licenses of intellectual property : If the license to the Company’s intellectual property is determined to be distinct from the other performance obligations identified in the arrangement, the Company recognizes revenues from consideration allocated to the license when the license is transferred to the customer and the customer is able to use and benefit from the licenses. For licenses that are combined 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. The Company evaluates the measure of progress each reporting period and, if necessary, adjusts the measure of performance and related revenue recognition. Milestone payments: At the inception of each arrangement that includes development milestone payments, the Company evaluates the probability of reaching the milestones 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 in the future, the associated milestone value is included in the transaction price. Milestone payments that are not within the control of the Company or the licensee, 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 possible. 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 levels of sales, and 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). To date, the Company has not recognized any royalty revenue resulting from any of its collaboration agreements. As of September 30, 2018, the Company’s only revenue recognized is related to the Purdue Collaboration (see Note 3). Recently Adopted Accounting Pronouncements In May 2014, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) 2014-09 (ASC 606), Revenue from Contracts with Customers . This ASU, as amended by ASU 2015-14, affects any entity that either enters into contracts with customers to transfer goods and services or enters into contracts for the transfer of nonfinancial assets. ASU 2014-09 replaces most existing revenue recognition guidance in GAAP when it becomes effective. The standard’s core principle is that a company will recognize revenue when it transfers promised goods or services to customers in an amount that reflects the consideration to which the company expects to be entitled in exchange for those goods or services. In doing so, companies will need to use more judgment and make more estimates than under the currently effective guidance. These may include identifying performance obligations in the contract, estimating the amount of variable consideration to include in the transaction price and allocating the transaction price to each separate performance obligation. ASU 2014-09 is effective for Exicure in the first quarter of 2018 and early adoption is permitted beginning in the first quarter of 2017. The Company adopted ASC 606 on a modified retrospective basis. See above “Revenue Recognition” for a discussion of the Company’s updated policies related to revenue recognition effective January 1, 2018. Impact of adoption of ASC 606 The Company adopted ASC 606 using the modified retrospective method. The cumulative effect of applying the new guidance to all contracts with customers that were not completed as of January 1, 2018 was recorded as an adjustment to accumulated deficit as of the adoption date. As a result of applying the modified retrospective method to adopt the new guidance, the Company recorded reductions to both accumulated deficit and deferred revenue, current of $1,034 as of the date of adoption. As a result of the adoption of ASC 606: (i) there were no impacts to the totals of our cash flows from operating activities, cash flows from investing activities, or cash flows from financing activities in the accompanying unaudited condensed consolidated statement of cash flows for the nine months ended September 30, 2018; (ii) there were no impacts to the balances of the accompanying unaudited condensed consolidated balance sheet as of September 30, 2018, (iii) there were no impacts to total revenue, operating loss, or net loss in the accompanying unaudited condensed consolidated statement of operations for the three months ended September 30, 2018, and (iv) total revenue, operating loss, and net loss were lower by $1,034 each in the accompanying unaudited condensed consolidated statement of operations for the nine months ended September 30, 2018. In August 2016, the FASB issued ASU 2016-15, Statement of Cash Flows (Topic 230): Classification of Certain Cash Receipts and Cash Payments . ASU 2016-15 addresses the classification of certain specific cash flow issues including debt prepayment or extinguishment costs, settlement of certain debt instruments, contingent consideration payments made after a business combination, proceeds from the settlement of certain insurance claims and distributions received from equity method investees. ASU 2016-15 is effective for the Company in the first quarter of 2018 and early adoption is permitted. An entity that elects early adoption must adopt all of the amendments in the same period. The Company adopted this guidance on January 1, 2018. The adoption of ASU 2016-15 did not have a material impact to the Company’s statement of cash flows. In May 2017, the FASB issued ASU 2017-09, Compensation - Stock Compensation (Topic 718): Scope of Modification Accounting . ASU 2017-09 clarifies when changes to the terms or conditions of a share-based payment award must be accounted for as modifications. Under the new guidance, modification accounting is required only if the fair value, the vesting conditions, or the classification of the award changes as a result of the change in terms or conditions. ASU 2017-09 will be applied prospectively to awards modified on or after the adoption date. ASU 2017-09 is effective for the Company for fiscal years beginning after December 15, 2017, and interim periods within those fiscal years. Early adoption is permitted. The Company adopted this guidance on January 1, 2018. The adoption of ASU 2017-09 did not have a material impact to the Company’s financial statements. Recent Accounting Pronouncements Not Yet Adopted In February 2016, FASB issued ASU 2016-02, Leases (Topic 842) , which requires lessees to recognize right-of-use assets and lease liabilities on the balance sheet. ASU 2016-02 is to be applied using a modified retrospective approach at the beginning of the earliest comparative period in the financial statements. ASU 2016-02 will be effective for the Company beginning in the first quarter of 2019. Early adoption is permitted. The Company is currently evaluating the impact of adopting this standard on its financial statements. |