XML 20 R8.htm IDEA: XBRL DOCUMENT v3.4.0.3
Recent Accounting Pronouncements
9 Months Ended
Apr. 30, 2016
Recent Accounting Pronouncements

2. Recent Accounting Pronouncements

Recently adopted

Classification of deferred taxes

In November 2015, the Financial Accounting Standards Board, or FASB, issued Accounting Standards Update, or ASU, No. 2015-17, “Income Taxes (Topic 740): Balance Sheet Classification of Deferred Taxes.” The standard requires that deferred tax assets and liabilities be classified as noncurrent on the balance sheet rather than being separated into current and noncurrent. ASU 2015-17 is effective for fiscal years, and interim periods within those years, beginning after December 15, 2016. Early adoption is permitted and the standard may be applied either retrospectively or on a prospective basis to all deferred tax assets and liabilities. We elected early adoption of ASU 2015-17 during our second quarter of fiscal year 2016 on a retrospective basis. Accordingly, we reclassified the current deferred taxes to noncurrent on our July 31, 2015 Consolidated Balance Sheets, which decreased refundable and deferred income taxes by $8.0 million, increased noncurrent deferred tax assets by $4.6 million and decreased noncurrent deferred tax liabilities by $3.4 million.

Consolidation

In February 2015, the FASB issued Accounting Standards Codification, or ASC, Update No. 2015-02, “Consolidation (Topic 810): Amendments to the Consolidation Analysis.” ASC Update No. 2015-02 amended the process that a reporting entity must perform to determine whether it should consolidate certain types of legal entities. ASC Update No. 2015-02 is effective for annual and interim periods beginning after December 15, 2015. Early adoption is permitted. The update would be effective for us beginning on August 1, 2016. We elected early adoption of ASU 2015-02 during our first quarter of fiscal year ending July 31, 2016. The adoption of this update did not have a material impact on our consolidated financial statements.

 

Not yet effective

Improvements to employee share-based payment accounting

In March 2016, the FASB issued Accounting Standards Update, or ASU, No. 2016-09, “Improvements to Employee Share-Based Payment Accounting,” which amends ASC 718, “Stock Based Compensation.” The amendments require that all excess tax benefits be recorded as an income tax benefit or expense in the income statement and be classified as an operating activity in the statement of cash flows. Entities may also elect to estimate the amount of forfeitures or recognize them as they occur. The amendments are effective for fiscal years, and interim periods within those years, beginning after December 15, 2016. The standard will be effective for us in the first quarter of our fiscal year ending July 31, 2018 and early adoption is permitted. We are currently evaluating the impact of the adoption of this update on our consolidated financial statements.

Leases

In February 2016, the FASB issued Accounting Standards Update, or ASU, No. 2016-02, “Leases (Topic 842)”. The standard requires lessees to recognize assets and liabilities for most leases on the balance sheet. For income statement purposes, the standard requires leases to be classified as either operating or finance. The standard is effective for annual and interim periods beginning after December 15, 2018. Early adoption is permitted. The standard will be effective for us in the first quarter of our fiscal year ending July 31, 2020. Adoption requires application of the new guidance for all periods presented. We are currently evaluating the impact of the adoption of this standard on our consolidated financial statements.

Cloud computing arrangements

In April 2015, the FASB issued ASU No. 2015-05, “Customer’s Accounting for Fees Paid in a Cloud Computing Arrangement,” which amends ASC 350, “Intangibles—Goodwill and Other.” The amendments provide guidance as to whether a cloud computing arrangement (e.g., software as a service, platform as a service, infrastructure as a service, and other similar hosting arrangements) includes a software license and, based on that determination, how to account for such arrangements. The amendments are effective for fiscal years, and interim periods within those years, beginning after December 15, 2015 and may be applied on either a prospective or retrospective basis. The provisions will be effective for us in the first quarter of our fiscal year ending July 31, 2017. Early adoption is not permitted. We do not expect the adoption of these provisions to have a material impact on our consolidated financial statements.

Disclosure of uncertainties about an entity’s ability to continue as a going concern

In August 2014, the FASB issued ASU No. 2014-15, “Presentation of Financial Statements — Going Concern (Subtopic 205-40) Disclosure of Uncertainties about an Entity’s Ability to Continue as a Going Concern”. The standard requires management to evaluate an entity’s ability to continue as a going concern within one year of the date of issuance of the entity’s financial statements. The amendments are effective for the annual period ending after December 15, 2016, and for annual periods and interim periods thereafter and should be applied on a prospective basis. Early adoption is permitted. The provisions will be effective for us in the first quarter of our fiscal year ending July 31, 2017. We do not expect the adoption of these provisions to have a material impact on our consolidated financial statements.

Revenue from contracts with customers

In May 2014, the FASB issued an update which provides guidance for revenue recognition. This update affects any entity that either enters into contracts with customers to transfer goods or services or enters into contracts for the transfer of nonfinancial assets. This update will supersede existing revenue recognition requirements and most industry-specific guidance. This update also supersedes some cost guidance, including revenue recognition guidance for construction-type and production-type contracts. The update’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 today’s 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. This update should be applied either on a retrospective or modified retrospective basis. This update will be effective for us in the first quarter of our fiscal year ending July 31, 2019. We are currently evaluating the impact of the adoption of this update on our consolidated financial statements.