How to Claim the UAE R&D Tax Credit: Pre-Approval, Documentation & Filing

Do you need pre-approval before claiming the UAE R&D tax credit?

Yes. To claim the UAE R&D tax credit you must obtain pre-approval for each R&D project before the credit is claimed in the Corporate Tax return [VERIFY]. This is a procedural gateway that sits entirely separate from the substantive question of whether your activities and costs qualify. Pass every technical test and fail the gateway, and the answer is still no credit.

Most businesses approaching the incentive for the first time spend their attention on eligibility — are the activities novel, creative, uncertain, systematic and transferable, and do the costs sit inside the four qualifying categories? Those questions matter, but they are the second question. The first is whether the project was approved before you claimed. A business can run a textbook qualifying programme through FY2026, incur AED 3,000,000 of impeccably documented qualifying expenditure, and recover nothing because no application was made.

The practical consequence is that R&D credit planning has to begin at project level, at project inception — not at the point the Corporate Tax return is being prepared. By the time your accountant is assembling the return, the decisions that determine whether a claim is possible were taken months earlier. This is the single most common reason a first-year claim fails, and it is entirely avoidable.

What are the eight stages of the claiming process?

The process runs from before the research starts to seven years after the tax period ends. Treating it as eight discrete stages, each with an owner and a trigger, is the most reliable way to make sure nothing is missed — particularly the stages that fall outside the finance calendar entirely.

1. Eligibility assessment — before R&D begins. Test the proposed activities against the qualifying criteria and the excluded fields before spending anything on an application.
2. Pre-approval application — before R&D begins or at early project stage. Submit in the prescribed form and window, demonstrating that the activities qualify and the planned expenditure will meet the criteria.
3. Contemporaneous documentation — throughout. Written, visual and electronic records of objectives, processes, methodologies, experiments and findings.
4. Qualifying cost tracking — throughout. Project-level capture of all four categories, with time allocation records for part-time R&D staff.
5. Progress updates — on request, at any time. Provide updates with technical documentation showing the work remains consistent with what was approved.
6. Credit computation — at period end. Apply the staff cost uplift, build the qualifying base and compute the credit under the applicable rate structure.
7. Claim in the CT return — at the filing deadline. Apply against Corporate Tax liability first, then Top-up Tax, then carry forward.
8. Record retention — seven years from period end. Application, project records, cost schedule and computation, available on request.

When does the pre-approval application have to be made?

The application must be made before the credit is claimed in the Corporate Tax return, and in practice that means at or near project inception [VERIFY the prescribed form, channel and window]. There is no mechanism to approve a project retrospectively once the tax period has concluded.

This creates a planning problem that is easy to underestimate. A tax period ending 31 December 2026 has a Corporate Tax return due nine months later, in September 2027. It is entirely natural for a finance team to first consider the R&D credit in mid-2027 while preparing that return — by which point every project that ran during 2026 without an application is permanently outside the regime. The gap between when the decision has to be taken and when the subject usually comes up is close to eighteen months.

The application itself has to demonstrate two things prospectively: that the proposed activities constitute qualifying R&D, and that the planned expenditure will meet the qualifying criteria. That second limb means you need a credible cost plan mapped to the four qualifying categories before the work begins, not just a technical narrative. If the cost plan is dominated by capital equipment, that is worth knowing before you apply — capital expenditure does not qualify, as set out in our guide to qualifying R&D expenditure and which costs count.

What technical documentation must you maintain?

The documentation standard is comprehensive, and that word is doing real work. The requirement is for written, visual and electronic records detailing objectives, processes, methodologies, experiments and findings for each qualifying project [VERIFY] — not a summary memo produced at year end, but the working record of the research itself.

Six evidence classes have to exist, and they split across two teams. The technical side owns objectives, methods, experiments and findings; finance owns cost records and staff records. Claims usually fail on the seam between the two — strong lab notebooks with no project cost coding, or a clean cost schedule with no technical narrative capable of demonstrating that uncertainty existed.

Failed experiments are worth calling out separately. Instinct says to document what worked; the regime rewards documenting what did not, because a failed experiment is the clearest possible evidence that genuine technological uncertainty existed. A project record showing only successful outcomes reads like development, not research. Our accounting and bookkeeping team maintains the cost side of this record monthly, which is the half that most often goes missing.

Can you be asked for progress updates mid-project?

Yes. A qualifying entity can be required to submit a project progress update, together with technical documentation, as evidence that the activities remain consistent with the approved qualifying R&D activities and expenditure [VERIFY]. The request can come at any time and must be answered in the prescribed form and manner.

This is the mechanism that turns the contemporaneous documentation requirement from good practice into an operational necessity. A request arriving in month seven of an eighteen-month project cannot be satisfied by records you intend to write later. Whatever exists on the day the request lands is the evidence.

It also matters where a project has drifted. Research changes direction — that is the nature of it — but a project that has evolved materially away from what was approved raises a question about whether the approval still covers the work being done. Document the pivot and the reasoning at the time it happens. A contemporaneous record of a considered change of direction is defensible; a silent divergence discovered years later is not.

How is the credit computed once the tax period ends?

Computation happens after the period closes and runs in a fixed order: build the qualifying expenditure base across the four cost categories, apply the staff cost uplift, then apply the credit rate structure to the resulting base. The uplift goes on before the rate, which is why it is worth more than it first appears.

The rate structure itself is tiered and gated on average R&D headcount. This is where you should be most careful with any figure you have seen quoted. Published guides across the market cite different tier boundaries and different bottom rates, and the Ministry of Finance’s own announcement of the incentive described a refundable credit in the 30–50% range rather than a structure starting at 15%. Do not budget, forecast or brief a board on a rate you have not read in the published decision. [VERIFY — rate tiers, band boundaries and the average R&D staff thresholds gating each tier are all unconfirmed.]

