UAE R&D Tax Credit Pre-Approval: 10 Mistakes That Will Get Your Application Rejected

What you need to know before the portal opens

The Emirates R&D Council's pre-approval portal has not yet launched as of April 2026. The operational mechanics, including the application form, evidence standards, turnaround times, and assessment criteria, are still unpublished.

What is published is the legislation. Ministerial Decision No. 24 of 2026 (MD 24/2026) and Cabinet Decision No. 215 of 2025 (CD 215/2025) tell us exactly what the Council must assess, and therefore exactly what an application needs to demonstrate. The mistakes below are drawn directly from those two documents.

A word on timing. Under Article 4 of MD 24/2026, pre-approval must be obtained for every R&D Project for which the credit is claimed, in the form, manner and within the timeline specified by the Council. The statutory sequence is pre-approval first, then claim. CD 215/2025 Article 12(2) and MD 24/2026 Article 4 expressly leave the operational timing rules, including the treatment of in-flight 2026 expenditure once the portal opens, to the Council's rule-making. Until the Council confirms those rules, businesses should assume a strict ex-ante sequence as the baseline: work incurred before pre-approval is granted carries real risk of being excluded from the claim.

At a glance:

• Pre-approval is mandatory under MD 24/2026 Article 4. There is no fallback if you miss it.

• The Emirates R&D Council assesses whether activities meet all five qualifying criteria simultaneously: novel, creative, uncertain, systematic, and transferable or reproducible.

• Routine software upgrades, UI redesigns, incremental product improvements that adapt known techniques, and engineering work that applies existing methods to new inputs are unlikely to satisfy those five criteria (particularly the uncertainty criterion).

• Entity eligibility is assessed separately from activity eligibility. Both must be confirmed before applying.

• The portal has not yet launched. Businesses should be building documentation and preparing applications now.

Mistake 1: Applying retrospectively

The most common mistake will be businesses that conduct R&D throughout 2026, assume they can sort out the pre-approval at year-end when the accountant files the return, and then discover there is no mechanism to do so.

Article 4 of MD 24/2026 requires pre-approval from the Emirates R&D Council for each R&D Project, in the form, manner and within the timeline specified by the Council. The statutory sequence is pre-approval first, then the claim. It is not a formality that can be completed retrospectively.

The practical position in April 2026 is that the Council's pre-approval portal has not yet launched, and neither the Council nor the Ministry of Finance has published how in-flight 2026 expenditure will be treated once the portal opens. That treatment is a rule-making matter for the Council under CD 215/2025 Article 12(2) and MD 24/2026 Article 4. Two conclusions follow:

• Businesses should assume a strict ex-ante sequence as the baseline. Work incurred before pre-approval is granted carries real risk of being excluded from the claim.

• Businesses should build the evidence base now: project definitions, technical uncertainty statements, staffing records, and expenditure logs created contemporaneously. When the portal opens, preparation means speed, and speed reduces the window of pre-portal expenditure exposed to risk.

Retrospective pre-approval is not available on the face of the legislation as currently drafted. Whether the Council will, on launch, accept applications for projects already in progress during 2026 is not yet confirmed.

Mistake 2: Describing what you built, not the uncertainty you faced

The five qualifying criteria in MD 24/2026 Article 3 are an assessment of scientific and technological process, not of commercial output.

A description of what was developed (a new feature, a product release, a platform upgrade) does not address a single criterion. The Council is asking whether the work involved genuine technical uncertainty, novel approaches, creative original concepts, systematic methodology, and results that are transferable or reproducible. None of those are answered by a product roadmap or a sprint log.

An application that describes activities in terms of product development will fail regardless of how technically complex the underlying work was. The application must identify the specific scientific or technological uncertainty that existed at the outset, describe the systematic approach taken to resolve it, and demonstrate why the outcome was not predictable in advance by a competent professional in the field.

The Frascati Manual is identified in MD 24/2026 Article 3(2) as the interpretive reference for assessing whether an activity is a Qualifying R&D Activity: the assessment "shall be made having regard to the criteria set out in the Frascati Manual". Frascati's structure (basic research, applied research, experimental development) is the conceptual map against which activities will be assessed. It is interpretive guidance rather than binding black-letter law, and the Emirates R&D Council has not yet confirmed which edition or specific paragraphs of Frascati will be deployed. Preparing an application without understanding how Frascati categorises the work is a significant risk, but Frascati is a guide to the statutory five-criterion test, not a substitute for it.

Mistake 3: Treating routine software or product development as R&D

This is the highest-volume misclassification in R&D tax credit regimes globally, and the UAE regime will be no different.

