Accounting Policies

Cash and cash equivalents

Cash and cash equivalents include investments that have terms to maturity of three months or less. Cash equivalents are recorded at cost and typically consist of term deposits, commercial paper, certificates of deposit and short-term interest bearing investment-grade securities of major banks in the countries in which we operate.

Allowance for doubtful accounts

We maintain an allowance for doubtful accounts for estimated losses resulting from the inability of customers to make payments. We evaluate the creditworthiness of our customers prior to order fulfillment and based on these evaluations, we adjust our credit limit to the respective customer. In addition to these evaluations, we conduct on-going credit evaluations of our customers' payment history and current creditworthiness. The allowance is maintained for 100% of all accounts deemed to be uncollectible and, for those receivables not specifically identified as uncollectible, an allowance is maintained for a specific percentage of those receivables based upon the aging of accounts, our historical collection experience and current economic expectations. To date, the actual losses have been within our expectations. No single customer accounted for more than 10% of the accounts receivable balance as of June 30, 2014 and 2013.

Property and equipment

Property and equipment are stated at the lower of cost or net realizable value, and shown net of depreciation which is computed on a straight-line basis over the estimated useful lives of the related assets. Gains and losses on asset disposals are taken into income in the year of disposition. Fully depreciated property and equipment are retired from the balance sheet when they are no longer in use. We did not recognize any significant property impairment charges in Fiscal 2014, Fiscal 2013, or Fiscal 2012. The following represents the estimated useful lives of property and equipment:



Furniture and fixtures	5 years
Office equipment	5 years
Computer hardware	3 years
Computer software	3 years
Capitalized software	5 years
Leasehold improvements	Lesser of the lease term or 5 years
Building	40 years

Capitalized Software

We capitalize software development costs in accordance with Financial Accounting Standards Board (FASB) Accounting Standards Codification (ASC) 350-40 – Accounting for the Costs of Computer Software Developed or Obtained for Internal-Use. We capitalize costs for software to be used internally when we enter the application development stage. This occurs when we complete the preliminary project stage, management authorizes and commits to funding the project, and it is feasible that the project will be completed and the software will perform the intended function. We cease to capitalize costs related to a software project when it enters the post implementation and operation stage. If different determinations are made with respect to the state of development of a software project, then the amount capitalized and the amount charged to expense for that project could differ materially.

Costs capitalized during the application development stage consist of payroll and related costs for employees who are directly associated with, and who devote time directly to, a project to develop software for internal use. We also capitalize the direct costs of materials and services, which generally includes outside contractors, and interest. We do not capitalize any general and administrative or overhead costs or costs incurred during the application development stage related to training or data conversion costs. Costs related to upgrades and enhancements to internal-use software, if those upgrades and enhancements result in additional functionality, are capitalized. If upgrades and enhancements do not result in additional functionality, those costs are expensed as incurred. If different determinations are made with respect to whether upgrades or enhancements to software projects would result in additional functionality, then the amount capitalized and the amount charged to expense for that project could differ materially.

We amortize capitalized costs with respect to development projects for internal-use software when the software is ready for use. The capitalized software development costs are generally amortized using the straight-line method over a 5-year period. In determining and reassessing the estimated useful life over which the cost incurred for the software should be amortized, we consider the effects of obsolescence, technology, competition and other economic factors. If different determinations are made with respect to the estimated useful life of the software, the amount of amortization charged in a particular period could differ materially.

Acquired intangibles

Acquired intangibles consist of acquired technology and customer relationships associated with various acquisitions.

Acquired technology is initially recorded at fair value based on the present value of the estimated net future income-producing capabilities of software products acquired on acquisitions. We amortize acquired technology over its estimated useful life on a straight-line basis.

Customer relationships represent relationships that we have with customers of the acquired companies and are either based upon contractual or legal rights or are considered separable; that is, capable of being separated from the acquired entity and being sold, transferred, licensed, rented or exchanged. These customer relationships are initially recorded at their fair value based on the present value of expected future cash flows. We amortize customer relationships on a straight-line basis over their estimated useful lives.

We continually evaluate the remaining estimated useful life of our intangible assets being amortized to determine whether events and circumstances warrant a revision to the remaining period of amortization.

Impairment of long-lived assets

