UAEServicesUAE Taxation & Regulatory ComplianceTransfer PricingTransfer Pricing Disclosure Form (TPDF) Filing

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

What Transfer Pricing Disclosure Form (TPDF) Filing is

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

Structure Comparison

TPDF disclosure obligation by taxable person profile

ProfileTPDF Filing RequiredLocal File RequiredMaster File RequiredTypical Trigger
Standalone UAE business, no related parties or connected personsNoNoNoNo qualifying relationship exists under Article 35 or 36 at all
UAE business with related-party or Connected Person transactions below disclosure thresholdNo (monitor annually)NoNoTransaction 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 thresholdYesNoNoMost 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 memberYesYesYes (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 dealingsYes, same as any taxable personYes, if thresholds met — status does not exempt from disclosureYes, if group threshold metFree 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 onlyYesDepends on thresholds — UAE-specific Local File cannot rely solely on a foreign group fileOften adapted from an existing group Master File where the threshold is metCross-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.

How it works
StageWhat HappensWho ActsTypical Output
Related-Party & Connected-Person ConfirmationEvery 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 listPNPC, working from the group ownership chart, shareholder registers and director details supplied by the clientA confirmed related-party and Connected Person list for the tax period, in writing
Transaction & Payment InventoryEvery 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 categoryPNPC, drawing on the trial balance, general ledger, payroll records and lease agreementsA complete transaction and payment inventory for the disclosure period
Threshold ScreeningCatalogued transactions and payments are screened, individually and in aggregate by category, against the current disclosure threshold under Ministerial Decision No. 97 of 2023PNPCConfirmation of which transaction categories and Connected Person payments must be disclosed
Reconciliation to Financial StatementsEvery figure destined for the disclosure schedule is traced to the audited or management financial statements for the period, line by linePNPC, cross-referencing the ledger and the accountsA 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 consistencyPNPCA confirmed alignment, or a flagged discrepancy resolved before filing
Connected Person Detail VerificationOwner and director remuneration, related-party rent, and shareholder loan interest are individually verified for correct classification and value under Article 36PNPC, with input from payroll and the client's finance teamA verified Connected Person schedule ready for the disclosure form
TPDF Population on EmaraTaxThe Related Party Transactions disclosure schedule is populated within the Corporate Tax return workflow on EmaraTax, category by category and counterparty by counterpartyPNPC, using the client's EmaraTax credentials or acting as authorised tax agentA completed, internally reconciled disclosure schedule ready for review
Internal Review Before SubmissionA senior reviewer independent of the original preparer checks the populated schedule against the reconciliation working papers before the return is finalisedPNPC senior reviewerA reviewed, sign-off-ready disclosure form
Filing With the Corporate Tax ReturnThe disclosure form is submitted on EmaraTax as part of the Corporate Tax return for the periodClient (or PNPC as authorised tax agent) via EmaraTaxA filed TPDF, timestamped and retained in the EmaraTax submission history
Retention & Next-Cycle SetupThe 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 filingPNPCAn 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.

Document Checklist
Group & Ownership Structure

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

Financial & Corporate Tax Records

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

Related-Party Transaction Evidence

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

Connected Person Payment Records

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

Reconciliation & Filing Support

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

Ongoing obligations
PhaseTriggered ByPNPC GuidanceRisk If Ignored
Initial Threshold ConfirmationFirst Corporate Tax registration, or first related-party or Connected Person transaction identifiedConfirm 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 RefreshEach tax period approaching its Corporate Tax return due dateRe-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 FilingFinancial statements finalised and the disclosure schedule ready for populationTrace 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 ReturnCorporate Tax return due date approachingFile 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 FiguresFTA raises a question about a specific related-party transaction or Connected Person payment referenced in the filed disclosureRespond 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 ChangeM&A, new subsidiary, mainland-to-Free-Zone conversion, or a change in directors or ownershipRe-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 ThresholdRelated-party transaction values or group revenue grow past the higher documentation thresholdsFlag 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.
Frequently asked
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.

Practitioner noteClients frequently assume the two are the same filing at different levels of detail. They are legally distinct obligations with different thresholds — a taxable person can owe the TPDF with no Local File obligation at all.
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.

Practitioner noteThis is the most commonly triggered transfer pricing obligation we see in practice — many SME and family-owned groups that assume transfer pricing 'doesn't apply to them' actually owe a TPDF simply because of owner remuneration or intercompany dealings between UAE entities.
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.

Practitioner noteThis is the single most common misunderstanding we correct at the scoping stage. 'We have no foreign parent' is not the same question as 'do we have related parties.'
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.

Practitioner noteFinance teams routinely file owner salary and director-owned premises rent as ordinary payroll or overhead in the accounts, and then forget it also belongs on the related-party disclosure. This omission is one of the most frequent gaps we find on take-on engagements.
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.

Practitioner noteWe catalogue every category before filing rather than disclosing only the categories the client remembers — smaller, less obvious flows like a shared-services recharge or an intercompany guarantee are easy to overlook if the exercise starts from memory rather than the ledger.
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.

Practitioner noteWe build a reconciliation working paper tying every disclosed figure to its source in the accounts before the form is ever submitted, precisely so this question never has to be answered under time pressure later.
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.

Practitioner noteWe have seen disclosure forms and Local Files prepared in different cycles by different teams that told subtly different stories about the same transaction. Reconciling the two is a deliberate, not automatic, step.
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.

Practitioner noteWe deliberately test the disclosure threshold and the documentation thresholds separately at scoping — assuming one determines the other is the single most frequent scoping error we correct.
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.

Practitioner noteA verified ownership chain, not a verbal description of 'who's related to whom,' is the only reliable starting point. We have found related parties clients themselves had not recognised as such, and, less often, entities clients assumed were related that no longer met the Article 35 threshold following a share transfer.
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.

Practitioner noteWe retain the full reconciliation trail for every filed TPDF specifically so a query, whenever it comes, can be answered from an existing file rather than reconstructed from scratch under time pressure.
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.

Practitioner noteWhat we can say with confidence: an inaccurate disclosure carries risk independent of whether the underlying related-party pricing itself was arm's length — getting the form right is a distinct compliance step, not just a byproduct of good pricing.
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.

Practitioner noteMost clients prefer PNPC to file directly once the reconciliation is complete, simply to avoid a transcription step between our working papers and the portal entry.
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.

Practitioner noteUsing a spot rate for the ledger and an average rate for the disclosure form is a common, avoidable source of a reconciliation gap that draws unwanted FTA attention.
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.

Practitioner noteWe recommend starting disclosure preparation well ahead of the Corporate Tax return deadline rather than treating it as a last step, since a rushed reconciliation is exactly where mismatches slip through.
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.

Practitioner noteFirst-year TPDF engagements benefit from being run alongside Corporate Tax registration and return preparation rather than as an afterthought once the return is otherwise finished.
Why PNPC Global

PNPC TPDF filing vs. generic return preparers and DIY filing

DimensionPNPCGeneric Preparer / DIY Filing
Related-party identificationIndependently verified against Article 35/36 ownership and control thresholdsRelies on the client's self-declared list without independent verification
Connected Person captureOwner/director remuneration, related-party rent and shareholder loan interest specifically identified and includedOften filed as ordinary payroll or overhead, omitted from the disclosure schedule
Reconciliation disciplineEvery disclosed figure traced line-by-line to the audited or management financial statements before filingFigures populated independently of the accounts, leaving mismatches that invite FTA queries
Local File consistencyCross-checked against any existing Local File or benchmarking study for internal consistencyPrepared in isolation, even where a Local File already exists
Threshold testingDisclosure threshold tested independently of the Local File/Master File thresholdsOne threshold assumed to determine the other, leaving gaps or unnecessary work
Working paper retentionFull reconciliation trail retained and indexed, ready if the FTA queries a figureFigures filed with no retained support behind them
Cross-border currency handlingConsistent exchange rate methodology applied across ledger, accounts and disclosureDifferent rates used in different places, creating reconciliation gaps
Escalation awarenessGrowth toward Local File/Master File thresholds flagged proactively year over yearEach year's filing treated in isolation with no forward threshold monitoring

What the PNPC package includes

  1. 01

    Related-party and Connected-Person mapping against Articles 35 and 36 of the Corporate Tax Law

  2. 02

    Transaction and Connected Person payment inventory for the relevant tax period

  3. 03

    Threshold screening against the current Ministerial Decision No. 97 of 2023 disclosure threshold

  4. 04

    Line-by-line reconciliation of every disclosed figure to the audited or management financial statements

  5. 05

    Cross-check against any existing Local File or benchmarking study for internal consistency

  6. 06

    Foreign-currency conversion methodology applied consistently across ledger, accounts and disclosure

  7. 07

    TPDF population within the EmaraTax Corporate Tax return workflow

  8. 08

    Independent senior review before submission

  9. 09

    Filing on EmaraTax directly as authorised tax agent, or hand-off to the client's own team

  10. 10

    Indexed retention of the final schedule and reconciliation working papers

  11. 11

    Following-year disclosure calendar entry aligned to the Corporate Tax return due date

  12. 12

    Proactive flag if transaction values or group revenue approach the Local File / Master File thresholds

  13. 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

🇦🇪
United Arab Emirates

Free zone, mainland & offshore

Ready to get started?

Tell us about your requirement — a UAE specialist responds within 24 hours.

← Back to Transfer Pricing