L
O
A
D
I
N
G
Zoho, Odoo, ERPNext, Dynamics 365 and custom ERP, delivered by one accountable team.
At 1,000 people the ERP becomes the group's control system: several entities, internal and external audit, a dozen integrations and a payroll that touches every family that depends on it.
A 1,000-employee UAE company usually needs an ERP programme built around group structure: several legal entities, consolidation with intercompany eliminations, single sign-on and segregation of duties, procurement with budget checks, payroll and WPS per entity, employee self-service and many integrations. Rollout typically runs in waves by entity after a pilot proves the template, and e-invoicing applies from 1 January 2027 for revenue above AED 50 million.
Choosing an ERP for a 1000 employee company in the UAE is a programme, not a software purchase. Organizations of this size are usually groups: a holding structure with five to ten legal entities, perhaps a free zone trading company, a mainland contracting or services arm, and sometimes subsidiaries in Saudi Arabia or Oman. Several hundred people may use the ERP each day, and the rest of the workforce interacts with it through self-service, attendance and approvals.
The organization has functions that smaller companies do not: a shared-services finance team, an internal audit or risk function, an IT team with its own identity and security policies, a procurement department running tenders, and a board that expects monthly packs on consolidated results. External auditors test controls, not just balances. Banks and lenders ask for covenant reporting.
Regulation also bites harder. Many groups of this size cross the AED 50 million revenue line that brings UAE e-invoicing into force from 1 January 2027, and some reach the AED 200 million revenue threshold at which corporate tax transfer pricing documentation (master and local file) applies. This page focuses on what changes at group scale; the 500 employee company guide covers the mid-size stage, and our large enterprise ERP overview explains the broader software market.
These problems are less about missing features and more about scale, control and coordination.
Each entity closes in its own system or file, and the group result is assembled by two or three finance staff in Excel with manual eliminations. Automated consolidation with mapped charts of accounts and currency translation removes that key-person risk.
Management fees, staff secondments, equipment hire and shared office costs flow between entities every month. Without mirrored postings and matching, differences surface only at the audit, and they also feed related-party disclosures for corporate tax.
Shared logins, users who can both create and approve a supplier, and approval limits enforced by habit rather than by system make audit findings repetitive. Role design and segregation-of-duties checks need to be part of the ERP build.
Banks, biometric devices, a CRM, a procurement portal, Power BI, an e-invoicing Accredited Service Provider and sometimes a legacy HR system all need data. Point-to-point scripts built by different vendors fail silently.
With a thousand staff, HR cannot answer every leave or certificate query by email. Self-service, document expiry control and structured onboarding and offboarding flows become operational necessities.
Each department has its own spreadsheets and preferences. Without a programme office, steering committee and process owners, the ERP is configured around exceptions and adoption stalls after go-live.
At this size the differences between platforms are sharper. Fit depends on the number of entities and countries, audit expectations, and the internal team you can dedicate. Confirm editions and limits for your case.
| Zoho | Odoo | ERPNext | Dynamics 365 | |
|---|---|---|---|---|
| Typical setup at this size | Zoho One across departments, often with Zoho Analytics for group reporting and Creator for bespoke apps | Odoo Enterprise multi-company on Odoo.sh or dedicated self-hosting | ERPNext and Frappe HR on dedicated infrastructure, managed by an in-house or partner team | Dynamics 365 Finance and Supply Chain Management for complex groups; Business Central for simpler ones |
| Licensing at 1,000 staff | All-employee or flexible-user model; model the total carefully at this headcount | Per internal user; self-service and portal access do not need full user licences | No licence fees; budget shifts to infrastructure, support and development | Per named user by application, with Team Members and other light licences for occasional users |
| Consolidation and intercompany | Separate Books organizations per entity, consolidated through Analytics or a consolidation process | Multi-company with intercompany rules; group consolidation often set up with reporting or a consolidation app | Multi-company with a consolidated financial statements report | Mature consolidation, intercompany and multi-currency features in Finance |
| Security and segregation of duties | Role profiles per app; Zoho Directory supports single sign-on options | Access groups and record rules; SoD checks usually designed by the partner | Role permissions and user permissions per document; SoD built through role design | Granular security roles, Microsoft Entra ID single sign-on and segregation-of-duties rules in Finance |
| HR and payroll at this scale | Zoho People for HR; confirm UAE payroll and SIF approach for your entities | Odoo HR and Payroll with UAE localization; SIF and gratuity rules to configure | Frappe HR with UAE rules configured or customized; strong for large employee bases without licence cost | HR in Finance and Operations apps; UAE payroll usually through an ISV or integrated payroll system |
| Hosting and performance | Zoho cloud; performance managed by Zoho | Dedicated Odoo.sh or self-hosted sizing for payroll runs and transaction volume | Your own servers or dedicated Frappe Cloud; you own tuning and backups | Microsoft cloud with environments for test and production |
| Internal team needed | An ERP owner and admins per suite area | An ERP owner, functional admins and developer access through a partner | A technical team comfortable with Python and the Frappe framework | An ERP centre of excellence working with the implementation partner |
| Best fit at 1,000 employees | Service and people-heavy groups that value one suite | Operations-heavy groups wanting one database across entities | Groups with strong IT that want control and no licence fees | Multi-country groups with complex finance and strict audit needs; see Dynamics 365 for enterprise |
We implement Zoho, Odoo, ERPNext and Dynamics 365 and recommend by fit. We do not implement SAP or NetSuite, though we compare them honestly when they are on your shortlist.
At this size the order of work is driven by control and risk, not by which module is easiest.
Common chart of accounts, entity structure, intercompany rules and consolidation with eliminations, configured once as a group template.
Single sign-on, role catalogue, approval matrices and segregation-of-duties rules signed off by finance and internal audit.
Purchase requisitions, tenders and RFQs, budget checks, contract pricing and three-way matching across entities.
Positions, grades, cost centres and reporting lines that every other module uses for approvals and cost allocation.
Pay groups per entity and bank, gratuity accruals for the full workforce, and SIF generation with validation before submission.
An employee self-service portal and mobile app for leave, payslips, letters and expense claims, so HR handles exceptions only.
A managed integration layer for banks, attendance devices, CRM and the Accredited Service Provider, with monitoring and error queues.
Board packs, entity scorecards and headcount analytics built on governed ERP data rather than exported spreadsheets.
These obligations affect system design for most groups of this size. They describe how the ERP supports compliance; confirm the position for your entities with your tax advisor.
Businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026 and exchange PINT AE invoices from 1 January 2027. Each entity's invoice data, TRNs and customer master must be clean. Check the latest Ministry of Finance and FTA guidance.
Related-party transactions between group entities need to be identifiable in the ledger. Transfer pricing documentation (master and local file) applies where revenue reaches AED 200 million or group revenue reaches AED 3.15 billion; see transfer pricing support in ERP.
Tax records must be kept for at least five years, and seven for real estate, under Cabinet Decision 74 of 2023. Archiving and data retention policies should be designed before old systems are switched off.
Salaries are paid through WPS with a Salary Information File per employer. Gratuity accrues at 21 days' basic wage per year for the first five years and 30 days per year after, capped at two years' wage, which is a material liability across a thousand staff.
General information, not tax or legal advice. Rules change; confirm current FTA, MOHRE and Ministry of Finance guidance with your advisor.
A group rollout is usually run as a template and waves. Ranges are typical and depend on entity count, integrations and data readiness.
Durations are typical ranges; your plan is agreed after discovery.
Steering committee, process owners, group template design, role catalogue and integration architecture agreed and signed off.
Configure the template, build integrations and migrate the pilot entity, followed by user acceptance testing and a controlled go-live.
Remaining entities go live in groups, reusing the template and adding local variations only where justified.
Employee data, document records and pay structures migrated, with parallel payroll runs per entity before WPS files move to the new system.
Controls review with internal audit, BI roll-out and a backlog of improvements managed by the ERP centre of excellence.
These are the outcomes groups of this size typically target; actual results depend on scope and adoption.
Entity closes run on the same calendar and consolidation is generated from the system, not rebuilt each month.
Approvals, role separation and change logs are enforced in the system, reducing repeat audit findings.
HR, payroll, attendance and costing share the same employee and position data across every entity.
Management packs come from the ERP and BI layer, so discussions are about decisions rather than reconciling numbers.
We configure the system for the rules UAE businesses report against, and test it before go-live.
General information, not tax or legal advice. Confirm current requirements with the FTA, MOHRE or your advisor. See all UAE compliance guides.
On-site workshops in Dubai, Abu Dhabi and Sharjah, and remote or on-site delivery across the Northern Emirates and free zones.
Official sources and references
Facts on this page were checked against these sources in October 2026. Rules change, so confirm current requirements before acting.
Still have a question? Our consultants are happy to help.
Ask an ExpertOften yes, if the group has a handful of UAE entities and moderate audit requirements. Headcount alone does not decide it; the number of entities and countries, consolidation complexity and control requirements matter more. Multi-country groups with strict audit expectations usually need an enterprise tier.
It varies widely by industry. A services group may have most staff as users, while a contracting or facility management group may have only a few hundred transacting users and many self-service users. Count roles, not people, when estimating.
One instance with multiple companies is usually better for consolidation, shared masters and intercompany. Separate instances can make sense for a business with very different processes or a planned divestment. Decide this in the global design phase.
Start with a role catalogue that lists who can create, approve and post each document, then test it against known conflicts such as creating a supplier and paying it. Internal audit should sign off the matrix before go-live and review it periodically.
Twelve to eighteen months across all waves is common for multi-entity groups, with the pilot entity often live within six to nine months. Tight scope, an empowered steering committee and clean data shorten it.
Yes, if it is reliable and integrated. The ERP then receives employees, cost centres and payroll journals through an interface. Many groups still choose to consolidate HR into the ERP later to remove duplicate employee records.
Related Solutions
Related Industries
Related ERP Platforms
Share your entity structure, systems landscape and audit requirements, and we will outline a template-and-waves plan for your group.
Dubai, United Arab Emirates
