RECENT ACCOUNTING PRONOUNCEMENTS

Improving the Presentation of Net Periodic Pension Cost and Net Periodic Postretirement Benefit Cost

In March 2017, the Financial Accounting Standards Board (FASB) issued Accounting Standards Update (ASU) No. 2017-07, “Compensation-Retirement Benefits (Topic 715) - Improving the Presentation of Net Periodic Pension Cost and Net Periodic Postretirement Benefit Cost” (ASU 2017-07). This ASU requires entities to disaggregate the service cost component from the other components of net periodic benefit costs and present the service cost component in the same line item as where other current compensation costs for related employees are recorded in the income statement. ASU 2017-07 also requires that the other components of net periodic benefit costs be presented elsewhere in the income statement and outside of income from operations, if that subtotal is presented. Currently we record our net periodic pension costs, including service cost, as a component of compensation expense all within income from operations. ASU 2017-07 is effective for us in our first quarter of our fiscal year ending June 30, 2019, on a retroactive basis, with early adoption permitted. We are currently evaluating the impact of ASU 2017-07 on our Condensed Consolidated Financial Statements.

Definition of a Business

In January 2017, the FASB issued ASU No. 2017-01, "Business Combinations (Topic 805): Clarifying the definition of a Business" (ASU 2017-01) which amends the current definition of a business. Under ASU 2017-01, to be considered a business, an acquisition would have to include an input and a substantive process that together significantly contributes to the ability to create outputs. ASU 2017-01 further states that when substantially all of the fair value of gross assets acquired is concentrated in a single asset (or a group of similar assets), the assets acquired would not represent a business. The new guidance also narrows the definition of the term “outputs” to be consistent with how it is described in Topic 606, Revenue from Contracts with Customers. The changes to the definition of a business will likely result in more acquisitions being accounted for as asset acquisitions. ASU 2017-01 is effective for us for acquisitions commencing on or after the first quarter of our fiscal year ending June 30, 2019, with early adoption permitted. Adoption of this guidance will be applied prospectively on or after the effective date. We have not early adopted ASU 2017-01 as yet.

Share-based Compensation

In March 2016, the FASB issued ASU No. 2016-09, "Compensation-Stock Compensation (Topic 718)." This standard makes several modifications to Topic 718 related to the accounting for forfeitures, employer tax withholding on share-based compensation and the financial statement presentation of excess tax benefits or deficiencies. ASU 2016-09 also clarifies the presentation within the statement of cash flows for certain components of share-based awards. The standard is effective for us during the first quarter of our fiscal year ending June 30, 2018, with early adoption permitted. While we are still evaluating the impact of ASU 2016-09, we currently believe the most significant impact of this ASU on our consolidated financial statements relate to the treatment of excess tax deficiencies or benefits as a component of income tax expense or (recovery). Under current U.S. GAAP, such amounts are recorded either as an offset to accumulated excess tax benefits or recognized in additional paid in capital. Under the ASU these amounts will directly impact our provision for income taxes. Although historically, over the past three fiscal years, our excess tax benefits on share-based compensation has not been material and we don’t anticipate that our provision for income taxes will be materially impacted by the pending adoption of ASU 2016-09, we note that the amount of excess tax benefits or deficiencies recorded are in part based on the movement of our share price over time as well as on the timing of when employees exercise their share-based compensation awards, both of which are out of the Company’s control and vary from period to period.

Investments-Equity Method and Joint Ventures

In March 2016, the FASB issued ASU No. 2016-07, "Investments - Equity Method and Joint Ventures (Topic 323): Simplifying the Transition to Equity Method of Accounting" (ASU 2016-07). The amendments in this update require that the equity method investor add the cost of acquiring any additional interest in an investee to the current basis of the investor's previously held interest and adopt the equity method of accounting as of the date the investment becomes qualified for equity method accounting. Upon qualifying for equity method accounting, no retroactive adjustment of the investment is required. We adopted ASU 2016-07 in the first quarter of our Fiscal 2017. The adoption did not have a material impact on our reported financial position or results of operations and cash flows.

Leases

