XML 50 R34.htm IDEA: XBRL DOCUMENT

Accounting Policies and Recent Accounting Pronouncements (Policies)

12 Months Ended

Jun. 30, 2019

The preparation of financial statements in conformity with U.S. GAAP requires us to make certain estimates, judgments and assumptions that affect the amounts reported in the Consolidated Financial Statements. These estimates, judgments and assumptions are evaluated on an ongoing basis. We base our estimates on historical experience and on various other assumptions that we believe are reasonable at that time, the results of which form the basis for making judgments about the carrying values of assets and liabilities that are not readily apparent from other sources. Actual results may differ from those estimates. In particular, key estimates, judgments and assumptions include those related to: (i) revenue recognition, (ii) accounting for income taxes, (iii) testing of goodwill for impairment, (iv) the valuation of acquired intangible assets, (v) the valuation of long-lived assets, (vi) the recognition of contingencies, (vii) restructuring accruals, (viii) acquisition accruals and pre-acquisition contingencies, (ix) the realization of investment tax credits, (x) the valuation of stock options granted and obligations related to share-based payments, including the valuation of our long-term incentive plans, and (xi) the valuation of pension obligations.

Accounting Pronouncements

Revenue Recognition

Effective July 1, 2018, we adopted Accounting Standards Codification (ASC) Topic 606 "Revenue from Contracts with Customers" (Topic 606) using the cumulative effect approach. We applied the accounting standard to contracts that were not completed as of the date of the initial adoption. Results for reporting periods commencing on July 1, 2018 are presented under the new revenue standard, while prior period results continue to be reported under the previous revenue standard. As a result of this adoption, we recorded a net increase of approximately $30 million to retained earnings as of July 1, 2018 on the Consolidated Balance Sheets, with the following corresponding impacts:


•	A decrease to deferred revenues of approximately $31 million;


•	A decrease to other assets of approximately $22 million in connection with deferred implementation costs;


•	An increase to other assets of approximately $14 million in connection with the capitalization of sales commission costs;


•	An increase in contract assets of approximately $18 million representing future billings in excess of revenues; and


•	An increase in net deferred tax liabilities of approximately $11 million.

Please refer to Note 3 "Revenues" for additional information relating to Topic 606, including our updated revenue recognition policies.

Additionally, certain prior period balances have been reclassified within other assets on the Consolidated Balance Sheets, to conform to the current period presentation as a result of this adoption. Please refer to Note 8 "Other Assets" for details.

Income Taxes

Effective July 1, 2018, we adopted Accounting Standards Update (ASU) No. 2016-16, "Income Taxes (Topic 740): Intra-Entity Transfers of Assets Other Than Inventory" (ASU 2016-16) which requires entities to recognize the income tax consequence of an intra-entity transfer of an asset, other than inventory, when the transfer occurs. We adopted ASU 2016-16 on a modified retrospective basis through a cumulative-effect adjustment to opening retained earnings. Results for reporting periods effective as of July 1, 2018 are presented under the new standard, while prior period results continue to be reported under the previous standard. As a result of this adoption, we recorded a net decrease of approximately $27 million to retained earnings as of July 1, 2018 on the Consolidated Balance Sheets, with the following corresponding impacts:


•	A decrease to deferred charges of approximately $38 million;


•	An increase to deferred tax assets of approximately $8 million; and


•	A decrease to deferred credits of approximately $3 million.

There was no impact to the Consolidated Statements of Income, Consolidated Statements of Comprehensive Income or Consolidated Statements of Cash Flows as a result of this adoption.

Restricted Cash

Effective July 1, 2018, we adopted ASU No. 2016-18, “Statement of Cash Flows (Topic 230): Restricted Cash” (ASU 2016-18), which requires amounts described as restricted cash and cash equivalents to be included with cash and cash equivalents when reconciling the beginning-of-period and end-of-period total amounts in the statement of cash flows. We adopted ASU 2016-18 using the retrospective method. As a result, certain prior period comparative figures in the Consolidated Statements of Cash Flows have been adjusted to conform to current period presentation as follows:



	Year Ended June 30, 2018							Year Ended June 30, 2017
	As Previously Reported		Adjustments			As Adjusted		As Previously Reported			Adjustments		As Adjusted

Net cash provided by operating activities	$	709,885	$	(1,804	)	$	708,081	$	439,253		$	1,100	$	440,353

