XML 24 R12.htm IDEA: XBRL DOCUMENT
v3.25.3

REVENUE RECOGNITION | 3 Months Ended
--- | ---
Sep. 30, 2025
Revenue from Contract with Customer [Abstract] |
REVENUE RECOGNITION | NOTE 3 – REVENUE RECOGNITION The Company determines revenue recognition through the following steps:
● | Identification of the contract, or contracts, with a customer;
● | Identification of the performance obligations in the contract;
● | Determination of the transaction price;
● | Allocation of the transaction price to the performance obligations in the contract; and
● | Recognition of revenue when, or as, the Company satisfies a performance obligation.
The Company records the amount of revenue and related costs by considering whether the entity is a principal (gross presentation) or an agent (net presentation) by evaluating the nature of its promise to the customer. Revenue is presented net of sales, value-added and other taxes collected from customers and remitted to government authorities. The Company has two primary revenue streams: core revenue and non-core revenue. Core Revenue The Company generates its core revenue from the following sources: (1) software licenses, (2) services, which include implementation and consulting services, and (3) subscription and support, which includes post contract support, of its enterprise software solutions for the lease and finance industry. The Company offers its software using the same underlying technology via two models: a traditional on-premises licensing model and a subscription model. The on-premises model involves the sale or license of software on a perpetual basis to customers who take possession of the software and install and maintain the software on their own hardware. Under the subscription delivery model, the Company provides access to its software on a hosted basis as a service and customers generally do not have the contractual right to take possession of the software. Non-Core Revenue The Company generates its non-core revenue by providing business process outsourcing (“BPO”), other IT services and internet services. Performance Obligations A performance obligation is a promise in a contract to transfer a distinct good or service to the customer and is the unit of account under Topic 606. The transaction price is allocated to each distinct performance obligation and recognized as revenue when, or as, the performance obligation is satisfied by transferring the promised good or service to the customer. The Company identifies and tracks the performance obligations at contract inception so that the Company can monitor and account for the performance obligations over the life of the contract. The Company’s contracts which contain multiple performance obligations generally consist of the initial purchase of subscription or licenses and a professional services engagement. License purchases generally have multiple performance obligations as customers purchase post contract support and services in addition to the licenses. The Company’s single performance obligation arrangements are typically post contract support renewals, subscription renewals and services engagements. For contracts with multiple performance obligations where the contracted price differs from the standalone selling price (“SSP”) for any distinct good or service, the Company may be required to allocate the contract’s transaction price to each performance obligation using its best estimate for the SSP. NETSOL TECHNOLOGIES, INC. Notes to Condensed Consolidated Financial Statements September 30, 2025 (Unaudited) Software Licenses Transfer of control for software is considered to have occurred upon delivery of the product to the customer. The Company’s typical payment terms tend to vary by region, but its standard payment terms are within 30 days of invoice. Subscription Subscription revenue is recognized ratably over the initial subscription period committed to by the customer commencing when the product is made available to the customer. The initial subscription period is typically 12 to 60 months. The Company generally invoices its customers in advance in quarterly or annual installments and typical payment terms provide that customers make payment within 30 days of invoice. Post Contract Support Revenue from support services and product updates, referred to as subscription and support revenue, is recognized ratably over the term of the maintenance period, which in most instances is one year. Software license updates provide customers with rights to unspecified software product updates and patches released during the term of the support period on a when-and-if available basis. The Company’s customers purchase both product support and license updates when they acquire new software licenses. In addition, most customers renew their support services contracts annually and typical payment terms provide that customers make payment within 30 days of invoice. Professional Services Revenue from professional services is typically comprised of implementation, development, data migration, training, or other consulting services. Consulting services are generally sold on a time-and-materials or fixed fee basis and can include services ranging from software installation to data conversion and building non-complex interfaces to allow the software to operate in integrated environments. The Company recognizes revenue for time-and-materials arrangements as the services are performed. In fixed fee arrangements, revenue is recognized as services are performed as measured by costs incurred to date, compared to total estimated costs to complete the services project. Management applies judgment when estimating project status and the costs necessary to complete the services projects. Several internal and external factors can affect these estimates, including labor rates, utilization and efficiency variances and specification and testing requirement changes. Services are generally invoiced upon milestones in the contract or upon consumption of the hourly resources and payments are typically due 30 days after invoice. BPO and Internet Services Revenue from BPO services is recognized based on the stage of completion which is measured by reference to labor hours incurred to date as a percentage of total estimated labor hours for each contract. Internet services are invoiced either monthly, quarterly, or half yearly in advance to the customers and revenue is recognized ratably overtime on a monthly basis. Disaggregated Revenue The Company disaggregates revenue from contracts with customers by category — core and non-core, as it believes it best depicts how the nature, amount, timing and uncertainty of revenue and cash flows are affected by economic factors. NETSOL TECHNOLOGIES, INC. Notes to Condensed Consolidated Financial Statements September 30, 2025 (Unaudited) The Company’s disaggregated revenue by category is as follows: SCHEDULE OF DISAGGREGATED REVENUE BY CATEGORY
|  | 2025 |  |  | 2024 |
|  | For the Three Months Ended September 30, |
|  | 2025 |  |  | 2024 |
Core: |  |  |  |  |  |  |  |
License |  | $ | 72,225 |  |  | $ | 1,229 |
Subscription and support |  |  | 8,960,555 |  |  |  | 8,192,471 |
Services |  |  | 5,094,911 |  |  |  | 5,530,629 |
Total core revenue, net |  |  | 14,127,691 |  |  |  | 13,724,329 |
Non-Core: |  |  |  |  |  |  |  |
Services |  |  | 884,232 |  |  |  | 874,169 |
Total non-core revenue, net |  |  | 884,232 |  |  |  | 874,169 |
Total net revenue |  | $ | 15,011,923 |  |  | $ | 14,598,498 |
Significant Judgments Due to the complexity of certain contracts, the actual revenue recognition treatment required under Topic 606 for the Company’s arrangements may be dependent on contract-specific terms and may vary in some instances. Judgment is required to determine the SSP for each distinct performance obligation. The Company rarely licenses or sells products on a stand-alone basis, so the Company is required to estimate the range of SSPs for each performance obligation. In instances where SSP is not directly observable because the Company does not sell the license, product, or service separately, the Company determines the SSP using information that may include market conditions and other observable inputs. In making these judgments, the Company analyzes various factors, including its pricing methodology and consistency, size of the arrangement, length of term, customer demographics and overall market and economic conditions. Based on these results, the estimated SSP is set for each distinct product or service delivered to customers. The most significant inputs involved in the Company’s revenue recognition policies are: The (1) stand-alone selling prices of the Company’s software license, and the (2) the method of recognizing revenue for installation/customization, and other services. The stand-alone selling price of the licenses was measured primarily through an analysis of pricing that management evaluated when quoting prices to customers. Although the Company has no history of selling its software separately from post contract support and other services, the Company does have historical experience with amending contracts with customers to provide additional modules of its software or providing those modules at an optional price. This information guides the Company in assessing the stand-alone selling price of the Company’s software, since the Company can observe instances where a customer had a particular component of the Company’s software that was essentially priced separate from other goods and services that the Company delivered to that customer. The Company recognizes revenue from implementation and customization services using the percentage of estimated “person-days” that the work requires. The Company believes the level of effort to complete the services is best measured by the amount of time (measured as an employee working for one day on implementation/customization work) that is required to complete the implementation or customization work. The Company reviews its estimate of person-days required to complete implementation and customization services each reporting period. Revenue is recognized over time for the Company’s subscription, post contract support and fixed fee professional services that are separate performance obligations. For the Company’s professional services, revenue is recognized over time, generally using costs incurred or hours expended to measure progress. Judgment is required in estimating project status and the costs necessary to complete projects. Several internal and external factors can affect these estimates, including labor rates, utilization, specification variances and testing requirement changes. NETSOL TECHNOLOGIES, INC. Notes to Condensed Consolidated Financial Statements September 30, 2025 (Unaudited) If a group of agreements are entered at or near the same time and so closely related that they are, in effect, part of a single arrangement, such agreements are deemed to be combined as one arrangement for revenue recognition purposes. The Company exercises significant judgment to evaluate the relevant facts and circumstances in determining whether agreements should be accounted for separately or as a single arrangement. The Company’s judgments about whether a group of contracts comprise a single arrangement can affect the allocation of consideration to the distinct performance obligations, which could have an effect on results of operations for the periods involved. If a contract includes variable consideration, the Company exercises judgment in estimating the amount of consideration to which the entity will be entitled in exchange for transferring the promised goods or services to a customer. When estimating variable consideration, the Company will consider all relevant facts and circumstances. Variable consideration will be estimated and included in the contract price only when it is probable that a significant reversal in the amount of revenue recognized will not occur. Contract Balances The timing of revenue recognition may differ from the timing of invoicing to customers, and these timing differences result in receivables, contract assets (revenues in excess of billings), or contract liabilities (unearned revenue) on the Company’s Consolidated Balance Sheets. The Company records revenues in excess of billings when the Company has transferred goods or services but does not yet have the right to consideration. The Company records unearned revenue when the Company has received or has the right to receive consideration but has not yet transferred goods or services to the customer. The revenues in excess of billings are transferred to receivables when the rights to consideration become unconditional, usually upon completion of a milestone. The Company’s revenues in excess of billings and unearned revenue are as follows: SCHEDULE OF REVENUES IN EXCESS OF BILLINGS AND DEFERRED REVENUE
|  | As of |  |  | As of |
|  | September 30, 2025 |  |  | June 30, 2025 |
Revenues in excess of billings |  | $ | 14,875,704 |  |  | $ | 19,134,385 |
Unearned revenue |  | $ | 3,735,828 |  |  | $ | 3,029,850 |
The Company’s unearned revenue reconciliation is as follows: SCHEDULE OF UNEARNED REVENUE RECONCILIATION
|  | Unearned Revenue |
Balance at June 30, 2025 |  | $ | 3,029,850 |
Invoiced |  |  | 8,793,181 |
Revenue Recognized |  |  | (8,003,905 | )
Adjustments |  |  | (83,298 | )
Balance at September 30, 2025 |  | $ | 3,735,828 |
During the three months ended September 30, 2025, the Company recognized revenue of $1,570,000, that was included in the unearned revenue balance at the beginning of the period. All other activity in unearned revenue is due to the timing of invoicing in relation to the timing of revenue recognition. NETSOL TECHNOLOGIES, INC. Notes to Condensed Consolidated Financial Statements September 30, 2025 (Unaudited) Revenue allocated to the remaining performance obligations represents the transaction price allocated to the performance obligations that are unsatisfied, or partially unsatisfied, which includes unearned revenue and amounts that will be invoiced and recognized as revenue in future periods. Contracted but unsatisfied performance obligations were approximately $18,664,000 as of September 30, 2025, of which the Company estimates to recognize approximately $13,440,000 in revenue over the next 12 months and the remainder over an estimated 3 years thereafter. Actual revenue recognition depends in part on the timing of software modules installed at various customer sites. Accordingly, some factors that affect the Company’s revenue, such as the availability and demand for modules within customer geographic locations, is not entirely within the Company’s control. In instances where the timing of revenue recognition differs from the timing of invoicing, the Company has determined that its contracts generally do not include a significant financing component. The primary purpose of invoicing terms is to provide customers with simplified and predictable ways of purchasing the Company’s products and services, and not to facilitate financing arrangements. Unearned Revenue The Company typically invoices its customers for subscription and support fees in advance on a quarterly or annual basis, with payment due at the start of the subscription or support term. Unpaid invoice amounts for non-cancelable license and services starting in future periods are included in accounts receivable and unearned revenue. Practical Expedients and Exemptions There are several practical expedients and exemptions allowed under Topic 606 that impact timing of revenue recognition and the Company’s disclosures. The Company has applied the following practical expedients:
| ● | The Company does not evaluate a contract for a significant financing component if payment is expected within one year or less from the transfer of the promised items to the customer.
| ● | The Company generally expenses sales commissions and sales agent fees when incurred when the amortization period would have been one year or less or the commissions are based on cashed received. These costs are recorded within sales and marketing expense in the Consolidated Statement of Operations.
| ● | The Company does not disclose the value of unsatisfied performance obligations for contracts for which the Company recognizes revenue at the amount to which it has the right to invoice for services performed (applies to time-and-material engagements).
Costs to Obtain a Contract The Company does not have a material amount of costs to obtain a contract capitalized at any balance sheet date. In general, the Company incurs few direct incremental costs of obtaining new customer contracts. The Company rarely incurs incremental costs to review or otherwise enter into contractual arrangements with customers. In addition, the Company’s sales personnel receive fees that are referred to as commissions, but that are based on more than simply signing up new customers. The Company’s sales personnel are required to perform additional duties beyond new customer contract inception dates, including fulfillment duties and collections efforts.

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 7 -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-7 Reference 2: 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 3: 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 4: 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 5: 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 6: 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 7: 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 8: 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 9: 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 10: 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 11: 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