XML 39 R12.htm IDEA: XBRL DOCUMENT
v3.26.1

ACCOUNTING POLICIES AND RECENT ACCOUNTING PRONOUNCEMENTS | 12 Months Ended
--- | ---
Jun. 30, 2026
Accounting Policies [Abstract] |
ACCOUNTING POLICIES AND RECENT ACCOUNTING PRONOUNCEMENTS | ACCOUNTING POLICIES AND RECENT ACCOUNTING PRONOUNCEMENTS Accounting Policies Cash and cash equivalents Cash and cash equivalents include balances with banks as well as deposits that have original 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 Credit Losses In accordance with ASC Topic 326, “Financial Instruments - Credit Losses” (Topic 326), we recognize expected credit losses for accounts receivable and contract assets based on lifetime expected losses. We recognize a loss allowance using a collective assessment for accounts receivable, including contract assets, with similar risk characteristics based on historical credit loss experience, adjusted for forward-looking factors specific to the debtors and economic environment. We continue to maintain an allowance for 100% of all accounts deemed to be uncollectible. Customer creditworthiness is evaluated prior to order fulfillment and based on 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 credit worthiness. 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, 2026 and 2025, respectively. 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 and are included in operating cash flows on the Consolidated Statements of Cash Flows. 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 Sheets when they are no longer in use. See the “Impairment of long-lived assets” section below for policy on property and equipment impairments. The following represents the estimated useful lives of property and equipment as of June 30, 2026:
Furniture, equipment and other | 5 to 15 years
Computer hardware | 3 to 5 years
Computer software | 3 to 7 years
Capitalized software development costs | 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, “Internal-Use Software.” 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. As of June 30, 2026 and 2025, our capitalized software development costs were $364.1 million and $283.4 million, respectively. Our additions relating to capitalized software development costs incurred during Fiscal 2026 and Fiscal 2025 were $81.9 million and $32.3 million, respectively. Leases We enter into operating leases, both domestically and internationally, for certain facilities, automobiles, data centers and equipment for use in the ordinary course of business. We also have finance leases, primarily comprised of equipment leases, all of which are sublet. Leases with an initial term of 12 months or less are not recorded on the Consolidated Balance Sheets. For operating leases where the Company is a lessor, rental income is recognized on a straight-line basis over the remaining non-cancelable lease terms. In accordance with ASC Topic 842, “Leases” (Topic 842), we account for a contract as a lease when we have the right to direct the use of the asset for a period of time while obtaining substantially all of the asset’s economic benefits. We determine the initial classification and measurement of our right of use (ROU) assets and lease liabilities at the lease commencement date and thereafter if modified. ROU assets represent our right to control the underlying assets under lease, and the lease liability is our obligation to make the lease payments related to the underlying assets under lease, over the contractual term. ROU assets and lease liabilities are recognized on the Consolidated Balance Sheets based on the present value of future minimum lease payments to be made over the lease term. When available, we will use the rate implicit in the lease to discount lease payments to present value. However, real estate leases generally do not provide a readily determinable implicit rate, therefore, we must estimate our incremental borrowing rate to discount the lease payments. We estimate our incremental borrowing rate based on a collateralized basis with similar terms and payments, in an economic environment where the leased asset is located. The ROU asset equals the lease liability, adjusted for any initial direct costs, prepaid rent and lease incentives on initial recognition. Fixed lease costs are included in the recognition of ROU assets and lease liabilities. Variable lease costs are not included in the measurement of the lease liability. These variable lease payments are recognized in the Consolidated Statements of Income in the period in which the obligation for those payments is incurred. Lease expense for minimum lease payments continues to be recognized in the Consolidated Statements of Income on a straight-line basis over the lease term. We have not elected the practical expedient to combine lease and non-lease components in the determination of lease costs for our facility leases. For all other asset classes, we have elected the practical expedient to combine the lease and the non-lease components. The lease liability includes lease payments related to options to extend or renew the lease term only if we are reasonably certain we will exercise those options. Our leases typically do not contain any material residual value guarantees or restrictive covenants. In certain circumstances, we sublease all or a portion of a leased facility to various other companies through a sublease agreement. 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, desktop as a service (DaaS) and platform as a service (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 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 data management 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 quantitative assessment of the impairment test is performed. In the quantitative assessment, 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. Our annual impairment analysis of goodwill was performed as of April 1, 2026. Our qualitative assessment indicated that there were no indications of impairment and therefore there was no impairment of goodwill required to be recorded for Fiscal 2026 (no impairments were recorded for Fiscal 2025 and Fiscal 2024, respectively). 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 in acquisitions. We amortize acquired technology on a straight-line basis over its estimated useful life. 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, ROU assets 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 significant impairment charges for long-lived assets during Fiscal 2026, Fiscal 2025 and Fiscal 2024, respectively. 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 record the effective portions of the gain or loss on derivative financial instruments that are designated as cash flow hedges in Accumulated other comprehensive income (loss), net of tax, in our accompanying Consolidated Balance Sheets. Any ineffective or excluded portion of a designated cash flow hedge, if applicable, is recognized in our Consolidated Statements of Income. In Fiscal 2023, we entered into certain derivative financial instruments, a portion of which were designated as a net investment hedge. In accordance with Topic 815, we recorded the effective portion of the gain or loss on derivative financial instruments that were designated as a net investment hedge within our currency translation adjustment component of Accumulated other comprehensive income (loss), in our accompanying Consolidated Balance Sheets. Any ineffective or excluded portion of our net investment hedge, if applicable, is recognized in Interest and other related expense, net of our Consolidated Statements of Income. See Note 17 “Derivative Instruments and Hedging Activities” for more details. 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 which are generally recorded within General and administrative expense in our Consolidated Statements of Income. 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 In accordance with ASC 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: cloud services and subscriptions, customer support, license, and professional service and other. 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 does not take possession of the software, as well as from end-to-end fully outsourced 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 PaaS, 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. As part of cloud services and subscriptions revenues, 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, 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. License revenue Our license revenue can be broadly categorized as perpetual licenses, term licenses and subscription licenses, which are primarily deployed on the customer’s premises. 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 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. Professional service and other revenue Our professional services, when offered along with software licenses, consist 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 as 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 the above criteria are met, we use an input-based measure of progress for recognizing professional service revenue. For example, we may consider total labour hours incurred compared to total expected labour 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 SSP basis. Standalone selling price The standalone selling price (SSP) reflects the price we would charge for a specific product or service if it were sold separately in similar circumstances and to similar customers. In most cases we can 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 based on the relative SSP established for the respective performance obligations. 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 regional system integrators We execute certain sales contracts through regional system integrators, distributors and channel partners (collectively referred to as regional system integrators). Typically, we conclude that the regional system integrators are OpenText customers in our regional system integrators' agreements. The regional system integrators have control over the pricing, service and products prior to being transferred to the end customer. We also assess the creditworthiness of each regional system integrator and if they are newly formed, undercapitalized or in financial difficulty, we defer any revenues expected to emanate from such regional system integrator and recognize revenue only when cash is received, and all other revenue recognition criteria under ASC 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. However, we do offer consumers who purchase certain of our products online directly from us an unconditional full 70-day money-back guarantee. Distributors and regional system integrators are also permitted to return the consumer products, subject to certain limitations. Revenue is reduced for such rights based on the estimate of future returns originating from contractual agreements with these customers. Additionally, 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. Certain of our subscription services and product support arrangements generally contain performance response time guarantees. For subscription services arrangements, we estimate variable consideration using a portfolio approach because performance penalties are tied to standard response time requirements. For product support arrangements, we estimate variable consideration on a contract basis because such arrangements are customer specific. For both subscription services and product support arrangements, we use an expected value approach to estimate variable consideration based on historical business practices and current and future performance expectations to determine the likelihood of incurring penalties. 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
Cloud services and subscriptions revenue: |
Outsourced Professional Services Managed Services / Ongoing Hosting / SaaS | As the services are provided (over time) 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)
License revenue: |
Software licenses (Perpetual, Term, Subscription) | When software activation keys have been made available for download (point in time)
Professional service and other revenue: |
Professional services | As the services are provided (over time)
Incremental Costs of Obtaining a Contract with a Customer 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 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. Our short-term capitalized costs to obtain a contract are included in Prepaid expenses and other current assets, while our long-term capitalized costs to obtain a contract are included in Other assets on our Consolidated Balance Sheets. 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. Advertising Expenses Advertising costs, which include digital advertising, marketing programs and other promotional costs, are expensed as incurred. Advertising expenses incurred in Fiscal 2026, Fiscal 2025 and Fiscal 2024 were $62.3 million, $64.8 million and $66.9 million, respectively. 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. The first step is to evaluate the tax position for recognition by determining if the weight of the available evidence indicates it is more likely than not, based solely on the technical merits, that the position will be sustained on audit, including the 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 15 “Income Taxes” for more details). Equity investments We invest in investment funds in which we are a limited partner. Our interests in each of these investees range from 4% to below 20%. These investments are accounted for using the equity method. Our share of net income or losses based on our interest in these investments, which approximates fair value, is recorded as a component of Other income (expense), net in our Consolidated Statements of Income (see Note 23 “Other Income (Expense), Net” 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 the fair value due to the relatively short period of time between origination of the instruments and their expected realization. The fair value of our Senior Notes is determined based on observable market prices and categorized as a Level 2 measurement. The carrying value of our other long-term debt facilities approximates the fair value since the interest rate is at market. We apply the provisions of ASC Topic 820, “Fair Value Measurement” (Topic 820), to our available-for-sale financial assets and derivative financial instruments that we are required to carry at fair value pursuant to other accounting standards (see Note 16 “Fair Value Measurement” 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 previous month of the transaction. The effect of foreign currency translation adjustments are recorded as a component of Accumulated other comprehensive income (loss). Transactional foreign currency gains (losses) included in the Consolidated Statements of Income under the line item Other income (expense), net for Fiscal 2026, Fiscal 2025 and Fiscal 2024 were $3.2 million, $(24.9) million, and $1.2 million, respectively. Restructuring charges We record restructuring charges relating to contractual lease obligations, not accounted for under Topic 842, 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 not accounted for under Topic 842. 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 18 “Special Charges (Recoveries)” for more details). 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. As of the date of this Annual Report on Form 10-K, the aggregate of such accrued liabilities was not material to our consolidated financial position or results of operations and we do not believe as of the date of this filing that it is reasonably possible that a loss exceeding the amounts already recognized will be incurred that would be material to our consolidated financial position or results of operations. As described more fully below, we are unable at this time to estimate a possible loss or range of losses in respect of certain disclosed matters (see Note 14 “Guarantees and Contingencies” 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. For periods in which we incur a net loss, our outstanding Common Share equivalents are not included in the calculation of diluted earnings (loss) per share as their effect is anti-dilutive. Accordingly, basic and diluted net loss per share for those periods are identical. See Note 24 “Earnings Per Share” for more details. Share-based compensation 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 13 “Equity and Share-based Compensation” 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), imputed interest on pension obligations and amortization of actuarial gain/loss. 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 (loss), net of tax, within Shareholders’ equity), respectively, on the Consolidated Balance Sheets. Actuarial gains or losses in excess of the greater of (i) 10% of the projected benefit obligation, or (ii) 10% of the plan assets, are recognized as a component of Other Comprehensive Income (Loss), net and subsequently amortized as a component of net periodic benefit costs over the weighted average of future working life of the plan’s active employees. See Note 12 “Pension Plans and Other Post-Retirement Benefits” for more details. Held for Sale Classification Assessments for held for sale accounting classification are performed by the Company when events or changes in business circumstances indicate that a change in classification may be necessary. The Company classifies assets and liabilities to be disposed of as held for sale in the period in which they are available for immediate sale in their present condition and when the sale is probable and expected to be completed within one year. Assets and liabilities classified as held for sale are presented separately within current assets and liabilities in our Consolidated Balance Sheets and are measured at the lower of their carrying amount or fair value less costs to sell. Further, the Company ceases to record depreciation and amortization expense on assets that are classified as held for sale. Accounting Pronouncements Adopted in Fiscal 2026 During Fiscal 2026, we adopted the following Accounting Standards Updates (ASU): Income Taxes In December 2023, the FASB issued ASU 2023-09 “Income Taxes (Topic 740): Improvements to Income Tax Disclosures,” that addresses requests for improved income tax disclosures from investors that use the financial statements to make capital allocation decisions. Public entities must adopt the new guidance for fiscal years beginning after December 15, 2024. The amendments in this ASU may be applied on a prospective or retrospective basis, with early adoption permitted. We adopted this ASU for our annual period beginning July 1, 2025 on a prospective basis. The adoption of this ASU expanded our disclosures, but did not have an impact on the Company’s Consolidated Financial Statements. See Note 15 “Income Taxes” for additional information. Accounting Pronouncements Not Yet Adopted in Fiscal 2026 Disaggregation of Income Statement Expenses In November 2024, the FASB issued ASU 2024-03 “Disaggregation of Income Statement Expenses (Subtopic 220-40),” which requires additional disclosures of specific expense categories included within income statement expense captions. The guidance will be effective for annual reporting periods beginning after December 15, 2026, and interim reporting periods beginning after December 15, 2027. The amendments in this ASU are to be applied on a prospective basis with the option for retrospective application, and early adoption is permitted. We are currently evaluating the impact of the adoption of ASU 2024-03 on the Company’s financial disclosures. Credit Losses In July 2025, the FASB issued ASU 2025-05 “Financial Instruments - Credit Losses (Topic 326)”, which provides a practical expedient for estimating expected credit losses for current accounts receivable and current contract assets that arise from transactions accounted for under Topic 606, Revenue from Contracts with Customers. The guidance will be effective for fiscal years beginning after December 15, 2025, and interim reporting periods within those annual reporting periods. The amendments in this ASU may be applied on a prospective basis, with early adoption permitted. We are currently evaluating the impact of the adoption of ASU 2025-05 on the Company’s financial disclosures. Internal-Use Software In September 2025, the FASB issued ASU 2025-06 “Intangible - Goodwill and Other - Internal-Use Software (Subtopic 350-40),” which amends guidance related to the accounting for internal-use software development costs. The guidance will be effective for annual reporting periods beginning after December 15, 2027, and interim reporting periods within those annual reporting periods. The amendments in this ASU may be applied on a prospective, modified prospective or retrospective basis, with early adoption permitted. We are currently evaluating the impact of the adoption of ASU 2025-06 on the Company’s financial disclosures. Derivatives and Hedging and Revenue from Contracts with Customers In September 2025, the FASB issued ASU 2025-07 “Derivatives and Hedging (Topic 815) and Revenue from Contracts with Customers (Topic 606),” which clarifies the application of derivative accounting to contracts that have features based on the operations or activities of one of the parties to the contract and to reduce diversity in the accounting for share-based payments in revenue contracts. The guidance will be effective for annual reporting periods beginning after December 15, 2026, and interim reporting periods within those annual reporting periods. The amendments in this ASU may be applied on a prospective or modified retrospective basis, with early adoption permitted. We do not expect ASU 2025-07 to have an impact on the Company’s financial disclosures.

