A group with one entity on SAP near KAFD and another on a different system entirely near Al Malaz turns a routine monthly consolidation into a manual reconciliation exercise every time.

This is frequently the single slowest step in a month-end close for multi-entity Riyadh groups, and it's closely tied to the underlying finance operating model, since how consolidation actually happens depends heavily on whether entities record transactions centrally or independently.

Why consolidation gets harder as groups grow organically

A Riyadh-headquartered company that adds a branch and later a subsidiary, each set up at different times with whatever system or chart of accounts made sense at the time, ends up with entities that don't naturally align for consolidation. Each new entity added without a deliberate chart of accounts standardization compounds the manual mapping work required every period.

What proper consolidation infrastructure actually requires

A standardized chart of accounts mapping across all entities, however different their day-to-day operations, a consistent intercompany elimination process that catches transactions between entities before they double-count group revenue or expenses, and clear ownership of the consolidation process itself rather than it falling to whoever has time during a busy close.

Intercompany transactions as a specific risk area

Transactions between related entities, management fees, intercompany loans, goods transferred between a Riyadh trading arm and a Riyadh subsidiary, need to be properly eliminated in consolidation and also correctly priced for transfer pricing purposes, since these are really two different requirements sitting on the same underlying transactions.

What we deliver

A standardized chart of accounts mapping across your entities, a documented intercompany elimination process, and a consolidation workflow that turns what's currently a manual reconciliation scramble into a repeatable, faster monthly step.

Making the transition without disrupting the current close

Standardizing the chart of accounts across entities that have operated independently for years takes careful sequencing, since you can't simply switch everything over mid-year without risking a broken close in the transition period. We typically phase this across two to three closing cycles rather than attempting it all at once.

Local context

Groups that grew through acquiring or establishing entities in Riyadh at different times, each on whatever system was convenient then, carry the heaviest consolidation burden, since the underlying data structures were never designed to come together cleanly in the first place.