Cash, cash equivalents and restricted cash at beginning of period	443,357		2,853			446,210		1,283,757			1,753		1,285,510
Increase (decrease) in cash, cash equivalents and restricted cash during the period	239,585		(1,804		)	237,781		(840,400		)	1,100		(839,300		)
Cash, cash equivalents and restricted cash at end of period	$	682,942	$	1,049		$	683,991	$	443,357		$	2,853	$	446,210

There was no impact to the Consolidated Balance Sheets, Consolidated Statements of Income, Consolidated Statements of Shareholders' Equity or Consolidated Statements of Comprehensive Income as a result of this adoption.

Pension Expense

Effective July 1, 2018, we adopted ASU No. 2017-07, “Retirement Benefits - Presentation of Net Period Pension Costs (Topic 715)” (ASU 2017-07), which provides guidance on the capitalization, presentation and disclosure of net benefit costs related to postretirement benefit plans. Upon adoption, only service-related net periodic pension costs will be recorded within operating expense. All other non-service related net periodic pension costs will be classified under "Interest and other related expense" on our Condensed Consolidated Statements of Income. We adopted ASU 2017-07 on a retrospective basis. As a result, certain prior period comparative figures in the Consolidated Statements of Income have been adjusted to conform to current period presentation as follows:



	Year Ended June 30, 2018									Year Ended June 30, 2017
	As Previously Reported			Adjustments			As Adjusted			As Previously Reported			Adjustments			As Adjusted
Cost of revenues - Cloud services	$	364,091		$	69		$	364,160		$	300,255		$	(405	)	$	299,850
Cost of revenues - Customer Support	$	134,089		$	(200	)	$	133,889		$	122,753		$	(188	)	$	122,565
Cost of revenues - Professional service and other	$	253,670		$	(281	)	$	253,389		$	195,195		$	(241	)	$	194,954
Total cost of revenues	$	951,411		$	(412	)	$	950,999		$	762,391		$	(834	)	$	761,557
Gross profit	$	1,863,830		$	412		$	1,864,242		$	1,528,666		$	834		$	1,529,500
Research and Development	$	323,461		$	(552	)	$	322,909		$	281,680		$	(465	)	$	281,215
Sales and Marketing	$	529,381		$	(240	)	$	529,141		$	444,838		$	(384	)	$	444,454
General and administrative	$	205,313		$	(86	)	$	205,227		$	170,438		$	(85	)	$	170,353
Total operating expense	$	1,358,427		$	(878	)	$	1,357,549		$	1,175,734		$	(934	)	$	1,174,800
Income from operations	$	505,403		$	1,290		$	506,693		$	352,932		$	1,768		$	354,700
Interest and other related expense, net	$	(137,250	)	$	(1,290	)	$	(138,540	)	$	(119,124	)	$	(1,768	)	$	(120,892	)

There was no change to net income or net earnings per share in any of the periods presented as a result of this adoption. Additionally, there was no impact to the Consolidated Balance Sheets, Consolidated Statements of Comprehensive Income, Consolidated Statements of Shareholders' Equity or Consolidated Statements of Cash Flows as a result of this adoption.

During Fiscal 2019, we adopted the following ASU's, in addition to those discussed in note 1 "Basis of Presentation". These ASU's did not have a material impact to our reported financial position, results of operations or cash flows:


•	ASU 2016-15 "Statement of Cash Flows (Topic 230) - Classification of Certain Cash Receipts and Cash Payments". When classifying distributions received from equity method investees, the Company uses the cumulative earnings approach.


•	ASU 2017-01 "Business Combinations (Topic 805): Clarifying the Definition of a Business"


•	ASU 2018-05 "Income Taxes (Topic 740): Amendments to SEC Paragraphs Pursuant to SEC Staff Accounting Bulletin No. 118"

Accounting Pronouncements Not Yet Adopted

Retirement Benefits

In August 2018, the Financial Accounting Standards Board (FASB) issued ASU No. 2018-14 “Compensation-Retirement Benefits-Defined Benefit Plans - General (Topic 715-20): Disclosure Framework - Changes to the Disclosure Requirements for Defined Benefit Plans” (ASU 2018-14), which modifies the disclosure requirements for defined benefit pension plans and other post retirement plans. ASU 2018-14 is effective for us in the first quarter of our fiscal year ending June 30, 2021. We are currently evaluating the impact of our pending adoption of ASU 2018-14 on our consolidated financial statements.

