The Free iPhone Illusion: Revenue Recognition under Ind AS 115 and IFRS 15

A telecom provider offers you the latest flagship smartphone for $0 upfront if you commit to a 24-month contract at $50 per month. You walk out of the store happy, phone in hand, wallet unopened.

At the telecom company’s headquarters, the CFO is looking at a very different picture. Under the legacy rules of IAS 18, if you billed the customer $0, you booked $0 revenue. Under Ind AS 115, along with its global counterparts IFRS 15 and ASC 606, that logic no longer holds. The standard introduced a fundamental disconnect between when cash arrives and when the company recognises revenue, and the implications run from the income statement straight through to dividend policy.

1. The Core Concept: Performance Obligations (PO)

The heart of the new standard is the Performance Obligation. The standard no longer views a contract as a single stream of revenue but as a bundle of distinct promises.

In a standard telecom bundle, the provider makes two distinct promises:

The Hardware: Transfer of the handset (Satisfied at a point in time: Day 1)
The Service: Provision of network access (Satisfied over time: 24 months)

The standard dictates that you recognise revenue as you satisfy each PO. Therefore, you recognise revenue for the handset on Day 1, even if the invoice handed to the customer says $0.

2. The Math: Allocating the Transaction Price

To determine the revenue amount, we use the Relative Standalone Selling Price (SSP) method. We cannot simply assign arbitrary values, so we look at what the components would sell for individually.

The Scenario Data

Contract Terms: $50/month for 24 months
Total Transaction Price (TTP): $1,200

The Standalone Reality

Handset SSP: $800 (price without contract)
Service SSP: $25/month (SIM-only equivalent), $600 total

Step 1: Determine Total Fair Value (SSP)

{Total SSP} = $800 {Phone} + $600 {Service} = $1,400

Step 2: Calculate Allocation Ratio

The customer is receiving a package worth $1,400 for a price of $1,200 (a discount of approximately 14.3%). You allocate this discount proportionally across all obligations.

\[\text{Handset Allocation} = \frac{\$800}{\$1{,}400} \times \$1{,}200 = \$685.71\] \[\text{Service Allocation} = \frac{\$600}{\$1{,}400} \times \$1{,}200 = \$514.29 \approx \$21.43\text{ per month}\]

3. The Accounting Disconnect

This is where the “Free iPhone Trap” manifests in the financial statements.

On Day 1 (Handset Delivery)

You hand over the phone and invoice $0.

Credit: Revenue: $685.71
Debit: Contract Asset (Unbilled Revenue): $685.71

On Month 1 (Service Billing)

You invoice the customer $50.

Credit: Service Revenue: $21.43
Credit: Contract Asset: $28.57 (Reducing the Day 1 “loan” for the handset)
Debit: Accounts Receivable / Cash: $50.00

4. Strategic Implications for CFOs & FP&A

I find this disconnect matters for three primary reasons:

A. EBITDA Distortion

During a major product launch (e.g., a new iPhone cycle), revenue and EBITDA will appear to explode because the standard front-loads handset revenue. However, Cash Flow from Operations (CFO) will remain flat.

Stakeholders need to recognise that this “growth” is an accounting entry, not immediate liquidity.

B. The Dividend & Liquidity Trap

If a Board of Directors declares dividends based purely on Net Income, they may be distributing profits that exist only as Contract Assets on the balance sheet.

The actual cash to back those profits may not arrive for another 12–18 months, potentially creating a liquidity crisis.

C. FP&A Modeling Errors

Standard forecasting models often assume:

Cash = Revenue * (1 - Days sales outstanding%)

In a bundled environment, this logic fails. Analysts must model Billing Schedules and Revenue Recognition as two entirely separate workstreams.

I always remind teams: revenue recognition under Ind AS 115 is not a billing schedule. It is a performance schedule. Cash arrives when the contract says it arrives. You recognise revenue when you satisfy the obligation. In a bundled contract, those two timelines diverge from Day 1, and a finance team that does not model both separately will consistently misread its own performance.

The “free” iPhone is not free. It is a contract asset sitting on the balance sheet, waiting for 24 months of service delivery before the contract fully settles. If you are navigating bundled revenue recognition or building FP&A models around contract assets, I would love to hear how your team approaches it. Let’s connect.