Company: PATH
Filing Date: 2025-03-24
Form Type: 10-K
Source: 0001734722-25-000007
Chunk: 158

Company: UiPath, Inc.
Filing Date: 2025-03-24
Form: 10-K
Item: Item 7
Chunk 158
---
 consolidated financial statements and amounts of revenue and expenses reported during the period. Our estimates are based on historical experience and various other assumptions that we believe to be reasonable under the circumstances, and we evaluate our estimates on an ongoing basis. The following are the accounting estimates that we believe have the most significant impact on our consolidated financial statements.

Revenue Recognition

We recognize revenue in accordance with ASC 606, Revenue from Contracts with Customers. ASC 606 requires recognition of revenue when control of promised goods or services is transferred to customers, in an amount that reflects the consideration we expect to be entitled to receive in exchange for those goods or services. Revenue recognition is inherently judgmental, particularly for complex arrangements that include multiple performance obligations, which are common for us. Our most significant judgment relates to allocation of the transaction price, specifically determining the SSP for each performance obligation, which impacts the pattern and timing of revenue recognition.

At the inception of a contract with a customer, we assess the goods or services promised to identify distinct performance obligations. The distinct performance obligations identified in our typical contracts include, but are not limited to, software licenses, SaaS, maintenance and support, and professional services. The pattern and timing of revenue recognition for each of these performance obligations varies. Specifically, revenue from licenses is recognized at the point in time at which the customer is able to use and benefit from the software, which is generally upon delivery to the customer or upon commencement of the renewal term; revenue from SaaS and maintenance and support services is recognized ratably over the contract term; and revenue from professional services is recognized over time as the services are performed.

Most of our contracts contain multiple of these performance obligations. In such arrangements, the transaction price is allocated to the separate performance obligations on a relative SSP basis. Since the performance obligations have different revenue recognition models, SSP estimates directly affect the timing and amount of revenue recognized during a particular period. For example, if the SSP of a license delivered in one period is greater than the SSP of professional services that are sold with that license but delivered in future periods, a greater portion of the transaction price will be recognized at contract inception in the current period versus over time as the services are performed in later periods.

Whenever possible, we allocate the transaction price based on observable SSP, which is the price of the same good or service in standalone sales to similar customers in similar circumstances. If observable SSP is not available, we estimate the SSP using data that may include historical prices, discounting practices, list prices, cost data, and other observable inputs. We may