Significant Accounting Policies	9 Months Ended
Mar. 31, 2014
Accounting Policies [Abstract]
Significant Accounting Policies	Accounting Policies Update 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 five-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. Revenue In addition to the disclosure under note 2 - Significant Accounting Policies, under "Revenue recognition" in the notes to Consolidated Financial Statements included in our Annual Report on Form 10-K for the year ended June 30, 2013, we have adopted the following revenue recognition and cost deferral policies in connection with revenues acquired through GXS: Managed services arrangements — 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 which, based on our current estimate, approximates the term of the related transaction processing arrangement. 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. 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 Condensed Consolidated Financial Statements.

Accounting Policies Update

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 five-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.

Revenue

In addition to the disclosure under note 2 - Significant Accounting Policies, under "Revenue recognition" in the notes to Consolidated Financial Statements included in our Annual Report on Form 10-K for the year ended June 30, 2013, we have adopted the following revenue recognition and cost deferral policies in connection with revenues acquired through GXS:

Managed services arrangements — 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 which, based on our current estimate, approximates the term of the related transaction processing arrangement. 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.

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 Condensed Consolidated Financial Statements.