We account for the impairment and disposition of long-lived assets in accordance with ASC Topic 360, “Property, Plant, and Equipment” (Topic 360). We test long-lived assets or asset groups, such as property and equipment and definite lived intangible assets, for recoverability when events or changes in circumstances indicate that their carrying amount may not be recoverable. Circumstances which could trigger a review include, but are not limited to: significant adverse changes in the business climate or legal factors; current period cash flow or operating losses combined with a history of losses or a forecast of continuing losses associated with the use of the asset; and a current expectation that the asset will more likely than not be sold or disposed of before the end of its estimated useful life.

Recoverability is assessed based on comparing the carrying amount of the asset to the aggregate pre-tax undiscounted cash flows expected to result from the use and eventual disposal of the asset or asset group. Impairment is recognized when the carrying amount is not recoverable and exceeds the fair value of the asset or asset group. The impairment loss, if any, is measured as the amount by which the carrying amount exceeds fair value, which for this purpose is based upon the discounted projected future cash flows of the asset or asset group.

We have not recorded any impairment charges for long-lived assets during Fiscal 2014, Fiscal 2013 and Fiscal 2012.

Goodwill

Goodwill represents the excess of the purchase price in a business combination over the fair value of net tangible and intangible assets acquired. The carrying amount of goodwill is periodically reviewed for impairment (at a minimum annually) and whenever events or changes in circumstances indicate that the carrying value of this asset may not be recoverable.

Our operations are analyzed by management and our chief operating decision maker (CODM) as being part of a single industry segment: the design, development, marketing and sales of Enterprise Information Management software and solutions. Therefore, our goodwill impairment assessment is based on the allocation of goodwill to a single reporting unit.

Effective Fiscal 2013, we opted to perform a qualitative assessment to test our reporting unit's goodwill for impairment. Based on our qualitative assessment, if we determine that the fair value of our reporting unit is more likely than not (i.e., a likelihood of more than 50 percent) to be less than its carrying amount, the two step impairment test will be performed. In the first step, we would compare the fair value of our reporting unit to its carrying value. If the fair value of the reporting unit exceeds its carrying value, goodwill is not considered impaired and we are not required to perform further testing. If the carrying value of the net assets of our reporting unit exceeds its fair value, then we must perform the second step of the impairment test in order to determine the implied fair value of our reporting unit's goodwill. If the carrying value of our reporting unit's goodwill exceeds its implied fair value, then we would record an impairment loss equal to the difference.

Our annual impairment analysis of goodwill was performed as of April 1, 2014. Our qualitative assessment indicated that there were no indications of impairment and the fair value of our reporting unit was in excess of its carrying value and therefore there was no impairment of goodwill required to be recorded for Fiscal 2014 (No impairments were recorded for Fiscal 2013 and Fiscal 2012).

Derivative financial instruments

We use derivative financial instruments to manage foreign currency rate risk. We account for these instruments in accordance with ASC Topic 815, “Derivatives and Hedging” (Topic 815), which requires that every derivative instrument be recorded on the balance sheet as either an asset or liability measured at its fair value as of the reporting date. Topic 815 also requires that changes in our derivative financial instruments' fair values be recognized in earnings; unless specific hedge accounting and documentation criteria are met (i.e. the instruments are accounted for as hedges). We recorded the effective portions of the gain or loss on derivative financial instruments that were designated as cash flow hedges in accumulated other comprehensive income in our accompanying Consolidated Balance Sheets. Any ineffective or excluded portion of a designated cash flow hedge, if applicable, was recognized in our Consolidated Statement of Income.

Asset retirement obligations

We account for asset retirement obligations in accordance with ASC Topic 410, “Asset Retirement and Environmental Obligations” (Topic 410), which applies to certain obligations associated with “leasehold improvements” within our leased office facilities. Topic 410 requires that a liability be initially recognized for the estimated fair value of the obligation when it is incurred. The associated asset retirement cost is capitalized as part of the carrying amount of the long-lived asset and depreciated over the remaining life of the underlying asset and the associated liability is accreted to the estimated fair value of the obligation at the settlement date through periodic accretion charges recorded within general and administrative expenses. When the obligation is settled, any difference between the final cost and the recorded amount is recognized as income or loss on settlement.

Business combinations

We apply the provisions of ASC Topic 805, “Business Combinations” (Topic 805), in the accounting for our acquisitions. It requires us to recognize separately from goodwill the assets acquired and the liabilities assumed at their acquisition date fair values. Goodwill as of the acquisition date is measured as the excess of consideration transferred over the net of the acquisition date fair values of the assets acquired and the liabilities assumed. While we use our best estimates and assumptions to accurately value assets acquired and liabilities assumed at the acquisition date as well as contingent consideration, where applicable, our estimates are inherently uncertain and subject to refinement. As a result, during the measurement period, which may be up to one year from the acquisition date, we may record adjustments to the assets acquired and liabilities assumed with the corresponding offset to goodwill. Upon the conclusion of the measurement period or final determination of the values of assets acquired or liabilities assumed, whichever comes first, any subsequent adjustments would be recorded to our consolidated statements of operations.

Costs to exit or restructure certain activities of an acquired company or our internal operations are accounted for as one-time termination and exit costs pursuant to ASC Topic 420, “Exit or Disposal Cost Obligations” (Topic 420) and are accounted for separately from the business combination.

For a given acquisition, we generally identify certain pre-acquisition contingencies as of the acquisition date and may extend our review and evaluation of these pre-acquisition contingencies throughout the measurement period in order to obtain sufficient information to assess whether we include these contingencies as a part of the purchase price allocation and, if so, to determine the estimated amounts.

If we determine that a pre-acquisition contingency (non-income tax related) is probable in nature and estimable as of the acquisition date, we record our best estimate for such a contingency as a part of the preliminary purchase price allocation. We often continue to gather information and evaluate our pre-acquisition contingencies throughout the measurement period and if we make changes to the amounts recorded or if we identify additional pre-acquisition contingencies during the measurement period, such amounts will be included in the purchase price allocation during the measurement period and, subsequently, in our results of operations.

Uncertain tax positions and tax related valuation allowances assumed in connection with a business combination are initially estimated as of the acquisition date. We review these items during the measurement period as we continue to actively seek and collect information relating to facts and circumstances that existed at the acquisition date. Changes to these uncertain tax positions and tax related valuation allowances made subsequent to the measurement period, or if they relate to facts and circumstances that did not exist at the acquisition date, are recorded in our provision for income taxes in our Consolidated Statement of Income.

Revenue recognition

License revenues

We recognize revenues in accordance with ASC Topic 985-605, “Software Revenue Recognition” (Topic 985-605).

We record product revenues from software licenses and products when persuasive evidence of an arrangement exists, the software product has been shipped, there are no significant uncertainties surrounding product acceptance by the customer, the fees are fixed and determinable, and collection is considered probable. We use the residual method to recognize revenues on delivered elements when a license agreement includes one or more elements to be delivered at a future date if evidence of the fair value of all undelivered elements exists. If an undelivered element for the arrangement exists under the license arrangement, revenues related to the undelivered element is deferred based on vendor-specific objective evidence (VSOE) of the fair value of the undelivered element.

Our multiple-element sales arrangements include arrangements where software licenses and the associated post contract customer support (PCS) are sold together. We have established VSOE of the fair value of the undelivered PCS element based on the contracted price for renewal PCS included in the original multiple element sales arrangement, as substantiated by contractual terms and our significant PCS renewal experience, from our existing worldwide base. Our multiple element sales arrangements generally include irrevocable rights for the customer to renew PCS after the bundled term ends. The customer is not subject to any economic or other penalty for failure to renew. Further, the renewal PCS options are for services comparable to the bundled PCS and cover similar terms.

It is our experience that customers generally exercise their renewal PCS option. In the renewal transaction, PCS is sold on a stand-alone basis to the licensees one year or more after the original multiple element sales arrangement. The exercised renewal PCS price is consistent with the renewal price in the original multiple element sales arrangement, although an adjustment to reflect consumer price changes is common.

If VSOE of fair value does not exist for all undelivered elements, all revenues are deferred until sufficient evidence exists or all elements have been delivered.

We assess whether payment terms are customary or extended in accordance with normal practice relative to the market in which the sale is occurring. Our sales arrangements generally include standard payment terms. These terms effectively relate to all customers, products, and arrangements regardless of customer type, product mix or arrangement size. Exceptions are only made to these standard terms for certain sales in parts of the world where local practice differs. In these jurisdictions, our customary payment terms are in line with local practice.

Cloud revenues

Cloud revenues consist of subscription revenues for our software as a service offering and managed service arrangements. The majority of the contracts for our software as a service offering and managed service arrangements are based on customers' usage over a period and the revenue associated with those contracts are recognized once the usage has been measured, the fee fixed and determinable and collection is probable.

