IFRS 15 — Revenue from Contracts with Customers — is the IFRS standard that governs how and when revenue is recognised from contracts with customers. It has been effective for annual reporting periods beginning on or after 1 January 2018. IFRS 15 replaced IAS 18 (Revenue) and IAS 11 (Construction Contracts) with a single, five-step revenue recognition model applicable across all industries and contract types, eliminating the inconsistency in revenue recognition that characterised the previous standards.
The five-step model: (1) Identify the contract with the customer. (2) Identify the performance obligations in the contract — the distinct goods or services that the entity has promised to deliver. (3) Determine the transaction price — the amount the entity expects to be entitled to in exchange for fulfilling all obligations. (4) Allocate the transaction price to the performance obligations based on their relative standalone selling prices. (5) Recognise revenue when (or as) each performance obligation is satisfied.
In the Context of Egypt and the GCC
IFRS 15 has had the most significant impact on GCC enterprises with complex, multi-element contracts — telecommunications (bundled device and service contracts), real estate developers (off-plan property sales with staged completion), professional services (long-term managed service contracts with variable components), and technology vendors (combined hardware, software, and support arrangements). The standard’s requirement to identify and separately price each performance obligation means that revenue recognised under IFRS 15 may differ substantially from cash received — creating deferred revenue balances and variable consideration estimates that were not required under IAS 18.
Egyptian finance teams implementing IFRS 15 for the first time — as convergence with IFRS continues under Egyptian Accounting Standards revision — face the additional challenge of retrofitting the five-step model onto contract structures and systems that were designed under a different recognition framework. ERP revenue recognition configuration and contract management system integration are both required to sustain IFRS 15 compliance at scale.
How This Connects to EPM and Systems
Revenue planning in an EPM model must reflect IFRS 15 recognition timing, not booking timing. For a real estate developer, a signed contract and deposit received is a booking — it generates deferred revenue, not recognised revenue. Revenue recognition flows into the income statement only as construction milestones are reached or as the performance obligation is otherwise satisfied. An EPM revenue plan that treats bookings as revenue will overstate near-term revenue and understate the deferred revenue liability. The EPM model must be built with an explicit recognition schedule that connects contract milestones to revenue release.
What Goes Wrong
The failure that creates recurring IFRS 15 audit adjustments is the absence of a variable consideration estimate process. IFRS 15 requires that variable consideration — discounts, rebates, performance bonuses, price concessions — be estimated and included in the transaction price to the extent that it is highly probable a significant reversal will not occur. Enterprises that do not maintain a structured process for estimating variable consideration at contract level default to recognising revenue at the contracted list price and recording adjustments when the actual consideration is determined. This produces revenue that is initially overstated and corrected in a later period — an avoidable volatility that a proper IFRS 15 process eliminates.
How Loop Wise Solutions Encounters This
In EPM implementations for revenue-complex businesses — real estate, telecoms, professional services — IFRS 15 revenue recognition modelling is a specific scope item. We design the revenue planning model to capture performance obligation satisfaction schedules, variable consideration estimates, and contract modification accounting alongside the standard revenue driver model. The EPM plan and the IFRS 15 compliant income statement are the same output — not a reconciliation problem to be solved at period end.