In February 2016, the FASB issued ASU 2016-02 “Leases (Topic 842)” (ASU 2016-02), which supersedes the guidance in former Accounting Standards Codification (ASC) Topic 840 “Leases”. The most significant change will result in the recognition of lease assets for the right to use the underlying asset and lease liabilities for the obligation to make lease payments by lessees, for those leases classified as operating leases under current guidance. The new guidance will also require significant additional disclosures about the amount, timing and uncertainty of cash flows related to leases. This standard is effective for us for our fiscal year ending June 30, 2020, with early adoption permitted. Upon adoption of ASU 2016-02, entities are required to recognize and measure leases at the beginning of the earliest period presented using a modified retrospective approach. We have formed a sub-committee consisting of internal members from various departments to assess the effect that the pending adoption of ASU 2016-02 will have on our Condensed Consolidated Balance Sheets. Although the sub-committee has not completed their assessment, we expect that the vast majority of the impact is expected to come from our facility leases, and we are currently analyzing the effects of adopting the standard and whether or not the effects will be material. We are also currently evaluating to what extent we want to make use of the practical expedients included in the standard. The financial statement impact of the new standard will depend on the lease agreements in effect at the time of adoption. It is expected that most of our operating lease commitments will be recognized as right of use assets and operating lease liabilities, which will increase our total assets and total liabilities, as reported on our Consolidated Balance Sheet, relative to such amounts prior to adoption. Based on the limited assessment of the impact of Topic 842 performed to date, we currently do not know and are not able to reasonably estimate the impact on our consolidated financial statements.

Revenue Recognition

In May 2014, the FASB issued ASU No. 2014-09, “Revenue from Contracts with Customers (Topic 606)” and issued subsequent amendments to the initial guidance in August 2015, March 2016, April 2016 and May 2016 within ASU 2015-04, ASU 2016-08, ASU 2016-10 and ASU 2016-12, respectively, (collectively referred to as Topic 606). These updates supersede the revenue recognition requirements in ASC Topic 605, "Revenue Recognition" and nearly all other existing revenue recognition guidance under U.S. GAAP. The core principal of Topic 606 is to recognize revenues when promised goods or services are transferred to customers in an amount that reflects the consideration that is expected to be received for those goods or services. ASU 2014-09 identifies five steps to be followed to achieve this core principal, which include (i) identifying contract(s) with customers, (ii) identifying performance obligations in the contract(s), (iii) determining the transaction price, (iv) allocating the transaction price to the performance obligations in the contract(s) and (v) recognizing revenue when (or as) the entity satisfies a performance obligation. The new guidance will be effective for us in the first quarter of our fiscal year ending June 30, 2019. Topic 606 can be applied either: (i) retrospectively to each prior reporting period presented with the option to elect certain practical expedients as defined within ASU 2014-09 or (ii) retrospectively with the cumulative effect of initially applying ASU 2014-09 recognized at the date of initial application and providing certain additional disclosures as defined within ASU 2014-09. We are currently evaluating the effect that the pending adoption of Topic 606 will have on our Condensed Consolidated Financial Statements and related disclosures. Further, we have not yet selected a transition method. Currently, we are still assessing the following:


•	the volume of contracts that will be affected by the different policy changes stemming from Topic 606 upon adoption; and


•	the potential changes in business practices that may result from the adoption of the new policies stemming from Topic 606 upon adoption.

To date, we have established a project team with the primary objective of evaluating the effect that the updated standard will have on our consolidated financial statements and related disclosures, and recommending the transition method to adopt. We are utilizing a bottoms-up approach to analyzing the impact of the new standard on our contracts by reviewing the current accounting policies and practices to identify potential differences that would result from applying the requirements of the new standard to our revenue contracts. In parallel, we are assessing the changes to our business processes, systems and controls in order to support the recognition and disclosure under the new standard. While we are continuing to assess all potential impacts of the new revenue recognition standard, we currently believe the most significant impacts will relate to our accounting for implementation services on cloud arrangements, and accounting for on premise subscription offerings. We expect to start quantifying any impact of the new standard in the near term.

Under current U.S. GAAP, fees charged for professional services to implement hosted software within a cloud arrangement are deferred and amortized over the estimated customer life because the activities are not deemed to be a separate element for which stand-alone value exists. The requirements for the identification of distinct performance obligations within a contract have changed under the new revenue recognition standard. Under this new standard we will be required to recognize certain implementation services that meet the criteria of being distinct as a separate performance obligation from the on-going cloud arrangement with corresponding revenues recognized as the services are provided to the customer. Costs relating to these implementation services will be expensed as they are incurred.

Under current U.S. GAAP, revenue attributable to subscription services related to on premise offerings is recognized ratably over the term of the arrangement because vendor-specific objective evidence (VSOE) does not exist for the undelivered maintenance and support element as it is not sold separately. The requirement to have VSOE for undelivered elements to enable the separation of the delivered software licenses is eliminated under the new revenue recognition standard. Accordingly, under this new standard we will be required to recognize as revenue a portion of the arrangement fee upon delivery of the initial software at the outset of the arrangement. This difference will result in allocating a transaction price to the software component of a subscription offering and thus an earlier recognition of that transaction price.

There have been no other significant changes in our reported financial position or results of operations and cash flows as a result of our adoption of new accounting pronouncements or changes to our significant accounting policies that were disclosed in our Annual Report on Form 10-K for the fiscal year ended June 30, 2016.