MD 24/2026 Article 3(1) is explicit: the work must aim to produce new findings (novel), involve original concepts or hypotheses (creative), address genuine scientific or technological uncertainty (uncertain), follow a systematic plan and budget (systematic), and produce results that are transferable or reproducible in other contexts (transferable or reproducible). Routine software upgrades, UI redesigns, incremental product improvements that adapt known techniques, and engineering work that applies existing methods to new inputs are unlikely to satisfy those five criteria, particularly the uncertainty criterion.

The critical test is the uncertainty criterion. If a competent software engineer or scientist in the relevant field could have predicted the technical outcome in advance, the work almost certainly does not qualify. The uncertainty must be scientific or technological, not commercial. Not knowing whether customers will adopt a feature is not the same as not knowing whether a technical approach is achievable.

The Council will assess substance, not labels. Internally calling a project "R&D" in project management tooling does not make it qualifying. The application must demonstrate, with evidence, that the activity crossed the threshold from product development into genuine research and development.

Mistake 4: Failing to satisfy all five criteria simultaneously

MD 24/2026 Article 3(1) requires that all five criteria, novel, creative, uncertain, systematic, and transferable or reproducible, be met at the same time. It is not sufficient to demonstrate four out of five. One missing criterion means the activity does not qualify.

The criterion most commonly missed is the fifth one, transferable or reproducible. MD 24/2026 Article 3(1)(e) uses the statutory disjunction "transferable or reproducible", so an activity satisfies the test if its results can be applied or replicated in other contexts, by either route. A result that is transferable in the strict sense (portable to a different project, site, or team) passes. A result that is reproducible (replicable elsewhere with the same inputs and method, for example a manufacturing process improvement bound to a single site but repeatable with the same inputs) also passes. A one-off bespoke solution developed exclusively for a single client, with no capacity for broader applicability or replication, fails this test even if it involved genuine technical uncertainty.

Systematic is the second most commonly missed. The work must follow a documented plan with objectives, methodology, and a budget. Undocumented experimentation, however technically sophisticated, does not satisfy this requirement. The Council needs evidence of a structured approach, which means project plans, research protocols, progress reports, and management sign-offs created contemporaneously.

Mistake 5: Applying as an ineligible entity

Before any assessment of whether activities qualify, the Council must confirm that the entity itself is eligible. An application from an ineligible entity will fail at the first gate regardless of the quality of the R&D described.

The qualifying entity conditions are set out in CD 215/2025 Article 3. The entity must be a UAE-incorporated juridical person subject to Corporate Tax and/or the Top-up Tax under Cabinet Decision No. 142 of 2024 (commonly called DMTT). This condition has two common failure modes.

First: Qualifying Free Zone Persons (QFZPs). The credit offsets Corporate Tax or Top-up Tax liability, and a pure QFZP paying 0% on its qualifying income has no liability to offset. CD 215/2025 Article 3(2) creates two pathways for a QFZP to access the credit. Pathway 1 (Article 3(2)(a)): the entity is subject to Corporate Tax at 9% on taxable income derived from the qualifying R&D activities. In practice, this most commonly arises where the entity has lost QFZP status for the period, either by breaching the CD 100/2023 de minimis threshold (triggering a 5-period lock-out) or by electing out of QFZP status under FDL 47/2022 Article 18(2). Pathway 2 (Article 3(2)(b)): the entity is subject to Top-up Tax for the fiscal year, typically as a Constituent Entity, Joint Venture, or JV Subsidiary of a Domestic Group within the scope of CD 142/2024. A QFZP outside both pathways is outside the regime. Confirming which pathway (if any) applies is an entity-level step that must precede the pre-approval application. For the full analysis, see Can Free Zone Companies Claim UAE R&D Tax Credits?

Second: any entity that has elected Small Business Relief for the relevant tax period under Article 21 of the Corporate Tax Law is excluded from the credit by Article 4(2) of CD 215/2025. The SBR election and the R&D credit are mutually exclusive for the same period. If your accountant has filed or intends to file an SBR election for 2026, the R&D credit is unavailable for 2026 regardless of how strong the R&D activities are.

Mistake 6: Failing the beneficial entitlement condition

Article 3(1)(d) of CD 215/2025 requires that the qualifying entity be beneficially entitled to a share in the returns derived from exploiting the outcomes of the R&D activities.

This condition catches a common multinational structure: a UAE subsidiary performs R&D and bears the cost, but the resulting intellectual property is owned by a foreign parent company under a group IP ownership policy. In that structure, the UAE entity performs the work but does not benefit from the outcome. The beneficial entitlement condition is not satisfied, and the credit is unavailable to the UAE entity.

