Saudi TP Documentation: Where Most Enforcement Risk Sits
Transfer pricing documentation is not just an administrative requirement. In Saudi Arabia, it is the primary line of defence in a ZATCA audit. The quality and completeness of your documentation determines whether the burden of proof sits with ZATCA or with you — and that distinction has a direct impact on the outcome of any dispute.
Chapter 8 of the Saudi TP Bylaws establishes a three-tier documentation structure: general documentation applicable to all taxpayers with controlled transactions, a Master File and Local File for entities above the SAR 6 million threshold, and a Country-by-Country Report for MNE groups with consolidated revenues above SAR 3.2 billion. Each tier serves a different purpose and carries different content obligations, thresholds, and deadlines.
This article covers exactly what each tier requires, who must prepare it, when it must be available, and what the consequences are for getting it wrong.
The Three-Tier Structure at a Glance
Before going into each tier in detail, here is the complete picture of who must prepare what, and when:
| Documentation Tier | Threshold | Who Prepares | Filing / Availability | Production Deadline |
|---|---|---|---|---|
| General Documentation | All controlled transactions (no threshold) | All taxable persons with controlled transactions | Not filed proactively — must be available on request | 30 calendar days from ZATCA request |
| Master File | SAR 6M+ controlled transactions in 12 months | Taxpayer (typically coordinated at group level) | Not filed proactively — must be available on request | 30 calendar days from ZATCA request |
| Local File | SAR 6M+ controlled transactions in 12 months | Taxpayer — Saudi entity specific | Not filed proactively — must be available on request | 30 calendar days from ZATCA request |
| TP Disclosure Form | All taxpayers with controlled transactions | All taxpayers | Filed with tax return — 120 days after fiscal year end | 120 days after fiscal year end |
| Chartered Accountant Certificate | SAR 6M+ controlled transactions | Licensed Saudi auditor | Filed with TP Disclosure Form — 120 days after fiscal year end | 120 days after fiscal year end |
| CbCR Notification | SAR 3.2B+ consolidated group revenue | Every constituent entity in KSA | Filed via ZATCA e-portal | 120 days after Reporting Year end |
| Country-by-Country Report | SAR 3.2B+ consolidated group revenue | UPE, Surrogate Parent Entity, or designated constituent entity | Filed via ZATCA e-portal (XML format) | 12 months after Reporting Year end |
General Documentation — The Baseline Obligation
Every taxable person party to a controlled transaction — whether a cross-border or domestic transaction, whether large or small — must maintain general documentation confirming that those transactions were conducted at arm’s length. This is not tied to any threshold. It applies to every entity with related-party transactions.
General documentation does not follow a prescribed format. ZATCA does not specify what the document must look like. What it must contain, however, is enough information to allow the Authority to determine whether the conditions of the controlled transactions are consistent with the arm’s length principle. In practice, this means documenting the nature of the related-party relationship, the description of the controlled transactions, the pricing methodology applied, and the rationale for concluding that the pricing is at arm’s length.
The absence of a prescribed format is not a licence for minimal effort. ZATCA can request general documentation at any time, and must receive it within 30 calendar days. Documentation that does not substantiate the arm’s length nature of the transactions — however it is formatted — will not satisfy the requirement. The lack of format is flexibility, not an exemption from substance.
The Master File — Global Overview of the MNE Group
The Master File provides ZATCA with a high-level picture of the MNE group as a whole — its global business operations, its transfer pricing policies, and the economic circumstances in which related-party transactions occur. It is intended to give context for the Local File analysis; it does not itself justify specific transaction pricing.
The Master File is prepared at the group level and covers all business lines. Where a specific business line operates independently, the Master File may be separated into parts for readability — but this does not eliminate the obligation to make the full Master File available on ZATCA’s request. The minimum content requirements are set out in Appendix 8 of ZATCA’s TP Guidelines and include:
| Master File Component | What It Must Cover |
|---|---|
| Group structure and legal entity overview | Organisational chart, ownership structure, jurisdictions of operation |
| Description of the group’s business | Sources of profit, principal markets, supply chain for top five products/services by revenue, intercompany service arrangements |
| Group-wide transfer pricing policies | TP policies applicable to all business lines, policies for intangible asset development and ownership, policies for intercompany financing |
| Intangibles | Description of group strategy for developing, owning, and exploiting intangibles; list of significant intangibles and legal ownership entities; agreements on cost sharing and R&D services |
| Intercompany financing | Description of how the group is financed, identification of any group financing entities and their jurisdictions, TP policies for financing arrangements |
| Financial and tax positions | Annual consolidated financial statements, unilateral APAs, other tax rulings |
The Local File — Saudi-Specific Transaction Analysis
The Local File is where the real compliance work lives. It is transaction-specific, Saudi-entity-specific, and is the document ZATCA will scrutinise most closely in an audit. It supplements the Master File by providing detailed information about each material controlled transaction involving the Saudi taxable person.
Minimum content requirements for the Local File are specified in Appendix 9 of ZATCA’s TP Guidelines. Key components include:
| Local File Component | What It Must Cover |
|---|---|
| Description of the Saudi entity | Management structure, local competitors, financial performance over prior years |
| Controlled transaction description | Nature and terms of each controlled transaction, amounts involved, related parties |
| Functional analysis | Functions performed, assets employed, and risks assumed by each party — in detail |
| Method selection and application | The chosen TP method, the reasons for its selection, and how it is applied to each controlled transaction |
| Comparability analysis | Identification of internal and external comparables, the search process, the financial data for selected comparables, and any adjustments made |
| Economic analysis and conclusions | The arm’s length range established, where the controlled transaction falls within or relative to that range, and the conclusion on arm’s length compliance |
| Financial information | Annual financial statements for the taxable year; schedules showing how the financial data used in the TP analysis ties to the financial statements |
The Local File must reflect the economic reality of the entity at the time the transaction was priced. Documentation that is accurate as of the analysis date but does not reflect the actual conditions of the transaction is not compliant — and ZATCA will identify the gap. Every controlled transaction in the Disclosure Form should be traceable to the Local File’s analysis.
Country-by-Country Reporting — Scope, Thresholds, and Filing
The Country-by-Country Report (CbCR) is the most administratively complex element of Saudi TP compliance. It provides ZATCA — and, through automatic exchange, other tax authorities — with a jurisdiction-by-jurisdiction picture of how the MNE group’s revenues, profits, taxes, employees, and assets are distributed globally.
Who Must File
The CbCR obligation applies where the MNE group’s consolidated revenue in the Reporting Year immediately preceding the current Reporting Year exceeds SAR 3.2 billion. This is the Statutory Consolidated Revenue Threshold (SCRT). In principle, the Ultimate Parent Entity (UPE) files the CbCR in its jurisdiction of residence, with automatic exchange to Saudi Arabia.
A Saudi constituent entity must file the CbCR directly with ZATCA in three situations: the UPE is not required to file in its own jurisdiction; the UPE’s jurisdiction does not have an effective automatic exchange agreement with Saudi Arabia; or the UPE’s jurisdiction systematically fails to provide Saudi Arabia with the relevant CbCRs.
The CbCR Notification — A Separate and Critical Obligation
Every constituent entity of an MNE group that meets the SCRT — regardless of whether it is the filing entity for the CbCR itself — must submit a CbCR Notification to ZATCA within 120 days of the end of the Reporting Year. The Notification must identify the Reporting Entity, confirm whether the taxpayer is the UPE, Surrogate Parent Entity, or another constituent entity, and provide the filing jurisdiction for the CbCR.
This is where Saudi subsidiaries of large MNE groups most commonly fail. The parent entity files the CbCR centrally — but each Saudi constituent entity must independently file the Notification. That obligation does not flow automatically from the group-level filing.
Global Tech Group is a multinational headquartered in Germany, with consolidated revenues of approximately USD 1.4 billion (approximately SAR 5.25 billion) in 2023. Person X is a Saudi-resident LLC, 100% owned by Global Tech Group. The Reporting Year for the group ends on 31 December 2023.
SCRT test: SAR 5.25 billion exceeds SAR 3.2 billion. The CbCR requirement applies.
Filing entity: The German parent (UPE) files the CbCR in Germany. Germany and Saudi Arabia have a qualifying automatic exchange agreement. Person X is therefore not required to file the CbCR directly with ZATCA.
But: Person X must still file the CbCR Notification with ZATCA within 120 days of 31 December 2023 — i.e., by 30 April 2024. The Notification confirms that the UPE is the German parent, that the CbCR will be filed in Germany, and the relevant filing period.
Failure to file the Notification is a compliance violation independent of whether the CbCR itself was correctly filed by the parent.
Content of the CbCR
The CbCR template comprises three tables. Table 1 contains the quantitative data: revenue from related and unrelated parties, profit or loss before income tax, income tax paid, income tax accrued, stated capital, accumulated earnings, number of employees, and tangible assets other than cash — all broken down by jurisdiction. Table 2 identifies each constituent entity, its tax residence jurisdiction, and its main business activities. Table 3 provides additional information the MNE considers relevant for understanding the data in Tables 1 and 2.
Worked Example — Documentation Obligations for a Saudi Subsidiary
Al-Rashid Trading Co. is a Riyadh-based distributor, 75% owned by a UAE parent company. In fiscal year 2023, Al-Rashid had the following controlled transactions:
Purchase of inventory from UAE parent: SAR 18 million | Management fee to UAE parent: SAR 2 million | Intercompany loan from UAE parent (outstanding balance SAR 10 million, interest SAR 0.5 million)
Total controlled transactions at arm’s length value: SAR 20.5 million
Documentation obligations triggered:
The SAR 6 million threshold is exceeded (SAR 20.5 million total). Al-Rashid must prepare a Master File and Local File. The 25% non-Saudi ownership means Al-Rashid is subject to the Income Tax Law for the UAE-owned portion — the TP Bylaws apply in full.
Disclosure Form: Due by 30 April 2024 (120 days after 31 December 2023). Must disclose each controlled transaction — inventory purchase, management fee, and intercompany loan interest — with transaction descriptions and the TP method applied to each.
Chartered Accountant Certificate: Due with the Disclosure Form by 30 April 2024. Must be provided by Al-Rashid’s licensed Saudi auditor, certifying that the MNE group’s TP policy has been consistently applied.
Master File and Local File: Not filed proactively. Must be maintained and available — producible within 30 calendar days of any ZATCA request. If ZATCA issues a request on 1 June 2024, the documents must be provided by 1 July 2024.
CbCR: Depends on the UAE parent group’s consolidated revenue. If the group’s revenue exceeds SAR 3.2 billion, Al-Rashid must file the CbCR Notification within 120 days of the group’s Reporting Year end. If the UAE group itself files the CbCR and the UAE-KSA exchange agreement is operative, Al-Rashid does not file the CbCR directly — but the Notification is still mandatory.
Common Documentation Gaps ZATCA Identifies
- No functional analysis — only a transaction description. Listing what transactions occurred does not constitute a Local File. ZATCA requires a genuine functional analysis: who performs what functions, who owns what assets, who bears what risks. The economic analysis must flow from this characterisation.
- Benchmark study not updated for the current year. A comparability study conducted three years ago is not automatically valid for the current year. If market conditions, the entity’s functional profile, or the transaction terms have changed, the benchmark must be updated. ZATCA can challenge documentation that uses stale comparables.
- Master File not covering the full group. The Master File should give ZATCA a picture of the entire MNE group — not just the part relevant to the Saudi entity. A Master File that covers only the Saudi operations or the immediately relevant holding company is incomplete.
- CbCR Notification not filed. The most commonly missed obligation in the CbCR framework. Every Saudi constituent entity of an MNE meeting the SCRT must file the Notification — regardless of where the CbCR itself is filed. This is a compliance failure independent of whether the group’s CbCR is correct.
- Documentation prepared after ZATCA contact. Retrospectively created documentation is identifiable and carries limited credibility. The 30-day production window assumes documentation already exists. Starting the preparation process only after ZATCA issues a request is not compliant with the contemporaneous preparation requirement.
- Disclosure Form inconsistent with Local File. Where the TP method or transaction descriptions in the Disclosure Form differ from those in the Local File, ZATCA has grounds to question whether the documentation reflects the actual transfer pricing position. Consistency across all TP-related filings is essential.
Frequently Asked Questions
Do I need a Local File if my controlled transactions are below SAR 6 million?
No. The formal Master File and Local File requirements are triggered only when the total arm’s length value of your controlled transactions exceeds SAR 6 million in a 12-month period. Below that threshold, you are a small enterprise for documentation purposes. However, you must still maintain general documentation supporting the arm’s length nature of your controlled transactions, and complete the TP Disclosure Form with your tax return.
When does the Master File need to be filed with ZATCA?
The Master File is not filed proactively. It must be prepared and maintained, and made available to ZATCA within 30 calendar days of a written request. The clock starts on the date ZATCA issues the request — not when you receive it. Given the 30-day window, the Master File must effectively be complete before the request arrives.
What is the SAR 3.2 billion threshold for CbCR?
It is the Statutory Consolidated Revenue Threshold (SCRT). Where an MNE group’s consolidated revenue in the Reporting Year immediately preceding the current year exceeds SAR 3.2 billion, the group is subject to CbCR obligations in Saudi Arabia. Note that this is assessed on the prior year’s revenue — not the current year. A group that crossed the threshold last year is required to file for the current year, even if current year revenue has declined.
Does every Saudi entity in an MNE group need to file a CbCR Notification?
Yes — every constituent entity of the MNE group that is resident in Saudi Arabia must file the CbCR Notification within 120 days of the Reporting Year end, provided the group meets the SCRT. This is a separate obligation from the CbCR itself. Filing the CbCR at the group level does not satisfy the Saudi constituent entity’s independent Notification obligation.
What language must the documentation be in?
All documents submitted to ZATCA must be in Arabic. Documents originally prepared in English (as most MNE group Master Files are) will require translation for ZATCA submission. The original English version should be retained as the primary document; the Arabic translation is the version provided to ZATCA.
- The Saudi TP documentation regime has three tiers: general documentation (all taxpayers), Master File and Local File (SAR 6M+ threshold), and Country-by-Country Report (SAR 3.2B+ consolidated revenue). Each has distinct content requirements and deadlines.
- General documentation applies to every entity with controlled transactions — there is no threshold. It must confirm arm’s length pricing and be producible within 30 days of a ZATCA request.
- The Master File and Local File are not filed proactively. They must be prepared contemporaneously and available for production within 30 calendar days of a ZATCA request. Starting preparation after the request arrives is not compliant.
- The TP Disclosure Form must be filed within 120 days of fiscal year end, along with the Chartered Accountant Certificate. These are proactive filing obligations — they are not request-based.
- The CbCR Notification is a separate, standalone obligation. Every Saudi constituent entity of a qualifying MNE group must file it within 120 days of the Reporting Year end — even if the group’s CbCR is filed centrally by the parent.
- Documentation gaps are ZATCA’s opening. Incomplete, inconsistent, or retrospectively prepared documentation shifts the burden of proof against the taxpayer and weakens every other aspect of the TP defence.