Revenue, Receivables & Inventory

Learning objectives

By the end of the week you can:

1. Apply the five-step revenue model (ASC 606 / IFRS 15 / Ind AS 115, one converged standard) to any contract: identify performance obligations, set and allocate the transaction price on relative standalone selling prices, and decide point-in-time vs over-time recognition.
2. Account end-to-end for three archetypal contracts (a simple product sale, a multi-element SaaS deal, and a long-term construction contract, over-time, cost-to-cost), including a mid-life estimate revision with cumulative catch-up.
3. Decide principal vs agent (gross vs net) from the control indicators, and explain precisely why Zomato's or DoorDash's revenue line is not comparable to DMart's or Costco's.
4. Distinguish contract liabilities (deferred revenue), contract assets, and receivables; read a contract-balances note; and use deferred revenue and contract-asset trends as early-warning indicators.
5. Build a receivables allowance under IFRS 9 / Ind AS 109 expected credit losses (both the 3-stage general model and the simplified-approach provision matrix), contrast it with US CECL, and post the provision, write-off, and recovery entries.
6. Run one inventory dataset under FIFO, LIFO, and weighted average; state the effects on COGS, profit, taxes, and inventory value in a rising-price world; and use the LIFO reserve to restate a LIFO company to FIFO for comparison.
7. Apply lower of cost and net realisable value (LCNRV), including the IFRS/Ind AS write-down reversal rule vs the US GAAP no-reversal rule.

Prerequisites & connections

Builds on: M1.01 (debits/credits: every treatment here is shown as journal entries), M1.02 (the P&L layers), M1.03 (receivables, inventory, contract balances, allowances, contra accounts), M1.04–M1.05 (how a revenue or provision entry ripples into CFO: accrual revenue with no cash is a working-capital drag).

Feeds into: M1.07 (impairment logic recurs for long-lived assets; compare the NRV reversal rule here), M1.10 (you will read these exact notes in a real 10-K and Indian AR), Phase 2 (DSO/DIO, receivables- and inventory-led red flags, Schilit's revenue shenanigans stand on this substrate), Phase 5 (take-rate economics; banks and NBFCs run on ECL machinery), and the teardown checklist (the revenue-policy note is a standing stop on the 45–60 minute statement read).

4.1 Why revenue is the first number you interrogate

Revenue is the top line of the P&L and an input to almost every metric you will compute: growth, margins, turnover, multiples. It is also structurally the easiest number to inflate: revenue is a claim, and claims rest on judgment about when performance happened. Most of the great frauds (Enron, Satyam, Luckin Coffee, Manpasand) were at heart revenue frauds.

First principles: under accrual accounting, the convention you met learning double-entry, revenue is recognized when earned by performance, not when cash arrives. An advance payment is not revenue: it is a debt payable in service. Goods delivered on credit are revenue now, plus a receivable that may never become cash (that is the ECL section). The gap between revenue recognized and cash collected is where analysis lives.

Since 2018 one model governs revenue almost everywhere: ASC 606 (US GAAP), IFRS 15, and Ind AS 115 (India) are converged in all but a few corners. Learn it once; apply it in Mumbai and New York. The core principle: recognize revenue to depict the transfer of promised goods or services, in the amount the entity expects to be entitled to, operationalized as five steps.

4.2 The five-step model

Step 1: Identify the contract. A contract exists when it is approved, rights and payment terms are identifiable, it has commercial substance, and collection is probable. One of the few genuine US/IFRS differences hides here: "probable" under US GAAP means roughly "likely" (~75–80% in practice); under IFRS 15/Ind AS 115 "probable" means more likely than not (>50%). A shaky-credit customer can therefore pass Step 1 under Ind AS but fail it under US GAAP, in which case the US seller books cash received as a deposit liability, not revenue.

Step 2: Identify the performance obligations (POs). A PO is a promise to transfer a distinct good or service. Distinct = the customer can benefit from it alone (or with readily available resources) and it is separately identifiable within the contract (not a mere input into one combined output). Bundles get unbundled here: a phone + 12-month plan is two POs; a construction contract's thousand activities are one PO (they integrate into one asset). Two classic judgment calls: an assurance warranty ("it will work as specified") is not a PO (accrue its expected cost as a provision) while a service warranty (extended coverage) is a PO with deferred revenue; and implementation services sold with software are distinct if generic, but combined with the subscription if they significantly customize the platform.