IFRS 15 Revenue Recognition in GCC Construction: Why Your EAC Is the Key to Getting It Right

The Revenue Problem Most GCC Construction Finance Teams Overlook

A SAR 300M residential tower in Riyadh, 14 months into a 28-month programme. The finance director signs off the monthly revenue figures based on progress certificates — and the books look healthy. Gross margin is holding, receivables are moving, the board is satisfied.

Then the QS updates the EAC. Materials have moved. A design variation added scope. The programme slipped six weeks. Suddenly the Estimate at Completion is SAR 18M higher than the original budget. Revenue already recognized is now overstated by SAR 6.4M. The finance director has to reverse it — in a single month.

This is not an edge case. It happens regularly on GCC construction projects, and it almost always traces back to the same root cause: revenue was recognized against an EAC that was never properly maintained.

Under IFRS 15, the percentage-of-completion calculation is only as accurate as the forecast underneath it. This post walks through how revenue recognition actually works on long-term construction contracts — and what GCC finance teams need to get right before the auditors arrive.

The Foundation: IFRS 15's Five-Step Model Applied to Construction

IFRS 15 replaced IAS 11 in 2018. The old standard was relatively straightforward for construction contractors — it essentially codified the percentage-of-completion method. IFRS 15 introduced a structured five-step model that requires more judgment, particularly on contracts with multiple performance obligations and variable consideration.

For most GCC construction contracts, the five steps work like this:

• Step 1 — Identify the contract. The signed contract with the employer, including approved variations that create enforceable rights. Unapproved variations sit in a separate bucket.
• Step 2 — Identify performance obligations. Most construction contracts have a single performance obligation: deliver the completed facility. Some have distinct phases (civil works vs MEP vs fit-out) that may need to be separated if they can be transferred independently.
• Step 3 — Determine the transaction price. This includes base contract sum, approved variations, and a constrained estimate of probable unapproved variations and claims (the variable consideration constraint).
• Step 4 — Allocate the transaction price. For single performance obligation contracts, this step is straightforward — the full price applies to the one obligation.
• Step 5 — Recognize revenue. For performance obligations satisfied over time (which construction always is), revenue is recognized as the obligation is satisfied — measured using either the input or output method.

Most complexity for GCC contractors sits in Steps 3 and 5. Getting the transaction price right means having a live, disciplined variation register. Recognizing revenue correctly means maintaining an accurate EAC.

The Two Revenue Recognition Methods — and Why GCC Contractors Mostly Use One

IFRS 15 allows two methods for measuring progress on a performance obligation satisfied over time:

Input Method (Cost-to-Cost)

Revenue recognized = (Costs incurred to date ÷ Total EAC) × Total contract price

If you are 40% of the way through costs on a SAR 200M contract, you recognize SAR 80M of revenue. This is the method used by the vast majority of GCC construction contractors, because it aligns naturally with how construction projects work — progress is driven by resource consumption, and the job cost system already tracks costs incurred.

Output Method

Revenue recognized based on outputs delivered — milestones, units completed, floor plates handed over. Appropriate for contracts where outputs can be measured independently (housing units in a residential development, for example). Most civil and infrastructure contracts do not lend themselves to clean output measurement across the full scope.

The input method is the default for most GCC construction contracts. But it has a critical dependency: the EAC must be accurate. If total forecast costs are understated, the percentage-complete calculation overstates revenue. If they are overstated, revenue is deferred unnecessarily, which distorts the P&L upward in later periods.

Why Your EAC Is the Linchpin of Revenue Recognition

The formula is simple. The execution is not. Three EAC failure patterns appear repeatedly in GCC construction finance reviews:

The Committed Cost Blind Spot

EAC calculations built from invoices received miss the cost already committed in purchase orders but not yet invoiced. On a SAR 200M structural contract, that gap can be SAR 30–50M at any point in the procurement cycle. If you calculate costs incurred from AP postings rather than committed costs (POs + work confirmations + timesheets), you are understating the denominator and overstating the percentage complete.

The fix: EAC must be built from committed costs — POs raised, work confirmations signed, timesheets allocated to WBS — not from invoices processed.

Optimistic Variation and Claim Inclusion

Contracts often include unapproved variations in the EAC as if they were approved — either in the cost forecast (the numerator) or by expanding the project scope (the denominator). If the variation is instructed but not yet valued, including it in both the cost and revenue forecasts may be appropriate. If it is submitted but disputed, including it breaches the variable consideration constraint in IFRS 15 Step 3.

GCC auditors increasingly ask for documentation of the probability threshold used to include instructed-but-unapproved variations. Contractors should document this judgment for each live project.

Stale EAC Reviews

On complex projects, the EAC is reviewed at project kick-off and then again six months later when the auditors request it. In between, cost has moved, programme has slipped, and subcontract rates have been agreed that differ from the tendered rates. The EAC has aged — and with it, the revenue figures.

Best practice: EAC reviewed and signed off by the project commercial manager every month as part of the cost report cycle. Any EAC movement above 1% of contract value triggers a formal note to the CFO.

Handling Variations and Contract Modifications Under IFRS 15

Variations are the point where IFRS 15 gets difficult for construction contractors. The standard distinguishes between contract modifications that are treated as separate contracts, and those that modify the existing contract.

