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 in exchange. It is the Singapore equivalent of IFRS 15 and Ind AS 115 in India, 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 to users of financial statements 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 to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. 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 is an agreement between two or more parties that creates enforceable rights and obligations. The standard applies to a contract only when specific criteria are met: 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 that the entity will collect the consideration to which it will be entitled.
Step 2 — Identify the performance obligations in the contract. At contract inception, the entity assesses the goods or services promised and identifies as a performance obligation each promise to transfer either a good or service (or a bundle) that is distinct, or a series of distinct goods or services that are substantially the same and have the same pattern of transfer. A good or service is distinct if the customer can benefit from it on its own or with other readily available resources, and the promise to transfer it is separately identifiable from other promises in the contract.
Step 3 — Determine the transaction price. The transaction price is the amount of consideration to which the entity expects to be entitled in exchange for transferring the promised goods or services, excluding amounts collected on behalf of third parties. Determining it requires 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 transaction price to each performance obligation in an amount that depicts the consideration to which it expects to be entitled for satisfying that 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 to the customer. Control may transfer over time (in which case revenue is recognised over time using an appropriate method to measure progress) or at a point in time.
Over time versus point in time
An entity recognises revenue over time if one of three criteria is met: the customer simultaneously receives and consumes the benefits as the entity performs (for example, many routine services); the entity's performance creates or enhances an asset the customer controls as it is created (for example, building on the customer's land); or the entity's performance does not create an asset with an alternative use to the entity and the entity has an enforceable right to payment for performance completed to date. If none of these 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 significant risks and rewards of ownership, and having accepted the asset.
Contract costs and other matters
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 (subject to a practical expedient for short amortisation periods), and certain costs to fulfil a contract are capitalised and amortised. The standard requires extensive disclosures about contracts with customers, the significant judgements made in applying the model, and the assets recognised from the costs to obtain or fulfil a contract — enabling users to understand the nature, amount, timing, and uncertainty of revenue and cash flows.
The Singapore context
For Singapore companies, SFRS(I) 15 applies to a wide range of arrangements common in the economy — professional and financial services, technology and software (including licences and subscriptions), construction and property development, logistics, and trading. The standard's careful analysis of performance obligations and of over-time versus point-in-time recognition is particularly relevant to Singapore's large services and technology sectors. As with all SFRS(I), the accounting text is identical to IFRS; the surrounding context is the Singapore Companies Act, ACRA filing, and (for listed entities) SGX rules.
A brief illustration
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. Applying the five-step model: it identifies the contract (Step 1); identifies the distinct performance obligations — the licence, the installation, and the support (Step 2); determines the transaction price of S$120,000 (Step 3); allocates that price to the three obligations in proportion to their stand-alone selling prices (Step 4); and recognises revenue as each obligation is satisfied — the installation when performed, the licence when control transfers, and the support over the 12-month period (Step 5). Rather than recognising the whole S$120,000 on signing, the company recognises revenue as it actually delivers each promised good or service.
How SFRS(I) 15 relates to IFRS and Ind AS
SFRS(I) 15 is identical to IFRS 15 under IFRS, and therefore very closely aligned with Ind AS 115 in India — 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. Because both Singapore and India converge to the IFRS text, revenue is recognised on materially the same basis across the three frameworks. For anyone coming from India's older AS framework, this is a significant change: AS 9 (and AS 7 for construction contracts) used a simpler risks-and-rewards model, whereas both SFRS(I) 15 and Ind AS 115 use the control-based five-step model.
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.