Contract Liability explained: this guide covers what it means, who it applies to, the step-by-step process, documents required, fees, due dates and penalties in India — so you can stay compliant with confidence and avoid costly mistakes.
Two neighbouring lines that catch what does not fit anywhere else on the liability side — one for financial liabilities, one created by the revenue standard.
Other financial liabilities
Presented as a separate line item on the face of the balance sheet under "Financial Liabilities". It collects items which meet the definition of financial liabilities as per Ind AS 32, the examples given being:
- contingent consideration;
- derivative contracts;
- financial guarantee contracts issued; and
- contractually reimbursable expenses.
The last one is the mirror image of the asset side, where contractually reimbursable expenses are excluded from trade receivables and classified as other financial assets. The same item, in the opposite direction, is excluded from trade payables for the same reason.
Ind AS 115 requires that when either party has performed, a contract liability is presented in the balance sheet. It arises where a customer pays consideration, or an entity has a right to an amount of consideration that is unconditional (i.e. a receivable), before the entity transfers a good or service — and the entity presents the contract as a contract liability when the payment is made or the payment is due, whichever is earlier.
The second limb is the one that catches people out. A contract liability can arise without any cash having been received: once the entity has an unconditional right to invoice, it recognises both a receivable and a contract liability, because it has not yet performed.
That produces the apparently odd result of a receivable and a liability recognised simultaneously for the same contract — which is exactly why the offsetting question follows: a company shall apply the requirements of Ind AS 1 and Ind AS 32 to determine whether it is appropriate to offset contract assets and liabilities against other balance sheet items such as receivables.
Current or non-current
Unless a company presents its balance sheet on a liquidity basis, it will need to present contract liabilities arising from contracts within the scope of Ind AS 115 as current or non-current, applying the general current/non-current classification requirements.
For a company under Ind AS Schedule III the liquidity option is not available on the face, so the split is always required — the same position as for contract assets.
Where a non-current head has no current twin
The general solution applies on the liability side as it does on the asset side: since Ind AS Schedule III permits the use of additional line items, the current portion should be classified under the "Current" category of the respective balance as a separate line item, and other relevant disclosures should be made.
Contract liability versus advance received
| Contract liability | Advance under other liabilities | |
|---|---|---|
| Arises from | A contract with a customer under Ind AS 115 | Amounts received in advance that are not financial liabilities under Ind AS 32 |
| Example | Payment received or due before transfer of the good or service | Amount received in advance against goods to be sold or services to be provided |
| Presented in | Contract liability, split current / non-current | Other current or non-current liabilities |
The overlap is real and the classification depends on whether the arrangement is a contract with a customer within Ind AS 115 and whether the obligation meets the Ind AS 32 financial liability definition.
Common mistakes
- Recognising a contract liability only when cash is received.
- Offsetting contract liabilities against receivables without applying Ind AS 1 and 32.
- Presenting derivatives or issued financial guarantees outside other financial liabilities.
- Leaving contract liabilities unsplit between current and non-current.