For most construction variations — additional scope additions at rates different from the original BOQ — the modification adjusts the existing contract. Revenue from that variation is recognized on a prospective or catch-up basis depending on whether it changes work already performed.

Variable Consideration and the Constraint

IFRS 15.56-58 requires that variable consideration (including disputed variations and claims) only be included in the transaction price to the extent that it is highly probable that a significant reversal of revenue will not occur. This is the variable consideration constraint.

In practice, GCC contractors should categorize variations in three tiers:

• Approved and valued — include fully in transaction price and EAC
• Instructed but not yet valued — include at a probability-weighted amount, with documentation
• Submitted or claimed but disputed — exclude unless probability of recovery is high and well-evidenced

A live variation register that tracks approval status, value, and aging for every variation event is not optional for IFRS 15 compliance — it is the audit trail that supports the transaction price calculation.

Contract Assets vs Contract Liabilities: What Your Balance Sheet Is Really Saying

Every GCC construction contract at period end sits in one of two balance sheet positions:

Contract Asset (Under-Billed Position)

Revenue recognized exceeds amounts billed to the client. This happens when the project is progressing faster than the billing schedule — common on milestone-billing contracts where the next milestone has not been triggered yet. The unbilled amount sits as a contract asset (previously called work-in-progress or amounts due from customers under IAS 11).

Contract Liability (Over-Billed Position)

Amounts billed to the client exceed revenue recognized. Common on contracts with front-loaded billing schedules or advance payment mechanisms. The excess sits as a contract liability (previously billings in excess of costs).

On a SAR 200M contract at month 14:

• Revenue recognized (cost-to-cost basis): SAR 108M (54% complete)
• Amounts billed: SAR 115M (front-loaded billing schedule)
• Contract liability: SAR 7M

On a milestone-billing variant:

• Revenue recognized: SAR 108M
• Amounts billed: SAR 100M (next milestone not yet triggered)
• Contract asset: SAR 8M

The GCC-specific complication: advance payment recoupment. As the advance is recovered from each certificate, it reduces amounts due — and the correct treatment is to reduce the contract asset or increase the contract liability, not to post it as income. Many GCC construction finance teams get this wrong, which distorts the contract position.

The Month-End Revenue Recognition Workflow

For a SAR 1B+ GCC construction portfolio, the month-end revenue recognition cycle runs like this when done properly:

• Days 1–3: Project cost reports finalized with QS sign-off. All POs, work confirmations, timesheets, and GRNs for the period closed off. EAC updated per project by commercial manager.
• Days 4–5: Revenue computation run per project: (Cumulative costs incurred ÷ EAC) × Transaction price. Revenue for the period = cumulative recognized minus prior period recognized.
• Days 5–6: Variation register reviewed. Instructed-but-unapproved variations assessed against variable consideration constraint. Items crossing into the transaction price documented with probability rationale.
• Days 6–7: Contract asset and liability positions calculated per project. Advance recoupment positions updated. Portfolio-level WIP schedule prepared for CFO review.
• Days 7–8: Revenue journal posted to GL. Certified billings reconciled to contract positions. EAC movements above threshold escalated.

The critical dependency at every step: all cost data must be in the system before the EAC can be finalized. This is why month-end close timelines on construction portfolios are so sensitive to PO posting, confirmation logging, and timesheet allocation discipline during the period.

Five Practical Starting Steps

• Map your current method. Document exactly how revenue is recognized today — which system generates the calculation, what cost data feeds it, and who reviews the EAC before it is posted. Identify where the gaps are.
• Audit your EAC inputs. For your three largest active projects, compare the EAC to committed costs (POs + confirmations + timesheets). If the EAC is built from AP ledger only, quantify the commitment gap. This is the number that represents your IFRS 15 non-compliance risk.
• Build a live variation register. Every variation event categorized as approved, instructed-unapproved, or submitted-disputed — with value and aging. Your auditors will ask for this. Prepare it from a single source, not by assembling spreadsheets at year-end.
• Establish a monthly EAC sign-off process. The project commercial manager signs the EAC before revenue is posted. Any movement above 1% of contract value triggers a written note to finance explaining the driver — procurement movement, programme extension, scope change, subcontractor rate variance.
• Prepare a project WIP schedule. A single document showing each project: contract price, revenue recognized to date, billings to date, contract asset or liability position, advance recoupment balance. This is the CFO's monthly view and the auditor's starting point.

The Audit You Want to Be Ready For

Big 4 audit teams conducting GCC construction group audits increasingly focus on three things: the EAC review process and who signs off, the variable consideration constraint applied to unapproved variations, and the completeness of committed costs in the revenue calculation.

Contractors with a unified platform — where POs, work confirmations, timesheets, and change orders all feed the same cost module — can pull the EAC from live data. The revenue calculation is a formula run against real numbers, not a judgment assembled from fragmented reports.

Contractors without that integration spend the audit week reconstructing what the EAC was at month-end, explaining why committed costs were excluded, and defending variation inclusion decisions that were never documented at the time.

The revenue number your board sees every month is only as reliable as the forecast underneath it. Get the EAC right, and IFRS 15 compliance follows. Get it wrong, and the reversal shows up when you can least afford it.