Summary of Significant Accounting Policies (Policies)

9 Months Ended

Sep. 30, 2018

The accompanying unaudited consolidated financial statements have been prepared pursuant to the rules and regulations of the Securities and Exchange Commission, or the SEC. Certain information and note disclosures normally included in annual financial statements prepared in accordance with U.S. generally accepted accounting principles, or U.S. GAAP, have been omitted. The accompanying unaudited consolidated financial statements include all known adjustments necessary for a fair presentation of the results of interim periods as required by U.S. GAAP. These adjustments consist primarily of normal recurring accruals and estimates that impact the carrying value of assets and liabilities. Operating results for the three and nine months ended September 30, 2018 are not necessarily indicative of the results that may be expected for the year ending December 31, 2018. The financial statements should be read in conjunction with our audited financial statements for the year ended December 31, 2017, included in our Annual Form 10-K, as amended on September 14, 2018.

Basis of Consolidation

The accompanying consolidated financial statements include us and our wholly-owned Australian subsidiary. All intercompany accounts and transactions have been eliminated in consolidation. We operate in one reportable segment and our functional and reporting currency is the U.S. dollar.

Use of Estimates

The preparation of the accompanying consolidated financial statements in conformity with U.S. GAAP requires management to make estimates and assumptions that affect the reported amounts of assets and liabilities, disclosure of contingent assets and liabilities at the date of the financial statements and reported amounts of revenues and expenses during the reporting periods. Actual results could differ from those estimates. We base our estimates and assumptions on historical experience when available and on various factors that we believe to be reasonable under the circumstances. We evaluate our estimates and assumptions on an ongoing basis. Our actual results could differ from these estimates under different assumptions or conditions.

Revenue Recognition

Revenue is recognized in accordance with revenue recognition accounting guidance, which utilizes five basic steps to determine whether revenue can be recognized and to what extent: (i) identify the contract with a customer; (ii) identify the performance obligation; (iii) determine the transaction price; (iv) allocate the transaction price; and (v) determine the recognition period.

Performance Obligations. We evaluate deliverables on a contract by contract basis to determine whether each deliverable represents a good or service that is distinct or has the same pattern of transfer as other deliverables. A deliverable is considered distinct if the customer can benefit from the good or service independently of other goods/services either in the contract or that can be obtained elsewhere, without regard to contract exclusivity, and the entity’s promise to transfer the good or service to the customer is separately identifiable from other promises in the contact. If the deliverable is not considered distinct, we combine such deliverables and account for them as a single performance obligation. We allocate the consideration to each deliverable at the inception of the arrangement based on the transaction price.

Our performance obligations may include the following:

•

License Arrangements. The performance obligations under our collaboration and license agreements generally include exclusive or nonexclusive licenses to one or more products generated using our technologies. Licenses for multiple antibodies within a single contract are generally combined as they have substantially the same pattern of transfer to the customer. Historically, our licenses have held no value to the customer, as the antibodies were in the discovery phase and required our expertise for further development. Accordingly, licenses are not considered distinct.

•

Research and Development Services. The performance obligations under our collaboration and license agreements generally include research and development services we perform on behalf of or with our collaborators. As discussed within license arrangements above, our licenses have historically held no value without the research and development services we provide. As we generally only provide research and development services for internally generated antibodies that require a license to be utilized by a third party, our research and development services are not considered distinct.


•	Steering Committee Meetings. The performance obligations under our collaboration and license agreements may also include our participation in a steering committees, which allows us to direct the progression of our discovery programs. As these steering committees would not occur or benefit the customer without the use of our licenses, these are not considered distinct.

We recognize consideration allocated to a performance obligation as the performance obligation is satisfied, and the determination as to whether consideration is recognized over time or at a point in time is made upon contract inception. For our collaboration agreements, this is generally over the period in which research and development services have been performed.

Transaction Price. Our collaboration and license agreements generally include both fixed and variable consideration. Fixed payments, such as those for upfront fees are included in the transaction price at contract value, while variable consideration such as reimbursement for research and development services, milestone and royalty payments are estimated and then evaluated for constraints upon inception of the contract and evaluated on a quarterly basis thereafter. Research and development services are updated for actual invoices. Given the nature of our agreements, milestones are estimated using the most likely amount and are evaluated on a quarterly basis. Upon commercialization, royalty payments are recognized in the period incurred.

Net Loss Per Common Share

Basic net loss per common share is computed by dividing net loss by the weighted-average number of common shares outstanding during the period. Diluted net loss per share is computed by dividing net loss by the weighted-average number of common equivalent shares outstanding for the period. Diluted net loss per share includes any dilutive effect from outstanding stock options and warrants using the treasury stock method. For each period presented, there is no difference in the number of shares used to calculate basic and diluted net loss per share.

Accounting Pronouncements Recently Adopted and Recent Accounting Pronouncements

Accounting Pronouncements Recently Adopted

In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers, which outlines a single comprehensive model for entities to use in accounting for revenue from contracts with customers and supersedes most current revenue recognition guidance, including industry-specific guidance. This standard is based on the principle that an entity should recognize revenue to depict the transfer of 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. This standard also requires additional disclosure about the nature, amount, timing and uncertainty of assets recognized from costs incurred to fulfill a contract and became effective for our annual reporting period beginning January 1, 2018, including interim periods within that reporting period. Entities have the option of using either a full retrospective or a modified retrospective approach for the adoption of the new standard. We assessed all potential impacts of the standard, and the most significant impacts relate to our accounting for variable consideration including revenues related to contingent “milestone” based payments and our disclosures required under the new standard as it relates to our two ongoing collaboration agreements, TESARO and Celgene. Application of the new standard requires that variable consideration be recognized to the extent that it is probable that a significant reversal in the amount of revenue will not occur when the uncertainty associated with the variable consideration is subsequently resolved. Accordingly, we may be required to recognize milestone payments earlier in the period in which we determine a significant reversal will not occur, rather than when the milestone is achieved. However, we have reviewed the TESARO and Celgene agreements and have determined that given the nature of potential milestones owed to us under these agreements, and the inherent risk involved in developing drugs, and have determined that these potential milestones were not recognizable as of the standard adoption date. Additionally, while we currently disaggregate our revenue disclosures by collaborative agreement, additional discussion surrounding significant estimates made by management was required in our disclosure and included in Note 4 below. We adopted this standard using the modified retrospective approach for our annual reporting period beginning January 1, 2018, and did not record any adjustments upon adoption of this standard.

In January 2016, the FASB issued ASU 2016-01, Financial Instruments—Overall (Subtopic 825-10): Recognition and Measurement of Financial Assets and Financial Liabilities, which intends to enhance the reporting model for financial instruments by providing users of financial instruments with more decision-useful information. The standard also addresses certain aspects of the recognition, measurement, presentation, and disclosure of financial instruments and requires additional disclosure about the nature, amount, timing and uncertainty of assets recognized from costs incurred to fulfill a contract and became effective for our annual reporting period beginning January 1, 2018, including interim periods within that reporting period; early adoption is permitted. We adopted this standard as of January 1, 2018 and there was no material impact on our consolidated financial statements. We did not record any adjustments upon adoption of this standard and have consistently applied our accounting policies to all periods presented in the consolidated financial statements.

In May 2017, the FASB issued ASU 2017-09, Compensation - Stock Compensation (Topic 718), which provides further guidance as to what constitutes a modification to the terms of shared based compensation, in order to create consistency in practice amongst all entities. ASU 2017-09 became effective for annual reporting periods beginning after December 15, 2017, including interim periods thereafter; early adoption is permitted, including adoption in an interim period. We adopted this standard as of January 1, 2018, and the impact was not material on our consolidated financial statements. We did not record any adjustments upon adoption of this standard.

Recent Accounting Pronouncements

In February 2016, the FASB issued ASU 2016-02, Leases (Topic 842), which requires that lessees recognize a right-of-use, or “ROU”, asset and a related lease liability on the balance sheet for all leases with a term longer than 12 months. Topic 842 was subsequently amended by ASU 2018-01, Land Easement Practical Expedient for Transition to Topic 842; ASU 2018-10, Codification Improvements to Topic 842, Leases; and ASU 2018-11, Targeted Improvements. ASU 2016-02 becomes effective for our annual reporting period beginning January 1, 2019, including interim periods thereafter; early adoption is permitted. A modified retrospective transition approach is required, applying the new standard to all leases existing at the date of initial application. An entity may choose to use either (i) its effective date or (ii) the beginning of the earliest comparative period presented in the financial statements as its date of initial application. We expect to adopt the new standard on January 1, 2019 and use the effective date as our date of initial application. The new standard provides a number of optional practical expedients in transition. We expect to elect the ‘package of practical expedients’, which permits us not to reassess under the new standard our prior conclusions about lease identification, lease classification and initial direct costs. While we continue to assess all of the effects of adoption, we expect the recognition of new ROU assets and lease liabilities on our balance sheet for current real estate leases as well as the enhanced disclosure requirements will not have a material effect on our financial statements.