In certain managed services arrangements, we sell transaction processing along with implementation and start-up services. The implementation and start-up services typically do not have stand-alone value and, therefore, they do not qualify as separate units of accounting and are not separated. We believe these services do not have stand-alone value as the customer generally only receives value from these services in conjunction with the use of the related transaction processing service, we do not generally sell such services separately, and the output of such services cannot be re-sold by the customer. Revenues related to implementation and start-up services are recognized over the estimated customer life. In some arrangements, we also sell professional services which do have stand-alone value and can be separated from other elements in the arrangement. The revenue related to these services is recognized as the service is performed.

We defer all direct and relevant costs associated with implementation of long-term customer contracts to the extent such costs can be recovered through guaranteed contract revenues.

Service revenues

Service revenues consist of revenues from consulting, implementation, training and integration services. These services are set forth separately in the contractual arrangements such that the total price of the customer arrangement is expected to vary as a result of the inclusion or exclusion of these services. For those contracts where the services are not essential to the functionality of any other element of the transaction, we determine VSOE of fair value for these services based upon normal pricing and discounting practices for these services when sold separately. These consulting and implementation services contracts are primarily time and materials based contracts that are, on average, less than six months in length. Revenues from these services are recognized at the time such services are performed.

We also enter into contracts that are primarily fixed fee arrangements wherein the services are not essential to the functionality of a software element. In such cases, the proportional performance method is applied to recognize revenues.

Revenues from training and integration services are recognized in the period in which these services are performed.

Customer support revenues

Customer support revenues consist of revenues derived from contracts to provide PCS to license holders. These revenues are recognized ratably over the term of the contract. Advance billings of PCS are not recorded to the extent that the term of the PCS has not commenced and payment has not been received.

Deferred revenues

Deferred revenues primarily relate to support agreements which have been paid for by customers prior to the performance of those services. Generally, the services will be provided in the twelve months after the signing of the agreement.

Long-term sales contracts

We entered into certain long-term sales contracts involving the sale of integrated solutions that include the modification and customization of software and the provision of services that are essential to the functionality of the other elements in this arrangement. As prescribed by ASC Topic 985-605, we recognize revenues from such arrangements in accordance with the contract accounting guidelines in ASC Topic 605-35, “Construction-Type and Production-Type Contracts” (Topic 605-35), after evaluating for separation of any non-Topic 605-35 elements in accordance with the provisions of ASC Topic 605-25, “Multiple-Element Arrangements” (Topic 605-25).

When circumstances exist that allow us to make reasonably dependable estimates of contract revenues, contract costs and the progress of the contract to completion, we account for sales under such long-term contracts using the percentage-of-completion (POC) method of accounting. Under the POC method, progress towards completion of the contract is measured based upon either input measures or output measures. We measure progress towards completion based upon an input measure and calculate this as the proportion of the actual hours incurred compared to the total estimated hours. For training and integration services rendered under such contracts, revenues are recognized as the services are rendered. We will review, on a quarterly basis, the total estimated remaining costs to completion for each of these contracts and apply the impact of any changes on the POC prospectively. If at any time we anticipate that the estimated remaining costs to completion will exceed the value of the contract, the resulting loss will be recognized immediately.

When circumstances exist that prevent us from making reasonably dependable estimates of contract revenues, we account for sales under such long-term contracts using the completed contract method.

Sales to resellers and channel partners

We execute certain sales contracts through resellers and distributors (collectively, resellers) and also large, well-capitalized partners such as SAP AG and Accenture Inc. (collectively, channel partners).

We recognize revenues relating to sales through resellers when all the recognition criteria have been met, in other words, persuasive evidence of an arrangement exists, delivery has occurred in the reporting period, the fee is fixed and determinable, and collectability is probable. In addition we assess the creditworthiness of each reseller and if the reseller is newly formed, undercapitalized or in financial difficulty any revenues expected to emanate from such resellers are deferred and recognized only when cash is received and all other revenue recognition criteria are met.

We recognize revenues relating to sales through channel partners in the reporting period in which we receive evidence, from the channel partner, of end user sales (collectively, the documentation) and all other revenue recognition criteria have been met. As a result, if the documentation is not received within a given reporting period we recognize the revenues in a period subsequent to the period in which the channel partner completes the sale to the end user.

Rights of return and other incentives

We do not generally offer rights of return or any other incentives such as concessions, product rotation, or price protection and, therefore, do not provide for or make estimates of rights of return and similar incentives.

Research and development costs

