A customer invoice does not settle the accounting
Under Ind AS 115 paragraphs 70–72, consideration payable to a customer generally reduces the transaction price and revenue unless it is paid for a distinct good or service transferred to the entity. A payment for a distinct purchase is accounted for like other supplier purchases, but any excess over its fair value reduces the transaction price. If that fair value cannot reasonably be estimated, the whole payment reduces the transaction price. Classifying every customer payment as marketing expense can therefore overstate revenue.
Read the applicable text: MCA: Ind AS 115, paragraphs 70–72 and referenced distinctness requirements.
Map the payment population
Include cash, credits and applicable coupons or vouchers. The standard’s scope also refers to parties purchasing the entity’s goods or services from its customer. Trace the commercial chain rather than screening only payments to the immediate invoice debtor. Record rebates, credits and claimed service fees with their contract references and beneficiaries. Whether a particular arrangement belongs in this population requires facts, not the payee name alone.
Establish a distinct purchase before measuring it
Identify the actual goods or services the customer transfers and apply the distinctness requirements referred to in paragraphs 26–30. Retain enforceable terms, evidence of delivery or performance and the benefit received. An invoice labelled promotion or listing fee is not conclusive. Conversely, a real distinct purchase should not automatically be netted against sales simply because its supplier is also a customer. Its asset or expense classification follows the applicable purchase accounting.
Use fair value as a separate control
Support the fair value of the distinct purchase using relevant evidence and explain comparability. The payment amount and fair value need not be equal. Divide an excess payment between the supported purchase and the transaction-price reduction. If the fair value cannot reasonably be estimated, paragraph 71 specifies the whole-payment reduction; do not use a convenient unsupported value to preserve gross revenue.
Apply the later-event timing rule
For consideration accounted for as a transaction-price reduction, paragraph 72 uses the later of recognition of revenue for the related transfer and payment or promise to pay the consideration. A promise may be conditional on a future event or implied by customary business practices. Consequently, waiting for a cash payment or formal credit note may be incorrect. Variable amounts also require the estimation and constraint assessment in paragraphs 50–58, as referenced by paragraph 70. Apply those requirements alongside the timing analysis; do not assume an invoice or cash date alone determines the accounting.
Keep a three-way reconciliation
Link the sales contract and revenue schedule, the customer-payment or purchase ledger and the evidence supporting distinctness, fair value and timing. Document the exact amount reduced from transaction price and the amount treated as a purchase. Avoid counting a credit twice through both a net sales report and an additional adjustment journal. This guide addresses financial reporting for entities applying Ind AS; it does not decide GST credit-note treatment, income-tax deductibility or the legal set-off of debts.
Six worked illustrations
All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.
Illustrative example 1: No distinct service received
Assume related sales consideration is ₹10,00,000 and a ₹50,000 customer payment buys no distinct good or service. The adjusted transaction price is ₹9,50,000. Apply the standard’s recognition requirements and timing rule; the ₹50,000 is not automatically a separate operating expense.
Illustrative example 2: Distinct purchase at supported fair value
The customer provides a distinct service, payment and supported fair value both being ₹40,000. On these facts the purchase amount is ₹40,000 and excess over fair value is ₹0. Determine expense or asset recognition under the applicable purchase requirements rather than assuming immediate expense solely from this test.
Illustrative example 3: Payment above fair value
A distinct service has reasonably estimated fair value ₹60,000 but the payment is ₹90,000. The purchase component is ₹60,000 and transaction-price reduction ₹30,000. For otherwise unchanged ₹8,00,000 related sales consideration, the adjusted transaction price is ₹7,70,000.
Illustrative example 4: Fair value cannot reasonably be estimated
Assume ₹75,000 is payable for a customer-provided item, but its fair value cannot reasonably be estimated. Paragraph 71’s rule reduces transaction price by the full ₹75,000. An assumed ₹12,00,000 price therefore becomes ₹11,25,000; do not invent an unsupported purchase value.
Illustrative example 5: Later-event timing
Assume related goods revenue is recognised on 10 June and a promise to pay ₹20,000 is first made on 25 June, with no earlier implied promise. The later event is 25 June, 15 days after the revenue event. Payment on 5 July does not postpone the reduction merely because cash moves later.
Illustrative example 6: Credit counted twice
Gross sales of ₹5,00,000 less a customer credit of ₹30,000 are already shown as net revenue of ₹4,70,000. A second ₹30,000 reduction would report ₹4,40,000 and understate the already adjusted population by ₹30,000. Reconcile the source report before posting another journal.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Confirm the framework | Ind AS reporting applicability and period. |
| 2 | Identify beneficiaries | Immediate customers and relevant downstream purchasers. |
| 3 | Collect payment promises | Cash, credits, vouchers, terms and customary practices. |
| 4 | Link related sales | Contracts, goods or services and revenue population. |
| 5 | Test distinctness | Actual transfer and paragraphs 26–30 assessment. |
| 6 | Support fair value | Comparable evidence and reasonable-estimation conclusion. |
| 7 | Split purchase and excess | Documented calculation under paragraph 71. |
| 8 | Assess variable amounts | Estimation and constraint analysis where applicable. |
| 9 | Apply the later-event rule | Revenue-transfer and payment-or-promise dates. |
| 10 | Reconcile postings | Gross sales, net reports, purchase entries and adjustments. |
Sixteen practitioner FAQs
1. Must every payment to a customer reduce revenue?
The general rule has an exception for a distinct good or service transferred to the entity, subject to the fair-value requirements.
2. Does a marketing invoice prove distinctness?
No. Analyse the actual promised and delivered benefit under the standard.
3. Can credits and vouchers be within scope?
Yes. Paragraph 70 includes relevant credit and other items applied against amounts owed.
4. Are only immediate customers relevant?
The provision also refers to other parties purchasing the entity’s goods or services from its customer.
5. What happens to a genuine distinct purchase?
Account for it in the same way as other supplier purchases, subject to the excess-payment rule.
6. Must every such purchase be expensed immediately?
No. Apply the relevant asset or expense recognition requirements.
7. What if payment exceeds fair value?
The excess reduces the transaction price.
8. What if fair value cannot reasonably be estimated?
Paragraph 71 requires the whole consideration payable to reduce the transaction price.
9. Is the customer’s invoice automatically fair value?
No. Retain a supported fair-value assessment.
10. Does the revenue reduction always wait for cash payment?
No. Payment or a promise to pay is relevant under the later-event rule.
11. Can an implied promise matter?
Yes. Paragraph 72 refers to a promise implied by customary business practices.
12. Can a conditional promise matter before the future event?
The paragraph expressly includes payment promises conditional on a future event; evaluate estimation requirements too.
13. What is the other event in the timing comparison?
Recognition of revenue for transfer of the related goods or services to the customer.
14. How are variable customer payments treated?
Estimate the transaction price and assess the applicable constraint requirements referred to in paragraph 70.
15. Can a net sales report still need a further identical journal?
Do not duplicate a reduction already included. Reconcile source and ledger populations first.
16. Does this conclusion determine the GST credit-note procedure?
No. The financial-reporting analysis and the applicable tax procedure require separate assessments.
Official sources
MCA: Ind AS 115, paragraphs 70–72 and referenced distinctness requirements