Implementation Costs in a Cloud Computing Arrangement

In August 2018, the FASB issued ASU No. 2018-15 “Intangibles-Goodwill and Other-Internal-Use Software (Subtopic 350-40): Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement that is a Service Contract” (ASU 2018-15). ASU 2018-15 clarifies the accounting treatment for implementation costs incurred as a customer in cloud computing arrangements. We will adopt ASU 2018-15 in the first quarter of our fiscal year ending June 30, 2020. We do not expect the adoption of ASU 2018-15 will have a material impact to our consolidated financial statements.

Financial Instruments

In June 2016, the FASB issued ASU No. 2016-13 “Financial Instruments - Credit Losses (Topic 326)” and also issued subsequent amendments to the initial guidance under ASU 2018-19, ASU 2019-04 and ASU 2019-05 (collectively Topic 326). Topic 326 requires the measurement and recognition of expected credit losses for financial assets held at amortized cost. This replaces the existing incurred loss model with an expected loss model and requires the use of forward looking information to calculate credit loss estimates. Topic 326 is effective for us in our first quarter of our fiscal year ending June 30, 2021 with earlier adoption permitted beginning in the first quarter of our fiscal year ending June 30, 2020. Topic 326 must be adopted by applying a cumulative effect adjustment to retained earnings. We are currently evaluating Topic 326, including its potential impact to our process and controls. We believe the effect on our consolidated financial statements will largely depend on the composition and credit quality of our financial assets and the economic conditions at the time of adoption.

Leases

In February 2016, the FASB issued ASU No. 2016-02 “Leases (Topic 842)” and issued subsequent amendments to the initial guidance under ASU 2017-13, ASU 2018-10, ASU 2018-11 and ASU 2018-20 (collectively, Topic 842). Topic 842 supersedes the guidance in former ASC Topic 840 “Leases”. Topic 842 requires companies to generally recognize on the balance sheet operating and financing lease liabilities and corresponding right-of-use (ROU) assets. For OpenText, 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. Upon adoption, we expect to recognize ROU assets ranging from approximately $218 million to $228 million and lease liabilities ranging from approximately $255 million to $265 million. The new guidance will also require significant additional disclosures about the amount, timing and uncertainty of cash flows related to leases. We will adopt Topic 842 in the first quarter of our fiscal year ending June 30, 2020 using the modified retrospective transition and by applying the new standard to all leases existing at the date of initial adoption and not restating comparative periods, as allowed for under Topic 842. Upon adoption, we will also elect the transition provisions of permitted practical expedients, which among other things, allows the carryforward of the historical lease classification. Furthermore, upon adoption, we will make an accounting policy election that will keep leases with an initial term of 12 months or less off our Consolidated Balance Sheets and we will recognize these short-term lease payments in the Consolidated Statements of Operations on a straight-line basis over the lease term.

Cash and cash equivalents

Cash and cash equivalents include balances with banks as well as deposits 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.

Accounts Receivable and Allowance for doubtful accounts

From time to time, we may sell certain accounts receivable to a financial institution on a non-recourse basis for cash, less a discount. Proceeds from the sale of receivables approximate their discounted book value are included in operating cash flows on the Consolidated Statement of Cash Flows.

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.

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 consolidated balance sheet when they are no longer in use. We did not recognize any significant property and equipment impairment charges in Fiscal 2019, Fiscal 2018, or Fiscal 2017. The following represents the estimated useful lives of property and equipment as of June 30, 2019:



Furniture and fixtures	5 years
Office equipment	5 years
Computer hardware	3 years
Computer software	3 to 7 years
Capitalized software	3 to 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 ASC Topic 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 3 to 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.

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, including contingent consideration where applicable, assumed at the acquisition date, our estimates are inherently uncertain and subject to refinement, particularly since these assumptions and estimates are based in part on historical experience and information obtained from the management of the acquired companies. 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 in the period identified. Furthermore, when valuing certain intangible assets that we have acquired, critical estimates may be made relating to, but not limited to: (i) future expected cash flows from software license sales, cloud SaaS, DaaS and PaaS contracts, support agreements, consulting agreements and other customer contracts (ii) the acquired company's technology and competitive position, as well as assumptions about the period of time that the acquired technology will continue to be used in the combined company's product portfolio, and (iii) discount rates. 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 Income.

For a given acquisition, we may 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 the "Provision for (recovery of) income taxes" line of our Consolidated Statements of Income.

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 (EIM) software and solutions. Therefore, our goodwill impairment assessment is based on the allocation of goodwill to a single reporting unit.

We 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 second step of the impairment test is performed. In the second step of the impairment test, we 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 an impairment loss equal to the difference, but not exceeding the total carrying value of goodwill allocated to the reporting unit, would be recorded.

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", net of tax, in our accompanying Consolidated Balance Sheets. Any ineffective or excluded portion of a designated cash flow hedge, if applicable, was recognized in our Consolidated Statements 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 in our Consolidated Statements of Income.

Revenue Recognition

Contract Balances

A contract asset will be recorded if we have recognized revenue but do not have an unconditional right to the related consideration from the customer. For example, this will be the case if implementation services offered in a cloud arrangement are identified as a separate performance obligation and are provided to a customer prior to us being able to bill the customer. In addition, a contract asset may arise in relation to subscription licenses if the license revenue that is recognized upfront exceeds the amount that we are able to invoice the customer at that time. Contract assets are reclassified to accounts receivable when the rights become unconditional.

In accordance with Topic 606, we account for a customer contract when we obtain written approval, the contract is committed, the rights of the parties, including the payment terms, are identified, the contract has commercial substance and consideration is probable of collection. Revenue is recognized when, or as, control of a promised product or service is transferred to our customers in an amount that reflects the consideration we expect to be entitled to in exchange for our products and services (at its transaction price). Estimates of variable consideration and the determination of whether to include estimated amounts in the transaction price are based on readily available information, which may include historical, current and forecasted information, taking into consideration the type of customer, the type of transaction and specific facts and circumstances of each arrangement. We report revenue net of any revenue-based taxes assessed by governmental authorities that are imposed on and concurrent with specific revenue producing transactions.

We have four revenue streams: license, cloud services and subscriptions, customer support, and professional service and other.

License revenue

Our license revenue can be broadly categorized as perpetual licenses, term licenses and subscription licenses, all of which are deployed on the customer’s premises (on-premise).

Perpetual licenses: We sell perpetual licenses which provide customers the right to use software for an indefinite period of time in exchange for a one-time license fee, which is generally paid at contract inception. Our perpetual licenses provide a right to use intellectual property (IP) that is functional in nature and have significant stand-alone functionality. Accordingly, for perpetual licenses of functional IP, revenue is recognized at the point-in-time when control has been transferred to the customer, which normally occurs once software activation keys have been made available for download.

Term licenses and Subscription licenses: We sell both term and subscription licenses which provide customers the right to use software for a specified period in exchange for a fee, which may be paid at contract inception or paid in installments over the period of the contract. Like perpetual licenses, both our term licenses and subscription licenses are functional IP that have significant stand-alone functionality. Accordingly, for both term and subscription licenses, revenue is recognized at the point-in-time when the customer is able to use and benefit from the software, which is normally once software activation keys have been made available for download at the commencement of the term.

Cloud services and subscriptions revenue

Cloud services and subscriptions revenue are from hosting arrangements where in connection with the licensing of software, the end user doesn’t take possession of the software, as well as from end-to-end fully outsourced business-to-business (B2B) integration solutions to our customers (collectively referred to as cloud arrangements). The software application resides on our hardware or that of a third party, and the customer accesses and uses the software on an as-needed basis. Our cloud arrangements can be broadly categorized as "platform as a service" (PaaS), "software as a service" (SaaS), cloud subscriptions and managed services.

PaaS/ SaaS/ Cloud Subscriptions (collectively referred to here as cloud-based solutions): We offer cloud-based solutions that provide customers the right to access our software through the internet. Our cloud-based solutions represent a series of distinct services that are substantially the same and have the same pattern of transfer to the customer. These services are made available to the customer continuously throughout the contractual period, however, the extent to which the customer uses the services may vary at the customer’s discretion. The payment for cloud-based solutions may be received either at inception of the arrangement, or over the term of the arrangement.

These cloud-based solutions are considered to have a single performance obligation where the customer simultaneously receives and consumes the benefit, and as such we recognize revenue for these cloud-based solutions ratably over the term of the contractual agreement. For example, revenue related to cloud-based solutions that are provided on a usage basis, such as the number of users, is recognized based on a customer’s utilization of the services in a given period.

