
Bill-and-hold and Customer Acceptance under Ind AS 115
Where practice commonly goes wrong
Year-end pressure often encourages teams to begin with the desired journal entry. A stronger approach begins with the underlying rights, obligations and economic events. For Bill-and-hold and Customer Acceptance under Ind AS 115, the decisive work often happens before any number is calculated. The team must recognise revenue before physical delivery only when strict control and customer-request conditions are satisfied and acceptance is substantive. Contract wording, operational practice and reporting-date evidence may point in different directions unless the accounting question is framed precisely. Ind AS 115 is designed to depict the transfer of promised goods or services to customers in an amount reflecting consideration to which the entity expects to be entitled. The analysis must connect the business fact, the applicable principle, the measurement method and the financial-statement message.
The technical boundary
A sound paper separates scope, recognition, measurement and presentation. The scope of Ind AS 115 covers contracts with customers, excluding leases, insurance contracts, financial instruments and specified non-monetary exchanges. Its operating logic is straightforward even when the facts are not: The five-step model identifies contracts and performance obligations, determines and allocates transaction price, and recognises revenue when or as control transfers, with separate requirements for contract costs and presentation. Applied to bill-and-hold and customer acceptance, this means the team must identify the triggering event, the relevant rights or obligations, and the information available at the reporting date before selecting a measurement method. Disclosure is the final part of the accounting, not an afterthought.
A disciplined close workflow
The work is easier to audit when it follows a visible sequence rather than a collection of disconnected spreadsheets:
- Frame the question. recognise revenue over time or at a point in time and reconcile contract balances, costs and disclosures. Link it explicitly to bill-and-hold and customer acceptance.
- Build the evidence base. identify enforceable customer contracts and combine or modify them where required. Trace it to the reported outcome for bill-and-hold and customer acceptance.
- Apply the accounting test. identify distinct promised goods, services and material rights. Record its effect on recognition, measurement or disclosure for bill-and-hold and customer acceptance.
- Quantify and reconcile. estimate fixed and variable consideration, financing effects and non-cash consideration. Give the conclusion on bill-and-hold and customer acceptance a date and an accountable owner.
Applying the analysis to a realistic fact pattern
Imagine that the year-end reviewer receives this fact pattern: A customer requests delayed shipment after production is complete but the goods remain in the seller's warehouse. The matter involves a carrying amount, transaction value or exposure of approximately ₹381 crore. Rather than starting with a spreadsheet output, the reviewer asks management to allocate transaction price using observable or estimated stand-alone selling prices and recognise revenue over time or at a point in time and reconcile contract balances, costs and disclosures. The answers should make clear how the entity intends to recognise revenue before physical delivery only when strict control and customer-request conditions are satisfied and acceptance is substantive and which evidence supports that intention or conclusion.
For bill-and-hold and customer acceptance, the likely source of misstatement is including variable consideration without applying the constraint. The strongest response is a calculation supported by delivery, acceptance, usage and progress evidence, together with a ledger-to-note reconciliation. Where judgement remains significant, the note should describe the entity-specific uncertainty and not simply reproduce the wording of Ind AS 115.
Audit evidence and challenge points
The following failure modes commonly create audit adjustments or weak disclosures:
- Confusing a contract asset with an unconditional receivable. The risk increases when different teams own the contract, model, journal and note disclosure. For bill-and-hold and customer acceptance, the working paper should show why the entity’s facts do or do not create this risk.
- Starting revenue analysis from invoice timing. This usually happens when the ledger label is accepted without tracing the underlying terms and timing. For bill-and-hold and customer acceptance, the working paper should show why the entity’s facts do or do not create this risk.
Connected standards and communication
A defensible file would normally contain:
- Variable-consideration, financing and selling-price models, specifically cross-referenced to the conclusion on bill-and-hold and customer acceptance and the affected financial-statement line items.
- Delivery, acceptance, usage and progress evidence, specifically cross-referenced to the conclusion on bill-and-hold and customer acceptance and the affected financial-statement line items.
- Contract-asset, receivable, liability and cost roll-forwards, specifically cross-referenced to the conclusion on bill-and-hold and customer acceptance and the affected financial-statement line items.
The presentation and disclosure review should be performed at the same time as the accounting analysis. Ind AS 115 often interacts with Ind AS 109, Ind AS 116 and Ind AS 12. The memorandum should allocate each issue to the correct standard, reconcile note amounts to the ledger and explain material judgement in entity-specific language. For bill-and-hold and customer acceptance, the paper should show where each material assumption is used.
Learning conclusion
The standard does not reward complexity for its own sake; it rewards faithful classification, consistent measurement and transparent communication. The practical objective is a conclusion that another competent reviewer can reproduce from the retained evidence. For bill-and-hold and customer acceptance, consistency across contract review, model, ledger, primary statements and notes is the strongest sign that the accounting has been applied in substance. Building that discipline is central to mastering Ind AS 115, not merely passing a technical checklist.
Continue learning on JUMOQ
Turn this guidance into practical capability
Explore focused courses, worked examples and activities related to this topic.
Explore related courses →References
- Ind AS 115, Revenue from Contracts with Customers — ICAI Compendium of Indian Accounting Standards 2025–2026
- JUMOQ learning pathway — Indian Accounting Standards
