UAE Taxation & Regulatory Compliance · Transfer Pricing
Master File & Local File Preparation
A Master File and Local File are not filed with the Federal Tax Authority as a matter of course — they are built, kept current, and produced within the stipulated window, generally 30 days, whenever the FTA asks.
Chartered Accountants · Dubai · Since 1986
Master File and Local File preparation is the documentation exercise that evidences a UAE taxable person's arm's length position under Article 34 of the Corporate Tax Law (Federal Decree-Law No. 47 of 2022, applicable to financial years starting on or after 1 June 2023). Ministerial Decision No. 97 of 2023 sets out the two-tier structure directly: the Master File presents the group-wide picture — organisational structure, description of the businesses conducted, ownership and location of intangibles, intercompany financing arrangements, and the group's consolidated financial and tax position — while the Local File is entity-specific, setting out the UAE taxable person's own material related-party and connected-person transactions, the Functional, Asset and Risk (FAR) analysis behind them, the transfer pricing method applied to each transaction category, and the benchmarking analysis that supports the pricing actually used.
Both documents are required where a taxable person is part of a Multinational Enterprise (MNE) Group meeting the prescribed consolidated group revenue threshold, or where the taxable person individually exceeds the prescribed standalone revenue threshold, or a combination of the two conditions set out in Ministerial Decision No. 97 of 2023 and related guidance. Critically, neither document is submitted automatically alongside the Corporate Tax return — the obligation is to maintain them, keep them current, and produce them to the FTA within the stipulated period, generally 30 days, if a request is issued. This 'maintain, don't file' structure is where PNPC sees the most costly misunderstanding: businesses treat the absence of an annual filing requirement as the absence of any obligation at all, and only discover the documentation was supposed to already exist the day an FTA information request lands.
The Local File is built from a Functional, Asset and Risk analysis of each material related-party and Connected Person transaction category — what the UAE entity actually does, what assets and intangibles it owns or uses, and what commercial risks it genuinely bears — because that analysis, not a template, determines which of the five OECD-recognised pricing methods (Comparable Uncontrolled Price, Resale Price, Cost Plus, Transactional Net Margin Method, or Transactional Profit Split) is appropriate for each transaction type. The Master File, by contrast, is a group-level narrative; where a foreign parent already prepares one for another jurisdiction under a comparable BEPS Action 13 regime, PNPC's role is frequently to adapt and align that existing document to UAE requirements rather than to build one from a blank page, provided it genuinely reflects the group's current structure and intangible ownership.
The FTA's own Transfer Pricing Guide (CTGTP1) is explicit that documentation should be contemporaneous — prepared and reassessed at least annually to reflect the business as it actually operates that year — rather than assembled reactively once a request arrives. A Local File built inside a 30-day response window, using historical data that has to be reconstructed rather than data captured as the year progressed, is measurably weaker than one maintained as a matter of course. PNPC scopes every Master File and Local File engagement to sit alongside the annual Corporate Tax return cycle specifically so the documentation is filing-ready well before any request could arrive, and reconciles every disclosed figure to the Related Party Transactions disclosure form and the audited financial statements before the file is considered complete.
When Master File and Local File preparation is required
The UAE taxable person is part of an MNE Group whose consolidated group revenue meets or exceeds the prescribed threshold under Ministerial Decision No. 97 of 2023, or the entity itself exceeds the prescribed standalone revenue threshold
The entity has material related-party transactions — intercompany sales of goods, management fees, royalties, intercompany loans, cost allocations — with a foreign parent, sister company, or a mainland-Free Zone affiliate under common control
A Qualifying Free Zone Person in the group needs its related-party pricing documented so an FTA review cannot recharacterise Qualifying Income and threaten the 0% rate
The group already prepares a global Master File for another jurisdiction's BEPS Action 13 regime and needs it adapted, reviewed for currency, and aligned to UAE-specific requirements rather than rebuilt from scratch
An FTA information request or Corporate Tax audit has been issued and the Local File or Master File must be produced within the stipulated window, generally 30 days
A prior-year Related Party Transactions disclosure form was filed without a Local File or benchmarking study behind the figures, leaving numbers on record with no supporting documentation
The group has grown, restructured, or crossed the Master File threshold for the first time and needs the documentation built from a related-party map and transaction inventory rather than assumed complete
Owner or director remuneration, related-party rent, or shareholder loan interest has never been benchmarked and needs Connected Person support within the Local File for Corporate Tax deductibility purposes
The group spans UAE mainland, one or more Free Zones, and one or more foreign jurisdictions, so the Local File needs entity-specific benchmarking rather than a single group-wide policy applied uniformly
When a full Master File and Local File build is not the immediate need
Related-party transaction values sit below the disclosure and documentation thresholds under Ministerial Decision No. 97 of 2023 — a scoping review is worthwhile, but a full Local File and Master File are unlikely to be proportionate
The taxable person has no related-party or connected-person transactions at all — the Master File and Local File obligation only arises where a qualifying relationship and threshold are both met
The immediate need is only the annual Related Party Transactions disclosure form, and the group is below the Local File and Master File thresholds — that is a narrower, separate filing exercise PNPC scopes independently
The group's Reporting Entity status and CbCR threshold position have not yet been confirmed — that determination is a distinct, earlier step from Local File and Master File preparation, though the three obligations are frequently assessed together
The entity is an Exempt Person under the Corporate Tax Law, or otherwise confirmed outside its scope, subject to the exemption conditions continuing to be met and periodically re-verified
Audited financial statements for the relevant year are not yet finalised — Local File figures need to reconcile to final numbers, so it is usually more efficient to align documentation timing with the closed accounts
The engagement is purely about designing a transfer pricing policy for a not-yet-implemented arrangement — that is prospective policy design, a related but distinct step PNPC typically sequences before the Local File captures the resulting transactions
Management expects the documentation to justify a pricing outcome already decided for tax-saving reasons rather than to evidence the genuinely arm's length position — the Local File documents what is defensible, not a predetermined answer
Master File and Local File obligation by taxable person profile
| Profile | Local File Required | Master File Required | Typical Trigger | Documentation Discipline Needed |
|---|---|---|---|---|
| Standalone UAE entity, no related parties | No | No | No qualifying related-party or connected-person relationship exists | Confirm and re-test annually — group structure can change |
| UAE entity with related-party transactions below the disclosure threshold | No | No | Transaction values sit below the Ministerial Decision No. 97 of 2023 thresholds | Monitor in aggregate — several small transactions can cross the threshold together even where none does alone |
| UAE entity above disclosure threshold, below Local File threshold | No | No | Related-party transactions material enough to disclose but below the standalone or group revenue threshold | Disclosure form only, reconciled to the financial statements |
| UAE entity meeting the standalone revenue threshold or part of an in-scope MNE Group | Yes | Yes, if the MNE Group consolidated revenue threshold is separately met | Standalone revenue threshold met independently, or the group as a whole meets the consolidated threshold | Full FAR analysis, method selection, benchmarking, and Master File narrative — maintained, not filed automatically |
| UAE subsidiary of a foreign MNE Group with an existing global Master File | Yes — UAE-specific, cannot rely solely on the foreign document | Often adapted from the existing group Master File rather than rebuilt | Group threshold met at the consolidated level; foreign parent already documents elsewhere | Currency and consistency review of the adapted Master File plus a UAE-specific Local File and benchmarking search |
| UAE Free Zone entity, including a Qualifying Free Zone Person, with related-party dealings | Yes, if thresholds met — QFZP status does not exempt from transfer pricing rules | Yes, if the group threshold is met | Related-party dealings with mainland or foreign affiliates at values crossing the applicable threshold | Local File must additionally address the QFZP Qualifying Income interaction, not just general arm's length compliance |
| UAE entity subject to an active FTA information request | Yes — must be produced within the stipulated window, generally 30 days | Yes, if group threshold met, produced in the same window | FTA has issued a specific request touching related-party transactions | Documentation must already exist or be assembled and defensible on an urgent timeline |
Thresholds for the Local File and Master File obligations are set by the Ministry of Finance under Ministerial Decision No. 97 of 2023 and can be revised by further Cabinet or Ministerial Decision. PNPC confirms which row applies to your structure against the current thresholds at the start of every engagement rather than assuming last year's conclusion still holds.
| # | Stage & What PNPC Does | What Groups Miss Without a CA Firm | Timeline |
|---|---|---|---|
| 1 | Threshold Confirmation — establish whether the Local File and/or Master File obligation actually applies | The standalone revenue threshold and the MNE Group consolidated revenue threshold are tested independently — an entity can be below one and still be caught by the other through its group membership. We test both against the current Ministerial Decision No. 97 of 2023 thresholds rather than assuming last year's position. | Week 1 |
| 2 | Related-Party & Connected-Person Mapping | Every related entity — foreign parent, sister companies, mainland-Free Zone pairs under common control — and every Connected Person under Article 36 is identified against the ownership and control tests, not taken from a self-declared list. | Week 1–2 |
| 3 | Transaction Inventory & Materiality Screening | Every intercompany flow catalogued by category — goods, services, management fees, royalties, loans and guarantees, cost allocations, Connected Person payments — and screened against the Local File threshold in aggregate, so smaller items that add up are not missed. | Week 2 |
| 4 | Functional, Asset & Risk (FAR) Analysis for the Local File | For each material transaction category, a structured analysis of which entity performs which functions, owns which assets including intangibles, and bears which risks — the technical basis the method selection has to rest on. | Week 2–3 |
| 5 | Method Selection Per Transaction Category | The most appropriate of the five OECD-recognised methods selected per category from the FAR analysis and comparable-data availability, not defaulted to a single method across every transaction type. | Week 3 |
| 6 | Benchmarking Study for the Local File | An independent comparable search using recognised commercial databases, with documented screening and rejection criteria, producing a defensible arm's length range rather than a single unsupported figure. | Week 3–5 |
| 7 | Local File Drafting | Entity-specific narrative — business description, FAR analysis, method rationale, benchmarking outcome, Connected Person treatment — written in the structure the FTA's Transfer Pricing Guide expects, ready to be produced within the stipulated window. | Week 4–6 |
| 8 | Master File Sourcing — new build or adaptation of an existing group document | Where a global Master File already exists for another jurisdiction, it is reviewed for whether it genuinely reflects current group structure, intangible ownership, and consolidated financials before being adapted — an outdated foreign Master File adopted without review is a common defect. | Week 5–7, parallel |
| 9 | Master File Drafting or Finalisation | Group-wide narrative — organisational structure, business description, intangibles, intercompany financing, consolidated financial and tax position — built or finalised to the content Ministerial Decision No. 97 of 2023 prescribes. | Week 6–7 |
| 10 | Reconciliation to the Related Party Transactions Disclosure Form and Financial Statements | Every figure in the Local File is checked against the disclosure form filed with the Corporate Tax return and against the audited financial statements — a mismatch between these documents is one of the most common triggers for an FTA follow-up query. | Week 7 |
| 11 | Internal Review & Sign-Off | A senior reviewer independent of the original preparer checks both files before presentation to management or the Board, creating a governance trail that itself supports the arm's length position. | Week 7 |
| 12 | Indexed Retention Pack Assembly — ready for production, not filed automatically | Both documents, the benchmarking evidence, the FAR working papers, and the reconciliation are indexed and stored ready to hand the FTA within the stipulated production window — the pack itself is the deliverable, since neither document is submitted routinely. | Week 8 |
| 13 | Ongoing Monitoring, Annual Refresh & FTA Query Support | The benchmarking study's financial inputs are refreshed annually, structural changes are reflected, and if the FTA raises a query, we produce documentation within the stipulated window and engage directly on the technical position. | Ongoing, PNPC on call |
A first-time Master File and Local File build typically runs 6–8 weeks from kick-off to a filing-ready, indexed pack, timed to complete well ahead of the Corporate Tax return due date (generally within nine months of financial year end). Annual refresh engagements for existing clients move materially faster since the structural analysis and comparable methodology carry forward.
Group organisational chart showing every entity, ownership percentage, and country of incorporation or tax residence, current as at the relevant financial year end
UAE trade licence(s) for every UAE entity involved, including Free Zone entities with the specific Free Zone authority named
Shareholder registers or equivalent evidence of ownership, needed to test related-party status against Article 35 thresholds
Details of directors, key management personnel, and their close family relationships relevant to Connected Person status under Article 36
Qualifying Free Zone Person election status and supporting basis, where any Free Zone entity in the group has elected the 0% regime
Audited or management financial statements for the UAE entity for the relevant financial year
Consolidated group financial statements, needed for Master File content and threshold testing at the group level
Corporate Tax Registration Number (TRN) for the UAE taxable person
Prior-year Corporate Tax computations and any Related Party Transactions disclosure forms already filed
Trial balance or general ledger extract isolating intercompany transaction values by counterparty and category
Signed intercompany agreements — management service agreements, cost-sharing arrangements, distribution or supply agreements, royalty or licence agreements, intercompany loan agreements
Invoices, debit/credit notes, or ledger entries evidencing actual intercompany flows and the amounts involved
Details of intercompany loans and guarantees — principal, interest rate applied, tenure, and any security arrangement
Existing global Master File, if one already exists at group level, for review and adaptation to UAE requirements
Transfer pricing documentation already prepared for other jurisdictions in the group, for consistency review
Description of the UAE entity's business activities and its role in the group's overall value chain
Details of tangible and intangible assets owned or used by the UAE entity, including any group intellectual property housed in the UAE
Risk allocation — which entity carries market risk, credit risk, inventory risk, and foreign exchange risk on the transactions being documented
Employee headcount and functional breakdown for the UAE entity — sales, operations, management, and support roles
Payroll records and employment contracts covering owner or director remuneration, including benefits-in-kind
Lease agreements where a related party or connected person is the landlord of business premises used by the company
Shareholder loan documentation — principal, interest rate, and repayment terms, in either direction
Any existing market benchmarking reference already available to support the current terms
Description of the group's overall business, its key value drivers, and its main geographic markets
List and description of important intangibles owned by the group and which entities legally own them
Description of the group's intercompany financing arrangements, including with unrelated lenders
Group's consolidated financial statements and a list of important agreements related to intangibles between group members
| Phase | Triggered By | PNPC Guidance | Risk If Ignored |
|---|---|---|---|
| Threshold Assessment | Corporate Tax registration or the group crossing the standalone or consolidated revenue threshold for the first time | Establish precisely whether the Local File, Master File, or both apply, against the current Ministerial Decision No. 97 of 2023 thresholds, and set up the transaction inventory from day one. | Assuming the threshold has not been crossed, without testing it against actual group-consolidated figures, leaves a genuine documentation obligation undiscovered until an FTA request arrives. |
| First-Time Build | Threshold confirmed as met, no existing Local File or Master File on record | Run the full related-party mapping, FAR analysis, method selection, benchmarking, and drafting sequence, timed to complete ahead of the Corporate Tax return due date, not reactively after a request. | A first Local File assembled inside a 30-day FTA response window, without contemporaneous records or a properly screened benchmarking search, is measurably weaker than one built in the ordinary course. |
| Annual Refresh Cycle | Each financial year approaching its Corporate Tax return due date | Refresh the benchmarking study's financial inputs, update the Local File and Master File for any structural change, reconcile every figure to the financial statements, and re-confirm the disclosure form matches. | Stale or inconsistent figures across the disclosure form, Local File and financial statements are a direct audit trigger, regardless of whether the underlying pricing was reasonable. |
| Master File Currency Check | Group restructuring, new intangible ownership, or a change in the group's financing arrangements | Re-verify that any adapted global Master File still reflects the group's actual current structure and intangible ownership before relying on it for a UAE production — an outdated adopted document is a documented weakness. | A Master File describing a structure the group has since outgrown reads as inconsistent with the Local File and the group's own consolidated accounts if an FTA reviewer compares them. |
| FTA Information Request or Audit | FTA issues a request touching related-party transactions | Produce the Local File and Master File within the stipulated period, generally 30 days, with a clear supporting narrative, and engage the FTA directly on the technical basis for the pricing applied. | Missing the response window, or handing over documentation that does not withstand scrutiny, risks a transfer pricing adjustment plus additional Corporate Tax, penalties, and interest. |
| Qualifying Free Zone Person Review | Annual QFZP status confirmation or a Free Zone entity restructuring | Confirm the Local File's related-party pricing conclusions have not caused Qualifying Income to fail the arm's length condition or breach the permitted non-qualifying revenue threshold. | Losing QFZP status because of undocumented or mispriced related-party dealings shifts the entity's income onto the standard 9% rate — often a far larger cost than the documentation itself. |
| Group Restructuring or Expansion | M&A, new subsidiary, mainland-to-Free-Zone conversion, or a new cross-border flow | Re-run the related-party map, transaction inventory, and threshold test whenever the structure changes materially — last year's Local File and Master File conclusions may no longer reflect this year's group. | An outdated related-party map means new flows go undocumented, and the exposure compounds with every additional year it is not caught. |
| Dispute or Adjustment | FTA proposes a transfer pricing adjustment following review of the produced Local File or Master File | Assess the technical merits, prepare a formal response or reconsideration request backed by the FAR analysis and benchmarking evidence, and advise on settlement versus escalation. | An unchallenged adjustment can set an unfavourable precedent for later years and invite a broader-scope review of other related-party dealings in the group. |
The Master File and Local File obligation is a recurring, maintain-and-produce-on-request obligation, not a one-time filing — it re-triggers every financial year and on every material change to group structure, ownership, or intercompany arrangement. PNPC's annual retainer is built to keep both documents contemporaneous rather than reconstructed under audit pressure.
What is the difference between the Master File and the Local File?
The Master File presents the group-wide picture — organisational structure, business description, intangible ownership, intercompany financing, and consolidated financial position — and is common across every entity in the group. The Local File is entity-specific, covering the UAE taxable person's own material related-party transactions, its FAR analysis, the method applied to each transaction category, and the benchmarking evidence supporting the pricing used. Ministerial Decision No. 97 of 2023 requires both where the applicable thresholds are met, and they serve different, complementary purposes for an FTA reviewer.
Do we have to file the Master File and Local File with the Corporate Tax return every year?
No. Neither document is submitted automatically alongside the Corporate Tax return. The obligation is to maintain both, keep them current, and produce them to the FTA within the stipulated period, generally 30 days, if the FTA requests them. What is filed with the return is the separate Related Party Transactions disclosure form, which is a shorter schedule, not the full Local File or Master File.
What triggers the requirement to prepare a Local File?
The Local File is required where the taxable person individually exceeds the prescribed standalone revenue threshold, or is part of an MNE Group meeting the prescribed consolidated group revenue threshold, under Ministerial Decision No. 97 of 2023. Both conditions are tested independently — an entity below the standalone threshold can still be caught through its group's consolidated position.
What does the Master File actually need to contain?
Ministerial Decision No. 97 of 2023 prescribes the Master File content in line with the OECD's BEPS Action 13 framework: the group's organisational structure, a description of its businesses and key value drivers, the ownership and location of important intangibles and related agreements, a description of the group's intercompany financing arrangements, and the group's consolidated financial and tax position. It is a narrative document about the group as a whole, not the UAE entity specifically.
What does the Local File need to contain?
A description of the UAE entity's business and its role in the group's value chain, a listing of its material related-party and connected-person transactions by category, the FAR analysis behind those transactions, the transfer pricing method selected for each category with supporting rationale, and the benchmarking analysis — comparable search, screening criteria, and resulting arm's length range — that evidences the pricing applied.
Our foreign parent already has a global Master File. Can we just use that for the UAE?
Often yes, with review — an existing global Master File can typically be adapted for UAE purposes rather than rebuilt from scratch, provided it genuinely reflects the group's current structure, intangible ownership, and consolidated financials. What cannot be borrowed from the parent's documentation is the Local File, which must be UAE-entity-specific and cannot rely solely on a foreign document's generic content.
How long do we have to produce the Local File and Master File if the FTA asks for them?
The stipulated production period is generally 30 days from the FTA's request, though the precise timeframe should be confirmed against the specific request received and current FTA guidance. Because this window is short relative to the analytical work involved in a defensible study, PNPC's standard approach is to have both documents already built and indexed before any request arrives, not to start the analysis once the clock starts running.
What happens if we cannot produce the Local File or Master File within the stipulated window?
If the FTA requests the documentation and the taxable person cannot produce it, or produces documentation that does not adequately support the pricing applied, the FTA can adjust the taxable income to what it considers the arm's length outcome would have been. This can mean additional Corporate Tax, administrative penalties for non-compliance, and interest on the additional tax from the original due date.
How does PNPC select the transfer pricing method for each transaction in the Local File?
Method selection follows the FAR analysis, not the other way around. For each material transaction category we assess which party performs which functions, owns which assets including intangibles, and bears which commercial risks, and select the most appropriate of the five OECD-recognised methods — Comparable Uncontrolled Price, Resale Price, Cost Plus, Transactional Net Margin Method, or Transactional Profit Split — based on that analysis and the availability of reliable comparable data.
Does the Local File need to cover owner or director remuneration?
Yes, where the amounts are material. Payments and benefits to Connected Persons under Article 36 — owner or director salary, rent paid on premises they personally own, interest on shareholder loans — must be at market value to remain fully deductible for Corporate Tax purposes, and the Local File should document the benchmarking that supports those terms alongside the entity's related-party transactions.
How does a Qualifying Free Zone Person's Local File differ from a mainland entity's?
The content requirements are the same, but a Qualifying Free Zone Person's Local File carries an additional, higher-stakes dimension: if related-party pricing with a mainland or foreign affiliate is found not to be arm's length, the FTA can recharacterise the income involved, which can affect whether it still counts as Qualifying Income and, in more serious cases, threaten the QFZP status itself if non-qualifying revenue exceeds the permitted threshold.
How often does the benchmarking study in the Local File need refreshing?
The financial data underlying the study is generally refreshed annually to reflect the tested party's actual results for the year. The underlying comparable company search itself is typically refreshed on a multi-year cycle, commonly every three years or sooner if the industry or the entity's functional profile changes materially, consistent with OECD guidance on documentation currency.
Do the Master File and Local File need to reconcile to the Related Party Transactions disclosure form?
Yes, and this reconciliation is one of the most important quality checks PNPC performs before considering either document complete. The disclosure form is filed with the Corporate Tax return and is what the FTA sees first — if its figures do not match the Local File and the audited financial statements exactly, that mismatch is one of the most common triggers for a follow-up FTA information request.
Is Country-by-Country Reporting the same thing as the Master File and Local File?
No, though they are related tiers of the same OECD BEPS Action 13 documentation framework. CbCR, governed by Cabinet Resolution No. 44 of 2020 as amended, is a group-level, jurisdiction-by-jurisdiction financial breakdown filed with the Ministry of Finance, separate from the FTA. The Master File and Local File are governed by Ministerial Decision No. 97 of 2023 and are maintained for, and produced to, the FTA. A group above the CbCR threshold is very likely also in scope for the Master File and Local File, and PNPC scopes and builds all three together where applicable.
How long does a first-time Master File and Local File build take?
For a first-time engagement with reasonably prompt data turnaround, PNPC typically completes related-party mapping, FAR analysis, method selection, benchmarking, and full drafting of both documents within 6 to 8 weeks, timed to be filing-ready ahead of the Corporate Tax return due date. Delays in document collection from the client are the most common cause of timeline slippage.
Can PNPC help if we already missed a year of Master File and Local File preparation?
Yes. For groups that have already passed one or more Corporate Tax financial years without formal documentation, we assess the exposure, reconstruct the best-available FAR analysis and benchmarking support for the closed periods using whatever records exist, and put a contemporaneous process in place going forward. Retrospective work is inherently constrained by data availability, but it puts the business in a materially stronger position than facing an FTA request with nothing on file.
How is the Master File and Local File engagement priced?
PNPC scopes the engagement based on the number of related-party transaction categories requiring benchmarking, whether the Master File needs to be built new or can be adapted from an existing group document, the complexity of the FAR analysis, and whether this is a first-time build or an annual refresh. A fixed, written fee is agreed after an initial scoping call and before work begins.
Why should we build the Local File and Master File now if the FTA hasn't asked for them yet?
Because the obligation to maintain contemporaneous documentation exists from the moment the thresholds are met, independent of whether a request is ever issued, and because a document built in the ordinary course — with FAR conversations held while they are current and a benchmarking search run without deadline pressure — is measurably stronger than one reconstructed inside a 30-day response window. Waiting also means several years of undocumented related-party activity can accumulate before the gap is discovered.
PNPC Master File & Local File preparation vs. generic compliance filers and DIY templates
| Dimension | PNPC | Generic Filer / DIY Template |
|---|---|---|
| Threshold testing | Standalone and MNE Group consolidated thresholds tested independently against current Ministerial Decision No. 97 of 2023 figures | Only the entity's own revenue tested, missing the group-level trigger |
| Related-party identification | Independently verified against Article 35/36 ownership and control thresholds | Relies on the client's self-declared list without independent verification |
| FAR analysis depth | Structured, transaction-category-specific analysis underpinning method selection | Generic industry description substituted for entity-specific functional analysis |
| Method selection | Selected per transaction category from the FAR analysis, not defaulted | Default TNMM applied broadly, regardless of transaction type |
| Benchmarking rigour | Documented, screened comparable set with a transparent rejection matrix | Templated or recycled comparable sets with limited screening detail |
| Master File currency check | Adopted global Master Files reviewed for whether they still reflect the current group structure before use | Foreign Master File adopted without review of currency or accuracy |
| Connected Person coverage | Owner and director remuneration, related-party rent, and loan interest independently benchmarked within the Local File | Often left undocumented or treated as ordinary payroll |
| QFZP interaction | Explicit review of how the Local File's pricing conclusions affect Qualifying Income and 0% status | Rarely addressed — treated as an unrelated filing |
| Production readiness | Indexed pack built and maintained ahead of any FTA request, ready within the stipulated window | Assembled reactively only after a request is received |
| Disclosure reconciliation | Every Local File figure tied line-by-line to the disclosure form and audited statements before sign-off | Disclosure form populated independently, leaving mismatches that invite queries |
What the PNPC package includes
- 01
Standalone and MNE Group consolidated threshold testing against current Ministerial Decision No. 97 of 2023 figures
- 02
Full related-party and connected-person mapping against Articles 35 and 36 of the Corporate Tax Law
- 03
Transaction inventory and materiality assessment across every intercompany flow, including Connected Person payments
- 04
Functional, Asset and Risk (FAR) analysis for each material transaction category
- 05
Transfer pricing method selection with documented rationale per category
- 06
Independent benchmarking study using recognised commercial comparable databases
- 07
Local File drafting in FTA Transfer Pricing Guide-ready format
- 08
Master File preparation or adaptation and currency review of an existing group document
- 09
Connected Person payment benchmarking — owner/director remuneration, related-party rent, shareholder loan interest
- 10
Qualifying Free Zone Person interaction review where a Free Zone entity sits in the group
- 11
Reconciliation of Local File figures to the Related Party Transactions disclosure form and audited financial statements
- 12
Indexed, production-ready retention pack maintained ahead of any FTA request
- 13
FTA information request and audit response support, including production within the stipulated window
- 14
Annual refresh retainer covering financial data updates, structural change reviews, and regulatory monitoring
- 15
Documented benchmarking search due-date tracker for the multi-year comparable refresh
- 16
Initial scoping call with a reasoned threshold conclusion and written assumptions before engagement
Build your Master File and Local File before the FTA's 30-day clock starts, not after — speak to PNPC's Dubai transfer pricing desk.
Jurisdiction
Free zone, mainland & offshore
Ready to get started?
Tell us about your requirement — a UAE specialist responds within 24 hours.