XML 46 R10.htm IDEA: XBRL DOCUMENT
v3.24.3

Revenue | 6 Months Ended
--- | ---
Sep. 30, 2024
Revenue from Contract with Customer [Abstract] |
Revenue | Revenue We generate revenues through subscription arrangements, perpetual software licenses, customer support contracts and other services. Subscription Subscription includes the revenues derived from term-based arrangements, including the software portion of term-based licenses and SaaS offerings. The software component of term-based licenses is typically recognized when the software is delivered or made available for download. The term of our subscription arrangements is typically one to three years but can range between one and five years. For SaaS offerings, revenue is generally recognized ratably over the contract term beginning on the date that the service is made available to the customer. Perpetual License Perpetual license includes the revenues from the sale of perpetual software licenses. Perpetual software license revenue is typically recognized when the software is delivered or made available for download. Customer Support Customer support includes revenues associated with support contracts tied to our software products. Customer support includes software updates on a when-and-if-available basis, telephone support, integrated web-based support, and other premium support offerings, for both subscription software and perpetual software license arrangements. We sell our customer support contracts as a percentage of net software purchases. Customer support revenue is recognized ratably over the term of the customer support agreement, which is typically one year on our perpetual licenses and over the term on our term-based licenses. Other Services Other services consist primarily of revenues related to professional service offerings, including consultation, assessment and design, installation services, and customer education. Revenues related to other services can vary period over period based on the timing services are delivered and are typically recognized as the services are performed. We do not customize our software licenses (both perpetual and term-based) and installation services are not required. Software licenses are delivered before related services are provided and are functional without professional services, updates, or technical support. We have concluded that our software licenses (both perpetual and term-based) are functional intellectual property that is distinct, as the user can benefit from the software on its own. Revenues for both perpetual and term-based licenses are typically recognized when the software is delivered and/or made available for download as this is the point the user of the software can direct the use of and obtain substantially all the remaining benefits from the functional intellectual property. We do not recognize software revenue related to the renewal of subscription software licenses earlier than the beginning of the new subscription period. We also offer appliances that integrate our software with hardware and address a wide range of business needs and use cases, ranging from support for remote or branch offices with limited IT staff up to large corporate data centers. Our appliances are almost exclusively sold via a software only model in which we sell software to a third party, which assembles an integrated appliance that is sold to end user customers. As a result, the revenues and costs associated with hardware are usually not included in our financial statements. Our typical performance obligations include the following:
Performance Obligation | When Performance Obligation is Typically Satisfied | When Payment is Typically Due | How Standalone Selling Price is Typically Estimated
Subscription
Term-based software licenses | Upon shipment or made available for download (point in time) | Within 90 days of shipment except for certain subscription licenses which are paid for over time | Residual approach
Software-as-a-service (SaaS) | Ratably over the course of the contract (over time) | Annually or at the beginning of the contract period | Observable in transactions without multiple performance obligations
Perpetual License
Perpetual software licenses | Upon shipment or made available for download (point in time) | Within 90 days of shipment | Residual approach
Customer Support
Software updates | Ratably over the course of the support contract (over time) | At the beginning of the contract period | Observable in renewal transactions
Customer support | Ratably over the course of the support contract (over time) | At the beginning of the contract period | Observable in renewal transactions
Other Services
Other professional services (except for education services) | As work is performed (over time) | Within 90 days of services being performed | Observable in transactions without multiple performance obligations
Education services | When the class is taught (point in time) | Within 90 days of services being performed | Observable in transactions without multiple performance obligations
Judgments related to revenue recognition Most of our contracts with customers contain multiple performance obligations. For these contracts, we evaluate and account for individual performance obligations separately if they are determined to be distinct. The transaction price is allocated to the separate performance obligations on a relative standalone selling price basis. Standalone selling prices of software licenses (both perpetual and term-based) are typically estimated using the residual approach. Standalone selling prices for SaaS, customer support contracts, and other services are typically estimated based on observable transactions when these services are sold on a standalone basis. We recognize revenue net of sales tax. Disaggregation of Revenues We disaggregate revenues from contracts with customers into geographical regions. Our Americas region includes the United States, Canada, and Latin America. Our International region primarily includes Europe, Middle East, Africa, Australia, India, Southeast Asia, and China.
| Three Months Ended September 30, |  | Six Months Ended September 30,
| 2024 |  | 2023 |  | 2024 |  | 2023
Americas | $ | 144,408 |  |  | $ | 120,300 |  |  | $ | 283,133 |  |  | $ | 242,424 |
International | 88,870 |  |  | 80,697 |  |  | 174,817 |  |  | 156,723 |
Total revenues | $ | 233,278 |  |  | $ | 200,997 |  |  | $ | 457,950 |  |  | $ | 399,147 |
Remaining Performance Obligations Remaining performance obligations represent expected future revenue from existing contracts where performance obligations are unsatisfied or partially unsatisfied at the end of the reporting period. Remaining performance obligations include unfulfilled contracts at the end of a given period and can include subscription arrangements (term-based licenses and SaaS agreements), customer support and other services. As of September 30, 2024, our remaining performance obligations (inclusive of deferred revenues) were $662,659, of which approximately 65% is expected to be recognized as revenue over the next 12 months and the remainder recognized thereafter. Remaining performance obligations, excluding deferred revenue, related to subscription arrangements, customer support revenue and other services were $46,761, $35,645, and $23,683, respectively. Of these balances, we expect approximately 70% of subscription arrangements, 39% of customer support and 100% of other services to be recognized as revenue over the next 12 months and the remainder recognized thereafter. We expect approximately 46% of subscription arrangements and 10% of customer support remaining performance obligations to be recognized as revenue in the third quarter of fiscal 2025. These balances represent transactions consisting primarily of early renewals, unbilled and undelivered support and other services, and orders received prior to the last day of the quarter that were not delivered or provisioned to customers. Remaining performance obligations will fluctuate period to period. We do not believe the amount of remaining performance obligations is indicative of future sales or revenue or that the mix at the end of any given period correlates with actual sales performance. Information about Contract Balances Amounts collected in advance of services being provided are accounted for as deferred revenue. Nearly all of our deferred revenue balance is related to SaaS arrangements, customer support, and other services. In some arrangements we allow customers to pay for term-based licenses over the term of the software license. Amounts recognized as revenue in excess of amounts billed are recorded as unbilled receivables. Unbilled receivables which are anticipated to be invoiced in the next twelve months are included in accounts receivable on the consolidated balance sheets. Long-term unbilled receivables are included in other assets. The opening and closing balances of our accounts receivable, unbilled receivables, and deferred revenues are as follows:
| Accounts receivable | Unbilled receivable (current) | Unbilled receivable (long-term) | Deferred revenue (current) | Deferred revenue (long-term)
Opening balance as of March 31, 2024 | $ | 196,951 |  | $ | 25,732 |  | $ | 14,471 |  | $ | 362,450 |  | $ | 168,472 |
Increase/(decrease) | (29,134) |  | 1,330 |  | 4,572 |  | (7,183) |  | 29,618 |
Ending balance as of September 30, 2024 | $ | 167,817 |  | $ | 27,062 |  | $ | 19,043 |  | $ | 355,267 |  | $ | 198,090 |
The net decrease in accounts receivable (inclusive of unbilled receivables) is primarily the result of the timing of our billings and cash collections. The net increase in deferred revenue is primarily the result of an increase in SaaS contracts which are billed upfront but recognized ratably over the contract period, partially offset by a decrease in professional service contracts. The amount of revenue recognized in the period that was included in the opening deferred revenue balance was $99,017 and $216,291 for the three and six months ended September 30, 2024, respectively. The vast majority of this revenue consists of SaaS arrangements and customer support. The amount of revenue recognized from performance obligations satisfied in prior periods was not significant.

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

X
- Definition The entire disclosure of revenue from contract with customer to transfer good or service and to transfer nonfinancial asset. Includes, but is not limited to, disaggregation of revenue, credit loss recognized from contract with customer, judgment and change in judgment related to contract with customer, and asset recognized from cost incurred to obtain or fulfill contract with customer. Excludes insurance and lease contracts. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 9 -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-9 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 10 -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-10 Reference 3: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 15 -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-15 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-12 Reference 5: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (b) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-12 Reference 6: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (c) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-12 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (d) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-12 Reference 8: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (e) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-12 Reference 9: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 13 -Subparagraph (b)(2) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-13 Reference 10: http://www.xbrl.org/2003/role/disclosureRef -Name Accounting Standards Codification -Topic 606 -Publisher FASB -URI https://asc.fasb.org/606/tableOfContent + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration