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

REVENUE | 6 Months Ended
--- | ---
Sep. 30, 2024
Revenue from Contract with Customer [Abstract] |
REVENUE | REVENUE Revenue Recognition Policy The Company exercises judgment and uses estimates in connection with determining the amounts of product and service revenues to be recognized in each accounting period. The Company derives revenues primarily from the sale of network management tools and cybersecurity solutions for service provider and enterprise customers, which include hardware, software, and service offerings. The Company's product sales consist of software only offerings and offerings which include hardware appliances with embedded software that are essential to providing customers the intended functionality of the solutions. The Company accounts for revenue once a legally enforceable contract with a customer has been approved by the parties and the related promises to transfer products or services have been identified. A contract is defined by the Company as an arrangement with commercial substance identifying payment terms, each party's rights and obligations regarding the products or services to be transferred and the amount the Company deems probable of collection. Customer contracts may include promises to transfer multiple products and services to a customer. Determining whether the products and services are considered distinct performance obligations that should be accounted for separately or as one combined performance obligation may require significant judgment. Revenue is recognized when control of the products or services are transferred to the Company's customers, in an amount that reflects the consideration the Company expects to be entitled to in exchange for products and services. Product revenue is typically recognized upon fulfillment, provided a legally enforceable contract exists, control has passed to the customer, and in the case of software products, when the customer has the rights and ability to access the software, and collection of the related receivable is probable. If any significant obligations to the customer remain post-delivery, typically involving obligations relating to installation and acceptance by the customer, revenue recognition is deferred until such obligations have been fulfilled. The Company's service offerings include installation, integration, extended warranty and maintenance services, post-contract customer support, stand-ready software-as-a-service (SAAS) and other professional services including consulting and training. The Company generally provides software and/or hardware support as part of product sales. Revenue related to the initial bundled software and hardware support is recognized ratably over the support period. In addition, customers can elect to purchase extended support agreements for periods after the initial software/hardware warranty expiration. Support services generally include rights to unspecified upgrades (when and if available), telephone and internet-based support, updates, bug fixes and hardware repair and replacement. Consulting services are recognized upon delivery or completion of performance depending on the terms of the underlying contract. Reimbursements of out-of-pocket expenditures incurred in connection with providing consulting services are included in services revenue, with the offsetting expense recorded in cost of service revenue. Training services include on-site and classroom training. Training revenues are recognized upon delivery of the training. Generally, the Company's contracts are accounted for individually. However, when contracts are closely interrelated and dependent on each other, it may be necessary to account for two or more contracts as one to reflect the substance of the group of contracts. Bundled arrangements are concurrent customer purchases of a combination of the Company's product and service offerings that may be delivered at various points in time. The Company allocates the transaction price among the performance obligations in an amount that depicts the relative standalone selling prices (SSP) of each obligation. Judgment is required to determine the SSP for each distinct performance obligation. The Company uses a range of amounts to estimate SSP for each of the products and services sold, based primarily on the performance obligation's historical pricing. The Company also considers its overall pricing objectives and practices across different sales channels and geographies, and market conditions. Generally, the Company has established SSP for a majority of its service performance obligations based on historical standalone sales. In certain instances, the Company has established SSP for services based upon an estimate of profitability and the underlying cost to fulfill those services. SSP has primarily been established for product performance obligations as the average or median selling price the performance obligation was recently sold for, whether sold alone or sold as part of a bundle transaction. The Company reviews sales of the product performance obligations on a quarterly basis and updates, when appropriate, its SSP for such performance obligations to ensure that it reflects recent pricing experience. The Company's products are distributed through its direct sales force and indirect distribution channels through alliances with resellers and distributors. Revenue arrangements with resellers and distributors are recognized on a sell-in basis; that is, when control of the product transfers to the reseller or distributor. The Company records consideration given to a customer as a reduction of revenue to the extent they have recorded revenue from the customer. With limited exceptions, the Company's return policy does not allow product returns for a refund. Returns have been insignificant to date. In addition, the Company has a history of successfully collecting receivables from its resellers and distributors. During the six months ended September 30, 2024, the Company recognized re ven ue of $183.5 million relate d t o the Company's deferred revenue balance reported at March 31, 2024. Performance Obligations Customer contracts may include promises to transfer multiple products and services to a customer. Determining whether the products and services are considered distinct performance obligations that should be accounted for separately or as one combined performance obligation may require significant judgment. The transaction price is allocated among performance obligations in bundled contracts in an amount that depicts the relative standalone selling prices of each obligation. For contracts involving distinct hardware and software licenses, the performance obligations are satisfied at a point in time when control is transferred to the customer. For standalone maintenance and post-contract support (PCS) the performance obligation is satisfied ratably over the contract term as a stand-ready obligation. For consulting and training services, the performance obligation may be satisfied over the contract term as a stand-ready obligation, satisfied over a period of time as those services are delivered, satisfied at the completion of the service when control has transferred, or the services have expired unused. Payments for hardware, software licenses, one-year maintenance, PCS and consulting services, are typically due up front with payment terms of 30 to 90 days. However, the Company does have contracts pursuant to which billings occur ratably over a period of years following the transfer of control for the contracted performance obligations. Payments on multi-year maintenance, PCS and consulting services are typically due in annual installments over the contract term. The Company did not have any material variable consideration su ch as obligations for returns, refunds or warranties at September 30, 2024. At September 30, 2024, the Company had total defer red revenue of $379.7 million, which represents the aggregate total contract price allocated to undelivered performance obligations. The Company expects to recognize $263.9 million, or 69%, of this revenue during the next 12 months, and expects to recognize the remaining $115.8 million, or 31%, of this revenue thereafter. Because of NetScout's revenue recognition policies, there are circumstances for which the Company does not recognize revenue relating to sales transactions that have been billed, but the related account receivable has not been collected. While the receivable represents an enforceable obligation, the Company does not believe its right to payment is unconditional, therefore for balance sheet presentation purposes, the Company has not recognized the deferred revenue or the related account receivable and no amounts appear in the consolidated balance sheets for such transactions because control of the underlying deliverable has not transferred. The aggregate amount of unrecognized accounts receivable and deferred revenue was $7.6 million and $5.9 million at September 30, 2024 and March 31, 2024, respectively. NetScout expects that the amount of billed and unbilled deferred revenue will change from quarter to quarter for several reasons, including the specific timing, duration and size of large customer support and service agreements, varying billing cycles of such agreements, th e specific timing of customer renewals, and foreign currency fluctuations. The Company did not have material significant financing components, or variable consideration or performance obligations satisfied in a prior period recognized during the six months ended September 30, 2024. Contract Balances The Company may receive payments from customers based on billing schedules as established by the Company's contracts. Contract assets relate to performance obligations where control has transferred to the customer in advance of scheduled billings. The Company records unbilled accounts receivable representing the right to consideration in exchange for goods or services that have been transferred to a customer conditional on the passage of time. Deferred revenue relates to scenarios where billings with an unconditional right to payment occur before all performance obligations are delivered or payments are received in advance of performance under the contract. Costs to Obtain Contracts The Company has determined that the only significant incremental costs incurred to obtain contracts with customers within the scope of Topic 606 are sales commissions paid to its employees. Sales commissions are recorded as an asset and amortized to expense ratably over the remaining performance periods of the related contracts with remaining performance obligations. The Company expenses costs as incurred for sales commissions when the amortization period would have been one year or less. At September 30, 2024, t he consolidated balance sheet included $9.0 million in assets related to sales commissions to be expensed in future periods. A balance of $4.8 million was included in prepaid expenses and other current assets, and a balance of $4.2 million was included in other assets in the Company's consolidated balance sheet at September 30, 2024. At March 31, 2024, the consolidated balance sheet included $9.3 million in assets related to sales commissions to be expensed in future periods. A balance of $4.8 million was included in prepaid expenses and other current assets, and a balance of $4.5 million was included in other assets in the Company's consolidated balance sheet at March 31, 2024. During the three and six months ended September 30, 2024 and 2023, respectively, the Company recognized $1.7 million, $1.7 million, $3.4 million and $3.4 million of amortization related to this sales commission asset, which is included in the sales and marketing expense line in the Company's consolidated statements of operations. Allowance for Credit Losses The Company continually monitors collections from its customers. The Company evaluates the collectability of its accounts receivable and determines the appropriate allowance for credit losses based on a combination of factors, including but not limited to, analysis of the aging schedules, past due balances, historical collection experience and prevailing economic conditions. The following table summarizes the activity in the allowance for credit losses (in thousands):
Balance at March 31, 2024 | $ | 479 |
Additions resulting in charges to operations | 28 |
Recoveries of previously reserved balances | (430) |
Deductions due to write-offs | (13) |
Balance at September 30, 2024 | $ | 64 |

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