Additionally, a software license is present in a cloud-based solutions arrangement if all of the following criteria are met:

(i) The customer has the contractual right to take possession of the software at any time without significant penalty; and

(ii) It is feasible for the customer to host the software independent of us.

In these cases where a software license is present in a cloud-based solutions arrangement it is assessed to determine if it is distinct from the cloud-based solutions arrangement. The revenue allocated to the distinct software license would be recognized at the point in time the software license is transferred to the customer, whereas the revenue allocated to the hosting performance obligation would be recognized ratably on a monthly basis over the contractual term unless evidence suggests that revenue is earned, or obligations are fulfilled in a different pattern over the contractual term of the arrangement.

Managed services: We provide comprehensive B2B process outsourcing services for all day-to-day operations of a customers’ B2B integration program. Customers using these managed services are not permitted to take possession of our software and the contract is for a defined period, where customers pay a monthly or quarterly fee. Our performance obligation is satisfied as we provide services of operating and managing a customer's electronic data interchange (EDI) environment. Revenue relating to these services is recognized using an output method based on the expected level of service we will provide over the term of the contract.

In connection with cloud subscription and managed service contracts, we often agree to perform a variety of services before the customer goes live, such as for example, converting and migrating customer data, building interfaces and providing training. These services are considered an outsourced suite of professional services which can involve certain project-based activities. These services can be provided at the initiation of a contract, during the implementation or on an ongoing basis as part of the customer life cycle. These services can be charged separately on a fixed fee or time and materials basis, or the costs associated may be recovered as part of the ongoing cloud subscription or managed services fee. These outsourced professional services are considered to be distinct from the ongoing hosting services and represent a separate performance obligation within our cloud subscription or managed services arrangements. The obligation to provide outsourced professional services is satisfied over time, with the customer simultaneously receiving and consuming the benefits as we satisfy our performance obligations. For outsourced professional services, we recognize revenue by measuring progress toward the satisfaction of our performance obligation. Progress for services that are contracted for a fixed price is generally measured based on hours incurred as a portion of total estimated hours. As a practical expedient, when we invoice a customer at an amount that corresponds directly with the value to the customer of our performance to date, we recognize revenue at that amount.

Customer support revenue

Customer support revenue is associated with perpetual, term license and on-premise subscription arrangements. As customer support is not critical to the customer's ability to derive benefit from its right to use our software, customer support is considered as a distinct performance obligation when sold together in a bundled arrangement along with the software.

Customer support consists primarily of technical support and the provision of unspecified updates and upgrades on a when-and-if-available basis. Customer support for perpetual licenses is renewable, generally on an annual basis, at the option of the customer. Customer support for term and subscription licenses is renewable concurrently with such licenses for the same duration of time. Payments for customer support are generally made at the inception of the contract term or in installments over the term of the maintenance period. Our customer support team is ready to provide these maintenance services, as needed, to the customer during the contract term. As the elements of customer support are delivered concurrently and have the same pattern of transfer, customer support is accounted for as a single performance obligation. The customer benefits evenly throughout the contract period from the guarantee that the customer support resources and personnel will be available to them, and that any unspecified upgrades or unspecified future products developed by us will be made available. Revenue for customer support is recognized ratably over the contract period based on the start and end dates of the maintenance term, in line with how we believe services are provided.

Professional service and other revenue

Our professional services, when offered along with software licenses, consists primarily of technical services and training services. Technical services may include installation, customization, implementation or consulting services. Training services may include access to online modules or delivering a training package customized to the customer’s needs. At the customer’s discretion, we may offer one, all, or a mix of these services. Payment for professional services is generally a fixed fee or is a fee based on time and materials.

Professional services can be arranged in the same contract as the software license or in a separate contract.

As our professional services do not significantly change the functionality of the license and our customers can benefit from our professional services on their own or together with other readily available resources, we consider professional services as distinct within the context of the contract.

Professional service revenue is recognized over time so long as: (i) the customer simultaneously receives and consumes the benefits as we perform them, (ii) our performance creates or enhances an asset the customer controls as we perform, and (iii) our performance does not create an asset with alternative use and we have enforceable right to payment.

If all of the above criteria are met, we use an input-based measure of progress for recognizing professional service revenue. For example we may consider total labor hours incurred compared to total expected labor hours. As a practical expedient, when we invoice a customer at an amount that corresponds directly with the value to the customer of our performance to date, we will recognize revenue at that amount.

