Excel is not the villain. It is the residue of good decisions made when the family had two entities and one bank.
The break point is predictable. Once a family office passes roughly five entities, three or more banking relationships and two currencies, spreadsheet finance starts costing more than it saves.
Around two-thirds of family offices still rely on manual methods for wealth aggregation and reporting. UBS research puts the average office at more than five financial institutions.
The UAE adds a regulatory deadline to a management problem. Corporate tax is filed per entity. E-invoicing pilots opened on 1 July 2026, with mandatory adoption from 1 January 2027 for businesses with AED 50 million in revenue or more. Structured XML replaces PDF, and free zone entities are in scope.
A workable finance system needs one entity hierarchy, a functional currency per entity, automated intercompany elimination, an audit trail per transaction, and reporting anyone trained can reproduce.
Walk into most UAE family offices and you will find a finance function that looks nothing like the wealth it manages. The portfolio is global. The structure spans DIFC or ADGM, mainland, a free zone or two, and several property SPVs. The reporting runs through a workbook that one person maintains and nobody else fully understands.
This is not carelessness. It is history. Every spreadsheet in that stack was the right answer at the moment it was created.
The question is whether it is still the right answer now, with ten entities, five banking relationships and three currencies in play. Usually it is not, and the family knows it. What is missing is a clear read on where exactly the model breaks and what replacing it involves.
Four reasons, and they are all rational.
1. Family offices are small. Ten or fifteen people can coordinate informally. Nobody feels the process gap until someone leaves.
2. Privacy instincts run deep. A spreadsheet feels contained. Enterprise software feels exposed, even when it is objectively more secure.
3. Structures grew one entity at a time. No single addition justified rebuilding the finance function, so none of them did.
4. Investment performance dominates attention. Operations get judged on whether the report arrived, not on how long it took to build.
The result is a finance function that is competent, overworked and structurally fragile. It performs well until something changes, and then it performs badly all at once.
With two or three entities, manual consolidation is a morning’s work. At five it becomes a multi-day exercise. At ten it becomes a role.
The reason is combinatorial. Each new entity adds a chart of accounts to reconcile, a set of intercompany relationships to track, a filing calendar to maintain and a bank account to reconcile. Five entities do not create five times the work of one. They create considerably more.
For context on scale, NetSuite OneWorld accounts support up to 250 subsidiaries before further discussion with Oracle is required. Family offices rarely approach that. They typically fail well before twenty because the process, not the platform, is the constraint.
Two currencies can be handled with a rate column. Three or more cannot, once you need consistent translation.
The issues stack up. Which rate applies to balance sheet items versus income statement items? What happens to translation differences? How do you compare this quarter to last when the rate moved? A family holding AED property, USD securities and GBP or EUR assets faces this every reporting cycle.
A proper system assigns a functional currency to each entity and translates consistently at consolidation. NetSuite OneWorld supports more than 190 currencies with real-time exchange rates and a base currency per subsidiary. A spreadsheet supports whatever the person building it remembered to apply that month.
This is the one that causes real damage, and it hides for years.
Family entities lend to each other constantly. The trading company funds an SPV fit-out. The foundation covers a shortfall. Sometimes both sides record it. Often only one does.
Over a decade, these unmatched balances become material. They inflate group assets if not eliminated. They distort entity-level accounts that now carry corporate tax obligations. They surface awkwardly during any due diligence, sale or external investment. And reconstructing them from bank statements years later is expensive work.
An ERP handles this by design. Mark a transaction as intercompany and the elimination journal generates automatically at consolidation. NetSuite also offers intercompany netting to settle balances between entities. The manual alternative depends on nobody forgetting, ever.
UBS research indicates the average family office works with more than five financial institutions. UAE families often exceed that, holding local relationships in Dubai and Abu Dhabi alongside international private banking.
Each institution delivers data in its own format, on its own timetable, with its own instrument classifications. Somebody normalises all of it by hand before reporting can start. That work is invisible in any job description and consumes a large share of the finance team’s month.
A spreadsheet records the answer, not the reasoning. Six months later, when someone questions a figure, the trail is a formula and a memory.
This was tolerable when family entities filed almost nothing. It is not tolerable now that corporate tax applies at 9% above AED 375,000 of taxable profit and filings are non-per-taxable-person. Substantiation is the point of the exercise, and formulas do not substantiate.
Management inconvenience can be deferred indefinitely. Compliance deadlines cannot, and the UAE now has one that touches every family group with a trading arm. For a full walkthrough of what's changing and why, see e-invoicing explained.
The e-invoicing framework was established through Ministerial Decisions No. 243 and 244 of 2025. The rollout runs like this:
• 1 July 2026: Pilot and voluntary phase opened. Early adopters are exempt from penalties during this window
• 30 October 2026: Businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider. This deadline was extended from 31 July 2026 by Ministerial Decision No. 56 of 2026
• 1 January 2027: Mandatory go-live for that group
• 31 March 2027: ASP appointment deadline for businesses below AED 50 million and for government entities
• 1 July 2027: Mandatory go-live for businesses below the threshold
• 1 October 2027: Mandatory go-live for government entities
• 1 January 2029: Full compliance required for intra-VAT-group transactions, following a transition period
The technical requirements matter more than the dates. A valid UAE e-invoice is a structured XML file under the PINT AE specification, based on UBL 2.1, exchanged through an Accredited Service Provider on a Peppol-based network with tax data reported to the FTA. In February 2026 the FTA published a technical document setting out 51 mandatory fields and confirming the Tax Identification Number as the participant identifier, defined as the first ten digits of the corporate tax registration number. Version 1.1 of the guidelines was followed on 1 June 2026, with updates on advance payment linking and retention billing. This sits within the broader shift toward digital VAT compliance that UAE businesses now need to plan around.
Paper, PDF, scanned copies and Excel files will not qualify as compliant e-invoices for B2B and B2G transactions. Free zone businesses, including DMCC, JAFZA, IFZA, RAKEZ, ADGM and DIFC entities, are explicitly in scope with no exemption.
Penalties under Cabinet Decision No. 106 of 2025 include AED 5,000 per month for failure to implement or appoint a provider, AED 100 per non-conforming invoice, and AED 1,000 per day for failing to notify the FTA of system malfunctions within the required window.
The practical implication is straightforward. Master data quality decides whether this goes smoothly. Mismatched customer records, inconsistent tax treatment and untidy product descriptions all fail in a structured system. Cleaning them is a multi-month job and it's where most businesses stumble. Our rundown of e-invoicing mistakes to avoid covers the ones we see most often.
The cost is rarely a line item, which is why it goes unmanaged. It shows up in five places.
• Time - A finance team spending ten to fifteen days a month on aggregation and reconciliation is spending most of its capacity on data assembly rather than analysis
• Error exposure - Every manual entry is a failure point. In a consolidated net worth statement, one miskeyed figure can misstate a position by millions, and no manual workflow reliably catches it before it reaches a decision-maker
• Decision lag - Reports that arrive three weeks after period end describe a position that has already moved. Liquidity decisions get made on instinct
• Key-person risk - When the person who built the model leaves, the model becomes an artefact rather than a process
• Deferred cost - Every year of unreconciled intercompany balances raises the eventual cost of cleaning them, and that bill always arrives at the worst moment, during a transition, a sale or an audit
For context, J.P. Morgan reporting places average family office operating cost around USD 3.2 million a year, rising to USD 6.6 million for offices above USD 1 billion in the 2026 edition, with staff costs dominating. A finance team consuming half its month on manual assembly is an expensive way to produce a late report.
• Consolidation: Manual, entity by entity, rebuilt each cycle
• Currency: Rates applied by hand, method varies by preparer
• Intercompany: Matched manually, frequently incomplete
• Audit trail: Formulas and file versions
• Close timeline: Two to four weeks, dependent on one person
• Corporate tax: Entity positions derived at year end
• E-invoicing: Not possible without a separate compliant tool
• Access control: File permissions, all or nothing
• Continuity: Knowledge held by an individual
• Consolidation: Automated across the subsidiary hierarchy, real time
• Currency: Functional currency per entity, consistent translation at consolidation
• Intercompany: Elimination journals generated automatically, netting available
• Audit trail: Transaction level, with drill-down from consolidated figures to source
• Close timeline: Predictable cycle with named owners and tracked tasks
• Corporate tax: Entity positions visible continuously
• E-invoicing: Structured invoice data mapped to mandatory fields and routed to an accredited provider
• Access control: Role-based, so branches and staff see only what they should
• Continuity: Process documented in the system, reproducible by new staff
The right comparison is not features. It is what happens on the day the person who built the workbook does not come in.
Search results split cleanly into two categories, and choosing the wrong one wastes both budget and a year.
These connect custodian and bank feeds and answer the investment question. Commonly shortlisted names include Addepar, Masttro, Asora, Aleta, Landytech’s Sesame, Asset Vantage, FundCount and Canoe Intelligence for private markets document extraction. Several now use AI to read capital call notices and NAV statements that previously required manual entry.
What they generally do not do is own the general ledger, file corporate tax positions, or issue compliant invoices.
Oracle NetSuite sits here. The relevant capabilities for a family office structure are OneWorld for multi-subsidiary consolidation, Multi-Book Accounting for parallel reporting standards, automated intercompany elimination, and multi-currency support across more than 190 currencies with a base currency per subsidiary. For a closer look at how it fits the region's compliance needs specifically, see our guide to NetSuite for UAE e-invoicing, or browse the broader field in our ERP comparison for e-invoicing compliance.
NetSuite’s 2026 releases moved AI into finance operations rather than offering it as an add-on. The 2026.1 release brought Intelligent Close Manager with AI-driven exception detection and projected activity, generative AI in bank transaction matching, and Exception Management with payment risk detection that flags vendor data changes near payment events. The 2026.2 release started the NetSuite Next rollout with Ask Oracle, a natural language assistant, plus batch payment runs, automated payment adjustments for bank fees and underpayments, and new CFO Insights labour cost reports across subsidiaries.
For a family group that owns operating businesses, the working answer is usually an ERP as the system of record with an aggregation platform layered on top for portfolio reporting. For families holding only liquid assets with no trading entities, an aggregation platform alone may be enough.
Families overestimate the software effort and underestimate the data effort. The realistic sequence for a group with five to fifteen entities runs four to seven months.
Entity register and scoping. Every entity, jurisdiction, licence, ownership chain, functional currency and filing obligation, documented in one place. Two to three weeks.
Chart of accounts design. One group mapping, with room for local detail at subsidiary level. Three to four weeks.
Intercompany reconciliation. The longest and least popular step. Six to twelve weeks depending on how many years need unwinding.
System build. Entity hierarchy, currencies, consolidation rules, elimination setup, opening balances. Six to ten weeks.
Parallel run. One or two cycles alongside the old process to validate outputs before switching. Four to eight weeks.
E-invoicing enablement. Field mapping, master data cleanup and accredited provider connection for in-scope entities, sequenced against the applicable deadline.
The two failure patterns are consistent. Families that skip intercompany reconciliation carry the mess into the new system. Families that skip the parallel run lose confidence in the outputs and quietly keep the spreadsheet alive, which produces the worst outcome of all: two versions of truth and twice the work.
The usual trigger is a combination rather than a single number: around five or more legal entities, three or more banking relationships, two or more currencies, and any entity with corporate tax filing or invoicing obligations. If three of those four apply, spreadsheet finance is already costing more in time and risk than a system would cost to run.
Yes, and this is a common structure. A dormant or low-activity SPV still needs a place in the entity hierarchy, a functional currency, a filing record and an intercompany position. Modelling it in the system costs very little and removes it from the manual pile. The effort concentrates on active trading entities, not on holding vehicles.
It depends on whether the entity issues invoices. The mandate covers B2B and B2G transactions, so a pure holding SPV with no invoicing activity has limited direct exposure. A family trading company, a property entity issuing rental invoices to businesses, or a management company charging fees to group entities all need to assess scope. Intra-VAT-group transactions have a transition period to 1 January 2029. Scope should be confirmed entity by entity rather than assumed for the group.
Cost varies with entity count, transaction volume, integration requirements and how much data cleanup is needed before go-live. The largest swing factor is almost always the state of the opening data, particularly unreconciled intercompany balances, rather than the licence itself. A scoping exercise that quantifies entity count, currencies, banking relationships and data condition gives a far more reliable estimate than any published range.
It generally increases both. A shared workbook offers file-level permissions, meaning anyone with access sees everything. A system of record offers role-based access, so a family branch sees its own position, an analyst sees the entities they support, and the group view stays restricted. Add transaction-level audit trails and controlled approvals, and oversight improves rather than weakens.
There is no case for treating Excel as a mistake. It carried the family office from one entity to ten, through several currencies and a lot of growth, and it did so cheaply.
The case is about fit. Ten SPVs, five banks and three currencies describe a group finance function, and group finance needs a ledger, an entity hierarchy, automated elimination and an audit trail. The UAE regulatory calendar has now put a date on that conclusion, and the pilot phase is already open.
SaasWorx works with UAE organisations that have outgrown spreadsheets, legacy systems and disconnected tools, implementing Oracle NetSuite for multi-entity accounting, consolidated reporting, corporate tax visibility and e-invoicing readiness. The right time to build that foundation is before the deadline, not during it.
