SFRS(I) 15 establishes a single, comprehensive model for recognising revenue from contracts with customers. Revenue — the "top line" — is one of the most important numbers in any set of financial statements, and before this standard, revenue recognition guidance was scattered and inconsistent. SFRS(I) 15 replaced that with one principle applied through a five-step model: recognise revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled. It is the Singapore equivalent of IFRS 15 under IFRS, and is in substance IFRS 15 as applied in Singapore.
Objective and scope
The objective is to establish the principles that an entity applies to report useful information about the nature, amount, timing, and uncertainty of revenue and cash flows arising from a contract with a customer. The core principle is that an entity recognises revenue to depict the transfer of promised goods or services in an amount reflecting the consideration to which it expects to be entitled. The standard applies to all contracts with customers, except leases (SFRS(I) 16), insurance contracts, financial instruments, and certain non-monetary exchanges.
The five-step model
SFRS(I) 15 applies a five-step model to every contract with a customer.
Step 1 — Identify the contract with a customer. A contract creates enforceable rights and obligations. The standard applies only when the parties have approved the contract and are committed to perform, each party's rights and payment terms can be identified, the contract has commercial substance, and it is probable the entity will collect the consideration to which it will be entitled.
Step 2 — Identify the performance obligations in the contract. At inception, the entity identifies as a performance obligation each promise to transfer a distinct good or service (or a bundle), or a series of distinct goods or services that are substantially the same. A good or service is distinct if the customer can benefit from it on its own or with readily available resources, and the promise to transfer it is separately identifiable from other promises.
Step 3 — Determine the transaction price. The transaction price is the consideration the entity expects to be entitled to, excluding amounts collected for third parties — considering variable consideration (and constraining estimates of it), any significant financing component, non-cash consideration, and consideration payable to the customer.
Step 4 — Allocate the transaction price to the performance obligations. The entity allocates the price to each obligation, generally in proportion to the stand-alone selling prices of the distinct goods or services.
Step 5 — Recognise revenue when (or as) the entity satisfies a performance obligation. Revenue is recognised when the entity transfers control of a promised good or service — either over time or at a point in time.
Over time versus point in time
Revenue is recognised over time if one of three criteria is met: the customer simultaneously receives and consumes the benefits as the entity performs; the entity's performance creates or enhances an asset the customer controls; or the entity's performance does not create an asset with an alternative use and the entity has an enforceable right to payment for performance to date. If none is met, revenue is recognised at a point in time — typically when control transfers, indicated by the customer having the present right to payment, legal title, physical possession, the risks and rewards of ownership, and acceptance.
A worked example
A Singapore software company sells a customer a one-year software licence bundled with installation services and 12 months of support, for a total of S$120,000. The three promises are distinct performance obligations, and the transaction price is allocated by stand-alone selling price:
| Performance obligation | Stand-alone selling price (S$) | Allocated transaction price (S$) | When revenue is recognised |
|---|---|---|---|
| Software licence | 90,000 | 90,000 | Point in time — when control of the licence transfers |
| Installation services | 10,000 | 10,000 | Point in time — when installation is performed |
| 12 months of support | 20,000 | 20,000 | Over time — across the 12-month period |
| Total | 120,000 | 120,000 | — |
Rather than recognising the whole S$120,000 on signing, the company recognises the installation revenue when performed (a point in time), the licence when control transfers (a point in time), and the support over the 12-month period (over time). If, at year-end, three months of support have been delivered, only S$5,000 of the S$20,000 support obligation is recognised, with the remaining S$15,000 held as a contract liability (deferred revenue).
Contract costs and disclosure
SFRS(I) 15 also addresses contract costs: the incremental costs of obtaining a contract (such as sales commissions) are recognised as an asset if the entity expects to recover them, and certain costs to fulfil a contract are capitalised and amortised. The standard requires extensive disclosures about contracts with customers, the significant judgements made, and the assets recognised from the costs to obtain or fulfil a contract.
How SFRS(I) 15 relates to IFRS
SFRS(I) 15 is identical to IFRS 15 under IFRS — the same five-step model, the same notion of distinct performance obligations, the same over-time versus point-in-time recognition, and the same contract-cost and disclosure requirements. An entity familiar with IFRS 15 will find SFRS(I) 15 to be the same standard.
Common pitfalls
Recurring issues include failing to identify all the distinct performance obligations in a bundled contract (and so recognising revenue at the wrong time); recognising revenue on signing rather than as control transfers; not constraining variable consideration; overlooking a significant financing component; misallocating the transaction price across performance obligations; and inadequate disclosure of the significant judgements applied.
Why this is cleaner on a unified system
Applying the five-step model reliably — identifying performance obligations, allocating the transaction price, and recognising revenue as each obligation is satisfied — depends on connected data about contracts, deliverables, and their fulfilment. When the systems that capture customer contracts and delivery, and the general ledger, share a single source of truth, recognising revenue at the right time and in the right amount, tracking contract assets and liabilities, and producing the required disclosures is more straightforward than reconciling separate billing and revenue systems against the accounts.
This article is a detailed educational summary of SFRS(I) 15 in plain language. It is not a substitute for the full text of the standard. Accounting standards are amended from time to time; always verify the current, authoritative text of SFRS(I) 15 as issued by the Singapore Accounting Standards Council before relying on it, and consult a qualified professional accountant for application to your specific circumstances.