Material rights

To the extent that we grant our customer an option to acquire additional products or services in one of our arrangements, we will account for the option as a distinct performance obligation in the contract only if the option provides a material right to the customer that the customer would not receive without entering into the contract. For example if we give the customer an option to acquire additional goods or services in the future at a price that is significantly lower than the current price, this would be a material right as it allows the customer to, in effect, pay in advance for the option to purchase future products or services. If a material right exists in one of our contracts then revenue allocated to the option is deferred and we would recognize revenue only when those future products or services are transferred or when the option expires.

Based on history, our contracts do not typically contain material rights and when they do, the material right is not significant to our consolidated financial statements.

Arrangements with multiple performance obligations

Our contracts generally contain more than one of the products and services listed above. Determining whether goods and services are considered distinct performance obligations that should be accounted for separately or as a single performance obligation may require judgment, specifically when assessing whether both of the following two criteria are met:


•	the customer can benefit from the product or service either on its own or together with other resources that are readily available to the customer; and


•	our promise to transfer the product or service to the customer is separately identifiable from other promises in the contract.

If these criteria are not met, we determine an appropriate measure of progress based on the nature of our overall promise for the single performance obligation.

If these criteria are met, each product or service is separately accounted for as a distinct performance obligation and the total transaction price is allocated to each performance obligation on a relative standalone selling price (SSP) basis.

Standalone selling price

The SSP reflects the price we would charge for a specific product or service if it was sold separately in similar circumstances and to similar customers. In most cases we are able to establish the SSP based on observable data. We typically establish a narrow SSP range for our products and services and assess this range on a periodic basis or when material changes in facts and circumstances warrant a review.

If the SSP is not directly observable, then we estimate the amount using either the expected cost plus a margin or residual approach. Estimating SSP requires judgment that could impact the amount and timing of revenue recognized. SSP is a formal process whereby management considers multiple factors including, but not limited to, geographic or regional specific factors, competitive positioning, internal costs, profit objectives, and pricing practices.

Transaction Price Allocation

In bundled arrangements, where we have more than one distinct performance obligation, we must allocate the transaction price to each performance obligation based on its relative SSP. However, in certain bundled arrangements, the SSP may not always be directly observable. For instance, in bundled arrangements with license and customer support, we allocate the transaction price between the license and customer support performance obligations using the residual approach because we have determined that the SSP for licenses in these arrangements are highly variable. We use the residual approach only for our license arrangements. When the SSP is observable but contractual pricing does not fall within our established SSP range, then an adjustment is required and we will allocate the transaction price between license and customer support at a constant ratio reflecting the mid-point of the established SSP range.

When two or more contracts are entered into at or near the same time with the same customer, we evaluate the facts and circumstances associated with the negotiation of those contracts. Where the contracts are negotiated as a package, we will account for them as a single arrangement and allocate the consideration for the combined contracts among the performance obligations accordingly.

Sales to resellers

We execute certain sales contracts through resellers, distributors and channel partners (collectively referred to as resellers). For these type of agreements, we assess whether we are considered the principal or the agent in the arrangement. We consider factors such as, but not limited to, whether or not the reseller has the ability to set the price for which they sell our software products to end users and whether or not resellers distribution rights are limited such that any potential sales are subject to OpenText’s review and approval before delivery of the software product can be made. If we determine that we are the

principal in the arrangement, then revenue is recognized based on the transaction price for the sale of the software product to the end user at the gross amount. If that is not known, then the net amount received from the reseller is the transaction price. If we determine that we are the agent in the agreement, then revenue is recognized based on the transaction price for the sale of the software product to the reseller, less any applicable commissions paid or discounts or rebates, if offered. Costs or commissions paid to the reseller would be recognized as a reduction of revenue unless we received a distinct good or service in return. Similarly, any discounts or rebates offered by the reseller would be recognized as a reduction of revenue.

Typically, we conclude that we are the principal in our reseller agreements, as we have control over the service and products prior to being transferred to the end customer.

We also assess the creditworthiness of each reseller and if they are newly formed, undercapitalized or in financial difficulty, we defer any revenues expected to emanate from such reseller and recognize revenue only when cash is received, and all other revenue recognition criteria under Topic 606 are met.

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. In some contracts, however, discounts may be offered to the customer for future software purchases and other additional products or services. Such arrangements grant the customer an option to acquire additional goods or services in the future at a discount and therefore are evaluated under guidance related to “material rights” as discussed above.

