2.10 Revenue from operations

Accounting policy

The Group derives revenues primarily from software development and related services and from the licensing of software products. Arrangements with customers for software related services are mainly either on a fixed-price, fixed-timeframe or on a time-and-material basis.

Revenue on time-and-material contracts are recognized as the related services are performed and revenue from the end of the last billing to the balance sheet date is recognized as unbilled revenues. Revenue from fixed-price, fixed-timeframe contracts, where there is no uncertainty as to measurement or collectability of consideration, is recognized as per the percentage-of-completion method. When there is uncertainty as to measurement or ultimate collectability, revenue recognition is postponed until such uncertainty is resolved. Efforts or costs expended have been used to measure progress towards completion as there is a direct relationship between input and productivity. Provisions for estimated losses, if any, on uncompleted contracts are recorded in the period in which such losses become probable based on the current contract estimates. Costs and earnings in excess of billings are classified as unbilled revenue while billings in excess of costs and earnings are classified as unearned revenue. Deferred contract costs are amortized over the term of the contract. Maintenance revenue is recognized ratably over the term of the underlying maintenance arrangement.

In arrangements for software development and related services and maintenance services, the Group has applied the guidance in IAS 18, Revenue, by applying the revenue recognition criteria for each separately identifiable component of a single transaction. The arrangements generally meet the criteria for considering software development and related services as separately identifiable components. For allocating the consideration, the Group has measured the revenue in respect of each separable component of a transaction at its fair value, in accordance with principles given in IAS 18. The price that is regularly charged for an item when sold separately is the best evidence of its fair value. In cases where the Group is unable to establish objective and reliable evidence of fair value for the software development and related services, the Group has used a residual method to allocate the arrangement consideration. In these cases, the balance of the consideration, after allocating the fair values of undelivered components of a transaction has been allocated to the delivered components for which specific fair values do not exist.

License fee revenues are recognized when the general revenue recognition criteria given in IAS 18 are met. Arrangements to deliver software products generally have three elements: license, implementation and Annual Technical Services (ATS). The Group has applied the principles given in IAS 18 to account for revenues from these multiple element arrangements. Objective and reliable evidence of fair value has been established for ATS. Objective and reliable evidence of fair value is the price charged when the element is sold separately. When other services are provided in conjunction with the licensing arrangement and objective and reliable evidence of their fair values have been established, the revenue from such contracts are allocated to each component of the contract in a manner, whereby revenue is deferred for the undelivered services and the residual amounts are recognized as revenue for delivered elements. In the absence of objective and reliable evidence of fair value for implementation, the entire arrangement fee for license and implementation is recognized using the percentage-of-completion method as the implementation is performed. Revenue from client training, support and other services arising due to the sale of software products is recognized as the services are performed. ATS revenue is recognized rateably over the period in which the services are rendered.

Advances received for services and products are reported as client deposits until all conditions for revenue recognition are met.

The Group accounts for volume discounts and pricing incentives to customers as a reduction of revenue based on the ratable allocation of the discounts/ incentives amount to each of the underlying revenue transaction that results in progress by the customer towards earning the discount/ incentive. Also, when the level of discount varies with increases in levels of revenue transactions, the Group recognizes the liability based on its estimate of the customer's future purchases. If it is probable that the criteria for the discount will not be met, or if the amount thereof cannot be estimated reliably, then discount is not recognized until the payment is probable and the amount can be estimated reliably. The Group recognizes changes in the estimated amount of obligations for discounts in the period in which the change occurs. The discounts are passed on to the customer either as direct payments or as a reduction of payments due from the customer.

The Group presents revenues net of indirect taxes in its statement of comprehensive income.

Revenues for fiscal 2018, 2017 and 2016 are as follows:

(Dollars in millions)
Particulars	Year ended March 31,
	2018		2017		2016
Revenue from software services		10,619		9,895		9,210
Revenue from software products		320		313		291
		10,939		10,208		9,501