UAE Climate Law for Foreign Branches and Multinational Groups

The most common multinational error is to ask whether the foreign parent is “covered”. The more useful question is whether an activity, branch, establishment or facility in the UAE is a Source and whether MOCCAE or the relevant competent authority has identified a reporting duty. The legal and operational unit may be the branch, a licensed site, a permit holder, an operator or another designated perimeter.

The second error is to rebuild the inventory locally from scratch. Parent systems can provide strong controls, consistent factor libraries, automated calculations and group assurance. The solution is controlled reuse: preserve the parent dataset, add a UAE overlay, document every adjustment and produce a local output that can stand on its own during verification or inspection.

Reuse the parent system, but preserve UAE-specific boundary, method, evidence, portal, retention and data-protection decisions.

Federal Decree-Law No. (11) of 2024 requires records for designated Sources but does not state a general rule that every GHG workbook, invoice or meter file must be hosted on a server physically located in the UAE. That does not make unrestricted overseas storage or access acceptable. The company must assess the nature of the information, the authority’s portal terms, cybersecurity requirements, commercial confidentiality, contracts, sector rules and any free-zone regime.

Personal data require particular care. Fleet, travel, access-control and maintenance systems may contain driver names, employee IDs, location histories, contact details or technician records. The UAE federal personal-data framework addresses processing security and cross-border transfer or sharing. DIFC, ADGM or another special regime may also apply. A climate inventory normally needs fuel, distance, asset and activity data - not an unrestricted copy of every personal identifier.

Maintain a local or locally accessible index of all evidence supporting the UAE submission, with owner, access level, system location and retention date.

Store authority correspondence, designation evidence, portal receipts, local approvals and verification findings in a controlled UAE compliance folder or repository.

Use immutable exports or hashes for material source-system extracts so a verifier can reproduce the reporting-period dataset after the parent system changes.

Retain factor and methodology versions, not only the current global library.

Ensure local management can retrieve the evidence during an inspection without relying on a person in another time zone or a deactivated parent account.

Keep personal and security-sensitive attachments outside the general evidence pack and grant access only where necessary.

Confirm the current UAE branch, subsidiary and facility records, including licences, permits, leases, operators and responsible managers.

Determine whether a Source has been designated and identify the competent authority, reporting unit, method, period, portal, verifier and deadline.

Map the UAE operation into the foreign parent’s legal, facility and GHG-system masters; identify any missing or misclassified assets.

Complete the UAE reporting-unit memo and parent-to-UAE adjustment register.

Classify data by sensitivity and document cross-border access, personal-data minimisation, cybersecurity, retention and local retrieval.

Load or extract the UAE data at source level; validate local units, suppliers, energy, process, refrigerant, mobile and contractor facts.

Calculate the authority output using the accepted method and reconcile it to the parent inventory.

Obtain local factual certification, parent methodology review, legal/HSE approval and any required verification.

Submit through the confirmed route, archive the receipt and maintain a query and resubmission log.

Update both the local compliance record and the group inventory, including any corrected data or methodology implications.

A European engineering company operates through a UAE branch in Dubai and a leased service centre in Abu Dhabi. The parent platform captures office electricity, company vehicles and business travel, but the service centre’s generator, refrigerant equipment, workshop gas and subcontracted mobile equipment are not mapped to a separate facility ID. Evidence is stored across the parent ERP, a UAE utility portal and local maintenance contractors.

The UAE team first confirms the legal and facility records and seeks written clarification of the reporting unit. It then creates a UAE overlay in the parent platform, adds the missing source population, records local factor and period adjustments, and separates direct inventory data from voluntary business-travel and supplier screening. Driver names are removed from the calculation dataset, while the original fuel-card evidence remains restricted. A local evidence mirror allows the country manager and verifier to retrieve all support without giving them unrestricted access to the parent’s global systems.