Other policies

Payment terms and conditions vary by contract type, although terms generally include a requirement of payment within 30 to 60 days of the invoice date. In certain arrangements, we will receive payment from a customer either before or after the performance obligation to which the invoice relates has been satisfied. As a practical expedient, we do not account for significant financing components if the period between when we transfer the promised good or service to the customer and when the customer pays for the product or service will be one year or less. On that basis, our contracts for license and maintenance typically do not contain a significant financing component, however in determining the transaction price we consider whether we need to adjust the promised consideration for the effects of the time value of money if the timing of payments provides either the customer or OpenText with a significant benefit of financing. Our managed services contracts may not include an upfront charge for outsourced professional services performed as part of an implementation and are recovered through an ongoing fee. Therefore, these contracts may be expected to have a financing component associated with revenue being recognized in advance of billings.

We may modify contracts to offer customers additional products or services. The additional products and services will be considered distinct from those products or services transferred to the customer before the modification and will be accounted for as a separate contract. We evaluate whether the price for the additional products and services reflects the SSP adjusted as appropriate for facts and circumstances applicable to that contract. In determining whether an adjustment is appropriate, we evaluate whether the incremental consideration is consistent with the prices previously paid by the customer or similar customers.

Performance Obligations

A summary of our typical performance obligations and when the obligations are satisfied are as follows:



Performance Obligation	When Performance Obligation is Typically Satisfied
License revenue:
Software licenses (Perpetual,Term, Subscription)	When software activation keys have been made available for download (point in time)
Cloud services and subscriptions revenue:
Outsourced Professional Services	As the services are provided (over time)
Managed Services / Ongoing Hosting	Over the contract term, beginning on the date that service is made available (i.e. "Go live") to the customer (over time)
Customer support revenue:
When and if available updates and upgrades and technical support	Ratable over the course of the service term (over time)
Professional service and other revenue:
Professional services	As the services are provided (over time)

We recognize deferred revenue when we have received consideration or an amount of consideration is due from the customer for future obligations to transfer products or services. Our deferred revenues primarily relate to customer support agreements which have been paid for by customers prior to the performance of those services.

Incremental costs of obtaining a contract include only those costs that we incur to obtain a contract that we would not have incurred if the contract had not been obtained, such as sales commissions. We have determined that certain of our commission programs meet the requirements to be capitalized. Some commission programs are not subject to capitalization as the commission expense is paid and recognized as the related revenue is recognized. In assessing costs to obtain a contract, we apply a practical expedient that allows us to assess our incremental costs on a portfolio of contracts with similar characteristics instead of assessing the incremental costs on each individual contract. We do not expect the financial statement effects of applying this practical expedient to the portfolio of contracts to be materially different than if we were to apply the new standard to each individual contract.

We pay commissions on the sale of new customer contracts as well as for renewals of existing contracts to the extent the renewals generate incremental revenue. Commissions paid on renewal contracts are limited to the incremental new revenue and therefore these payments are not commensurate with the commission paid on the original sale. We allocate commission costs to the performance obligations in an arrangement consistent with the allocation of the transaction price. Commissions allocated to the license performance obligation are expensed at the time the license revenue is recognized. Commissions allocated to professional service performance obligations are expensed as incurred, as these contracts are generally for one year or less and we apply a practical expedient to expense costs as incurred if the amortization period would have been one year or less. Commissions allocated to maintenance, managed services, on-going hosting arrangements or other recurring services, are capitalized and amortized consistent with the pattern of transfer to the customer of the services over the period expected to benefit from the commission payment. As commissions paid on renewals are not commensurate with the original sale, the period of benefit considers anticipated renewals. The benefit period is estimated to be approximately six years which is based on our customer contracts and the estimated life of our technology.

Expenses for incremental costs associated with obtaining a contract are recorded within sales and marketing expense in the Consolidated Statements of Income.

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 expense 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 (recovery of) income taxes" line of our Consolidated Statements of Income

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 since the interest rate is at market.

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

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 previous 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”.

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

Loss Contingencies

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.

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

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

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”, net of tax, within “Shareholders' equity”), respectively, on the Consolidated Balance Sheets