Real estate developers and contractors in Egypt and the GCC manage a finance structure defined by project-level P&L, long-cycle revenue recognition, and rapid portfolio growth. This page covers how Oracle EPM, BI, and automation apply to project accounting, IFRS 15 revenue, and multi-project consolidation in this sector.
Start a conversation →A real estate group in Saudi Arabia that was running five projects five years ago is now running forty — each with its own P&L, its own capitalisation structure, its own financing arrangement, and its own ZATCA e-invoicing obligation. The finance team is larger than it was, but the close cycle is longer, not shorter, because the complexity grew faster than the process.
Revenue recognition is the structural challenge. Under IFRS 15, revenue on long-term development and construction contracts must be staged by completion milestones, not by cash received — and that staging has to live in the planning model, not only in the statutory accounts. A budget that recognises revenue at handover, when the accounting recognises it over time, will never reconcile to the reported result.
Consolidation across a project portfolio is its own problem: each project may be a separate legal entity, with joint-venture partners, different financing, and different completion timelines, all rolling up to a group view that must remain clean as projects launch and complete.
PBCS/EPBCS for project-level planning with IFRS 15 revenue staging built in as a driver; FCCS for multi-project and multi-entity consolidation including JV structures; PCMCS where cost allocation across shared services and projects is needed; ARCS to reduce the reconciliation burden of a large project portfolio. Project P&L maps to both the legal-entity and the physical-project structure.
Margin by project, by phase, and by product type from the same source that feeds the group accounts. Integration with project-management and cost-control systems so the CFO sees project performance against budget in real time, not at month-end reconciliation.
AP for large subcontractor and supplier bases, purchase-order-to-invoice reconciliation, subcontractor payment certification, and cost-variance reporting are the highest-volume targets. Arabic-language contracts and vendor invoices — routine in this sector — are processed with Arabic OCR.
System selection and IFRS 15 model design run vendor-neutral, with an understanding that real estate EPM must stage revenue by completion, map project P&L to two structures at once, and remain maintainable as the portfolio grows.
Developers and contractors face tax and e-invoicing obligations on every project entity, alongside long-cycle revenue rules.
For developers specifically: IFRS 15 revenue recognition on long-term contracts creates planning complexity — revenue in the budget must be staged by completion milestones, not by cash received. This is a planning-model design requirement most EPM implementations in the sector do not address from the start.
Project-level P&L must map to both the financial-entity structure and the physical-project structure — these are rarely the same, and EPM must handle both.
IFRS 15 revenue staging by completion milestone belongs in the planning model as a driver, so the budget reconciles to the reported result.
JV and co-development structures require consolidation logic that reflects each partner’s share and financing — not a wholly-owned assumption.
The consolidation perimeter changes as projects launch and complete; EDMCS keeps the entity and ownership hierarchy clean.
Subcontractor payment certification and cost-variance explanation are high-volume, Arabic-language-heavy processes well-suited to automation.
For AP, subcontractor certification, and cost-variance reporting; contracts.
Yes. FCCS consolidates multiple project entities — including JV structures — into a group view, while PBCS/EPBCS handles project-level planning. The design requirement is mapping each project P&L to both the legal-entity structure and the physical-project structure, since these differ, and maintaining the consolidation perimeter in EDMCS as projects launch and complete. Done well, this replaces the spreadsheet consolidation that slows large developers’ closes.
By building revenue staging into the planning model as a driver, so budgeted revenue is recognised by completion milestone in line with the accounting treatment — not at cash receipt or handover. This alignment between the plan and the IFRS 15 accounting is what most sector implementations miss, and its absence is why budgets and reported results fail to reconcile. It is a design decision made at the start of the implementation.
Yes. FCCS handles proportional and equity consolidation for JV and co-development entities, reflecting each partner’s share and financing arrangement. The key is configuring the consolidation logic to the actual ownership and funding structure of each project, rather than assuming wholly-owned entities — which is common in developer portfolios where projects are frequently structured with partners.
Accounts payable for large subcontractor bases, purchase-order-to-invoice reconciliation, and subcontractor payment certification. These are high-volume, document-heavy, and largely Arabic-language, making them strong candidates for UiPath or Power Automate combined with Arabic OCR. Automating payment certification in particular removes a recurring bottleneck and reduces disputes with subcontractors.
Let’s talk about your sector.
Implementing or reviewing EPM, BI, or automation for a real estate or construction group in Egypt or the GCC? The conversation starts with how your projects should be planned, staged, and consolidated — not a generic corporate template.