UAE Taxation & Regulatory Compliance · Transfer Pricing
Transfer Pricing Disclosure Form (TPDF) Filing
The Related Party Transactions disclosure form is the schedule most UAE taxable persons meet first on the transfer pricing spectrum — filed with every Corporate Tax return via EmaraTax the moment related-party or connected-person transactions cross the disclosure threshold, whether or not a Local File or Master File is ever required.
Chartered Accountants · Dubai · Since 1986
The Related Party Transactions disclosure form (commonly referred to as the TPDF, or Transfer Pricing Disclosure Form) is a schedule filed alongside the UAE Corporate Tax return on the Federal Tax Authority's EmaraTax portal, disclosing a taxable person's transactions and arrangements with Related Parties and payments or benefits provided to Connected Persons for the relevant tax period. It is the broadest and most frequently triggered of the UAE's transfer pricing compliance obligations under Federal Decree-Law No. 47 of 2022 and its implementing Ministerial Decision No. 97 of 2023 — reaching far more taxable persons than the Local File or Master File requirements, because the disclosure obligation engages once related-party or connected-person transaction values cross the prescribed threshold, independent of whether the taxable person also meets the higher revenue thresholds that trigger full documentation.
The form itself is structured around the categories the FTA needs to assess transfer pricing risk at a portfolio level: related-party transactions broken out by counterparty and by type (sale and purchase of goods, provision or receipt of services, royalties and licence fees, intercompany financing, and other arrangements), and Connected Person payments — owner and director remuneration, rent paid to a related landlord, and interest on shareholder loans, among others captured under Article 36. Every figure disclosed is expected to be internally consistent with the audited or management financial statements for the same period, and where a Local File exists, consistent with that document's transaction detail and benchmarking conclusions as well. The FTA's own Transfer Pricing Guide (CTGTP1) is explicit that the disclosure form is not an isolated filing exercise — it is read alongside the Corporate Tax return, and where applicable the Local File, Master File and CbCR, as part of a single risk-assessment picture for the taxable person.
What makes the TPDF deceptively easy to get wrong is precisely that it looks like a simple compliance schedule rather than an analytical exercise. A taxable person can correctly conclude it has no obligation to build a Local File or Master File — because its related-party transaction values or group revenue sit below those higher thresholds — and still owe a fully populated, accurate disclosure form because the lower disclosure threshold under Ministerial Decision No. 97 of 2023 has been crossed. Equally common is the opposite gap: a finance team files a Corporate Tax return believing there is nothing to disclose because 'we have no foreign related parties,' when in fact two UAE mainland entities under common family ownership, or a mainland trading company and its own Free Zone affiliate, are related parties under Article 35 regardless of geography — and owner remuneration or director-owned premises rent is a Connected Person payment under Article 36 that belongs on the same schedule, not filed away as ordinary payroll or overheads.
PNPC treats TPDF preparation as the reconciled output of a proper related-party and connected-person mapping exercise, not a form-filling task performed in isolation from the rest of the transfer pricing picture. We identify every related party and connected person against the actual ownership and control chain, catalogue every intercompany flow and Connected Person payment for the period, screen the totals against the current disclosure threshold, and only then populate the EmaraTax schedule — with every figure traced back to the audited financial statements line by line before submission, and cross-checked against any existing Local File so the two documents tell the same story if the FTA ever reads them together.
When a Related Party Transactions disclosure form is due
The taxable person has related-party transactions — with a foreign parent, subsidiary, sister company, or a UAE group entity under common ownership including a mainland-Free Zone pairing — above the disclosure threshold prescribed under Ministerial Decision No. 97 of 2023
Owners, directors, officers or their relatives receive salary, rent, or loan interest from the company that qualifies as a Connected Person payment under Article 36, above the applicable disclosure threshold
The Corporate Tax return for the period is being prepared and the taxable person has not yet confirmed whether its related-party or connected-person transaction values cross the disclosure threshold for the year
The business sits below the Local File and Master File thresholds but still has related-party dealings that need to be correctly identified, valued, and disclosed — the TPDF obligation is independent of the higher documentation thresholds
A Local File or benchmarking study already exists and the disclosure form figures need to be reconciled to it, so the schedule and the underlying study are internally consistent
Prior-year disclosure forms were filed without a clear related-party mapping behind them, and the current year's filing needs to be built on a properly verified list rather than repeating an unverified prior position
A new intercompany arrangement — a management fee, cost-sharing agreement, royalty, or shareholder loan — started during the period and needs to be captured correctly on this year's schedule
Group restructuring, a new subsidiary, or a mainland-to-Free-Zone conversion has changed who counts as a related party or connected person since the last filing, and the disclosure needs to reflect the current-year position
The taxable person wants confirmation, before filing, of exactly which transaction categories and Connected Person payments must appear on the schedule so the return is not filed with an incomplete or inaccurate disclosure
When TPDF filing is not the immediate need
The taxable person has genuinely no related-party or connected-person transactions for the period — the disclosure obligation only engages where a qualifying relationship and transaction exist in the first place
Related-party and connected-person transaction values sit clearly and comfortably below the prescribed disclosure threshold — worth a short confirmatory review rather than a full filing exercise, though PNPC recommends verifying this rather than assuming it
The entity is an Exempt Person under the Corporate Tax Law or otherwise confirmed outside its scope, subject to the exemption conditions continuing to hold and being re-verified periodically
The real need is a full Local File and Master File build because the group meets the higher documentation thresholds — that is a broader, separate engagement PNPC also provides, of which the reconciled disclosure form is one output, not the whole scope
The pressing question is whether the related-party pricing itself is arm's length and defensible, rather than how to complete the disclosure schedule — that is upstream transfer pricing advisory and benchmarking work, not a filing exercise
Audited financial statements for the period are not yet finalised — disclosure figures must reconcile to final numbers, so it is generally more efficient to prepare the schedule once accounts are closed rather than against provisional figures that will move
The client wants the disclosed figures adjusted to a predetermined tax outcome rather than an accurate reflection of the actual related-party and connected-person transactions for the period — the form reports what happened, it does not manage a tax result
TPDF disclosure obligation by taxable person profile
| Profile | TPDF Filing Required | Local File Required | Master File Required | Typical Trigger |
|---|---|---|---|---|
| Standalone UAE business, no related parties or connected persons | No | No | No | No qualifying relationship exists under Article 35 or 36 at all |
| UAE business with related-party or Connected Person transactions below disclosure threshold | No (monitor annually) | No | No | Transaction values have not yet crossed the Ministerial Decision No. 97 of 2023 disclosure threshold |
| UAE business with related-party or Connected Person transactions above disclosure threshold, below Local File threshold | Yes | No | No | Most common profile — related-party dealings or owner/director payments exceed the disclosure threshold without the group meeting the higher revenue thresholds |
| UAE entity meeting standalone revenue threshold or in-scope MNE Group member | Yes | Yes | Yes (if MNE Group threshold also met) | Related-party transaction values and/or group revenue cross the Local File / Master File thresholds |
| UAE Free Zone entity (including Qualifying Free Zone Person) with related-party dealings | Yes, same as any taxable person | Yes, if thresholds met — status does not exempt from disclosure | Yes, if group threshold met | Free Zone status affects the tax rate, not whether the disclosure or documentation obligations apply |
| UAE subsidiary of a foreign MNE Group, related-party flows with the foreign parent only | Yes | Depends on thresholds — UAE-specific Local File cannot rely solely on a foreign group file | Often adapted from an existing group Master File where the threshold is met | Cross-border related-party transactions with the parent or sister entities |
The disclosure threshold under Ministerial Decision No. 97 of 2023 is materially lower than the Local File and Master File thresholds — a taxable person can owe a fully populated TPDF while having no obligation to build the heavier documentation at all. PNPC confirms which row applies to your structure during the initial scoping call against the current thresholds rather than inferring it from business size.
| Stage | What Happens | Who Acts | Typical Output |
|---|---|---|---|
| Related-Party & Connected-Person Confirmation | Every related entity and connected individual is identified against the actual ownership and control chain under Articles 35 and 36, not taken from a self-declared list | PNPC, working from the group ownership chart, shareholder registers and director details supplied by the client | A confirmed related-party and Connected Person list for the tax period, in writing |
| Transaction & Payment Inventory | Every intercompany flow (goods, services, management fees, royalties, loans) and every Connected Person payment (remuneration, rent, loan interest) for the period is catalogued by counterparty and category | PNPC, drawing on the trial balance, general ledger, payroll records and lease agreements | A complete transaction and payment inventory for the disclosure period |
| Threshold Screening | Catalogued transactions and payments are screened, individually and in aggregate by category, against the current disclosure threshold under Ministerial Decision No. 97 of 2023 | PNPC | Confirmation of which transaction categories and Connected Person payments must be disclosed |
| Reconciliation to Financial Statements | Every figure destined for the disclosure schedule is traced to the audited or management financial statements for the period, line by line | PNPC, cross-referencing the ledger and the accounts | A reconciliation working paper tying each disclosed figure to its source in the accounts |
| Cross-Check Against Local File (Where One Exists) | Where a Local File or benchmarking study has already been prepared, the disclosure figures are checked against its transaction detail and conclusions for internal consistency | PNPC | A confirmed alignment, or a flagged discrepancy resolved before filing |
| Connected Person Detail Verification | Owner and director remuneration, related-party rent, and shareholder loan interest are individually verified for correct classification and value under Article 36 | PNPC, with input from payroll and the client's finance team | A verified Connected Person schedule ready for the disclosure form |
| TPDF Population on EmaraTax | The Related Party Transactions disclosure schedule is populated within the Corporate Tax return workflow on EmaraTax, category by category and counterparty by counterparty | PNPC, using the client's EmaraTax credentials or acting as authorised tax agent | A completed, internally reconciled disclosure schedule ready for review |
| Internal Review Before Submission | A senior reviewer independent of the original preparer checks the populated schedule against the reconciliation working papers before the return is finalised | PNPC senior reviewer | A reviewed, sign-off-ready disclosure form |
| Filing With the Corporate Tax Return | The disclosure form is submitted on EmaraTax as part of the Corporate Tax return for the period | Client (or PNPC as authorised tax agent) via EmaraTax | A filed TPDF, timestamped and retained in the EmaraTax submission history |
| Retention & Next-Cycle Setup | The final schedule, reconciliation working papers and supporting evidence are retained, and the related-party map is carried forward as the starting point for next year's filing | PNPC | An indexed retention file and a following-year disclosure calendar entry |
For a taxable person with an already-verified related-party map and reasonably organised records, TPDF preparation and filing typically runs a matter of weeks, aligned to the Corporate Tax return due date. First-time engagements take longer because the related-party and Connected Person mapping has to be built from scratch rather than confirmed and carried forward.
Group organisational chart showing every entity, ownership percentage, and country of incorporation or tax residence
UAE trade licence(s) for the taxable person and every related UAE entity, including Free Zone entities with the specific Free Zone authority named
Shareholder registers or equivalent evidence of ownership, needed to confirm related-party status against Article 35 thresholds
Details of directors, officers and their close family relationships relevant to Connected Person status under Article 36
Audited or management financial statements for the relevant tax period
Corporate Tax Registration Number (TRN) for the taxable person
Prior-year disclosure forms already filed, for continuity and comparison
Trial balance or general ledger extract isolating related-party and Connected Person transaction values by counterparty and category
Intercompany agreements — management service agreements, distribution or supply agreements, royalty or licence agreements, intercompany loan agreements, where they exist
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, and tenure
Any existing Local File or benchmarking study covering the same transactions, for reconciliation
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 board resolutions or minutes authorising Connected Person payments during the period
Foreign-currency conversion methodology used for any related-party transaction not denominated in AED
Rounding and netting conventions applied consistently across ledger, accounts and disclosure figures
EmaraTax access credentials or authorised tax agent appointment, for portal filing
Corporate Tax return draft or filing timeline, so disclosure preparation is scheduled against the actual due date
| Phase | Triggered By | PNPC Guidance | Risk If Ignored |
|---|---|---|---|
| Initial Threshold Confirmation | First Corporate Tax registration, or first related-party or Connected Person transaction identified | Confirm whether related-party and Connected Person transaction values cross the disclosure threshold, independent of whether Local File or Master File thresholds are met — the TPDF obligation is the broader, more commonly triggered one. | Assuming that falling below the Local File threshold also means no disclosure is due conflates two different thresholds and can leave a genuine TPDF obligation unfiled. |
| Annual Related-Party & Connected-Person Refresh | Each tax period approaching its Corporate Tax return due date | Re-run the related-party and Connected Person mapping every year rather than carrying forward last year's list unchanged — new arrangements, changed ownership, or a new director all shift who and what belongs on the schedule. | A stale related-party list means new intercompany flows or Connected Person payments go undisclosed, compounding the exposure with each additional year they are missed. |
| Reconciliation Before Filing | Financial statements finalised and the disclosure schedule ready for population | Trace every disclosed figure to the audited or management accounts line by line before submission, and check against any existing Local File for consistency. | A disclosure form that does not reconcile to the accounts is one of the most common, and most avoidable, triggers for an FTA follow-up query. |
| Filing With the Corporate Tax Return | Corporate Tax return due date approaching | File the TPDF as an integrated part of the return on EmaraTax, not as an afterthought once the return itself is otherwise complete. | A late or incomplete disclosure filed alongside an otherwise timely Corporate Tax return still exposes the taxable person to disclosure-specific compliance risk. |
| FTA Query on Disclosed Figures | FTA raises a question about a specific related-party transaction or Connected Person payment referenced in the filed disclosure | Respond with the underlying reconciliation working papers and, where one exists, the supporting Local File or benchmarking analysis — not just the figure as filed. | A disclosure figure with no supporting working paper behind it is difficult to explain convincingly once queried, even where the original figure was correct. |
| Threshold or Group Structure Change | M&A, new subsidiary, mainland-to-Free-Zone conversion, or a change in directors or ownership | Re-test the related-party and Connected Person position whenever the structure changes materially, rather than waiting for the next annual filing cycle to catch it. | An outdated related-party map means new obligations go unrecognised until the next filing, by which point a period may already have passed without proper disclosure. |
| Escalation to Local File / Master File Threshold | Related-party transaction values or group revenue grow past the higher documentation thresholds | Flag proactively when a taxable person's growth trajectory suggests it may cross into Local File or Master File territory in an upcoming period, so the heavier documentation is scoped ahead of time rather than discovered at filing. | Discovering mid-filing-season that a Local File is now required, with no benchmarking study in place, compresses the available preparation time significantly. |
What exactly is the TPDF, and how is it different from a Local File?
The TPDF (Transfer Pricing Disclosure Form), formally the Related Party Transactions disclosure schedule, is filed with every Corporate Tax return on EmaraTax once related-party or Connected Person transaction values cross the disclosure threshold under Ministerial Decision No. 97 of 2023. It summarises transactions by category and counterparty. A Local File is a much more detailed, entity-specific document — business description, FAR analysis, method selection, benchmarking — required only once higher revenue thresholds are met, and produced to the FTA on request rather than filed with the return.
Who has to file the TPDF?
Any UAE taxable person with related-party transactions or Connected Person payments that cross the disclosure threshold prescribed under Ministerial Decision No. 97 of 2023, for the relevant tax period — regardless of whether the taxable person also meets the separate, higher thresholds for Local File or Master File preparation. This threshold is materially lower and catches far more UAE businesses than the documentation thresholds.
We only transact between UAE entities under common family ownership. Do we still need to file?
Yes, if those entities are related parties under Article 35 — which turns on ownership and control thresholds, not on whether a border was crossed. Two mainland companies, or a mainland entity and its own Free Zone affiliate, under common family control are related parties for Corporate Tax purposes, and their intercompany dealings are disclosable once they cross the threshold, exactly as a cross-border related-party transaction would be.
Does owner or director salary need to be disclosed on the TPDF?
Yes, if it qualifies as a Connected Person payment under Article 36 and crosses the applicable disclosure threshold. Owners, directors, officers and their relatives are Connected Persons, and payments to them — salary, benefits-in-kind, rent on premises they personally own, interest on loans they have advanced to the company — belong on the disclosure schedule, separate from ordinary third-party payroll.
What categories of transaction actually appear on the disclosure form?
Broadly: sale and purchase of goods with related parties, provision or receipt of services, royalties and licence fees, intercompany financing (loans, guarantees, interest), other intercompany arrangements such as cost-sharing, and Connected Person payments captured separately under Article 36. The exact categorisation and required detail follow the EmaraTax Corporate Tax return workflow and current FTA guidance.
Do our disclosed figures need to reconcile exactly to the audited financial statements?
Yes. Every figure on the TPDF should trace back to the audited or management financial statements for the same period. A mismatch — whether from netting intercompany balances differently, using a different exchange rate, or simply an unreconciled figure — is one of the most common triggers for an FTA follow-up query, even where the underlying transaction was entirely legitimate.
We already have a Local File. Does that mean the TPDF is automatically correct?
Not automatically — the two should be consistent, but the disclosure form is populated and filed separately with the Corporate Tax return, and it is the taxable person's responsibility to ensure the figures match. PNPC cross-checks the disclosure schedule against the Local File's transaction detail as a standard step, precisely because the two documents being prepared independently, even by the same advisor, can otherwise drift apart.
What if we are below the Local File threshold but still have related-party transactions?
You very likely still owe a TPDF. The disclosure threshold under Ministerial Decision No. 97 of 2023 is materially lower than the Local File and Master File thresholds, so a taxable person can have a full disclosure obligation while having no requirement to build the heavier documentation at all. This is, in fact, the most common profile PNPC sees.
How does PNPC identify every related party correctly?
We do not rely on a client's self-declared list. We map the actual ownership and control chain against Article 35's definitions — shareholder registers, group organisational charts, and where relevant, indirect ownership through common shareholders or family control — and separately identify Connected Persons under Article 36 from director registers and known family relationships. Only once that map is confirmed do we screen transactions for disclosure.
What happens if the FTA queries a figure on our filed disclosure form?
The FTA can request supporting detail or clarification for any disclosed related-party transaction or Connected Person payment. Having a reconciliation working paper — tracing the figure to the ledger and the accounts, and where relevant to a Local File's benchmarking conclusion — is what allows a query to be answered quickly and credibly, rather than triggering a broader review of the entire filing.
Is there a penalty for an inaccurate or incomplete disclosure form?
The Federal Tax Procedures Law (Federal Decree-Law No. 28 of 2022, as amended) and its implementing Cabinet Decisions on administrative penalties set the general penalty framework for tax non-compliance, which extends to incorrect or incomplete Corporate Tax return schedules including the related-party disclosure. Because exact administrative penalty amounts are fixed by Cabinet Decision and can be revised, PNPC confirms the current schedule with clients rather than quoting a figure that may be outdated.
Can PNPC file the TPDF on our behalf as authorised tax agent?
Yes. PNPC can act as authorised tax agent on EmaraTax and file the Corporate Tax return, including the related-party disclosure schedule, directly, or prepare the reconciled schedule for the client's own finance team to submit under their own EmaraTax credentials — whichever the client prefers.
Our related-party transactions are in a foreign currency. How is that handled on the disclosure form?
Corporate Tax computations and related-party disclosures are ultimately expressed in AED, so foreign-currency related-party transactions need converting using a consistently applied exchange rate methodology. PNPC documents the conversion approach used and applies it uniformly across the ledger, the accounts and the disclosure figures, so the three do not diverge from using different rates in different places.
How long does TPDF preparation typically take?
For a taxable person with an already-verified related-party map and reasonably organised financial records, disclosure preparation and filing typically takes a matter of weeks, timed to the Corporate Tax return due date. A first-time engagement, where the related-party and Connected Person mapping has to be built from scratch, takes longer — the mapping and reconciliation work, not the form itself, is the time-consuming part.
If this is our first year filing a Corporate Tax return, is the TPDF also new for us?
Yes, for most taxable persons — the disclosure obligation runs alongside the Corporate Tax return itself, so a first-time Corporate Tax filer with related-party or Connected Person transactions above the disclosure threshold is filing the TPDF for the first time in the same cycle. PNPC treats first-year engagements as requiring the full related-party mapping exercise before any figures are populated, rather than assuming a shortcut is available because it is a new filing relationship.
PNPC TPDF filing vs. generic return preparers and DIY filing
| Dimension | PNPC | Generic Preparer / DIY Filing |
|---|---|---|
| Related-party identification | Independently verified against Article 35/36 ownership and control thresholds | Relies on the client's self-declared list without independent verification |
| Connected Person capture | Owner/director remuneration, related-party rent and shareholder loan interest specifically identified and included | Often filed as ordinary payroll or overhead, omitted from the disclosure schedule |
| Reconciliation discipline | Every disclosed figure traced line-by-line to the audited or management financial statements before filing | Figures populated independently of the accounts, leaving mismatches that invite FTA queries |
| Local File consistency | Cross-checked against any existing Local File or benchmarking study for internal consistency | Prepared in isolation, even where a Local File already exists |
| Threshold testing | Disclosure threshold tested independently of the Local File/Master File thresholds | One threshold assumed to determine the other, leaving gaps or unnecessary work |
| Working paper retention | Full reconciliation trail retained and indexed, ready if the FTA queries a figure | Figures filed with no retained support behind them |
| Cross-border currency handling | Consistent exchange rate methodology applied across ledger, accounts and disclosure | Different rates used in different places, creating reconciliation gaps |
| Escalation awareness | Growth toward Local File/Master File thresholds flagged proactively year over year | Each year's filing treated in isolation with no forward threshold monitoring |
What the PNPC package includes
- 01
Related-party and Connected-Person mapping against Articles 35 and 36 of the Corporate Tax Law
- 02
Transaction and Connected Person payment inventory for the relevant tax period
- 03
Threshold screening against the current Ministerial Decision No. 97 of 2023 disclosure threshold
- 04
Line-by-line reconciliation of every disclosed figure to the audited or management financial statements
- 05
Cross-check against any existing Local File or benchmarking study for internal consistency
- 06
Foreign-currency conversion methodology applied consistently across ledger, accounts and disclosure
- 07
TPDF population within the EmaraTax Corporate Tax return workflow
- 08
Independent senior review before submission
- 09
Filing on EmaraTax directly as authorised tax agent, or hand-off to the client's own team
- 10
Indexed retention of the final schedule and reconciliation working papers
- 11
Following-year disclosure calendar entry aligned to the Corporate Tax return due date
- 12
Proactive flag if transaction values or group revenue approach the Local File / Master File thresholds
- 13
Support responding to any FTA query on a specific disclosed transaction or Connected Person payment
Get the disclosure schedule reconciled correctly the first time — PNPC's Dubai desk turns TPDF filing into the confirmed output of a proper related-party mapping, not a last-minute form-fill before the Corporate Tax return deadline.
Jurisdiction
Free zone, mainland & offshore
Ready to get started?
Tell us about your requirement — a UAE specialist responds within 24 hours.