Design the note around economic differences
Ind AS 115 paragraph 114 and B87–B89 require disaggregation of customer-contract revenue into categories depicting how economic factors affect the nature, amount, timing and uncertainty of revenue and cash flows. One aggregate revenue figure is not automatically sufficient; neither is every conceivable cross-tabulation mandatory. Select categories that communicate the entity’s actual business and explain why materially different revenue streams are combined or separated.
Read the applicable text: MCA Ind AS 115: paragraphs 110–115 and B87–B89.
Use management and external reporting as evidence
B88 requires consideration of information presented outside the financial statements, information regularly reviewed by the chief operating decision maker and similar information used to evaluate performance or allocate resources. Compare earnings releases, investor presentations and management packs with the proposed categories. A different presentation is not automatically prohibited, but unexplained inconsistent populations should be investigated. Keep the accounting perimeter clear: recognised customer-contract revenue is not automatically the same as bookings, cash collections, gross merchandise value or a tax-return turnover figure.
Choose categories that answer a real question
B89 examples include product/service type, geography, customer market, contract type, duration, transfer timing and channel. These are examples, not an instruction to disclose a mandatory seven-table template. An equipment-and-maintenance business may need both product and timing information; two genuinely homogeneous activities may need less granularity. Paragraphs 110–112 require useful detail without obscuring information through excessive aggregation or insignificant detail. Under paragraph 112, information already provided under another standard need not be disclosed again; a clear cross-reference can help users find the relevant information. Retain a reasoned materiality and relevance assessment.
Use one population with several independent views
Give every recognised revenue line a unique identifier and the category fields needed for the selected views. A transaction can be both export revenue and equipment revenue, but adding the export table total to the product table total counts it twice. Each complete view should reconcile to the same population unless a different scope is explicitly explained. Treat credit notes and transaction-price adjustments consistently with the revenue they adjust. Retain unclassified lines as visible exceptions rather than dropping them to make a table balance.
Explain the relationship to segment reporting
Paragraph 115 requires enough information to understand the relationship with revenue information disclosed for each reportable segment when Ind AS 108 applies. A segment bridge should identify differences such as inter-segment amounts, eliminations or revenue outside the customer-contract population where relevant. Do not assert that Ind AS 115 categories must always be identical to segments or that every management division is a reportable segment. The chosen categories and segment disclosures serve connected but distinct reporting purposes.
Validate the note beyond a matching total
Matching grand totals can conceal misclassification between categories. Test samples back to contracts and recognition workings, review category changes and check comparatives. Where classifications change, assess the applicable presentation and comparative requirements rather than silently relabelling numbers. Keep calculation controls, judgement on categories and approval of the published note together. The examples are fictional amounts of already recognised revenue, exclude taxes and do not determine when revenue should first be recognised.
Six worked illustrations
All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.
Illustrative example 1: Product categories reconcile
Equipment revenue ₹60 lakh and maintenance revenue ₹40 lakh total ₹100 lakh. If the ledger’s customer-contract revenue is ₹100 lakh, the first arithmetic bridge agrees. Confirm that the categories reflect economic differences rather than only convenient account codes.
Illustrative example 2: Timing view is not additional revenue
Of the same ₹100 lakh, ₹65 lakh transfers at a point in time and ₹35 lakh over time. This view totals ₹100 lakh. Adding it to the ₹100 lakh product view produces an erroneous ₹200 lakh because it counts the same population twice.
Illustrative example 3: A credit note follows its category
Initial category A revenue is ₹45 lakh and B ₹55 lakh. A valid ₹3 lakh revenue adjustment relates entirely to A. Revised figures are A ₹42 lakh, B ₹55 lakh and total ₹97 lakh. Reducing the grand total without adjusting A leaves a misleading category note.
Illustrative example 4: Expose unclassified revenue
The ledger has ₹120 lakh of recognised customer-contract revenue, but mapped categories total ₹114 lakh. Unclassified revenue is ₹6 lakh, 5% of the population. Investigate and classify it; deleting the exception would conceal the incomplete mapping.
Illustrative example 5: Segment bridge with elimination
Assume segment revenue measures total ₹150 lakh, including ₹20 lakh inter-segment revenue. Eliminating that amount gives ₹130 lakh external revenue. If ₹5 lakh of that is outside Ind AS 115, the customer-contract revenue population is ₹125 lakh. Explain both adjustments rather than changing a category total to match ₹150 lakh.
Illustrative example 6: Equal totals can hide misclassification
A ₹10 lakh item was wrongly tagged domestic instead of export. Original categories domestic ₹70 lakh and export ₹30 lakh still total ₹100 lakh. Correct categories are ₹60 lakh and ₹40 lakh, again ₹100 lakh. A grand-total check cannot detect this ₹10 lakh classification error.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Define the revenue population | Recognised customer-contract revenue and exclusions. |
| 2 | Review economic drivers | Contracts, products and cash-flow characteristics. |
| 3 | Review external reporting | Investor information and releases. |
| 4 | Review management information | CODM packs and resource-allocation reports. |
| 5 | Choose useful categories | Documented relevance and granularity judgements. |
| 6 | Map unique revenue lines | Stable identifiers and category fields. |
| 7 | Assign adjustments consistently | Credit-note and price-adjustment links. |
| 8 | Reconcile each complete view | Ledger bridge and visible unmapped amounts. |
| 9 | Bridge reportable-segment revenue | Ind AS 108 relationship and explained scope differences. |
| 10 | Approve the disclosure | Sample checks, comparatives and final-note totals. |
Sixteen practitioner FAQs
1. Is one category type always enough?
No. B87 says the extent depends on the entity’s facts; some need several category types.
2. Must all seven B89 examples be used?
No. They are examples for selecting useful categories.
3. Can product and geography views coexist?
Yes. Keep them as separate views of the population and avoid adding their totals together.
4. Is the CODM pack relevant?
Yes. B88 specifically identifies information regularly reviewed by the chief operating decision maker.
5. Are investor presentations relevant?
Yes. Consider revenue information outside the financial statements as B88 requires.
6. Are bookings automatically revenue for this note?
No. Reconcile to recognised customer-contract revenue.
7. Should cash receipts determine categories?
Cash-flow economics can inform category design, but receipts alone do not replace the revenue population.
8. Do categories have to equal reportable segments?
Not automatically. Explain their relationship under paragraph 115 when Ind AS 108 applies.
9. Can inter-segment revenue cause a bridge difference?
Yes, depending on the actual segment measure and eliminations; explain the facts.
10. How should an identified credit note be mapped?
Consistently with the revenue category it adjusts, supported by the underlying linkage.
11. Can unclassified lines be omitted?
No. Investigate them and retain visibility until the mapping is complete.
12. Does a matching total prove correct category allocation?
No. Offsetting classification errors may leave the total unchanged.
13. Is every management division a reportable segment?
No. That determination belongs to the applicable Ind AS 108 analysis.
14. Can excessive detail reduce usefulness?
Yes. Apply the disclosure objective and appropriate aggregation principles.
15. What about category changes?
Assess presentation and comparative implications and document the rationale rather than silently changing labels.
16. What is the final review evidence?
Category judgements, population mapping, independent reconciliations, sample checks and the segment relationship.