Classify the right, not the ledger label
Ind AS 115 paragraphs 105–109 require an entity to distinguish contract assets, contract liabilities and unconditional receivables. A receivable exists when only the passage of time is required before payment is due. A contract asset reflects a right arising from transferred goods or services that remains conditional on something else. Neither an invoice heading nor the age of an unbilled balance decides the classification. This guide assumes the arrangement and revenue recognition already satisfy Ind AS 115; it focuses on the balance-sheet bridge.
Read the applicable text: ICAI Ind AS 115: paragraphs 105–109 and 116–118 ICAI 2025–26 compendium, Volume I.
Start with performance and enforceable payment terms
Read the contract’s billing milestones, acceptance conditions and right-to-payment terms. Assess whether a purported certification is a substantive condition or an administrative step. Do not assume every retention is a contract asset or every issued invoice is an unconditional receivable. First establish that revenue has been properly recognised for goods or services transferred; contract-asset presentation cannot cure premature revenue recognition.
Recognise the liability when consideration comes first
Paragraph 106 requires a contract liability when the customer pays, or an unconditional amount becomes due, before the entity transfers the relevant goods or services; use the earlier of payment and the due point. Accordingly, an unpaid advance invoice can produce both a receivable and a contract liability where the payment right is unconditional. A cash-only deferred-revenue report can miss that liability.
Reclassify without recording revenue twice
When a previously conditional right becomes unconditional, transfer the supported amount from contract asset to receivable. Collection then reduces the receivable; it is not a second sale. Link the reclassification to the event that removed the condition rather than a month-end instruction to clear all unbilled balances. Keep taxes, financing effects and credit losses in separate workings; the illustrations omit those effects explicitly.
Build the bridge at the proper contract level
Track performance and consideration for each accounting contract, after applying any relevant contract-combination analysis. Do not pool unrelated contracts merely because they share a customer code. Present unconditional receivables separately under paragraph 105. Paragraphs 116–118 also require information about opening/closing balances, payment-performance relationships and significant changes. Paragraph 116 additionally identifies revenue recognised from the opening contract-liability balance and revenue from performance obligations satisfied or partly satisfied in earlier periods; a clear movement schedule supports those disclosures without treating every movement as revenue.
Impairment and alternative captions
Paragraph 107 directs contract-asset impairment to Ind AS 109; paragraph 108 also applies Ind AS 109 to receivables. Reclassification is not a credit-loss exemption. Paragraph 109 allows alternative descriptions, but users must still be able to distinguish contract assets from receivables. Labels such as unbilled revenue or accrued income need a documented rights analysis and a reconciliation to the financial statements.
Six worked illustrations
All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.
Illustrative example 1: Performance with a substantive later condition
A company has properly recognised ₹8 lakh revenue for transferred services, with entitlement to billing conditional on completing a further milestone. No amount is unconditionally due or paid. On these assumptions the ₹8 lakh is a contract asset, not a receivable. The remaining milestone must be real; its wording alone is not conclusive evidence of substance.
Illustrative example 2: Unbilled does not always mean conditional
Transferred goods generate an unconditional ₹5 lakh right; only the 45-day payment period remains. Administrative invoicing will occur later. The balance is a ₹5 lakh receivable on the assumed terms, with contract asset ₹0 for that right. The example’s 45 days is a contract term, not an accounting threshold.
Illustrative example 3: Cash advance consumed by performance
The customer pays ₹12 lakh before performance. A contract liability of ₹12 lakh arises. Properly recognised performance revenue of ₹7 lakh then reduces that liability to ₹5 lakh, assuming no other billing or movements. The cash received is not all recognised as revenue merely because it is non-disputed.
Illustrative example 4: An unconditional advance becomes due before payment
Before performance, an unconditional ₹4 lakh payment becomes due and remains unpaid. The company records a ₹4 lakh receivable and ₹4 lakh contract liability under the stated conditions. Later collection gives cash ₹4 lakh and receivable ₹0, while the contract liability remains ₹4 lakh until performance or another justified movement.
Illustrative example 5: Condition removal and collection
Opening contract asset is ₹9 lakh. A substantive condition is removed for ₹6 lakh, which is reclassified to receivable; ₹4 lakh is then collected against that receivable. Closing contract asset is ₹3 lakh and receivable ₹2 lakh. Together these remaining balances are ₹5 lakh. No additional revenue arises from these two movements alone.
Illustrative example 6: Separate two accounting contracts
Contract A has ₹10 lakh recognised performance and ₹6 lakh consideration already paid, leaving a ₹4 lakh contract asset on the assumed conditional-right facts. Unrelated contract B has ₹7 lakh advance consideration and ₹2 lakh recognised performance, leaving a ₹5 lakh contract liability. Do not replace these by a single ₹1 lakh net liability merely because the customer is the same. No combination or offset right is assumed.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Confirm scope and recognition | Valid Ind AS 115 arrangement and performance conclusion. |
| 2 | Identify each accounting contract | Contract terms and any combination analysis. |
| 3 | Map performance | Transferred goods/services and supported revenue. |
| 4 | Map consideration | Cash, amounts due and billing schedules. |
| 5 | Test unconditional rights | Evidence that only passage of time remains. |
| 6 | Test remaining conditions | Milestone, acceptance or other substantive entitlement terms. |
| 7 | Build separate movements | Contract asset, receivable, cash and contract liability bridge. |
| 8 | Check advance amounts due | Unpaid unconditional advance and matching liability. |
| 9 | Assess credit losses | Ind AS 109 working for relevant assets. |
| 10 | Tie presentation and notes | Paragraphs 105–109 and 116–118 disclosure reconciliation. |
Sixteen practitioner FAQs
1. Is every unbilled balance a contract asset?
No. An unconditional right is presented as a receivable even if invoicing is administrative.
2. Is every invoice a receivable?
Inspect enforceability and conditions; the invoice label alone is insufficient.
3. What distinguishes a receivable under paragraph 108?
Only passage of time is required before payment is due.
4. Can performance without a qualifying revenue conclusion create a contract asset?
Contract-asset classification cannot validate prematurely recognised revenue.
5. What if a certification is merely administrative?
Assess its substance; an administrative step need not make an otherwise unconditional right conditional.
6. Is every retention conditional?
No. Analyse the terms rather than classifying all retentions alike.
7. Can an unpaid advance create a contract liability?
Yes, where an unconditional amount becomes due before performance under paragraph 106.
8. Does collecting that advance extinguish the performance obligation?
No. Collection reduces the receivable; the liability tracks the remaining obligation.
9. Does reclassification to receivable create revenue?
Not by itself. It changes presentation of the existing right.
10. Does collection of a receivable create revenue again?
No. Link it to the existing receivable and underlying recognition.
11. Can unrelated contracts be netted under one customer code?
Do not use a common customer code as a substitute for contract-level and presentation analysis.
12. Are the examples gross of GST?
They exclude taxes, financing effects and credit losses to isolate classification.
13. Are contract assets exempt from impairment?
No. Paragraph 107 requires assessment under Ind AS 109.
14. Are receivables also within Ind AS 109?
Yes, paragraph 108 directs their accounting to that standard.
15. Can alternative balance-sheet captions be used?
Paragraph 109 permits them while requiring sufficient distinction between contract assets and receivables.
16. What supports the balance disclosures?
Opening/closing balances, movement explanations and the relationship between payment terms and performance.
Official sources
ICAI Ind AS 115: paragraphs 105–109 and 116–118 ICAI 2025–26 compendium, Volume I