XML 20 R33.htm IDEA: XBRL DOCUMENT
v3.19.3

Recent Accounting Pronouncements (Policies) | 3 Months Ended
--- | ---
Sep. 30, 2019
Accounting Policies [Abstract] |
Use of estimates | 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 Condensed 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 | Leases Effective July 1, 2019, we adopted Accounting Standards Update (ASU) No. 2016-02 “Leases (Topic 842)” (Topic 842) using the modified retrospective transition approach. In accordance with this adoption method, results for reporting periods as of July 1, 2019 are presented under the new standard, while prior period results continue to be reported under the previous standard. Additionally, we elected the package of practical expedients permitted under the transition guidance within Topic 842, which allowed us to (i) carry forward the historical lease classification for any expired or existing leases, (ii) not reassess whether any expired or existing contracts contain leases and (iii) not reassess any initial direct cost for existing leases. We did not elect the practical expedient of hindsight when determining the lease term of existing contracts at the effective date. As a result of this adoption, we recorded the following adjustments as of July 1, 2019 on the Consolidated Balance Sheets:
• | An increase in operating lease right of use assets of approximately $217.5 million;
• | An increase in total operating lease liabilities of approximately $253.5 million;
• | A decrease in prepaid expenses and other current assets of approximately $6.6 million in connection with lease fair value adjustments and prepaid rent;
• | A decrease in other assets of approximately $0.2 million in connection with lease fair value adjustments; and
• | A decrease in total accrued liabilities of approximately $42.8 million in connection with tenant allowances, deferred rent, lease fair value adjustments, and amounts payable in respect of restructured facilities.
The adoption of Topic 842 had no impact to the Condensed Consolidated Statements of Income, Condensed Consolidated Statements of Comprehensive Income, Condensed Consolidated Statement of Shareholders' Equity or Condensed Consolidated Statements of Cash Flows. Please refer to Note 6, “Leases,” for additional information. Accounting Pronouncements Adopted in Fiscal 2020 During Fiscal 2020, we have adopted the following ASUs, in addition to those discussed in note 1 "Basis of Presentation". The ASUs listed below did not have a material impact to our reported financial position, results of operations or cash flows:
• | ASU 2017-12 “Derivatives and Hedging (Topic 815) Targeted Improvements to Accounting for Hedging Activities” (ASU 2017-12)
• | 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”
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. 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.
Revenues | 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. 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 Condensed Consolidated Statements of Income. In accordance with Accounting Standards Codification (ASC) Topic 606 "Revenue from Contracts with Customers" (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)
Leases | 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. 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. Consistent with previous lease accounting rules under ASC Topic 840, lease expense for minimum lease payments continue 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.

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 Disclosure of accounting policy for leasing arrangement entered into by lessee. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 842 -SubTopic 20 -Section 50 -Paragraph 1 -Subparagraph (b) -URI http://asc.fasb.org/extlink&oid=77888426&loc=SL77918666-209980 + Details
Name: | us-gaap_LesseeLeasesPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy pertaining to new accounting pronouncements that may impact the entity's financial reporting. Includes, but is not limited to, quantification of the expected or actual impact. + References No definition available. + Details
Name: | us-gaap_NewAccountingPronouncementsPolicyPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for revenue from contract with customer. + References Reference 1: http://www.xbrl.org/2003/role/exampleRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 4 -Subparagraph (e) -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18823-107790 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI http://asc.fasb.org/topic&trid=49130388 + Details
Name: | us-gaap_RevenueFromContractWithCustomerPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for the use of estimates in the preparation of financial statements in conformity with generally accepted accounting principles. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 12 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6191-108592 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 11 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6161-108592 Reference 3: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 9 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6143-108592 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 1 -Subparagraph (b) -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e5967-108592 Reference 5: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 4 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6061-108592 Reference 6: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 8 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6132-108592 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 1 -Subparagraph (c) -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e5967-108592 + Details
Name: | us-gaap_UseOfEstimates
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration