From time to time, new accounting pronouncements are issued by the FASB, or other standard setting bodies, that the Company adopts as of the specified effective date.

In May 2014, the FASB issued Accounting Standards Update ("ASU") No. 2014-09, "Revenue from Contracts with Customers (Topic 606)" (“ASU 2014-09”). In subsequent ASU’s, the FASB issued ASU 2015-14 “Revenue from Contracts with Customers: Topic 606”, ASU 2016-08 "Principal versus Agent Considerations (Reporting Revenue Gross Versus Net), ASU 2016-10 "Identifying Performance Obligations and Licensing", ASU 2016-12 "Revenue from Contracts with Customers - Narrow Scope Improvements and Practical Expedients", and ASU 2016-20 “Technical Corrections and Improvements to Topic 606, Revenue from Contracts with Customers” (collectively “Topic 606”) to amend and clarify ASU 2014-09. This new set of standards will supersede nearly all existing revenue recognition guidance in GAAP. The core principle of Topic 606 is that an entity should recognize revenue for the transfer of goods or services equal to the amount it expects to receive for those goods and services. The standard defines a five step process to achieve this core principle and, in doing so, it is possible more judgment and estimates may be required within the revenue recognition process than are required under existing GAAP, including 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. The standard allows entities to apply either of two adoption methods: (a) retrospective application to each prior reporting period presented with the option to elect certain practical expedients as defined within Topic 606 (“Retrospective Transition;” or (b) retrospective application with the cumulative effect of initially applying the standard recognized at the date of initial application and providing certain additional disclosures as defined per Topic 606. The effective date for Topic 606 is for annual reporting periods beginning after December 15, 2017, including interim reporting periods within that reporting period.

We will adopt the requirements of Topic 606 effective January 1, 2018, most likely using the Retrospective Transition method, whereby Topic 606 will be applied to the prior year as presented with the use of certain applicable practical expedients, and any effects on periods preceding the periods reported will appear as an adjustment to retained earnings as of the beginning of the earliest period reported. As the ASU supersedes substantially all existing revenue guidance affecting us under current GAAP, it will impact revenue and cost recognition across the whole of our business, as well as our business processes and our information technology systems.

We began our evaluation of the impact of Topic 606 in early 2017 by evaluating its impact on selected contracts of each type under which we operate. With this baseline understanding, we developed a project plan to evaluate the remainder of our contracts, develop processes and tools to dual-report financial results under both current GAAP and Topic 606, and assess the internal control structure in order to adopt Topic 606 on January 1, 2018. We have briefed our Audit Committee on our progress made towards adoption. Based on our progress to date, we anticipate being able to estimate the impacts of adopting Topic 606 on our operating results in the third quarter of 2017.

We currently operate under time-and-materials, fixed-price, fixed-price-per-unit, and fixed-term third-party software license and/or third-party software maintenance contracts. Some of these contracts involve more than one type of deliverable, which adds complexity to the application of Topic 606.

Under Topic 606, revenue will be recognized as the customer obtains control of the goods and services promised in the contract (i.e., performance obligations). Given the nature of our professional services and the terms and conditions in our contracts, the customer generally obtains control as we perform work under the contract. Therefore, we expect to recognize revenue over time for substantially all of our professional services contracts, while we expect to recognize revenue over time, at a point in time, or some of each for our software sales contracts, based on what was sold and whether we have any continuing performance obligations, such as the obligation to provide first-line support under a maintenance contract supporting third-party software.

Under Topic 606, guidance related to principal versus agent considerations rely heavily on control of an asset before delivery over some of the considerations used under previous guidance, including the negotiation of selling price and credit risk of the seller. This will likely lead to the reclassification of a percentage of our software sales transactions to be reported on a net sales basis, rather than on a gross sales basis, as Topic 606 guidance shifts our responsibility from a principal seller to an agent. This reclassification will not affect the Company’s net operating results.

In February 2016, the FASB issued ASU 2016-02, “Leases: Topic 842,” which provided updated guidance on lease accounting. ASU 2016-02 is effective for annual reporting periods beginning after December 15, 2018, including interim periods within that annual period, with early adoption permitted. The Company does not expect the adoption of this new standard will have a material impact on its financial statements. When adopted, the Company’s operating lease for office space will be presented as a right-of-use asset and as an offsetting liability for the present value of the contractual cash flows. The Company does not currently have any other lease obligations.

In August 2016, the FASB issued ASU 2016-15, “Classification of Certain Cash Receipts and Cash Payments,” to provide additional guidance and reduce diversity in practice in how certain cash receipts and cash payments are presented and classified in the statement of cash flows. This guidance is effective for fiscal years beginning after December 15, 2017 and early adoption is permitted, including adoption in an interim period. The Company does not expect the adoption of this guidance will have a material impact on its financial statements.