UAE Taxation & Regulatory Compliance · Transfer Pricing
TP Audit Support
An FTA information request touching related-party transactions rarely arrives with a generous runway — the Local File or Master File is usually due within a stipulated window, commonly around 30 days, and a benchmarking study reconstructed under that pressure reads very differently from one built in the ordinary course of business.
Chartered Accountants · Dubai · Since 1986
TP Audit Support is PNPC's engagement for UAE taxable persons facing a Federal Tax Authority (FTA) information request, desk review, or formal audit that touches related-party or connected-person transactions under Article 34 of the Corporate Tax Law (Federal Decree-Law No. 47 of 2022) and its documentation rules under Ministerial Decision No. 97 of 2023. It sits downstream of transfer pricing advisory and documentation — the analytical, policy-setting work done before a query arrives — and picks up the moment the FTA actually asks a question: a request to produce a Local File or Master File within the stipulated period, a desk-based query on a figure in the Related Party Transactions disclosure schedule, or a full-scope Corporate Tax audit in which related-party pricing is one of several lines under review.
The FTA's Transfer Pricing Guide (CTGTP1) sets out that documentation is expected to be contemporaneous — prepared and reassessed in the ordinary course, not reconstructed reactively — and an FTA reviewer reading a Local File produced inside a live audit window will test it accordingly: does the benchmarking search predate the request or follow it, does the FAR (Functions, Assets and Risks) analysis describe the entity's actual operations or a generic industry template, and do the disclosed figures reconcile line-by-line to the audited financial statements and the Corporate Tax return. Where documentation already exists, PNPC's role is to stress-test it against exactly those questions before it is produced, close any gap that would otherwise surface for the first time under FTA scrutiny, and manage the actual submission and correspondence. Where no adequate documentation exists at all, PNPC's role shifts to rapid, defensible reconstruction — a materially harder exercise than a documentation build undertaken with no deadline pressure, but one built on the same OECD-aligned methodology: Comparable Uncontrolled Price, Resale Price, Cost Plus, Transactional Net Margin Method, or Transactional Profit Split, selected on the facts rather than by convenience.
Audit support also covers the procedural side that is easy to underweight when the substance of the pricing analysis is the immediate worry: confirming exactly what the FTA has asked for and by when, managing the correspondence trail so every request and response is documented, coordinating internally so the figures produced to the FTA are consistent with what has already been filed on the Related Party Transactions disclosure schedule and the Corporate Tax return, and — where the FTA proposes an adjustment — assessing whether the technical position genuinely supports a formal reconsideration request or whether settlement is the more proportionate route. A transfer pricing adjustment that increases UAE taxable income can also create economic double taxation if the counterparty jurisdiction does not make a corresponding adjustment, which is where a Double Taxation Avoidance Agreement's Mutual Agreement Procedure (MAP) becomes relevant, albeit as a longer, formal mechanism rather than a first-line response.
What distinguishes a well-run audit support engagement from a reactive scramble is sequencing: confirm the actual scope and deadline of the FTA's request before drafting anything; assemble the underlying financial and transactional evidence before writing the narrative; test the FAR analysis and method selection against the entity's real operations rather than reusing whatever was filed previously without re-checking it still fits; and only then produce the response. PNPC brings this discipline whether the underlying documentation was originally prepared by our own Dubai desk, inherited from a prior advisor, or — in the more exposed cases — never properly prepared at all. Because a Qualifying Free Zone Person's 0% rate on Qualifying Income depends in part on related-party pricing not breaching the arm's length standard or the permitted non-qualifying revenue threshold, an audit touching a Free Zone entity's intercompany dealings carries stakes well beyond the immediate adjustment amount, and PNPC treats that QFZP exposure as a distinct checkpoint within the audit response, not an afterthought.
The mainland-versus-Free-Zone distinction surfaces again once an audit is actually underway, not just at the QFZP checkpoint noted above. A mainland taxable person's related-party audit is assessed purely against the standard Corporate Tax base — a finding simply increases the tax due on any additional income at the applicable rate. A Free Zone entity's audit carries a second, structural question layered on top: even where the adjustment itself is modest, the FTA's finding on whether the underlying related-party dealing was genuinely arm's length feeds directly into whether the entity's wider Qualifying Income position still holds together for the year, because a pricing failure on one related-party stream can, in combination with other non-qualifying revenue, tip the entity past the permitted de minimis threshold and move all of its income — not just the mispriced portion — onto the standard rate. PNPC therefore scopes a Free Zone audit response as two linked but distinct exercises: defending the specific pricing under review, and separately confirming what happens to the QFZP position under each plausible outcome of that defence, so the client understands the full financial stakes before deciding how hard to contest a given adjustment.
The FTA's practical approach to a taxable person already inside a broader, orderly compliance relationship — an existing Corporate Tax registration with a clean filing history, a group that has proactively made a voluntary disclosure on an unrelated matter, or one that has previously responded promptly and fully to an earlier information request — tends to differ, in tone if not in the underlying legal standard, from its approach to a first-time or unresponsive filer. None of this changes the substantive arm's length test a related-party transaction has to meet, but it does shape how PNPC frames the audit response itself: a group with a demonstrated pattern of good-faith engagement can credibly reference that history as context, while a group facing its first FTA contact of any kind needs the response to establish credibility from a standing start. PNPC tracks this posture deliberately rather than treating every audit response as an identical technical exercise regardless of the client's broader compliance record.
When TP audit support is the right engagement
The FTA has issued an information request specifically asking for a Local File, Master File, or supporting benchmarking analysis, with a response due within the stipulated period
A Corporate Tax audit or desk review is underway and related-party or connected-person transactions are among the items being examined
The FTA has queried a figure on the Related Party Transactions disclosure schedule that does not appear to reconcile to the audited financial statements
Existing transfer pricing documentation was prepared by another advisor or an in-house team, and it needs an independent stress-test before being produced to the FTA under a live request
No adequate Local File or Master File exists at all, and one needs to be reconstructed rapidly and defensibly within the FTA's response window
The FTA has proposed a transfer pricing adjustment and the taxable person needs a technical assessment of whether a reconsideration request is warranted, or whether settlement is the more proportionate path
A related-party adjustment in the UAE risks creating economic double taxation with a counterparty jurisdiction, and the group needs to evaluate whether a Mutual Agreement Procedure route under an applicable Double Taxation Avoidance Agreement is worth pursuing
A Qualifying Free Zone Person entity's related-party pricing is under review, and the outcome could affect whether its income continues to qualify for the 0% rate
A prior year's disclosure, Local File, or Master File contains an error or inconsistency that has surfaced during an FTA review and needs correction, explanation, or a formal amendment before the audit proceeds further
Management wants a pre-emptive readiness check — simulating how the existing documentation would perform if an FTA request landed tomorrow — before any actual query has been received
A voluntary disclosure on a related-party pricing or disclosure-form error is being considered before the FTA identifies it independently, and the taxable person wants the technical position assessed first
More than one entity in the same group has received related or overlapping FTA information requests, and the responses need to be coordinated so the group tells one consistent story across every entity involved
When TP audit support is not the right starting point
No FTA query, audit notice, or request has been received, and the actual need is building transfer pricing documentation from scratch — that is the advisory and documentation engagement, not audit support, though PNPC frequently recommends starting there specifically to avoid ever needing this one
The business has no related-party or connected-person transactions at all, so there is no transfer pricing exposure for an audit to examine in the first place
The FTA's request or audit is focused on matters unrelated to related-party pricing — for example, a general VAT compliance review with no Corporate Tax transfer pricing dimension — which calls for a different specialist engagement
The dispute has already moved beyond FTA reconsideration into formal tax litigation or a Mutual Agreement Procedure negotiation requiring lead counsel — PNPC supports the technical transfer pricing analysis underlying such proceedings but the litigation itself sits with legal counsel
The matter is a genuine shareholder or contractual dispute between related parties that happens to involve intercompany pricing, rather than an FTA-driven transfer pricing question — that calls for legal advice first
Audited financial statements for the year under review are not yet finalised and the FTA has not yet issued a formal request — better to complete the documentation refresh on the normal cycle than treat an anticipated, undated query as an active audit
The client is looking for a guaranteed audit outcome or a promise that no adjustment will be raised — PNPC prepares and defends the strongest available technical position, but the FTA's ultimate determination is outside any advisor's control
The FTA request concerns a purely procedural or administrative matter — for example, confirming Corporate Tax registration details — with no reference at all to related-party or connected-person transactions
The FTA contact is still at a very early, informal stage — a general query or portal message flagging a possible future review with no formal information request yet issued — where a quiet internal readiness check is the more proportionate first step rather than full audit-support mobilisation
TP audit support scope by trigger and starting documentation position
| Trigger / Starting Position | PNPC's Immediate Focus | Documentation Position | Typical Urgency | Likely Next Step If Unresolved |
|---|---|---|---|---|
| FTA information request for Local File / Master File, documentation already exists | Stress-test existing file against the specific request, close gaps, manage submission | Exists — needs review, not rebuild | High — response window is stipulated, commonly around 30 days | Submission with narrative addressing any weak points proactively |
| FTA information request, no adequate documentation exists | Rapid, defensible reconstruction of FAR analysis, method selection and benchmarking | Absent or materially incomplete | Very high — reconstruction under deadline pressure | Best-available submission plus voluntary explanation of the documentation gap |
| Desk review query on Related Party Transactions disclosure figure | Reconcile disclosed figure to Local File, ledgers and financial statements | May exist but reconciliation not previously tested | Moderate to high, depending on FTA's stated deadline | Corrected disclosure or explanatory response, escalating to full audit if unresolved |
| Full Corporate Tax audit with transfer pricing as one line item | Coordinate TP-specific response within the broader audit timeline | Varies by entity | High — audit-wide deadlines govern, not TP alone | Audit findings letter, potential proposed adjustment |
| FTA has proposed a transfer pricing adjustment | Technical assessment of the adjustment; reconsideration request or settlement analysis | Existing documentation now under direct challenge | High — reconsideration requests are themselves time-bound | Formal reconsideration, or acceptance and payment of additional tax, penalties and interest |
| Proposed adjustment risks double taxation with a treaty partner jurisdiction | Assess Mutual Agreement Procedure eligibility under the relevant DTAA | Existing documentation used as MAP submission basis | Lower urgency but long lead time — MAP is a lengthy process | MAP request lodged with UAE and counterparty competent authorities |
| Pre-emptive readiness check, no live FTA query | Simulate an FTA request against current documentation to find gaps in advance | Exists — being validated proactively | Low — scheduled, not reactive | Remediation plan actioned before any real request arrives |
| Multiple group entities receiving simultaneous or overlapping FTA requests | Coordinate a single, consistent group-wide response across every entity involved | Varies by entity | High — parallel deadlines across entities | Consolidated response package, with one group-level narrative referenced by each entity's individual filing |
| Taxable person identifies its own pricing or disclosure error before the FTA does | Assess whether voluntary disclosure is the appropriate route, and prepare the submission if so | Existing documentation being corrected proactively | Moderate — self-initiated, not FTA-deadline-driven | Voluntary disclosure lodged, or continued monitoring if the matter does not warrant formal disclosure |
| FTA audit response needing alignment with a parallel India-side transfer pricing position | Align UAE and Indian technical positions on the same cross-border related-party transaction | Exists on one or both sides, needs cross-checking | High, governed by the tighter of the two jurisdictions' deadlines | Consistent submissions filed in both jurisdictions, coordinated across PNPC's India and Dubai desks |
Every audit support engagement starts with confirming exactly what the FTA has asked for, the stated deadline, and the specific transactions or years in scope — assumptions about scope drawn from a prior year's documentation or a different client's experience are a common and avoidable source of a mismatched response.
| # | Stage & What PNPC Does | What Groups Miss Without a CA Firm | Timeline |
|---|---|---|---|
| 1 | Triage the FTA Request — read the actual scope, deadline and legal basis before drafting anything | FTA requests vary in scope — a narrow desk query on one transaction category is not the same exercise as a full Local File production request. Responding to the wrong scope wastes the limited window and can read as non-responsive. | Day 1–2 of engagement |
| 2 | Existing Documentation Review — assess what exists against what has been asked for | Groups often assume last year's Local File 'covers' this year's request without checking whether the transaction values, entities, or FAR profile have moved since it was prepared. | Days 2–5 |
| 3 | Gap Analysis — identify every point the existing file would not withstand FTA scrutiny | The gaps that matter most are rarely the headline numbers — they are unscreened comparables, a FAR narrative that doesn't match the entity's actual 2024–2025 operations, or Connected Person payments omitted from the disclosure entirely. | Days 3–7 |
| 4 | Rapid Benchmarking Refresh or Build (Where Needed) | A benchmarking search run under audit pressure still needs a documented, defensible screening methodology — a rushed comparable set with no rejection trail is easily challenged by a reviewing officer. | Week 1–3, compressed relative to a non-audit engagement |
| 5 | Reconciliation to Disclosure Form & Financial Statements | Every figure produced to the FTA must trace cleanly to the Related Party Transactions schedule already filed and the audited accounts — an unexplained mismatch discovered mid-audit is worse than one caught and explained beforehand. | Week 1–2, parallel |
| 6 | Connected Person Payment Check — owner remuneration, director rent, shareholder loan interest | Connected Person payments are frequently the weakest point in an existing file because they were originally treated as ordinary payroll or overheads rather than benchmarked under Article 36. | Week 1–2, parallel |
| 7 | Draft the Response Narrative | A response that simply attaches documents without a covering narrative explaining the FAR analysis and method rationale leaves the FTA reviewer to draw their own conclusions — PNPC writes the narrative the reviewer needs to reach the right one. | Week 2–3 |
| 8 | Internal Review & Client Sign-Off | A senior reviewer independent of the drafter checks the response before submission — a discipline that matters even more under deadline pressure, not less. | Week 2–3 |
| 9 | Submission Within the Stipulated Window | The response is submitted with time to spare wherever the timeline allows, not on the deadline itself, to absorb any last-minute FTA clarification request. | Before the stated deadline, with buffer where possible |
| 10 | FTA Follow-Up Query Management | A first response often generates a follow-up question rather than a final determination — PNPC stays engaged through the full query cycle rather than treating the first submission as the end of the engagement. | As triggered, typically weeks after initial submission |
| 11 | Proposed Adjustment Assessment (If Raised) | Not every proposed adjustment should be contested, and not every one should be accepted — PNPC assesses the technical merits specifically rather than defaulting to either extreme. | Within the reconsideration request window if applicable |
| 12 | Reconsideration Request or Settlement Recommendation | A reconsideration request needs its own evidentiary and legal grounding, distinct from the original documentation — PNPC prepares it as a standalone submission, not a resubmission of the same file. | As triggered, time-bound once an adjustment is formally proposed |
| 13 | Double Taxation / MAP Assessment (Where Relevant) | Where a proposed adjustment risks double taxation with a treaty partner, the MAP window and process are easy to miss if the group is focused solely on the UAE-side response. | Assessed alongside the adjustment response; MAP itself runs over a longer, separate timeline |
| 14 | Post-Audit Documentation Remediation | Once the audit closes, the underlying documentation gaps that caused the difficulty should be fixed for future years — otherwise the same weaknesses resurface in the next audit cycle. | Following audit closure, feeding into the ongoing annual documentation retainer |
| 15 | Multi-Entity Coordination (Where Applicable) | Where more than one group entity has received an overlapping request, responses drafted independently by different local teams can describe the same transaction inconsistently — PNPC coordinates a single group-level narrative referenced consistently across every entity's filing. | Parallel to the main response timeline, as triggered |
| 16 | Voluntary Disclosure Assessment (Where the Gap Is Self-Identified) | Not every documentation gap is best handled by waiting for an FTA request — where PNPC's own gap analysis surfaces an error the FTA has not yet queried, we assess with the client whether a voluntary disclosure is the more favourable route. | As triggered during documentation review, before any formal request lands |
| 17 | Annual Retainer Transition | A group that has just been through an audit is the group most likely to underinvest in the following year's documentation once the immediate pressure lifts — PNPC proposes the ongoing annual retainer explicitly at this stage rather than waiting for the client to raise it. | Immediately following post-audit remediation |
Timelines compress hard once an FTA deadline is live — a realistic first-response turnaround is one to three weeks depending on how much of the underlying documentation already exists and how quickly financial and transactional data can be produced. PNPC prioritises live audit engagements ahead of routine advisory work once a stipulated deadline is confirmed.
Copy of the FTA's information request, audit notice, or desk review query, including the stated response deadline
Identification of the specific transactions, transaction categories, or financial years the request covers
Any prior correspondence with the FTA on the same or a related matter
Confirmation of the Corporate Tax Registration Number (TRN) and filing history for the entity under review
Local File and Master File as previously prepared, if any exist, for the years under review
Prior-year Related Party Transactions disclosure forms as filed on EmaraTax
Benchmarking study and comparable-set screening record underlying any existing documentation
Board-approved transfer pricing policy, if one was formally adopted
Group organisational chart with ownership percentages current as at the years under review
Trade licences for every UAE entity involved, including the issuing Free Zone authority where applicable
Qualifying Free Zone Person election status and supporting basis, where a Free Zone entity is part of the transactions under review
Details of directors, officers and their relatives relevant to Connected Person status under Article 36
Audited financial statements for every year under review
Trial balance or general ledger extract isolating the related-party and connected-person transactions in question
Signed intercompany agreements covering the transactions under review
Invoices, debit/credit notes, and payment records evidencing the actual transaction flows
Payroll records and employment contracts for owners, directors and officers whose remuneration is under review
Lease agreements where a related party or connected person is the landlord of premises used by the business
Shareholder loan documentation — principal, interest rate, tenure — for any loan under review
Any market benchmarking reference already available for the payments in question
The FTA's formal adjustment notice or audit findings letter, in full
Technical grounds identified for any reconsideration request, supported by economic analysis
Assessment of double taxation risk and the relevant Double Taxation Avoidance Agreement, where a treaty partner jurisdiction is involved
Internal management sign-off on whether to contest the adjustment or proceed to settlement
A consolidated log of every FTA request received across the group's UAE entities, with dates and stated deadlines, so overlapping response windows are tracked centrally rather than entity by entity
Confirmation of which UAE entity is the counterparty on each intercompany transaction referenced across the multiple requests, to avoid inconsistent descriptions of the same transaction in separate responses
A single group-level FAR narrative reference point that each entity-specific response can draw from consistently, rather than each entity's response being drafted independently
Prior correspondence between the FTA and any other group entity on a related or overlapping matter
Internal record of how and when the pricing or disclosure error was identified, and by whom, ahead of any FTA request
A working calculation of the corrected position and the resulting impact on taxable income for the affected year(s)
Management's basis for treating the matter as suitable for voluntary disclosure rather than continued monitoring, prepared with PNPC's technical input
Draft voluntary disclosure submission and supporting explanation, prepared for internal review before formal lodgement
| Phase | Triggered By | PNPC CA Guidance | Risk If Ignored |
|---|---|---|---|
| Initial FTA Request Received | FTA issues an information request or audit notice referencing related-party transactions | Confirm the exact scope, deadline and legal basis of the request within the first day or two, and engage PNPC before drafting any response internally. | A response drafted against the wrong scope, or without professional review, can read as incomplete or evasive even where the underlying position is defensible. |
| Documentation Assembly | Existing files reviewed against the specific request | Stress-test every element — FAR narrative, method selection, comparable screening, reconciliation to filed figures — before anything is produced to the FTA. | Producing a document with an unscreened comparable set or an inconsistent FAR narrative invites a follow-up query that widens the audit's scope. |
| Response Submission | Deadline approaching or reached | Submit with a clear covering narrative and, wherever the window allows, a buffer ahead of the actual deadline to absorb any last-minute issue. | A late submission, even by a short margin, can itself trigger a separate compliance penalty independent of the substantive transfer pricing question. |
| FTA Follow-Up & Clarification | FTA raises a further question on the initial submission | Treat the follow-up with the same rigour as the original request — a hurried or informal reply at this stage can undo a strong initial submission. | Follow-up questions left unanswered or answered inconsistently with the original submission are a common trigger for escalation to a formal audit. |
| Proposed Adjustment | FTA determines the pricing applied does not reflect an arm's length outcome | Assess the technical merits independently before deciding whether to contest — not every proposed adjustment is worth challenging, and not every one should be accepted without scrutiny. | Accepting an unsupported adjustment without challenge sets a precedent that can be referenced in later years' reviews; contesting a well-founded one without a genuine technical basis wastes time and cost. |
| Reconsideration or Settlement | Formal decision point on how to respond to a proposed adjustment | Prepare a standalone reconsideration submission with fresh economic analysis where the merits support it, or negotiate settlement terms where they do not. | Missing the reconsideration request window closes off that route entirely, leaving escalation through a more formal, costlier dispute process as the only remaining option. |
| Double Taxation Exposure | Adjustment increases UAE taxable income without a corresponding reduction in a counterparty jurisdiction | Evaluate Mutual Agreement Procedure eligibility under the applicable Double Taxation Avoidance Agreement promptly, since MAP is a lengthy process best started early. | Delaying a MAP assessment can push the group past any time limits the relevant treaty imposes on raising the request. |
| Post-Audit Remediation | Audit or query cycle concludes | Fix the underlying documentation gaps that caused the difficulty — refresh the benchmarking study, formalise the transfer pricing policy, and correct any disclosure inconsistency going forward. | Closing the audit without remediating the root documentation weakness means the same gap resurfaces, often with less goodwill, in the next review cycle. |
| Voluntary Disclosure Decision | PNPC's own review of existing documentation surfaces an error before any FTA request is received | Assess the technical and financial impact of the error, and decide with the client whether voluntary disclosure is the more favourable route compared with waiting for the FTA to identify it independently. | An error identified internally but left unaddressed can be treated less favourably if the FTA later identifies it independently, compared with a proactive voluntary disclosure. |
| Multi-Entity Audit Coordination | More than one group entity receives an overlapping or related FTA request | Coordinate a single, consistent narrative and factual position across every entity's response, rather than allowing each entity to respond independently. | Inconsistent descriptions of the same intercompany transaction across two entities' separate responses is itself a red flag that can widen the scope of the audit. |
| Annual Retainer Onboarding | Audit closes and post-audit remediation is agreed | Formalise an ongoing annual transfer pricing documentation retainer so next year's filing is contemporaneous, not reconstructed under pressure again. | Treating the completed audit as the end of the engagement, rather than the start of an ongoing documentation discipline, is the most common reason the same weaknesses resurface in the next review cycle. |
Drafting the response narrative before the underlying financial and transactional evidence has been fully assembled and reconciled, producing a narrative the evidence does not fully support once gaps are found later
Submitting an existing Local File unchanged because it exists, without checking whether the transaction values, entities, or FAR profile it describes still match the year actually under review
Treating every FTA information request the same way regardless of its stated scope, and missing that the actual request is narrower — or broader — than assumed
Waiting for full internal review and sign-off to conclude before engaging PNPC or beginning documentation assembly, compressing the response window unnecessarily
Producing a benchmarking analysis without a documented screening and rejection trail for the comparable set, leaving the reviewer unable to see how the accepted comparables were chosen
Addressing the headline related-party transactions while leaving Connected Person payments — owner remuneration, director rent, shareholder loan interest — unaddressed because they were originally booked as ordinary payroll or overheads
Failing to check the Qualifying Free Zone Person exposure separately before responding, when a Free Zone entity's related-party pricing is part of what is under review
Assuming a global or India-side transfer pricing study automatically covers the UAE position, without a UAE-specific FAR analysis and benchmarking reconciled to UAE figures
Submitting figures that do not reconcile line-by-line to the Related Party Transactions disclosure form and the audited financial statements already on file
Attaching documents without a covering narrative that walks the FTA reviewer through the FAR analysis and method rationale, leaving the reviewer to draw unassisted conclusions
Filing a reconsideration request that resubmits the same original documentation rather than building a standalone submission with fresh economic grounding for why the adjustment should not stand
Missing the reconsideration request window because the internal decision on whether to contest was not made in time
What triggers an FTA transfer pricing audit or information request?
Common triggers include an inconsistency between the Related Party Transactions disclosure figures and the audited financial statements, a related-party or connected-person transaction value that appears disproportionate to the entity's size or function, a Qualifying Free Zone Person whose related-party dealings are being checked for arm's length compliance, or simply routine risk-based selection as part of the FTA's broader Corporate Tax compliance programme. The specific trigger is not always disclosed in the request itself.
How much time do we typically have to respond to an FTA transfer pricing information request?
The FTA generally sets a stipulated period for producing a Local File or Master File on request — commonly around 30 days, though the exact window is stated in the specific request and can vary. Desk review queries and full audit timelines can differ from this. The response deadline stated in the actual notice governs, not a general assumption carried over from a different engagement.
We already have a Local File — can we just hand it over as-is?
Only after it has been checked against the specific request and the current facts. A Local File prepared a year or more ago may reference transaction values, entities, or a FAR profile that has since moved, and producing an outdated file without review can create a new inconsistency rather than resolve the FTA's query. PNPC always stress-tests existing documentation before it goes to the FTA, even where PNPC originally prepared it.
We don't have proper transfer pricing documentation at all — can it still be produced in time?
It depends on how much underlying data — ledgers, agreements, financial statements — is readily available, and how compressed the FTA's deadline is. PNPC prioritises live audit engagements and moves as quickly as the facts allow, but a genuine first-time build under audit pressure is a materially harder and more constrained exercise than the same build with no deadline, because comparable data availability and FAR interviews cannot always be rushed without weakening the result.
What happens if we miss the FTA's response deadline?
Missing the stipulated response period can itself be treated as non-compliance, separate from and in addition to any substantive finding on the transfer pricing position itself, and can expose the taxable person to administrative penalties. It can also affect how the FTA weighs the eventual submission once it does arrive. PNPC treats the deadline as a hard constraint from day one of any audit support engagement.
The FTA has queried our Related Party Transactions disclosure figure specifically — is this a full audit?
Not necessarily. A desk-based query on a single disclosure figure is often narrower than a full Corporate Tax audit, and can sometimes be resolved with a focused reconciliation showing how the figure was derived and how it ties to the financial statements. It can, however, escalate into a broader review if the response raises further questions, so PNPC treats even a narrow query with the same rigour as a full audit response.
Can PNPC take over an audit response even though a different advisor prepared our original transfer pricing documentation?
Yes. PNPC regularly steps into audit support where another firm, or an in-house team, prepared the original Local File, Master File, or benchmarking study. We review the existing work on its own merits, identify what holds up and what does not, and build the audit response from that assessment rather than assuming the prior work is either entirely sound or entirely inadequate.
What is a proposed transfer pricing adjustment, and does it mean we automatically owe more tax?
A proposed adjustment is the FTA's determination that a related-party or connected-person transaction was not priced at arm's length, and its recalculation of what the taxable income would have been on an arm's length basis. It is a proposal, not a final, unchallengeable outcome — the taxable person can respond with a reconsideration request backed by technical and economic analysis before it becomes final, or, where the merits support it, accept the adjustment and the resulting additional tax, penalties and interest.
How does PNPC decide whether to contest a proposed adjustment or recommend accepting it?
We assess the technical merits independently — whether the FAR analysis, method selection, and comparable set underlying the original pricing genuinely support an arm's length conclusion, and whether the FTA's own basis for the adjustment has a defensible flaw. This is a case-by-case judgement, not a default posture of contesting everything or accepting everything, and we give the client a clear, reasoned recommendation either way.
Can a UAE transfer pricing adjustment lead to double taxation with another country?
Yes, in principle. If the FTA increases UAE taxable income through a transfer pricing adjustment but the counterparty jurisdiction does not make a corresponding downward adjustment for the same transaction, the group can face the same profit taxed twice. Where the UAE has a Double Taxation Avoidance Agreement with the counterparty's jurisdiction, a Mutual Agreement Procedure (MAP) request can be pursued between the two tax authorities — a formal, longer process, but a genuine remedy.
Does an FTA transfer pricing audit affect our Qualifying Free Zone Person status?
It can, if the entity under review is a Qualifying Free Zone Person and the audit finds that related-party pricing was not arm's length in a way that pushes non-qualifying revenue past the permitted de minimis threshold for Qualifying Income. PNPC treats this QFZP interaction as a distinct checkpoint within any audit response involving a Free Zone entity, because the consequence — losing the 0% rate — is disproportionate to the transfer pricing adjustment amount itself.
How does PNPC handle Connected Person payments — owner salary, director rent, shareholder loans — during an audit?
These are frequently the weakest point in an existing file because they were originally categorised as ordinary payroll or overheads rather than benchmarked under Article 36. During audit support, PNPC independently checks whether owner and director remuneration, related-party rent, and shareholder loan interest have a defensible market benchmark on file, and builds one where none exists.
What does PNPC actually produce in an audit response?
Depending on the request, this can include the Local File and/or Master File itself, a benchmarking study with its full screening and rejection trail, a FAR analysis narrative, a reconciliation of the disclosed figures to the audited financial statements, and a covering narrative explaining the pricing approach for the FTA reviewer — assembled and submitted within the stipulated deadline, with the correspondence trail retained.
Can this engagement be handled entirely remotely, given the tight deadlines?
Yes. Audit support is a documentation, analysis and correspondence exercise — there is no physical-presence or biometric step. Almost all of it is delivered through document exchange, video calls with finance and operations leads to confirm the FAR narrative, and EmaraTax or direct FTA correspondence. The binding constraint is timely access to records and to people who can explain what each entity actually does, not geography.
Does PNPC coordinate with our India transfer pricing advisor if the audit touches an India-UAE related party?
Yes. Where a UAE audit response touches a transaction with an Indian related party, PNPC's India and Dubai desks coordinate so the UAE audit response and any parallel Indian transfer pricing position — under Section 92 to 92F of the Income-tax Act — tell a consistent story, rather than the two jurisdictions' filings inadvertently contradicting each other.
How is TP Audit Support priced, given the urgency involved?
PNPC scopes a fee based on the complexity of the request, the state of existing documentation, and the deadline pressure involved — agreed as quickly as the urgency allows, typically within the first day or two of engagement, so there is no delay to actual work starting. Live audit engagements are prioritised operationally ahead of routine advisory work once a stipulated FTA deadline is confirmed.
Should we tell PNPC as soon as we receive an FTA request, or wait until we've reviewed it internally first?
As soon as possible. The stipulated response window starts running from the date of the FTA's request, not from whenever the internal review concludes, and the first few days are often the most valuable for confirming scope and beginning documentation assembly. Waiting to fully understand the request internally before engaging PNPC typically compresses the available response time unnecessarily.
What if the FTA's audit uncovers issues beyond transfer pricing — VAT, Corporate Tax computation errors, or other compliance gaps?
PNPC's transfer pricing audit support is scoped specifically around the related-party and connected-person pricing dimension of an audit. Where a broader Corporate Tax or VAT audit surfaces other issues, PNPC's wider tax and compliance teams can be engaged alongside the transfer pricing desk so the full audit is handled coherently rather than in disconnected pieces.
Is a reconsideration request the same as a formal tax appeal or litigation?
No. A reconsideration request is an administrative step asking the FTA itself to review its own determination, generally submitted within a specific window after a decision or adjustment is issued. It sits before, and is distinct from, any formal escalation through the Tax Disputes Resolution Committee or the courts, which involves a different process and typically legal counsel rather than a CA-led response.
We found a pricing or disclosure error ourselves, before the FTA raised anything — should we voluntarily disclose it?
Often yes, though it is a case-by-case judgement. Coming forward with a voluntary disclosure once a genuine error is identified is generally viewed more favourably than the same error being found later by the FTA, and it puts the taxable person in control of the narrative and the corrected figures rather than reacting to an FTA-initiated review. PNPC assesses the technical position and the financial impact first, then works with the client on whether voluntary disclosure is the proportionate response or whether continued monitoring is sufficient for an immaterial matter.
More than one entity in our group has received an FTA information request around the same time — do we need separate engagements for each?
Not necessarily separate engagements, but the responses need to be coordinated even if each entity technically responds on its own. PNPC builds a single group-level factual and FAR narrative that every entity's individual response draws from consistently, so the same intercompany transaction is not described differently by two entities answering two different FTA requests.
Can an FTA transfer pricing audit cover more than one financial year at once?
Yes. An information request or audit notice can specify a single year or a range of years, and the scope stated in the FTA's own request governs. Where multiple years are in scope, PNPC checks whether the group's FAR profile, related-party structure or pricing approach changed across those years, since a single narrative that assumes no change across several years is itself a common weakness if the underlying facts actually moved.
Does a transfer pricing audit ever spill over into our VAT position?
It can, though the two are assessed under separate legal frameworks — VAT under Federal Decree-Law No. 8 of 2017, and Corporate Tax transfer pricing under Federal Decree-Law No. 47 of 2022. Where an intercompany transaction under TP review also carries a VAT treatment — a management fee, an intercompany sale — an inconsistency between the value used for VAT and the value used for Corporate Tax arm's length purposes can itself draw the FTA's attention across both regimes.
Will PNPC represent us in a direct meeting with FTA officers, or is this all handled through written correspondence?
Both, depending on how the FTA chooses to run the specific request or audit. Much of transfer pricing audit support is written correspondence and document submission through the FTA's channels, but where the FTA requests a meeting or clarification call, PNPC represents the client directly, prepared with the same technical rigour as the written submission.
What if management and finance disagree internally about whether to contest a proposed adjustment?
This happens, and PNPC's role is to give both sides the same independent, technical assessment of the merits so the decision is made on the evidence rather than on differing internal instincts. We lay out the strength of the technical position, the likely cost and timeline of contesting versus accepting, and let the client's own decision-makers reach a final call informed by that analysis.
What if a transaction we treated as unrelated-party turns out to actually be with a related party — common ownership we didn't identify?
This is more common than it sounds, particularly in groups with informal or evolving ownership structures. If PNPC's review during audit support identifies a previously unrecognised related-party relationship, we reassess the transaction under Article 34 immediately, since treating it as unrelated when it is not is itself a disclosure gap independent of whether the pricing was actually reasonable.
Is a Free Zone entity treated differently from a mainland entity during an FTA transfer pricing audit?
The arm's length standard under Article 34 applies identically regardless of whether the entity is mainland or Free Zone — there is no lighter or heavier substantive test for either. What differs is the additional consequence layered on top for a Free Zone entity: where the entity is a Qualifying Free Zone Person, the audit outcome also has to be assessed against whether it affects the entity's Qualifying Income position and its continued eligibility for the 0% rate, a consideration that simply does not arise for a mainland entity taxed at the standard rate.
What if the FTA's information request or correspondence is issued in Arabic only?
PNPC works in both English and Arabic and can prepare and review the response in either language as the specific request requires. Where a request or notice is in Arabic, we ensure the scope and deadline are understood precisely before drafting begins, rather than working from an informal translation that may miss a technical distinction.
Can we ask the FTA for more time to respond to an information request?
It is possible to request an extension, though it is granted at the FTA's discretion and is not guaranteed. PNPC assesses, on a case-by-case basis, whether requesting more time is worthwhile given the specific circumstances, or whether it is more effective to submit the strongest possible response within the original window, potentially supplemented with a follow-up once further information is available.
Once a reconsideration request is submitted, how does the process play out from there?
The FTA reviews the reconsideration request and the supporting technical and economic analysis, and issues its own determination on whether the original position is upheld, varied, or overturned. If the taxable person remains unsatisfied with that determination, the further, more formal escalation route is through the Tax Disputes Resolution Committee or the courts, which is a distinct legal process typically requiring legal counsel.
If we accept a proposed transfer pricing adjustment for one year, does that create a precedent for future years?
It can influence how the FTA and the taxable person's own advisors approach the same recurring transaction in later years, even though each year is technically assessed on its own facts. PNPC weighs this precedent effect explicitly as part of the contest-or-accept recommendation — accepting an adjustment on a genuinely weak position may be the right call for that year, but the group should go into that decision aware it may shape how the same transaction type is viewed going forward.
If the matter escalates beyond FTA reconsideration to the Tax Disputes Resolution Committee, does PNPC charge separately for that?
Escalation beyond FTA reconsideration into formal dispute resolution is a distinct legal process, typically led by legal counsel with PNPC continuing to support the underlying technical transfer pricing analysis. This is scoped and priced as a separate stage from the original audit support engagement, since it is a materially different type of work with a different professional lead.
What is literally the first thing PNPC does when we bring you in partway through an active FTA audit?
We read the FTA's actual request or notice in full — the specific transactions, years and deadline referenced — before looking at anything else, including whatever internal response work may already be underway. Confirming the real scope and deadline first prevents effort being spent on a response built against an assumed scope that turns out to be wrong.
Can a transfer pricing audit trigger a wider review of Corporate Tax items unrelated to related-party pricing?
It can, if something surfaces during the FTA's review that raises a separate question — an inconsistency in the general Corporate Tax computation, for example, unrelated to the transfer pricing point originally under review. PNPC's engagement is scoped around the transfer pricing dimension specifically, but we flag promptly if the audit appears to be widening into other areas so the client can bring in the right additional specialists without delay.
How does PNPC keep sensitive intercompany financial data confidential during an audit response?
Audit support involves handling commercially sensitive information — intercompany pricing, margins, ownership structures — and PNPC treats it with the same confidentiality standard applied across all client engagements, sharing it only as far as the FTA's specific request requires and only through the appropriate FTA channels.
What if the comparables used in our original benchmarking study no longer exist or have changed industry — does that undermine our position?
It can weaken a study if left unaddressed, since a comparable set built years ago can genuinely go stale as individual comparable companies cease trading, change activity, or are acquired. As part of audit support, PNPC checks whether the original comparable set is still valid for the year under review and, where it is not, refreshes the screening rather than defending a comparable set that no longer reflects genuinely independent, functionally similar businesses.
Does a proposed transfer pricing adjustment automatically come with a penalty, or just additional tax?
A proposed adjustment itself is a recalculation of taxable income; whether administrative penalties also apply depends on the circumstances — including whether documentation was maintained and produced as required, and whether the position taken had a reasonable technical basis. PNPC assesses penalty exposure as part of the overall response, since the penalty question is a separate analysis from the underlying tax adjustment itself.
An FTA information request just landed today — what should we do internally before PNPC is even engaged?
Preserve the request exactly as received, note the stated deadline precisely, avoid responding informally or partially to the FTA before a full response is ready, and gather whoever internally can quickly locate the underlying financial records and existing transfer pricing documentation, if any. The single most useful thing management can do is get PNPC the actual request document as early as possible rather than a summary of it.
PNPC TP audit support vs. a generic response prepared without specialist transfer pricing input
| Dimension | PNPC | Generic / Unsupported Response |
|---|---|---|
| Initial triage | FTA request scope and deadline confirmed precisely before any drafting begins | Response drafted against an assumed scope, risking a mismatched or incomplete submission |
| Existing documentation review | Stress-tested against the current facts and the specific request, regardless of who originally prepared it | Produced as-is without checking whether it still reflects current transaction values or structure |
| Benchmarking under deadline pressure | Documented, defensible screening methodology maintained even on a compressed timeline | Rushed comparable set assembled with limited or no screening trail |
| Connected Person exposure | Owner, director and shareholder-loan payments independently benchmarked as part of the response | Often left unaddressed, treated as ordinary payroll or overheads |
| QFZP interaction | Explicit checkpoint on whether the audit outcome threatens Qualifying Income or 0% status | Rarely assessed as a distinct risk within the audit response |
| Reconciliation discipline | Every figure produced traced line-by-line to the disclosure form and audited financial statements | Figures produced independently, risking a new inconsistency mid-audit |
| Adjustment response | Case-by-case technical assessment of whether to contest or accept, backed by economic analysis | Default posture of either accepting everything or contesting everything without technical grounding |
| Cross-border coordination | India-UAE (and other jurisdiction) positions kept consistent where the group spans both | Single-jurisdiction response with no check against a parallel foreign filing |
| Post-audit remediation | Root documentation gaps fixed for future years, feeding into an ongoing annual retainer | Audit closed with no follow-through, leaving the same weaknesses for the next cycle |
| Multi-entity coordination | Single group-level narrative maintained across every entity facing an overlapping request | Each entity's response drafted independently, risking inconsistent descriptions of the same transaction |
| Voluntary disclosure judgement | Proactively assessed where PNPC's own review surfaces an error before the FTA does | Errors typically surface only once the FTA raises them, foreclosing the more favourable voluntary route |
| Continuity after audit closure | Annual retainer proposed immediately, keeping documentation contemporaneous going forward | Engagement ends at audit closure, with no structured follow-through into the next filing cycle |
- 01
Immediate triage of the FTA's request, deadline, and scope
- 02
Independent stress-test of any existing Local File, Master File, or benchmarking study
- 03
Rapid, defensible documentation reconstruction where no adequate file exists
- 04
Reconciliation of all figures to the Related Party Transactions disclosure form and audited financial statements
- 05
Connected Person payment benchmarking — owner/director remuneration, related-party rent, shareholder loan interest
- 06
Qualifying Free Zone Person exposure assessment where a Free Zone entity is involved
- 07
Drafted covering narrative and full response package submitted within the stipulated FTA deadline
- 08
Management of FTA follow-up queries through to resolution
- 09
Technical assessment of any proposed adjustment, with a clear contest-or-accept recommendation
- 10
Formal reconsideration request preparation, backed by economic analysis, where the merits support it
- 11
Mutual Agreement Procedure eligibility assessment where double taxation risk arises with a treaty partner jurisdiction
- 12
India-UAE coordinated response where the group has related parties spanning both jurisdictions
- 13
Post-audit remediation plan feeding into the ongoing annual transfer pricing documentation retainer
- 14
Direct engagement with the FTA on technical merits throughout the query or audit lifecycle
If an FTA request or audit notice has already landed, the clock is running — speak to PNPC's Dubai transfer pricing desk today, not after the internal review is complete.
Jurisdiction
Free zone, mainland & offshore
Ready to get started?
Tell us about your requirement — a UAE specialist responds within 24 hours.