10 Critical Red Flags in UAE Transfer Pricing Local Files That Trigger FTA Penalties
Under Federal Decree-Law No. 47 of 2022 and Ministerial Decision No. 97 of 2023, a UAE taxable person must prepare and maintain a transfer pricing local file uae businesses rely on to justify related-party pricing if it earns AED 200 million or more in revenue during a tax period, or belongs to a multinational group with consolidated revenue of AED 3.15 billion or more.
The obligation is not to file the document with the Federal Tax Authority (FTA) every year – it is to have it ready. When the FTA asks, the taxable person has 30 days to produce it, and by that point, the quality of the file is fixed. There is no time left to fix a weak benchmarking study or a missing functional analysis.
This article works through the ten Local File weaknesses that come up most often in local file uae corporate tax reviews, why each one draws FTA attention, and what a defensible file looks like instead. For background on how UAE transfer pricing rules work more broadly, see this complete guide to transfer pricing in the UAE. For hands-on support building or reviewing a file, ADEPTS’ transfer pricing services cover the full process, from scoping to benchmarking to FTA-ready documentation.
What the FTA Asks For, and What Happens When You Miss the 30 Days
FTA has specific requirements and they are listed clearly down below:
The Thirty-Day Production Window Under Article 55(2)
Here’s the part that catches businesses off guard: the FTA doesn’t need advance notice to ask for your Local File. Under Article 55 of Federal Decree-Law No. 47 of 2022, the Authority can issue a written request at any point, and you then have 30 days to hand over a complete Master File and Local File.
This is the transfer pricing 30 day rule uae businesses need to plan around, not react to. Thirty days is enough time to compile a file that already exists. It is nowhere near enough time to run a fresh benchmarking study, rebuild a functional analysis, or reconstruct intercompany agreements from three years ago. If your file isn’t contemporaneous, prepared alongside the transactions it covers, not written after the fact, the 30-day clock is the moment that becomes obvious to everyone, including the FTA.
Record-Keeping Penalties Under Cabinet Decision No. 75 of 2023
Missing that window carries a direct cost. Under cabinet decision 75 of 2023 penalties, failure to keep the records and information required by the Corporate Tax Law, which covers a missing or incomplete Local File, draws a fine of AED 10,000 per violation, rising to AED 20,000 for a repeat violation within 24 months.
These figures were reviewed and left unchanged when Cabinet Decision No. 129 of 2025 updated the UAE’s wider administrative penalty framework from 14 April 2026, which tells you something: the FTA still treats documentation failures as a distinct, deliberately-priced violation, not a technicality.
The Larger Exposure: Adjustment, Additional Tax, Penalty and Interest
The fixed fine is the smallest part of the exposure. A weak or absent Local File doesn’t just draw a penalty, it removes your ability to defend the pricing itself. Once the FTA is unconvinced that a related-party transaction was priced at arm’s length, it can raise a fta transfer pricing adjustment, recalculating taxable income and the corporate tax due on it.
Under Cabinet Decision No. 129 of 2025, unpaid tax resulting from that adjustment now accrues at a flat 14% per annum, calculated monthly, instead of the old 2%-plus-4%-monthly structure. Come forward voluntarily before the FTA opens an audit, and the exposure is a 1% monthly penalty on the tax difference.
Wait until after an audit notice, and it becomes a fixed 15% penalty plus the same 1% monthly charge, on top of the tax itself. For a QFZP entity, there’s a further consequence: a documented failure to meet the arm’s length standard on related-party transactions can jeopardize the 0% qualifying income status entirely. For the full penalty picture across corporate tax, see UAE corporate tax penalties.
Red Flag 1: Assuming Every Domestic Related Party Is Excluded
The most common scope error starts with a half-true assumption. It’s true that Ministerial Decision No. 97 of 2023 lets you exclude transactions with a Resident Related Party taxed at the same 9% Corporate Tax rate, provided neither party has unutilized losses, hasn’t claimed Small Business Relief, and isn’t a Qualifying Free Zone Person. But that’s a narrow exception, not a blanket rule. Teams often extend it to every UAE-to-UAE transaction on the assumption that “domestic means safe.”
Any related party taxed differently, a Free Zone entity on 0% qualifying income, a group company under Small Business Relief, one carrying forward losses, belongs in the file, and leaving it out is one of the fastest ways to undermine an otherwise solid local file uae corporate tax submission. Get the underlying related-party mechanics right first; this arm’s length and related-party pricing guide walks through how the exclusion actually works.
Red Flag 2: Connected Persons Omitted Altogether
Related parties and Connected Persons are not the same population, and files that treat them as one category consistently miss half the picture. A Connected Person is typically an owner, director, or key individual with significant influence over the business, not a group entity.
Connected persons transfer pricing uae obligations sit alongside the related-party rules, not underneath them, and a Local File that only maps intercompany transactions while ignoring payments, benefits, or arrangements involving Connected Persons is incomplete by design. This gap is easy for an FTA reviewer to spot: it’s the first thing checked against your Connected Persons disclosure schedule.
Red Flag 3: EmaraTax Disclosure Figures That Do Not Reconcile to the Local File
Numbers that don’t match are a red flag before the FTA reads a single paragraph. The Transfer Pricing Disclosure Form filed through EmaraTax with your corporate tax return should tie directly to the transaction values, categories, and counterparties described in the Local File.
When the two documents disagree, a different revenue figure for the same intercompany service, a related party listed in one but not the other, it signals that the file was assembled separately from the return rather than as one coherent record. Reconciliation between the disclosure schedules and the Local File narrative is one of the simplest checks a reviewer can run, and one of the easiest for a business to get right before submission.
This connects directly to your broader filing obligations; see how transfer pricing affects your corporate tax filing and intercompany accounting in the UAE for how the underlying transaction records should flow through to both.
Red Flag 4: A Stale Benchmarking Set, or a Result Outside the Interquartile Range
A benchmarking study is not a one-time exercise. Comparable company sets shift as businesses merge, delist, or change activity, and a study run in 2023 rarely still reflects the market by the time a 2026 tax period is under review.
The FTA’s stated preference, consistent with OECD guidance, is that a tested transaction’s result should fall within the interquartile range of the comparable set – the middle 50% of outcomes, not just anywhere inside the full spread. A margin sitting outside that range, with no adjustment or explanation attached, is one of the clearest triggers for a fta transfer pricing adjustment.
Refresh the comparable set on a regular cycle, and document the search criteria used to build it, not just the final numbers.
Red Flag 5: A Tested Party Chosen for Convenience Rather Than as the Least Complex Entity
Tested party selection transfer pricing decisions get made too casually, often defaulting to whichever entity has the most accessible financial data rather than the one the methodology actually calls for.
The tested party should be the participant in the transaction with the least complex functions, the fewest valuable intangibles, and the most reliable comparable data, usually a routine distributor or service provider, not the principal entity carrying the group’s IP and risk. Picking the UAE entity as tested party simply because its accounts are on hand, when the UAE entity is actually the more complex party to the transaction, produces a benchmarking result that doesn’t answer the question the FTA is asking.
Red Flag 6: A Functional Analysis Copied From the Group Template
A functional analysis describes what an entity actually does, the functions it performs, the assets it uses, the risks it bears, and it has to be specific to that entity’s UAE operations, not lifted wholesale from a global group template.
Files that recycle a group-wide FAR (functions, assets, risks) write-up without adjusting it for the local business consistently fail to explain why the UAE entity earns the margin it does. If the UAE entity has taken on functions the group template doesn’t capture, local marketing, credit risk on regional customers, warehousing, the analysis needs to say so, because that’s exactly the detail an FTA reviewer will test against the numbers.
Red Flag 7: Management and Head Office Charges That Fail the Benefit Test
Management fee and head office charge allocations are consistently among the first line items an FTA reviewer tests, because they’re the easiest to allocate without real analysis behind them. The benefit test management fees uae requires the Local File to show, transaction by transaction, that the UAE entity actually received an economic or commercial benefit that an independent party would have paid for.
A flat percentage-of-revenue allocation with no description of the services actually delivered, no evidence of what was done, when, or by whom, rarely survives scrutiny. Support the allocation with time records, service descriptions, or a documented cost-plus calculation, and the benefit test becomes far easier to demonstrate.
Red Flag 8: Intra-Group Financing Priced Without Credit Analysis
Loans and cash-pooling arrangements between related parties need pricing that reflects the borrower’s actual creditworthiness, not a rate copied from the parent’s external facility. Intra group financing transfer pricing uae analysis should include a credit rating assessment of the borrowing entity, standalone, not with implicit group support baked in, along with a comparison to market interest rates for a borrower of similar risk, tenor, and currency.
A related-party loan priced at the group’s blended cost of capital, with no borrower-specific credit work behind it, is a mismatch the FTA can identify by comparing the rate to public bond or lending benchmarks for entities of similar risk.
Red Flag 9: Intangibles Where Legal Ownership Is Documented but DEMPE Is Not
Legal title to a trademark or patent tells you who owns the IP on paper. It does not tell you who created it, developed it, maintained it, protected it, or exploited it, and that is exactly what a dempe analysis uae file needs to establish. Under OECD-aligned principles that the FTA follows, the entity performing the DEMPE functions is entitled to the return the intangible generates, regardless of where legal ownership sits.
A Local File that documents legal ownership and stops there, without mapping which entity actually funds R&D, manages brand strategy, or bears the commercial risk of the IP, leaves the most valuable, and most scrutinized, transaction type in the file effectively unsupported.
Red Flag 10: A Persistent Loss-Maker With No Economic Explanation
A UAE entity that reports losses year after year, while performing routine functions and carrying limited risk, is a pattern the FTA’s risk-assessment process is built to catch. Independent businesses performing low-risk functions don’t typically accept multi-year losses, they either earn a modest, stable return or exit the arrangement.
If your UAE entity fits that profile and the losses continue, the Local File needs a specific economic explanation: a market entry phase with a defined end point, a one-off restructuring cost, a documented downturn affecting the whole comparable set. Silence on this point reads as exactly what it looks like.
Red Flag 10 Companion - Contemporaneous Documentation Versus an Ex-Post Rationale
The explanation has to exist at the time the pricing decision was made, not get written for the first time when the FTA’s 30-day letter arrives. A rationale drafted after the fact, once the audit is already underway, carries far less weight than a Local File paragraph or intercompany memo dated to the relevant tax period. This is the trap that catches otherwise well-built files: nine sections of solid analysis, and then a persistent loss position with a justification that was clearly written last week.
How ADEPTS Reviews a Local File Before the FTA Does
Building a Local File that holds up under FTA review takes more than filling in a template. It means testing the scope against your actual related-party and Connected Person map, refreshing the benchmarking set against current data, and making sure every number in the file reconciles to what’s already been filed through EmaraTax.
- Scope and threshold assessment against Ministerial Decision No. 97 of 2023
- Functional and DEMPE analysis specific to your UAE operations
- Benchmarking studies with documented search criteria and interquartile range testing
- Benefit-test documentation for management fees and intra-group financing
- A pre-audit reconciliation between your Local File and your Disclosure Form
With ADEPTS, you’re not handed a document to sign off. You get a file that has already been tested the way an FTA reviewer would test it. Our transfer pricing advisory services cover this end to end, from the first scoping call to a file that’s ready the day the 30-day letter arrives.
Conclusion
A Local File rarely fails on one obvious mistake. It fails on a scope gap here, a stale benchmark there, a management fee allocation with no benefit test behind it — small weaknesses that, together, give the FTA enough to question the whole document. None of that has to be discovered during an audit. Every red flag on this list can be tested and fixed before the 30-day letter ever arrives, and doing that work now is what turns a Local File from a compliance formality into a genuine defence. If it’s been more than a year since your file was reviewed against current thresholds and benchmarks, that review is worth having before the FTA asks for one.
FAQs
Yes. Falling below the AED 200 million or AED 3.15 billion thresholds removes the obligation to maintain a formal Master File and Local File, but not the underlying arm’s length requirement. The FTA can still request evidence that related-party pricing is commercially reasonable, so keeping lighter internal records is strongly advisable regardless of size.
No, generally not. The Master File is required where the taxable person belongs to a multinational group with foreign constituent entities. A group operating entirely within the UAE, with no establishments abroad, typically only needs the Local File once it crosses the AED 200 million revenue threshold.
The FTA can direct a later date at its discretion, but there’s no automatic extension. Requests for more time are considered case by case, and a business that hasn’t started preparing until the letter arrives is in a weak position to ask for one.
UAE tax law generally requires records to be retained for seven years from the end of the relevant tax period. Local Files should be kept for each tax period they cover, in a format that can be reproduced quickly if requested — not archived in a way that takes weeks to reassemble.
Yes. A qfzp related party transactions local file entry is required whenever a mainland or other related entity transacts with a QFZP, because the different tax treatment (0% versus 9%) is exactly the kind of mismatch the Local File exclusion doesn’t cover. These transactions need full arm’s length support.
Benchmarks can often be rolled forward for a limited period if the functional profile hasn’t changed, but the underlying financial data should still be updated annually. A full refresh of the comparable set is generally advisable every three years, or sooner if the market or the business itself shifts materially.
There’s no single mandated signatory under UAE law, but internal ownership matters. Most businesses have the CFO or Head of Tax formally approve the file, with external advisers providing the technical benchmarking and analysis behind it, so accountability is clear if the FTA has questions.
The FTA can request documents and records in Arabic, and failure to provide them when asked carries its own penalty. Many businesses maintain the working Local File in English but should be prepared to provide an Arabic translation of key sections on request.
Possibly. If the same pricing policy or intercompany arrangement was in place in prior tax periods, an adjustment in one year can prompt the FTA to review those earlier periods too, particularly if the Local Files for those years share the same weakness.
A voluntary disclosure made before an audit notice attracts a 1% monthly penalty on the tax difference. Waiting until after an FTA audit notice raises that to a fixed 15% penalty plus the same 1% monthly charge, on top of the tax itself – coming forward early is materially cheaper. For guidance on this route, see corporate tax advisory services.
References
- Federal Tax Authority. Corporate Tax – Transfer Pricing Guide. Abu Dhabi: Federal Tax Authority, 2023.
Federal Tax Authority Transfer Pricing Guide - Federal Tax Authority. Corporate Tax – Guides, References and Public Clarifications. Abu Dhabi: Federal Tax Authority. Federal Tax Authority Corporate Tax Guides and References
- Federal Tax Authority. Corporate Tax – General Guide (CTGGCT1). Abu Dhabi: Federal Tax Authority, 2023.
Federal Tax Authority Corporate Tax General Guide - Ministry of Finance, United Arab Emirates. Ministerial Decision No. 97 of 2023: Requirements for Maintaining Transfer Pricing Documentation for the Purposes of Federal Decree-Law No. 47 of 2022 on the Taxation of Corporations and Businesses. Abu Dhabi: Ministry of Finance, 2023.
Ministerial Decision No. 97 of 2023 (UAE Ministry of Finance) - United Arab Emirates. Federal Decree-Law No. 47 of 2022 on the Taxation of Corporations and Businesses. Abu Dhabi: Government of the United Arab Emirates, 2022.
Federal Decree-Law No. 47 of 2022 (UAE Corporate Tax Law) - Organisation for Economic Co-operation and Development. OECD Transfer Pricing Guidelines for Multinational Enterprises and Tax Administrations 2022. Paris: OECD Publishing, 2022.
OECD Transfer Pricing Guidelines 2022 - Organisation for Economic Co-operation and Development. Transfer Pricing Documentation and Country-by-Country Reporting, Action 13 – 2015 Final Report. Paris: OECD Publishing, 2015.
OECD BEPS Action 13 Final Report - Organisation for Economic Co-operation and Development. Transfer Pricing Guidance on Financial Transactions: Inclusive Framework on BEPS Actions 4, 8–10. Paris: OECD Publishing, 2020.
OECD Transfer Pricing Guidance on Financial Transactions - United Nations Department of Economic and Social Affairs. United Nations Practical Manual on Transfer Pricing for Developing Countries. New York: United Nations, 2021.
UN Practical Manual on Transfer Pricing for Developing Countries - Organisation for Economic Co-operation and Development. Country-by-Country Reporting for Tax Purposes. Paris: OECD. OECD Country-by-Country Reporting for Tax Purposes
Related Articles