Research and development costs internally incurred in creating computer software to be sold, licensed or otherwise marketed are expensed as incurred unless they meet the criteria for deferral and amortization, as described in ASC Topic 985-20, “Costs of Software to be Sold, Leased, or Marketed” (Topic 985-20). In accordance with Topic 985-20, costs related to research, design and development of products are charged to expenses as incurred and capitalized between the dates that the product is considered to be technologically feasible and is considered to be ready for general release to customers. In our historical experience, the dates relating to the achievement of technological feasibility and general release of the product have substantially coincided. In addition, no significant costs are incurred subsequent to the establishment of technological feasibility. As a result, we do not capitalize any research and development costs relating to internally developed software to be sold, licensed or otherwise marketed.

Income taxes

We account for income taxes in accordance with ASC Topic 740, “Income Taxes” (Topic 740). Deferred tax assets and liabilities arise from temporary differences between the tax bases of assets and liabilities and their reported amounts in the Consolidated Financial Statements that will result in taxable or deductible amounts in future years. These temporary differences are measured using enacted tax rates. A valuation allowance is recorded to reduce deferred tax assets to the extent that we consider it is more likely than not that a deferred tax asset will not be realized. In determining the valuation allowance, we consider factors such as the reversal of deferred income tax liabilities, projected taxable income, and the character of income tax assets and tax planning strategies. A change to these factors could impact the estimated valuation allowance and income tax expense.

We account for our uncertain tax provisions by using a two-step approach to recognizing and measuring uncertain tax positions. The first step is to evaluate the tax position for recognition by determining if the weight of available evidence indicates it is more likely than not, based solely on the technical merits, that the position will be sustained on audit, including resolution of related appeals or litigation processes, if any. The second step is to measure the appropriate amount of the benefit to recognize. The amount of benefit to recognize is measured as the maximum amount which is more likely than not to be realized. The tax position is derecognized when it is no longer more likely than not that the position will be sustained on audit. On subsequent recognition and measurement the maximum amount which is more likely than not to be recognized at each reporting date will represent the Company's best estimate, given the information available at the reporting date, although the outcome of the tax position is not absolute or final. We recognize both accrued interest and penalties related to liabilities for income taxes within the "Provision for Income Taxes" line of our Consolidated Statements of Income (see note 14 for more details).

Fair value of financial instruments

Carrying amounts of certain financial instruments, including cash and cash equivalents, accounts receivable and accounts payable (trade and accrued liabilities) approximate their fair value due to the relatively short period of time between origination of the instruments and their expected realization.

The fair value of our total long-term debt approximates its carrying value.

We apply the provisions of ASC 820, “Fair Value Measurements and Disclosures”, to our derivative financial instruments that we are required to carry at fair value pursuant to other accounting standards (see note 15 for more details).

Foreign currency

Our Consolidated Financial Statements are presented in U.S. dollars. In general, the functional currency of our subsidiaries is the local currency. For each subsidiary, assets and liabilities denominated in foreign currencies are translated into U.S dollars at the exchange rates in effect at the balance sheet dates and revenues and expenses are translated at the average exchange rates prevailing during the month of the transaction. The effect of foreign currency translation adjustments not affecting net income are included in Shareholders' equity under the “Cumulative translation adjustment” account as a component of “Accumulated other comprehensive income”. Transactional foreign currency gains (losses) included in the Consolidated Statements of Income under the line item “Other income (expense) net” for Fiscal 2014, Fiscal 2013 and Fiscal 2012 were $4.0 million, $(2.6) million and $3.6 million, respectively.

Restructuring charges

We record restructuring charges relating to contractual lease obligations and other exit costs in accordance with ASC Topic 420, “Exit or Disposal Cost Obligations” (Topic 420). Topic 420 requires that a liability for a cost associated with an exit or disposal activity be recognized and measured initially at its fair value in the period in which the liability is incurred. In order to incur a liability pursuant to Topic 420, our management must have established and approved a plan of restructuring in sufficient detail. A liability for a cost associated with involuntary termination benefits is recorded when benefits have been communicated and a liability for a cost to terminate an operating lease or other contract is incurred, when the contract has been terminated in accordance with the contract terms or we have ceased using the right conveyed by the contract, such as vacating a leased facility.

The recognition of restructuring charges requires us to make certain judgments regarding the nature, timing and amount associated with the planned restructuring activities, including estimating sub-lease income and the net recoverable amount of equipment to be disposed of. At the end of each reporting period, we evaluate the appropriateness of the remaining accrued balances (see note 17 for more details).

