The GCC M&A market in 2026 is active at scale. Saudi healthcare is consolidating rapidly in the wake of the Almoosa Health IPO. Logistics firms with digital infrastructure are attracting sovereign wealth fund attention — the Gulf Navigation and Brooge Petroleum transaction reached USD 1.4 billion. Vision 2030 giga-projects are creating supply chain consolidation across energy, infrastructure, and manufacturing. Family conglomerates across Saudi Arabia, the UAE, and Qatar are making acquisitions to enter new sectors or build scale ahead of generational transition. Private equity firms are deploying capital in the GCC at levels not seen since before 2014.
Most of the due diligence guidance available to CFOs evaluating acquisition targets in the region addresses the legal, regulatory, and financial dimensions of deal assessment. The finance systems dimension — what is the target’s ERP, how reliable is its financial data, what will it cost to integrate the target’s finance infrastructure into the acquirer’s reporting environment, and what is the hidden liability represented by a chart of accounts that cannot be reconciled to the acquirer’s consolidation model — receives almost no attention until the deal has closed and the integration reality becomes apparent.
That sequence produces an outcome that is consistent across the GCC acquisitions we have been engaged to support post-close: the financial due diligence confirmed the target’s EBITDA, the deal closed on a valuation based on that EBITDA, and the acquirer subsequently discovered that producing a consolidated financial statement that includes the target requires six to twelve months of systems integration work that was not in the integration budget, was not in the deal model, and is consuming senior finance team capacity that was supposed to be deployed elsewhere.
This guide addresses the finance systems and reporting infrastructure dimension of M&A due diligence and post-acquisition integration for GCC and Egyptian enterprises — from the pre-deal assessment questions that reveal finance systems risk, through the due diligence findings that most commonly destroy value, to the post-acquisition integration sequence that produces a consolidated finance environment within a timeline the board can accept.
Why Finance Systems Are the Most Underestimated M&A Risk in the GCC
Every M&A due diligence process evaluates earnings quality. The question of whether the target’s EBITDA is real, recurring, and reproducible — the Quality of Earnings (QoE) analysis — is the foundation of every deal assessment. It is well-understood, well-executed by GCC financial advisory firms, and appropriately weighted in deal valuation.
The question that QoE does not answer is whether the financial information used to calculate that EBITDA can be reproduced reliably going forward — whether the target’s ERP, chart of accounts, and reporting architecture will support the acquirer’s consolidation requirements, public company reporting obligations, and management reporting standards.
In the GCC and Egypt specifically, the finance systems risk is elevated by three regional factors.
The prevalence of manual and hybrid finance architectures. A significant proportion of GCC enterprises that are targets for acquisition have finance functions that rely heavily on manual processes, Excel-based consolidation, and reporting assembled from multiple disconnected sources. The financial statements produced by these architectures can be accurate — an experienced finance team can produce reliable IFRS accounts from manual processes. But they cannot be scaled, audited at depth, or integrated into an acquirer’s Oracle or SAP-based finance environment without significant remediation.
The ERP fragmentation in multi-entity GCC groups. GCC family conglomerates and diversified enterprises frequently operate multiple entities on different ERP systems — Oracle EBS in the holding company, a legacy Arabic local ERP in an older subsidiary, SAP in a subsidiary acquired from a Western group, Microsoft Dynamics in a UAE retail entity, no ERP at all in a recently incorporated entity that books in Excel. Each entity in a GCC acquisition target may represent a different integration challenge.
The regulatory complexity of the GCC operating environment. UAE Corporate Tax, Saudi zakat, ZATCA Phase 2 e-invoicing, PDPL data governance, GOSI compliance, WPS wage protection — the regulatory obligations that the acquired entity is subject to may not be fully reflected in its ERP configuration or its reported financials. Hidden tax liabilities, ZATCA compliance gaps, GOSI underreporting, and PDPL non-compliance in the target’s data architecture are specific GCC due diligence findings that standard Western M&A due diligence frameworks do not systematically identify.
Part 1: The Finance Systems Due Diligence Assessment
Financial due diligence in the GCC context should include a finance systems assessment alongside the standard QoE and financial statements analysis. The finance systems assessment answers three questions: Can the target’s financial data be trusted? Can it be integrated into the acquirer’s finance environment? And what does that integration cost?
What the Finance Systems Due Diligence Covers
ERP inventory and architecture assessment
The starting question: what ERP systems does the target operate, in which entities, on which versions, and hosted where? The answer reveals the integration challenge that the acquirer inherits.
A target operating Oracle Fusion across all entities, with ZATCA-certified e-invoicing, PDPL-compliant data residency in Saudi Arabia, and a consistent chart of accounts — is a target whose finance integration will be relatively straightforward for an Oracle ERP acquirer. A target operating five different ERP systems across six entities, with the largest subsidiary on Oracle EBS version 12.1.3 with heavy customisation and the remainder on a mix of Arabic local ERPs and Excel — presents an integration programme whose cost and timeline will be a material consideration in deal structuring.
Chart of accounts and reporting architecture review
The chart of accounts is the coding framework that determines how every transaction is classified for financial reporting. When an acquirer consolidates an acquired entity into its Oracle FCCS environment, the target’s chart of accounts must map to the acquirer’s consolidation structure — every account in the target must have an equivalent in the acquirer’s consolidation model.
In GCC acquisitions, chart of accounts misalignment is the most consistently encountered and most consistently underestimated integration challenge. The target’s chart of accounts was designed for its own management reporting — not for the acquirer’s consolidation structure. The mapping exercise that bridges the two — identifying which of the target’s accounts map to which of the acquirer’s consolidation accounts, and what to do with accounts that have no direct equivalent — requires both accounting expertise and ERP configuration capability, and typically takes six to twelve weeks after the deal closes.
What due diligence should assess pre-deal: obtain a full chart of accounts from the target, map it to the acquirer’s consolidation model at the account level, identify the misalignment gaps, and quantify the integration effort before the deal model is finalised. This prevents the post-close discovery that a significant integration cost was not in the deal model.
Intercompany transaction architecture
For target entities that have intercompany transactions — whether with other entities in the target group or, post-acquisition, with the acquirer’s entities — the consistency and reliability of intercompany transaction recording determines how much manual intervention will be required at every consolidation cycle.
In most GCC target entities, intercompany transactions are recorded differently on the two sides — the payable in one entity does not match the receivable in the other entity in amount, period, or description. This asymmetry produces intercompany reconciliation gaps at every close that the consolidation team must investigate and resolve manually. Quantifying the intercompany reconciliation burden before the deal closes allows the acquirer to build the remediation cost into the integration plan.
Data quality and audit trail completeness
The reliability of the target’s financial data depends not only on the accounting judgments applied to produce the financial statements but on the integrity of the underlying transaction data in the ERP. Data quality review in M&A due diligence should specifically assess:
- Are journal entries documented with a stated purpose, a documented approver, and supporting calculations?
- Is the ERP audit trail enabled and complete for the relevant historical periods?
- Are there periods where data was imported in bulk from external sources without the individual transaction detail that would allow auditors to verify the underlying transactions?
- Are there unexplained balance movements — account balances that changed between periods without a corresponding journal entry visible in the ERP?
These questions are not standard in financial due diligence, which typically works from the financial statements rather than from the ERP transaction data. But they are the questions whose answers determine whether the EBITDA derived from the financial statements can be reproduced reliably in the acquirer’s finance environment.
GCC-specific regulatory compliance assessment
Standard financial due diligence quantifies the known tax liabilities. GCC due diligence should additionally assess:
ZATCA compliance status for Saudi entities: Has the target completed ZATCA Phase 2 integration? Is the ERP certified? Are all invoices being submitted to Fatoora? Is there a reconciliation between ERP-recorded invoices and ZATCA-confirmed invoices? A target that is operating outside ZATCA Phase 2 compliance carries enforcement risk that represents a financial liability not captured in the financial statements.
UAE Corporate Tax position: Has the target calculated and accrued UAE CT correctly from the June 2023 effective date? Has a deferred tax asset or liability been recognised where applicable? Are UAE free zone entities correctly classified as qualifying income entities and is the qualifying income calculation documented? UAE CT miscalculation is a specific due diligence risk in any acquisition of a UAE entity since June 2023.
GOSI compliance for Saudi entities: Is the GOSI contributory salary calculation correct? Are all Saudi employees registered and reported correctly? GOSI audits in Saudi Arabia can identify contribution underpayments going back multiple years, and this liability transfers to the acquirer in a share acquisition.
PDPL data architecture: Does the target store personal data in Saudi Arabia for Saudi operations and in the UAE for UAE operations? A target whose ERP or HR system hosts personal data outside the required jurisdiction carries a PDPL remediation liability.
Part 2: The GCC-Specific Due Diligence Red Flags
The following findings, encountered with consistent frequency in GCC acquisition due diligence, warrant specific attention because they are underweighted in standard Western due diligence frameworks.
Red Flag 1: Related-Party Transactions That Have Not Been Arm’s-Length Priced
GCC family-owned targets frequently have significant related-party transactions — rental of properties from family-connected entities, management fees paid to family holding vehicles, procurement from family-controlled suppliers. These transactions are often priced on terms that reflect the family relationship rather than market rates. In the consolidated financial statements, they may appear as operating costs at below-market rates (understating operating expenses and overstating EBITDA) or as revenues at above-market prices (overstating revenue).
Under UAE CT and Saudi transfer pricing regulations, related-party transactions must be priced on an arm’s-length basis. An acquirer inheriting related-party arrangements that are not arm’s-length priced inherits both a financial reporting adjustment (the EBITDA normalisation required to reflect market-rate costs) and a tax compliance risk (the transfer pricing adjustment that regulators may apply retrospectively).
Red Flag 2: Deferred Revenue and Working Capital Artificially Managed at Deal Date
Working capital management in the months before a transaction — accelerating collections, deferring payments, front-loading revenue recognition — is a standard deal preparation technique that inflates working capital at the measurement date and produces a working capital target in the deal agreement that the business cannot sustain post-close.
In the GCC, the most common variants are: accelerating government contract revenue recognition in the quarter before the measurement date; deferring supplier payments to GCC government-related entities where payment terms are flexible; and managing the timing of GOSI and ZATCA submissions to reduce the accrued liability at the measurement date.
Identifying working capital normalisation in a GCC acquisition requires understanding not just the accounting but the specific payment dynamics of GCC government contracts, GOSI submission timing, and the seasonal patterns of the target’s working capital cycle.
Red Flag 3: ERP Data That Cannot Be Reconciled to the Audited Financial Statements
One of the most revealing due diligence procedures in a GCC acquisition is to request the ERP trial balance at the same date as the audited financial statements and reconcile the two. When they do not reconcile — and in a significant proportion of GCC acquisition due diligence processes they do not, by material amounts — the investigation of the reconciling items reveals the quality of the target’s financial close process.
The most common causes of ERP-to-audit reconciliation gaps in GCC targets: manual journal entries posted outside the ERP to adjust the financial statements; period adjustments that were applied to the audited statements but not reflected in the ERP; intercompany eliminations performed outside the ERP in Excel; and depreciation and amortisation calculated outside the ERP and entered as a bulk journal rather than recorded by the fixed asset module.
Each of these represents a finance system weakness that will require remediation post-close. The sum of the remediation required is the finance systems integration cost that should have been in the deal model.
Red Flag 4: The Consolidation Is Performed in Excel With No Documented Methodology
A target that is part of a multi-entity group — or whose acquisition will make it part of the acquirer’s multi-entity structure — must be consolidated. If the target’s current consolidation is performed in Excel, the due diligence should assess: how many entities are consolidated, what is the elimination methodology, has it been consistently applied across all periods presented, and can it be reproduced independently?
If the answer to “can it be reproduced independently” is no — because the consolidation model is held by one person, uses formulas that are not documented, or relies on data inputs that are manually prepared — then the consolidation methodology is not transferable to the acquirer’s governed consolidation environment without a rebuild. The rebuild cost should be in the integration budget.
Red Flag 5: Arabic-Language ERP With No Bilingual Reporting Capability
For acquirers from outside the GCC, or for listed GCC acquirers who produce English-language reporting, an acquisition target whose ERP and finance function operates entirely in Arabic with no English-language reporting capability presents a specific integration challenge. The chart of accounts is in Arabic; the transaction descriptions are in Arabic; the management reports are in Arabic; and the finance team’s working language is Arabic.
Integrating this target’s financial data into the acquirer’s consolidation environment requires either Arabic-to-English data mapping at the account level (a data governance exercise), bilingual configuration of the target’s ERP (a systems configuration exercise), or a translation layer in the consolidation process (an ongoing operational overhead). The cost and time of this integration path should be assessed pre-close.
Part 3: The Post-Acquisition Finance Integration Programme
When the deal closes, the acquirer must integrate the acquired entity’s finance infrastructure into its own — combining the charts of accounts, connecting the ERP data to the consolidation environment, bringing the acquired entity into the close cycle, and producing consolidated financial statements that include the new entity on the first reporting date after acquisition.
The timeline pressure on this integration is typically underestimated. A GCC acquirer with a quarterly reporting obligation must produce consolidated financials that include the acquired entity within 45 days of the quarter-end. A Tadawul-listed acquirer has an even tighter timeline. The finance integration programme must be designed to deliver a fully functioning consolidated finance environment within the first reporting period after acquisition close — not within a comfortable eighteen-month programme timeline.
Phase 1 — Day 1 Readiness (Weeks 1–8)
Day 1 readiness means the acquired entity can produce financial data that the acquirer can read, classify, and include in a consolidated report — even if that inclusion is done with manual adjustments and workarounds while the full integration programme runs. Specifically:
Emergency chart of accounts mapping: A working mapping from the target’s chart of accounts to the acquirer’s consolidation chart of accounts, sufficient to produce a first-cut consolidation for the first post-close reporting period. This mapping will be imperfect — some accounts will require judgment calls, some reclassifications will be interim — but it must be sufficient to produce a consolidated financial statement that is auditable.
Intercompany transaction identification: A list of all intercompany transactions that now exist between the acquirer’s entities and the acquired entity — management fees, shared service charges, financing arrangements, property leases — and the current recording methodology on both sides, with any asymmetry identified and quantified.
ZATCA and UAE CT compliance status confirmation: Confirmation that the acquired entity is currently compliant with ZATCA (Saudi entities) and UAE CT (UAE entities), or a quantified assessment of the compliance gap that must be closed before the next regulatory deadline.
Close calendar alignment: The acquired entity’s monthly close calendar aligned with the acquirer’s close calendar — which day of the month the ERP is closed, which accounts are reconciled before the trial balance is extracted, and which manual adjustments are applied outside the ERP.
Phase 2 — Consolidation Integration (Weeks 8–20)
Oracle FCCS expansion to include the acquired entity: The consolidation hierarchy in Oracle FCCS is updated to include the acquired entity — either as a new node in an existing regional sub-tree or as a new consolidated group below the existing group structure. The acquired entity’s trial balance data is configured to feed Oracle FCCS, either through the native Oracle ERP connector (if the target runs Oracle) or through a data file import process (if the target runs SAP, Dynamics, or another ERP).
Chart of accounts harmonisation — full reconciliation: The interim Day 1 mapping is replaced by a fully reconciled chart of accounts mapping that addresses every account in the target’s ERP, including judgment calls documented and approved by both the acquirer’s and target’s finance leadership. Accounts that need to be split (one account in the target maps to two accounts in the acquirer’s structure) or merged (two accounts in the target map to one in the acquirer) are handled and the ERP reconfiguration is completed.
Purchase price allocation (PPA) accounting: The IFRS 3 Business Combinations purchase price allocation — identifying and valuing the intangible assets acquired, calculating goodwill, and recording the fair value adjustments in the consolidation — requires both accounting expertise and EPM configuration. Oracle FCCS’s consolidation journals are used to record the PPA adjustments at the consolidation level, separate from the target’s standalone entity accounts.
IFRS 3 consolidation adjustments: First-time consolidation under IFRS 3 requires specific accounting — the elimination of the cost of investment against the acquired entity’s equity, the recognition of non-controlling interests where applicable, and the consolidation of the acquired entity’s results from the acquisition date rather than from the beginning of the period. These adjustments must be correctly configured in Oracle FCCS for the first consolidated financial statements post-acquisition.
Phase 3 — Operational Integration (Months 5–12)
ERP harmonisation decision: The acquirer must decide whether to migrate the acquired entity onto the acquirer’s ERP (Oracle Fusion, SAP S/4HANA, or Dynamics) or to maintain the existing ERP and manage the integration through data feeds. This decision depends on the size of the acquired entity, the complexity of the ERP migration, the regulatory compliance configuration required on the acquirer’s ERP for the target entity’s jurisdiction, and the business case for ERP standardisation.
For large GCC acquirers with significant Oracle investment — Oracle Fusion ERP plus Oracle Cloud EPM — the migration of the acquired entity onto Oracle Fusion is typically the most coherent long-term path. Oracle Fusion’s ZATCA integration, UAE CT configuration, and Oracle EPM native connection provide the compliance and management reporting infrastructure that the acquired entity needs. The migration programme typically takes six to twelve months from initiation for a mid-size entity.
Arabic-language configuration standardisation: Where the acquired entity operates in Arabic and the acquirer’s finance environment is English-primary, the bilingual configuration of the integrated ERP and EPM environment — bilingual chart of accounts, Arabic management reports, Arabic board pack templates — must be completed as part of the operational integration phase.
Oracle EPM workforce planning inclusion: The acquired entity’s headcount and salary data is incorporated into the Oracle EPM Workforce Planning model — expanding the plan-versus-actual workforce cost view to include the new entity from the first planning cycle post-acquisition.
Implementation Scope, Timeline, and Cost Reality
| Integration Scope | Timeline | Professional Services (USD) |
|---|---|---|
| Finance systems due diligence assessment (pre-deal) | 2–4 weeks | 18,000–45,000 |
| Day 1 readiness — emergency chart of accounts mapping, IFRS 3 first close | 4–8 weeks post-close | 25,000–60,000 |
| Oracle FCCS expansion to include acquired entity | 6–14 weeks | 40,000–100,000 |
| Chart of accounts full harmonisation | 6–12 weeks | 30,000–80,000 |
| Purchase price allocation (PPA) EPM accounting configuration | 4–8 weeks | 20,000–50,000 |
| ZATCA compliance remediation for acquired Saudi entity | 4–10 weeks | 25,000–65,000 |
| UAE corporate tax prior-period compliance assessment and remediation | 3–6 weeks | 18,000–45,000 |
| ERP migration — acquired entity to Oracle Fusion | 6–14 months | 150,000–400,000 |
| Arabic-language integration (bilingual chart of accounts, reports) | 4–8 weeks | 20,000–50,000 |
| Full post-acquisition finance integration programme (medium enterprise) | 10–18 months | 200,000–550,000 |
Notes:
- Finance systems due diligence is ideally conducted during the exclusivity or confirmatory due diligence phase — after LOI but before deal close. The assessment output feeds directly into the integration budget and can be used to negotiate deal terms or price adjustments where material system liabilities are identified.
- Day 1 readiness work must begin before deal close — the acquirer’s finance team cannot wait until close to start mapping the target’s chart of accounts.
- Oracle FCCS expansion timeline assumes the acquirer already runs Oracle FCCS. If Oracle FCCS needs to be implemented from scratch to accommodate the acquisition, add 10–20 weeks and USD 80,000–200,000 for the base FCCS implementation.
- ERP migration (acquired entity to Oracle Fusion) is an optional but commonly pursued Phase 3 activity for large acquirers committed to Oracle standardisation.
The Five Most Costly Post-Acquisition Finance Integration Failures in the GCC
1. The Day 1 Consolidation Was Delayed Because Nobody Had Mapped the Chart of Accounts
A Saudi conglomerate acquired a UAE manufacturing business and closed the transaction on March 31. The first quarterly consolidated financial statements — due within 45 days of quarter-end — were required to include the acquired entity’s April to June results. Nobody had mapped the acquired entity’s SAP chart of accounts to the acquirer’s Oracle FCCS consolidation model before deal close. The emergency chart of accounts mapping exercise took six weeks and was still incomplete when the consolidated financial statements were due. The acquirer published its quarterly results with a note that the acquired entity’s contribution had been estimated pending completion of the purchase accounting. The Capital Market Authority (for the listed acquirer) required a supplementary disclosure.
2. ZATCA Non-Compliance Was Discovered Post-Close
A GCC PE fund acquired a majority stake in a Saudi retail group. Financial due diligence confirmed the group’s EBITDA and identified no material tax liabilities. Three months post-close, a ZATCA compliance review — initiated as part of the post-acquisition regulatory audit — found that the acquired entity had not completed ZATCA Phase 2 integration for two of its five operating entities. ZATCA invoices were being issued manually in non-compliant formats. The compliance remediation cost and the estimated penalty exposure represented a material adjustment to the deal economics that had not been in the acquisition price.
3. The Intercompany Transactions Had Not Been Recorded Symmetrically and Three Years of Back-Reconciliation Was Required
A UAE holding company acquired three subsidiaries from a family conglomerate. The three entities had extensive intercompany transactions between them — management fees, property rentals, shared service recharges. In the target group’s consolidated accounts, these had been eliminated manually by the family group’s finance team, who understood informally what the positions were. Post-acquisition, the acquirer’s Oracle FCCS environment attempted to eliminate the intercompany transactions automatically. The automatic elimination failed for 68 percent of intercompany balances because the amounts did not match between entities. Three years of back-reconciliation — understanding why each side of each intercompany transaction had been recorded differently — took eight months and consumed 1.2 FTE of the acquirer’s senior finance team.
4. The Acquired Entity’s ERP Was an Arabic Local System With No API and No English Reporting
A Saudi industrial acquirer bought a UAE logistics company whose finance function operated on a UAE-developed Arabic ERP that had no API, no data export capability beyond printed reports, and no English-language interface. The integration path to the acquirer’s Oracle Fusion environment required a complete finance data re-entry exercise — manually transcribing three years of historical transaction data from the target’s ERP into Oracle Fusion — which took eleven months and produced a reconstructed financial history whose accuracy the acquirer’s auditors could not fully verify.
5. The Purchase Price Allocation Was Done by the Audit Firm and Never Reflected in the Oracle EPM Consolidation
The IFRS 3 purchase price allocation was performed by the acquirer’s Big Four audit firm, producing a PPA schedule that identified USD 45 million of customer relationships, USD 18 million of technology intangibles, and USD 12 million of goodwill. The PPA adjustments were reflected in the audited consolidated financial statements. They were never configured in Oracle FCCS — the consolidation system continued to hold the acquired entity at its historical net asset value rather than at the PPA-adjusted fair value. For two years, the amortisation of the acquired intangible assets was calculated offline and entered as a manual journal adjustment at every annual close. When the acquirer was itself subject to an acquisition, the due diligence team found that the Oracle FCCS consolidation did not reconcile to the audited financial statements — the PPA had never been in the system.
Frequently Asked Questions
Q: What does financial due diligence cover in a GCC acquisition that is different from standard Western M&A due diligence? Financial due diligence in the GCC covers the standard QoE (Quality of Earnings) analysis — revenue quality, EBITDA normalisation, working capital assessment, net debt identification — and adds GCC-specific dimensions that standard Western frameworks do not systematically address. The most material additions: ZATCA Phase 2 compliance assessment for Saudi entities (whether ZATCA integration is certified, complete, and current, with a quantified exposure for any non-compliance); UAE Corporate Tax compliance since June 2023 (whether CT has been correctly calculated, accrued, and filed, including deferred tax and qualifying income assessments for free zone entities); GOSI contribution compliance for Saudi entities (whether the contributory salary basis is correct and whether all employees are registered); related-party transaction arm’s-length pricing assessment (whether management fees, property rents, and procurement from family-connected entities are priced on market terms or at terms that inflate EBITDA); and finance systems assessment (whether the target’s ERP data is reliable, reconcilable to the audited accounts, and integrable into the acquirer’s consolidation environment).
Q: How long does post-acquisition finance integration take in Saudi Arabia or the UAE? A focused post-acquisition finance integration for a mid-size GCC entity — chart of accounts harmonisation, Oracle FCCS consolidation expansion, Day 1 close capability, and IFRS 3 purchase accounting configuration — typically takes ten to eighteen months from deal close to a fully integrated, independently operable finance environment. The Day 1 component — the emergency chart of accounts mapping and first consolidated close — must be operational within four to eight weeks of deal close for acquirers with quarterly reporting obligations. The full programme, including ERP migration to the acquirer’s platform and bilingual Arabic-English configuration where applicable, runs twelve to eighteen months. The most consistent accelerator is pre-close preparation: acquirers that begin the chart of accounts mapping and Oracle FCCS hierarchy design before deal close achieve Day 1 readiness materially faster than those that start post-close.
Q: What is purchase price allocation (PPA) and how does it affect Oracle FCCS after an acquisition? IFRS 3 Business Combinations requires that when an acquisition closes, the acquirer identifies and measures at fair value all assets acquired and liabilities assumed — including identifiable intangible assets (customer relationships, technology, brand, contracts) that were not on the target’s balance sheet. The difference between the total consideration paid and the fair value of net assets acquired is goodwill. These purchase price allocation adjustments affect the Oracle FCCS consolidation model: the acquired entity’s assets must be restated to their IFRS 3 fair values in the consolidation, goodwill must be recognised and monitored for impairment, and the amortisation of acquired intangibles must be calculated and posted as a consolidation adjustment at every close period. PPA adjustments that are not configured in Oracle FCCS — left as manual adjustments to the audited accounts — create a persistent reconciliation gap between the Oracle FCCS output and the audited consolidated financial statements.
Q: How should a GCC acquirer prepare for the first post-acquisition consolidation close? The first post-acquisition consolidation close is the most technically demanding close the acquirer’s finance team will run — it introduces a new entity with an unfamiliar chart of accounts, requires IFRS 3 purchase accounting adjustments that have never been through the Oracle FCCS environment before, adds new intercompany balances to the elimination schedule, and must be completed within the same reporting deadline as the standard close. Preparation should begin before deal close: map the target’s chart of accounts to the acquirer’s consolidation structure, identify the intercompany transactions that will exist on Day 1, design the Oracle FCCS hierarchy change that accommodates the new entity, and prepare the first draft IFRS 3 opening balance sheet. Run a mock close before the actual close. Have the finance systems integration team available during the close period rather than waiting to engage them after the close has been attempted.
Q: Should we migrate the acquired entity to our Oracle Fusion ERP or maintain their existing system? The migration decision depends on four factors. First, the size and complexity of the acquired entity: a large entity with complex operations is a more disruptive migration target than a small, straightforward business. Second, the regulatory compliance configuration required: a Saudi entity needs ZATCA certification, GOSI integration, and Saudi localisation in the ERP — if these already exist in the acquirer’s Oracle Fusion environment, the migration path is cleaner than maintaining them in the target’s existing ERP. Third, the cost and disruption of migration versus the ongoing cost of maintaining a separate ERP and managing the data integration between the two systems: the break-even point depends on the entity size and the data complexity, but for entities above a few hundred employees, the ongoing cost of maintaining a separate ERP typically exceeds the migration cost within three to four years. Fourth, the EPM integration benefit: for acquirers running Oracle Cloud EPM, an acquired entity on Oracle Fusion ERP connects natively to Oracle FCCS, Oracle EPM Planning, and Oracle Analytics Cloud — the same native connection that makes Oracle ERP the preferred choice for Oracle EPM users, as described in the ERP comparison pillar. An acquired entity running SAP or Dynamics requires a custom data integration to achieve the same Oracle EPM connectivity.
Q: What GCC-specific liabilities should acquirers look for in financial due diligence that might not appear in the financial statements? Four GCC-specific liability categories that standard financial statements may not fully reflect. First, ZATCA compliance exposure: uninvoiced transactions, incorrectly formatted e-invoices, and Phase 2 integration gaps represent a regulatory liability that is not typically accrued in the financial statements until a ZATCA audit is initiated. Second, GOSI contribution underpayment: if the target has been calculating GOSI contributions on the wrong salary basis — excluding allowances that should be included — the underpayment liability goes back to the employment start date and is subject to GOSI audit recovery. Third, UAE CT prior-period exposure: if the target has incorrectly classified free zone income as qualifying income, or has not correctly calculated the corporate tax provision since June 2023, the prior-period tax exposure is a liability that accrues from the effective date, not from when it is identified. Fourth, PDPL remediation liability: if the target’s ERP or HR system stores personal data outside the required jurisdiction, the cost of migrating to a compliant hosting arrangement — or establishing a transfer framework — is a compliance cost that should be quantified and included in the deal model.
About Loop Wise Solutions
Loop Wise Solutions is an enterprise performance consultancy based in Cairo, serving medium and large enterprises across Egypt, Saudi Arabia, the UAE, Qatar, and the broader Arab world. Our Business and Technical Consultancy practice provides independent finance systems due diligence assessments for GCC acquisitions and post-acquisition finance integration advisory for enterprises that have completed or are completing a transaction.
Our M&A finance systems work covers pre-deal ERP architecture assessment and chart of accounts risk quantification, Day 1 readiness planning that begins before deal close, Oracle FCCS consolidation expansion to include acquired entities, IFRS 3 purchase price allocation EPM configuration, ZATCA and UAE CT compliance remediation for acquired entities, chart of accounts harmonisation, and ERP migration planning for acquirers standardising on Oracle Fusion.
If you are in the due diligence phase of a GCC acquisition and want to understand the finance systems risk embedded in the target, or if you have recently closed a GCC acquisition and need to integrate the acquired entity’s finance infrastructure into your Oracle EPM consolidation environment, we are happy to have a direct conversation.
Contact: contact@loop-wise.com | Website: www.loop-wise.com
Where performance meets precision.