X
- References No definition available. + Details
Name: | us-gaap_AccountingPoliciesAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure for change in accounting principle. Includes, but is not limited to, nature, reason, and method of adopting amendment to accounting standards or other change in accounting principle. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Topic 815 -SubTopic 20 -Name Accounting Standards Codification -Section 65 -Paragraph 7 -Subparagraph (i) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480528/815-20-65-7 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Topic 250 -SubTopic 10 -Name Accounting Standards Codification -Section S99 -Paragraph 5 -Subparagraph (SAB Topic 11.M.Q2) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480530/250-10-S99-5 Reference 3: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 3 -Subparagraph (e)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479719/606-10-65-3 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 3 -Subparagraph (d) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479719/606-10-65-3 Reference 5: http://www.xbrl.org/2003/role/disclosureRef -Topic 815 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 8 -Subparagraph (f)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480339/815-10-65-8 Reference 6: http://www.xbrl.org/2003/role/disclosureRef -Topic 815 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 8 -Subparagraph (e) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480339/815-10-65-8 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Topic 350 -SubTopic 40 -Name Accounting Standards Codification -Section 65 -Paragraph 4 -Subparagraph (f) -Publisher FASB -URI https://asc.fasb.org/1943274/2147482705/350-40-65-4 Reference 8: http://www.xbrl.org/2003/role/disclosureRef -Topic 350 -SubTopic 40 -Name Accounting Standards Codification -Section 65 -Paragraph 4 -Subparagraph (e) -Publisher FASB -URI https://asc.fasb.org/1943274/2147482705/350-40-65-4 Reference 9: http://www.xbrl.org/2003/role/disclosureRef -Topic 350 -SubTopic 40 -Name Accounting Standards Codification -Section 65 -Paragraph 4 -Subparagraph (d) -Publisher FASB -URI https://asc.fasb.org/1943274/2147482705/350-40-65-4 Reference 10: http://www.xbrl.org/2003/role/disclosureRef -Topic 250 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 1 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org/1943274/2147483443/250-10-50-1 Reference 11: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (e)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479719/606-10-65-2 Reference 12: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (d)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479719/606-10-65-2 Reference 13: http://www.xbrl.org/2003/role/disclosureRef -Topic 805 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 5 -Subparagraph (d) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479279/805-10-65-5 Reference 14: http://www.xbrl.org/2003/role/disclosureRef -Topic 250 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 1 -Subparagraph (c)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147483443/250-10-50-1 Reference 15: http://www.xbrl.org/2003/role/disclosureRef -Topic 105 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 9 -Subparagraph (e) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479343/105-10-65-9 Reference 16: http://www.xbrl.org/2003/role/disclosureRef -Topic 718 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 17 -Subparagraph (d)(2) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480336/718-10-65-17 Reference 17: http://www.xbrl.org/2003/role/disclosureRef -Topic 718 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 17 -Subparagraph (d)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480336/718-10-65-17 Reference 18: http://www.xbrl.org/2003/role/disclosureRef -Topic 250 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 1 -Subparagraph (b)(4) -Publisher FASB -URI https://asc.fasb.org/1943274/2147483443/250-10-50-1 Reference 19: http://www.xbrl.org/2003/role/disclosureRef -Topic 105 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 7 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479343/105-10-65-7 Reference 20: http://www.xbrl.org/2003/role/disclosureRef -Topic 805 -SubTopic 60 -Name Accounting Standards Codification -Section 65 -Paragraph 1 -Subparagraph (g) -Publisher FASB -URI https://asc.fasb.org/1943274/2147476176/805-60-65-1 Reference 21: http://www.xbrl.org/2003/role/disclosureRef -Topic 848 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (c) -Publisher FASB -URI https://asc.fasb.org/1943274/2147483550/848-10-65-2 Reference 22: http://www.xbrl.org/2003/role/disclosureRef -Topic 740 -SubTopic 323 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (g)(2) -Publisher FASB -URI https://asc.fasb.org/1943274/2147478666/740-323-65-2 Reference 23: http://www.xbrl.org/2003/role/disclosureRef -Topic 740 -SubTopic 323 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (g)(4) -Publisher FASB -URI https://asc.fasb.org/1943274/2147478666/740-323-65-2 Reference 24: http://www.xbrl.org/2003/role/disclosureRef -Topic 740 -SubTopic 323 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (g)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147478666/740-323-65-2 Reference 25: http://www.xbrl.org/2003/role/disclosureRef -Topic 848 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (d)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147483550/848-10-65-2 Reference 26: http://www.xbrl.org/2003/role/disclosureRef -Topic 848 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 1 -Subparagraph (e)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147483550/848-10-65-1 Reference 27: http://www.xbrl.org/2003/role/disclosureRef -Topic 944 -SubTopic 40 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (g)(2)(i) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480016/944-40-65-2 Reference 28: http://www.xbrl.org/2003/role/disclosureRef -Topic 944 -SubTopic 40 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (g)(2)(ii) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480016/944-40-65-2 Reference 29: http://www.xbrl.org/2003/role/disclosureRef -Topic 944 -SubTopic 40 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (g)(2)(iii) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480016/944-40-65-2 Reference 30: http://www.xbrl.org/2003/role/disclosureRef -Topic 944 -SubTopic 40 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (g)(2)(iv) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480016/944-40-65-2 Reference 31: http://www.xbrl.org/2003/role/disclosureRef -Topic 944 -SubTopic 40 -Name Accounting Standards Codification -Section 65 -Paragraph 2 -Subparagraph (h)(2) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480016/944-40-65-2 Reference 32: http://www.xbrl.org/2003/role/disclosureRef -Topic 326 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 4 -Subparagraph (e)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479654/326-10-65-4 Reference 33: http://www.xbrl.org/2003/role/disclosureRef -Topic 326 -SubTopic 10 -Name Accounting Standards Codification -Section 65 -Paragraph 4 -Subparagraph (e)(2) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479654/326-10-65-4 Reference 34: http://www.xbrl.org/2003/role/disclosureRef -Topic 250 -SubTopic 10 -Name Accounting Standards Codification -Section S99 -Paragraph 6 -Publisher FASB -URI https://asc.fasb.org/1943274/2147480530/250-10-S99-6 Reference 35: http://www.xbrl.org/2003/role/disclosureRef -Topic 470 -SubTopic 20 -Name Accounting Standards Codification -Section 65 -Paragraph 4 -Subparagraph (f)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147481538/470-20-65-4 Reference 36: http://www.xbrl.org/2003/role/disclosureRef -Topic 470 -SubTopic 20 -Name Accounting Standards Codification -Section 65 -Paragraph 4 -Subparagraph (e) -Publisher FASB -URI https://asc.fasb.org/1943274/2147481538/470-20-65-4 Reference 37: http://www.xbrl.org/2003/role/disclosureRef -Topic 250 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 1 -Subparagraph (b)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147483443/250-10-50-1 Reference 38: http://www.xbrl.org/2003/role/disclosureRef -Name Accounting Standards Codification -Topic 250 -Publisher FASB -URI https://asc.fasb.org/250/tableOfContent Reference 39: http://www.xbrl.org/2003/role/disclosureRef -Topic 815 -SubTopic 40 -Name Accounting Standards Codification -Section 65 -Paragraph 1 -Subparagraph (e)(1) -Publisher FASB -URI https://asc.fasb.org/1943274/2147480175/815-40-65-1 + Details
Name: | us-gaap_NewAccountingPronouncementsAndChangesInAccountingPrinciplesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration