Contract Assets vs Contract Liabilities
Under Ind AS 115, a contract asset arises when an entity has transferred goods or services to a customer before the customer pays, while a contract liability (deferred revenue) arises when the customer pays before the entity performs — both reflecting timing differences between performance and billing.
Ind AS 115 replaced the earlier, more fragmented guidance on revenue recognition and introduced a new terminology of contract assets and contract liabilities that reflects the economic timing difference between when an entity earns the right to receive consideration and when it actually receives that consideration from the customer.
A contract asset represents an entity's right to receive payment for goods or services already transferred, but where that right is conditional on something other than the mere passage of time. It differs from a trade receivable in a critical way: a trade receivable is an unconditional right to payment — the company has performed and simply awaits settlement. A contract asset is a conditional right — performance has partially occurred but the right to bill has not yet crystallised, typically because a milestone must be met or additional performance obligations remain. In the Indian IT services sector, this distinction is particularly relevant for large fixed-price projects where billing milestones and revenue recognition percentages do not coincide. Revenue may be recognised on a percentage-of-completion basis, creating a contract asset for unbilled revenue that will only become billable upon reaching the next client-agreed milestone.
A contract liability — the formal name for what practitioners call deferred revenue — represents the obligation to transfer goods or services for which the entity has already received consideration. Advance payments for annual maintenance contracts, prepaid software licences, and retainers in professional services all create contract liabilities. As the entity delivers, the liability is reclassified to revenue.
The same contract can give rise to both a contract asset and a contract liability simultaneously if multiple performance obligations are involved, some of which have been over-delivered relative to billing and others under-delivered. Companies must present the net position per contract — netting contract assets against contract liabilities — on a contract-by-contract basis and present the aggregate net asset or net liability position on the face of the balance sheet.
For financial analysts, monitoring trends in contract assets is valuable. A rising contract asset balance without a corresponding increase in revenue may signal collection risk, aggressive revenue recognition ahead of billing milestones, or project delays that are preventing the billing trigger from being reached. A rising contract liability, on the other hand, generally signals healthy advance booking activity, though it also creates future execution obligations that must be monitored.