What you can do reliably at this stage is get the base right, because the base is arithmetic rather than interpretation. Total employment cost rather than basic salary, apportioned by documented R&D time, uplifted; consumables net of anything capital, group-sourced or sold on; subcontract fees that clear every condition; CCA contributions at arm’s length. The full breakdown sits in our companion guide to qualifying R&D expenditure, and you can model the surrounding Corporate Tax position with the UAE corporate tax calculator.

How is the credit claimed and utilised in the CT return?

The credit is claimed as part of the Corporate Tax return filed with the FTA, and it is utilised in a fixed order: Corporate Tax liability first, Top-up Tax second, carry forward third. You do not get to choose the order, and the sequence matters for cash planning because it determines how much of the credit converts into a reduced payment this year rather than an asset on the balance sheet.

Two points on the residual. First, carry-forward is conditional: ownership continuity conditions test whether substantially the same owners remain in place, so a funding round or a share sale between periods can put an accumulated credit at risk. Second, in some circumstances credit can be transferred rather than merely carried forward. Both the continuity test and any time limit on the carry-forward period should be confirmed before you recognise anything as an asset.

Who is responsible when the claimant is in a Tax Group?

The Parent Company. Where the qualifying entity is a Tax Group member, the Parent Company applies for pre-approval for each project run by any member, submits the credit claim as part of the group Corporate Tax return, and carries the other obligations [VERIFY]. Individual members do not file their own applications, and a member that assumes it can is likely to discover otherwise after the window has closed.

Credit arising to qualifying members is utilised against the Corporate Tax liability of the group as a whole, in a defined priority order. Pre-grouping credits — those accumulated by an entity before it joined the group — are applied ahead of the group’s own credits.

A worked illustration: a group with a Corporate Tax liability of AED 1,200,000 has a joining entity carrying AED 300,000 of pre-grouping credit and AED 750,000 of its own group credits. The pre-grouping credit is applied first, then the group credits, leaving AED 150,000 of Corporate Tax payable and no residual to carry forward. Reverse the order and the outcome is the same total, but the pre-grouping credit — which typically carries the tighter conditions — would have been left exposed. That is why the order is fixed.

Group structure also interacts with the qualifying base itself. Intra-group staff recharges, group-sourced consumables and subcontracting between Tax Group members are all excluded from qualifying expenditure, so a group service company employing the technical staff can produce a near-zero base at the claiming entity. If that describes your structure, review it with our Corporate Tax consultants before the next project starts, and read the corporate tax guide for UAE businesses on Tax Group formation generally.

How does the credit interact with Domestic Minimum Top-up Tax?

Where an entity is within the scope of the UAE’s Domestic Minimum Top-up Tax — introduced by Cabinet Decision No. 142 of 2024 for large multinational groups, effective for financial years starting on or after 1 January 2025 — the R&D credit can be applied against Top-up Tax liability as well as Corporate Tax. Corporate Tax comes first; only the residual reaches Top-up Tax.

The DMTT applies to constituent entities of multinational groups with consolidated global revenues of at least EUR 750 million in at least two of the four preceding financial years, bringing their effective rate in the UAE to 15%. For those groups, an R&D credit that reduces Corporate Tax without reducing the effective rate calculation would be of limited value, which is why the ordering rule matters commercially and not just mechanically.

Where the qualifying entity is a constituent entity of a Domestic Group with a Domestic Designated Filing Entity, that DDFE takes responsibility for the pre-approval application and the Top-up Tax return [VERIFY]. In a group with both a Tax Group parent and a DDFE, establish in writing which entity owns which filing before the first application, because the two roles do not necessarily sit in the same place.

What VAT and e-invoicing obligations sit alongside a claim?

An R&D claim does not change your VAT or e-invoicing position, but it raises the cost of getting either wrong, because both generate the documentary trail the claim depends on. Input VAT incurred on R&D consumables acquired for business purposes is generally recoverable through the normal VAT return at the 5% standard rate, filed within 28 days of the end of each tax period.

Get the VAT treatment wrong and you create a reconciliation problem: an R&D cost schedule built gross where input tax was recoverable will not tie back to the ledger, and a schedule that will not reconcile is the weakest form of claim. Late VAT filing attracts AED 1,000 for a first offence and AED 2,000 for a repeat within 24 months, and late payment now runs at 14% per annum charged monthly under Cabinet Decision No. 129 of 2025 — a separate penalty authority from the Corporate Tax regime in Cabinet Decision No. 75 of 2023 as amended by Cabinet Decision No. 10 of 2024.

On e-invoicing, R&D subcontracts, licensing arrangements and supplier invoices that fall within the UAE regime must run through a compliant system, which in practice strengthens the record behind the claim rather than complicating it. The UAE model is Peppol-based with an accredited service provider appointment required ahead of go-live [VERIFY current phase dates] — see our e-invoicing readiness page for where the phasing currently stands.

What are the retention rules — and where do claims go wrong?

All documentation must be retained for seven years from the end of the relevant tax period, consistent with the record-keeping obligation under Federal Decree-Law No. 47 of 2022, and produced on request. That covers the pre-approval application, the full project technical record, the qualifying cost schedule, the credit computation and every supporting document behind them.

Seven years is longer than most businesses keep project-level technical records by default. Lab notebooks get archived, test data ages out of the systems that held it, and the engineer who ran the critical experiment leaves. Build the retention decision into the project close-out, not into the audit file, because the audit file is not where most of this evidence lives.