Revenue recognition is the application of accounting standards to determine when revenue should be recorded in the income statement and how much should be recorded. The fundamental principle under IFRS 15 (Revenue from Contracts with Customers), effective since 2018, is that revenue is recognised when — and only when — a performance obligation is satisfied: when the promised good or service is transferred to the customer. The cash receipt is irrelevant to timing; a customer who pays twelve months in advance does not generate revenue at the payment date, only as the service is delivered. The practical implication for finance leaders is that revenue is a judgment, not a cash fact — and that judgment must be consistently applied, documented, and defensible to auditors and regulators.
In the Context of Egypt and the GCC
Revenue recognition under IFRS 15 has particular complexity in the GCC sectors that dominate the regional economy. Real estate developers — common across Saudi Arabia, UAE, and Egypt — face the question of whether revenue from off-plan property sales is recognised over time (as construction progresses, under an over-time method) or at a point in time (when the completed property is transferred to the buyer). The answer depends on whether the buyer controls the asset under construction, which in turn depends on the contract structure. Getting this analysis wrong — and recognising revenue at completion rather than over construction, or vice versa — produces material restatements when auditors challenge the treatment.
For Saudi and UAE construction and engineering companies, IFRS 15’s five-step model requires identification of every performance obligation in a contract. A contract to design, build, and commission a facility may contain one combined obligation (if the outputs are highly interrelated) or three separate obligations (if each can be sold independently). The distinction changes the timing of revenue recognition materially and must be documented for every significant contract, not applied as a blanket policy across all contract types.
What Correct Revenue Recognition Requires
Correct application of IFRS 15 requires four things operating together. A contract review process that assesses the performance obligation structure of every significant new contract before revenue recognition begins. A system that tracks obligation satisfaction — whether through a percentage-of-completion measurement, a milestone trigger, or a delivery event — and generates the revenue entry automatically rather than relying on manual journal entries. A disclosure process that communicates the revenue recognition policies clearly in the notes to the financial statements. And an internal audit or review function that periodically verifies that the policies are being applied consistently across all business units and contract types.
What Goes Wrong
The specific revenue recognition failure that most frequently produces audit adjustments in GCC enterprises is the application of a single recognition method to all contracts in a category, without assessing whether individual contracts within that category have different performance obligation structures. A telecommunications company that recognises revenue from all bundled device-and-service contracts on the same basis — without assessing whether each contract meets the separate performance obligation criteria for the device component — may be misclassifying revenue between periods in ways that materially affect quarterly earnings trends.
How Loop Wise Solutions Encounters This
In EPM implementations for industries with complex revenue — construction, real estate, telecoms, professional services — we design the revenue planning and reporting model to reflect the IFRS 15 recognition basis, not the billing basis. When the EPM plan is built on billing milestones rather than performance obligation satisfaction, the plan is measuring cash flow, not revenue — and the variance between plan and actual becomes an IFRS 15 timing difference rather than an operational performance signal.
