European SME, UAE Subsidiary: Compliant Reporting From Day One

Dubai Chamber counted 2,719 active German member companies by the end of Q1 2025, and German company formations in the emirate kept climbing at a fast clip through the rest of the year. Italian companies are showing up at a similar pace: DMCC alone now counts more than 530 of them, part of a broader run-up in Italian investment across the Gulf. This isn’t a trickle. It’s a genuine corridor, and most of these companies are landing with a finance-stack problem nobody warned them about.

DATEV doesn’t travel, and neither does the commercialista’s system

Here’s the detail that trips up almost every one of these expansions. The German parent keeps DATEV and its Steuerberater relationship exactly where it’s always been, at home. The new UAE subsidiary doesn’t run DATEV; it runs whatever the local outsourced accounting firm sets it up with, usually Zoho Books, Xero, QuickBooks, or Odoo. Italian groups run the same pattern with a different name on it: the commercialista keeps Italian GAAP, consolidation, and transfer pricing at the parent, while the UAE sub’s day-to-day bookkeeping, VAT, corporate tax, and soon e-invoicing get handled locally.

That means the actual problem isn’t “which ERP should the subsidiary use.” Someone local has already made that call, usually sensibly. The problem is what happens next: getting a trial balance and a set of compliant figures back to a parent that has no visibility into the UAE system and no reason to trust a number it can’t independently check. That’s a reporting-back problem, not a ledger-replacement problem, and it’s worth being precise about the difference, because a lot of tools in this space try to solve the wrong one.

The forcing function isn’t optional anymore

UAE corporate tax changed the calculus for every one of these subsidiaries. A 9% rate, mandatory registration, IFRS-compliant financial statements, seven years of retained records, and an audit that’s effectively required if the entity wants to keep 0% treatment under the Qualifying Free Zone Person regime. On the Saudi side, ZATCA’s e-invoicing rollout (Phase 2) is pulling more businesses into mandatory scope every wave. Put together, these subsidiaries need IFRS-grade, locally compliant reporting from day one, not once they’ve grown large enough to justify hiring a full finance team.

Most of these entities are small: often one to ten people, with the “finance function” effectively being whichever local fiduciary firm set the entity up in the first place. There usually isn’t an internal finance team to hand this problem to.

Where a reconciled reporting layer fits

If your UAE subsidiary is already on Zoho, Xero, QuickBooks, or Odoo (which it almost certainly is if a local firm set it up), the practical move is a reporting layer that ingests that existing trial balance and produces a cited, reconciled version both the local authorities and the parent’s home-country advisor can trust, without asking anyone to migrate off a system that’s working fine. That’s the shape of what’s needed for ZATCA Phase 2 readiness on the Saudi side and UAE corporate tax preparation on the UAE side: not a new ledger, a trustworthy layer on top of the one already in place.

The same logic applies the moment a group formalizes the entity itself: see new subsidiary setup for what that first ninety days of compliance actually involves, and ERP migration continuity if the local system ever does need to change without breaking the reporting history built on top of it.

A slightly larger tier, worth naming honestly

A minority of these subsidiaries, a meaningful but not dominant share, grow into ten to a hundred staff with an actual controller on the ground. Their real pain shifts slightly: it’s group reporting back to a DATEV, LucaNet, or commercialista-managed parent, plus the UAE corporate tax and IFRS obligations layered on top. The artifact that solves both sides at once is a cited trial balance and a compliance-ready pack that the local authority and the home-country advisor can both independently verify, not a DATEV integration, and not a claim that the UAE side ever needs to look like the German or Italian one.

Who this is for

This is for the finance function, however small, behind a European SME’s UAE subsidiary: whether that’s a lean internal controller or the local fiduciary firm effectively running the books. If your subsidiary’s books are already sound but the parent company and the tax authority both need a version of the truth they can each check independently, that’s the specific gap this closes.

For more on how Rexfin approaches compliance and reporting across the region’s different use cases, visit the finance team use cases hub.