Litigation

We are currently involved in various claims and legal proceedings. Quarterly, we review the status of each significant legal matter and evaluate such matters to determine how they should be treated for accounting and disclosure purposes in accordance with the requirements of ASC Topic 450-20 "Loss Contingencies" (Topic 450-20). Specifically, this evaluation process includes the centralized tracking and itemization of the status of all our disputes and litigation items, discussing the nature of any litigation and claim, including any dispute or claim that is reasonably likely to result in litigation, with relevant internal and external counsel, and assessing the progress of each matter in light of its merits and our experience with similar proceedings under similar circumstances.

If the potential loss from any claim or legal proceeding is considered probable and the amount can be reasonably estimated, we accrue a liability for the estimated loss in accordance with Topic 450-20. As of the date of this filing on Form 10-K for the year ended June 30, 2014, we do not believe that the outcomes of any of these matters, individually or in the aggregate, will result in losses that are materially in excess of amounts already recognized (see note 13 for more details).

Net income per share

Basic net income per share is computed using the weighted average number of Common Shares outstanding including contingently issuable shares where the contingency has been resolved. Diluted net income per share is computed using the weighted average number of Common Shares and stock equivalents outstanding using the treasury stock method during the year (see note 22 for more details).

Share-based payment

We measure share-based compensation costs, in accordance with ASC Topic 718, “Compensation - Stock Compensation” (Topic 718) on the grant date, based on the calculated fair value of the award. We have elected to treat awards with graded vesting as a single award when estimating fair value. Compensation cost is recognized on a straight-line basis over the employee requisite service period, which in our circumstances is the stated vesting period of the award, provided that total compensation cost recognized at least equals the pro rata value of the award that has vested. Compensation cost is initially based on the estimated number of options for which the requisite service is expected to be rendered. This estimate is adjusted in the period once actual forfeitures are known (see note 12 for more details).

Accounting for Pensions, post-retirement and post-employment benefits

Pension expense is accounted for in accordance with ASC Topic 715, “Compensation-Retirement Benefits” (Topic 715). Pension expense consists of: actuarially computed costs of pension benefits in respect of the current year of service, imputed returns on plan assets (for funded plans) and imputed interest on pension obligations. The expected costs of post retirement benefits, other than pensions, are accrued in the Consolidated Financial Statements based upon actuarial methods and assumptions. The over-funded or under-funded status of defined benefit pension and other post retirement plans are recognized as an asset or a liability (with the offset to “Accumulated Other Comprehensive Income” within “Shareholders' equity”), respectively, on the Consolidated Balance Sheet (see note 11 for more details).

Recent Accounting Pronouncements

Presentation of Unrecognized Tax Benefits

On July 18, 2013, the FASB issued Accounting Standards Update No. 2013-11, Income Taxes (Topic 740): Presentation of an Unrecognized Tax Benefit When a Net Operating Loss Carryforward, a Similar Tax Loss, or a Tax Credit Carryforward Exists (ASU 2013-11). ASU 2013-11 requires an entity to present an unrecognized tax benefit, or a portion of an unrecognized tax benefit, as a reduction of a deferred tax asset for a net operating loss carryforward, a similar tax loss, or a tax credit carryforward except as follows: to the extent a net operating loss carryforward, a similar tax loss or a tax credit carryforward is not available at the reporting date under the tax law of the applicable jurisdiction to settle any additional income taxes that would result from the disallowance of a tax position or the tax law of the applicable tax jurisdiction does not require the entity to use, and the entity does not intend to use, the deferred tax asset for such purpose, the unrecognized tax benefit should be presented in the financial statements as a liability and should not be combined with a deferred tax asset. We adopted ASU 2013-11 in the second quarter of Fiscal 2014 and the adoption thereof did not have a material impact on our Consolidated Financial Statements.

Revenue Recognition

In May 2014, the FASB issued Accounting Standards Update No. 2014-09, “Revenue from Contracts with Customers: Topic 606” (ASU 2014-09). This update supersedes 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 ASU 2014-09 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 includes i) identifying contract(s) with customers, ii) identifying performance obligations in the contract, 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. ASU 2014-09 is effective for us in the first quarter of our fiscal year ending June 30, 2018. Early adoption is not permitted. When applying ASU 2014-09 we can either apply the amendments: 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 impact of the pending adoption of ASU 2014-09 on our Consolidated Financial Statements.