For any business where IP ownership, cost allocation, and group transfer pricing are governed by a group policy rather than by the specific entity's arrangements, this condition requires active review before an application is submitted. The structure may need to be amended to ensure the UAE entity retains a beneficial interest in the R&D outcomes.

Mistake 7: Including R&D activities performed outside the UAE

MD 24/2026 Article 3(3) states that only R&D activities carried out within the UAE constitute qualifying R&D activities for the purposes of the credit.

This is a direct territorial restriction. Work performed by remote employees based outside the UAE, by overseas contractors, or in overseas laboratories does not qualify regardless of who is paying for it, where the qualifying entity is incorporated, or where the results will be used.

For businesses with distributed teams, including free zone companies with overseas technical staff, this requires careful apportionment. Only the UAE-based element of the work qualifies. Expenditure attributable to overseas activity must be excluded from the qualifying expenditure calculation, and the application must be scoped accordingly.

The statutory position is clear: only UAE-performed activity qualifies (MD 24/2026 Article 3(3)), and subcontractors must be UAE-based and UAE-performing (MD 24/2026 Article 10(1)(a) and (b)). The precise application of that position in multi-jurisdiction collaboration patterns, for example mixed UAE and overseas teams on the same activity, UAE-based subcontractors interacting with overseas client teams, or the use of overseas cloud infrastructure to host UAE-based R&D work, is expected to be refined by Emirates R&D Council guidance. RDvault will update this guidance as the Council publishes case-specific clarifications.

Mistake 8: Not having audited financial statements

This is a procedural requirement that catches many smaller UAE businesses off guard.

CD 215/2025 Article 9(1)(d) requires audited financial statements of the Qualifying Entity as part of every R&D tax credit claim submission. There is no exemption for smaller entities. A business that has never prepared audited accounts, which is common for UAE SMEs and startups operating under a simplified reporting regime, faces a mandatory compliance cost before any claim can be processed.

Audited financials take time to prepare, commission, and have signed off. A business planning to claim the credit for the 2026 tax period should confirm now whether its accounts will be audited for that period. If not, the cost and timeline of engaging an audit firm should be built into the planning calendar, not discovered when the claim is being assembled.

This applies to the claim submission, not the pre-approval application itself. But a business that secures pre-approval and then cannot file the claim because it lacks audited accounts has wasted the pre-approval and missed the credit for that period.

Mistake 9: Submitting without contemporaneous documentation

The Council cannot approve an activity on the basis of a description alone. The application must be supported by evidence that the activities were conducted as described, that technical uncertainty existed, and that a systematic approach was followed.

Contemporaneous documentation, records created at the time the work was done, is the gold standard. This means project plans drafted before the R&D began, research protocols that pre-date the experimental phase, lab notebooks and test records created during the work, progress reports and management sign-offs from the period, and financial records that link costs to specific projects in real time.

Documentation created at the point of application, to describe work that was done months earlier, is worth considerably less. The Council will assess the substance of the evidence, not just whether documents exist. Records that pre-date the application carry more weight than records that post-date it.

The record-keeping obligation under MD 24/2026 Article 12 requires that all records supporting a claim be retained for seven years. That obligation begins at the point the R&D activity is undertaken, not at the point of application.

Mistake 10: Applying for a project that does not reach the AED 500,000 threshold

Article 5(3)(b) of CD 215/2025 imposes a minimum qualifying expenditure threshold of AED 500,000 per R&D project per tax period. This threshold is calculated before the 30% staff cost uplift under MD 24/2026 Article 8(3).

A project with AED 480,000 of base qualifying expenditure does not satisfy the threshold even after the uplift is applied. The pre-approval application covers a specific project. If the project is below the threshold, there is no credit available for it regardless of how well the activities meet the five criteria.

The threshold applies per project, not per entity. A business running three R&D projects must reach AED 500,000 on each individually. A project that falls short of the threshold in isolation cannot borrow expenditure from a stronger project to satisfy it.

In a Tax Group, the test remains at project level, not entity level. Where two members of a Tax Group jointly contribute to a single R&D project, their combined contributions count toward the AED 500,000 threshold because the test is at project level: two subsidiaries each contributing AED 300,000 to the same project reach AED 600,000 of project-level qualifying expenditure and satisfy the minimum. MD 24/2026 Article 2(3) is a separate rule: it aggregates group-wide qualifying expenditure and R&D Staff across all Tax Group members for the rate-band thresholds in Article 2(1) (the AED 1M / 2M / 5M bands and the 2/6/14 staff counts). It does not create a group-level workaround for the AED 500,000 per-project minimum. Separate projects below AED 500,000 individually cannot be pooled across the Tax Group to reach it.

What to do now

The pre-approval portal will open. When it does, businesses that have been preparing will move quickly and those that have not will spend months reconstructing records, reclassifying activities, and addressing entity-level issues that could have been resolved in advance.

The preparation work is the same regardless of when the portal opens: define projects rigorously with clear technical objectives and documented uncertainties; build contemporaneous records now; confirm entity eligibility and IP ownership arrangements; confirm that audited financials are in scope for 2026; and exclude any overseas activity from the planned expenditure calculation.

RDvault works with UAE businesses to assess eligibility, scope qualifying activities against the five criteria, structure the pre-approval application, and build the documentation necessary to support it. Use our eligibility checker for an initial read on your position, or book a free assessment to discuss your specific R&D programme.

For a full breakdown of the pre-approval process under Article 4 of MD 24/2026, see the Emirates R&D Council Pre-Approval: The Definitive Guide. For the five qualifying criteria in full, see the step-by-step guide to claiming the UAE R&D Tax Credit.

Frequently asked questions

Is pre-approval from the Emirates R&D Council mandatory?

Yes. Article 4 of Ministerial Decision No. 24 of 2026 makes pre-approval mandatory for every qualifying R&D project. A credit cannot be claimed without it. There is no retrospective mechanism to obtain pre-approval for work that has already been completed without it.

When will the Emirates R&D Council pre-approval portal open?

As of April 2026, the portal has not yet been formally launched. The Emirates R&D Council has not published the application form, turnaround times, or evidence standards. RDvault will update this guidance as soon as the portal details are published. Businesses should prepare documentation and project definitions now so they can submit promptly when the portal opens.

What happens if you conduct R&D in 2026 without pre-approval?

The legislation as currently drafted does not provide a retrospective mechanism to recover a missed pre-approval. CD 215/2025 Article 12(2) and MD 24/2026 Article 4 leave the operational timing rules, including the treatment of in-flight 2026 expenditure, to the Council's rule-making. Until the Council publishes those rules, expenditure incurred before pre-approval is granted should be treated as at risk of being excluded from the claim. Businesses conducting R&D in 2026 should prepare documentation now and apply for pre-approval as soon as the portal is available, not wait until the tax return is being prepared.

Does a Qualifying Free Zone Person qualify for the UAE R&D Tax Credit?

Only under specific conditions. A pure QFZP paying 0% Corporate Tax on qualifying income, and not within the scope of the Top-up Tax under Cabinet Decision No. 142 of 2024 (commonly called DMTT), does not currently qualify. CD 215/2025 Article 3(2) creates two pathways. Pathway 1 (Article 3(2)(a)): the entity is subject to Corporate Tax at 9% on taxable income derived from the qualifying R&D activities, most commonly because QFZP status has been lost for the period (by breach of the Cabinet Decision 100 of 2023 de minimis threshold, triggering a 5-period lock-out, or by election out under FDL 47/2022 Article 18(2)). Pathway 2 (Article 3(2)(b)): the entity is within the scope of the Top-up Tax under CD 142/2024, typically as a Constituent Entity, Joint Venture, or JV Subsidiary of a Domestic Group. For the full breakdown, see Can Free Zone Companies Claim UAE R&D Tax Credits?

Can a loss-making company apply for pre-approval?

Yes. The pre-approval is granted based on the qualifying nature of the R&D activities and the entity's eligibility, not on whether the entity is profitable. A loss-making company can obtain pre-approval and build a credit balance that carries forward to future periods under MD 24/2026 Article 5. The credit is non-refundable under the current Phase 1 regime, but the carry-forward is uncapped in time subject to ownership continuity conditions.

What is the minimum expenditure to qualify?

AED 500,000 per R&D project per tax period, calculated before the 30% staff cost uplift under Article 8(3) of MD 24/2026. This is a per-project threshold, not an entity-level aggregate. Where two Tax Group members jointly contribute to the same project, their contributions count toward that project's AED 500,000 threshold at project level. MD 24/2026 Article 2(3) is a separate rule that aggregates group-wide qualifying expenditure and R&D Staff for the rate-band thresholds in Article 2(1), not for the per-project minimum. Separate projects below AED 500,000 individually cannot be pooled across the Tax Group to reach it.

Sources: Ministerial Decision No. 24 of 2026 | Cabinet Decision No. 215 of 2025 | UAE Ministry of Finance. This article is for informational purposes only and does not constitute tax advice. Portal mechanics, turnaround times, and evidence standards are based on the published legislation; the Emirates R&D Council has not yet published the pre-approval application form or operational guidance.

Last reviewed: 20 April 2026