Saudi Transfer Pricing: What General Documentation Requires

Many UAE headquartered groups run operations across the border in Saudi Arabia through subsidiaries, branches, and shared service arrangements. When those Saudi entities transact with the rest of the group, Saudi transfer pricing rules apply. What often gets missed is that falling below the Local File and Master File thresholds does not switch off the documentation obligation. It changes the format, not the substance.

That is where general documentation comes in. It is the catch-all transfer pricing record required from Saudi taxpayers and zakat payers that transact with related parties but sit below the Local File and Master File thresholds. It has no prescribed template, yet it must still prove that every controlled transaction was priced on an arm's length basis, and it must reach the Zakat, Tax and Customs Authority (ZATCA) within a short window once requested.

This guide explains what general documentation is, where it sits in the Saudi transfer pricing framework, who must prepare it, how it differs from the Local File and Master File, and why UAE groups with Saudi operations need to treat it seriously. It is written for UAE business owners, CFOs, finance teams, tax professionals, and accountants who need a clear, practical view.

What is Saudi transfer pricing general documentation?

General documentation is the fallback transfer pricing record that keeps below-threshold taxpayers within reach of the arm's length principle. It applies to taxpayers and zakat payers that have related-party (controlled) transactions but are exempt from preparing the Local File and Master File.

Confirmed legal fact: it is set out in Article 19 of the KSA Transfer Pricing Bylaws, which fall under the broader Saudi income tax framework administered by ZATCA. You can review the wider body of Saudi rules on the ZATCA rules and regulations page, and the income tax regime it sits within on the ZATCA income tax regulations page, which links to the full Implementing Regulations of the Income Tax Law.

The key distinction is simple. The Local File and Master File exemption removes a filing format. It does not remove the arm's length principle. General documentation exists to make sure no related-party dealing escapes arm's length testing simply because it falls below a monetary threshold.

Why "exempt" does not mean "off the hook"

Professional interpretation: a Local File exemption is never a clean pass. A small trading company, a natural person doing business in the Kingdom, a zakat-exempt entity, or an investment fund can each fall outside the Local File regime and still have to show, on request, that its intercompany pricing was reasonable.

The practical standard is lighter in form but not in substance. ZATCA does not hand you a template, and any format that does the job is acceptable. What it does expect is content: the identity of the related parties, the nature of each controlled transaction, how the price was arrived at, and why the terms are consistent with what independent parties would have agreed.

Where does general documentation sit in the Saudi transfer pricing framework?

Saudi transfer pricing compliance is built on layered obligations. Understanding where general documentation fits helps a UAE group decide what it actually needs to prepare for its Saudi entities.

The framework has four main documentation components, plus the arm's length principle that underpins all of them. The arm's length principle itself follows the international consensus set out in the OECD Transfer Pricing Guidelines, which Saudi Arabia's rules broadly align with.

The disclosure form applies to everyone with related-party dealings. Above the thresholds, the Local File and Master File apply. Below them, general documentation applies. In other words, there is no gap in the system where a taxpayer with controlled transactions has no documentation duty at all.

For a fuller view of how the disclosure form works, see our article on the Saudi transfer pricing disclosure form and the 30 April deadline. For where the Local File and Master File lines fall, see our KSA Local File and Master File thresholds guide.

What does Article 19 of the KSA Transfer Pricing Bylaws require?

Confirmed legal fact: Article 19 of the KSA Transfer Pricing Bylaws sets out the general documentation obligation. It requires a taxpayer that is exempt from the Local File and Master File to keep information sufficient to verify the arm's length nature of its controlled transactions.

The Article does not prescribe a fixed template. That is deliberate. It gives ZATCA flexibility to request the evidence it needs while allowing smaller taxpayers to prepare a proportionate record rather than a full OECD-style file.

Professional interpretation: the absence of a template is often misread as an absence of obligation. It is the opposite. The taxpayer carries the burden of demonstrating arm's length pricing, and the format freedom simply means the taxpayer decides how to present that proof, not whether to hold it.

Who must prepare general documentation?

General documentation is required from any taxpayer or zakat payer with related-party transactions that is exempt from the Local File and Master File. That population is broader than many UAE groups assume, because it captures the entities that sit at the smaller end of a group or that pay zakat rather than corporate income tax.

The categories most commonly caught include:

• Taxpayers and mixed entities with controlled transactions below the SAR 6 million Local File threshold.
• Zakat payers below the applicable phased zakat thresholds.
• Natural persons who conduct business in the Kingdom and transact with related parties.
• Zakat-exempt entities that still have related-party dealings.
• Investment funds that transact with related parties, such as a fund on-lending to a portfolio company.

The important point is that the trigger is having controlled transactions, not being large. A single related-party dealing is enough to bring an entity within the arm's length principle, and if the entity is below the Local File threshold, general documentation is the record that supports it.

How the position differs across taxpayer types

The classification of the Saudi entity matters, because it drives both which documentation tier applies and how the entity is taxed. Whether an entity pays zakat, corporate income tax, or both depends on ownership. For the underlying distinction, see our explainer on zakat versus corporate income tax in Saudi Arabia.

Practical advisory observation: for a UAE headquartered group, the Saudi entities most at risk of overlooking general documentation are the ones finance teams treat as "small." A modest Saudi service company or a fund vehicle can carry a real documentation duty even though it never approaches the Local File threshold.

How does general documentation differ from the Local File and Master File?

The three records share a purpose and a timeline, but they differ in who prepares them and how prescriptive they are. Seeing them side by side makes the boundary clear.

The Local File is entity-specific and detailed. The Master File zooms out to the whole group, describing its structure, value chain, intangibles, financing, and global transfer pricing policies. General documentation covers the same ground as the Local File in purpose, but without the prescribed format and with a lighter, proportionate level of content.

Professional interpretation: in practice, the sensible approach is to keep general documentation close to what a Local File would contain, especially the functional analysis and the economic analysis. A proportionate file assembled while the facts are fresh costs far less than reconstructing one under time pressure after a request lands.

What arm's length evidence should be retained?

Because Article 19 sets no template, the content is what matters. General documentation should contain enough to let ZATCA verify that each controlled transaction was priced on an arm's length basis. In practice, that means the file should identify the related parties, describe each transaction, explain how the price was set, and support why the terms match what independent parties would have agreed.

A proportionate general documentation file typically includes:

• A description of the group and the entity's place within it.
• A list of the related parties and the controlled transactions with each.
• The intercompany agreements or a description of the terms where no formal agreement exists.
• A functional analysis covering who does what, who owns what, and who bears which risks.
• The selected transfer pricing method and the reason it fits the transaction.
• The economic or benchmarking analysis that supports the price or margin.
• A reconciliation to the disclosure form and the financial statements.

The two most important elements are the functional analysis and the economic analysis. Everything else supports them.

How the functional analysis should be approached

The functional analysis is the foundation. It sets out the functions performed, the assets used, and the risks assumed by each party to a controlled transaction, often shortened to FAR. This is what decides how the Saudi entity should be characterised and, therefore, what return it should earn.

Practical example: a Saudi service subsidiary of a UAE group provides back-office support to related entities. If the functional analysis shows that the subsidiary performs routine support functions, uses limited assets, and bears little risk, it should earn a routine return. Documenting that fact pattern is what makes a modest cost-plus margin defensible.

How the economic analysis should be approached

The economic analysis tests the price or margin against what unrelated parties would have agreed. For most routine transactions, that means selecting comparable data and showing that the tested result falls within an arm's length range.

Professional interpretation: benchmarking cannot be allowed to go stale. Comparable financial data should be refreshed against the existing comparable set, and the full search re-run when the entity's functions or the market move materially. ZATCA is more likely to challenge a file that leans on outdated comparables or that shows a thin functional analysis. The methods themselves follow the international standard set out in the OECD Transfer Pricing Guidelines for Multinational Enterprises and Tax Administrations 2022.

What are the production timelines?

Confirmed legal fact: general documentation is not filed with the return. It is maintained internally and produced to ZATCA within a set period of a formal request, measured in calendar days rather than business days.

Practical advisory observation: the short window is the whole point. Format-free does not mean preparation-free. A taxpayer cannot realistically build a defensible functional and economic analysis from scratch inside that window, so the file has to exist before the request arrives. Treating contemporaneous preparation as the real deadline, rather than the request date, is the only reliable approach.

Format freedom is not a reason to wait. When ZATCA asks, the clock starts, and it does not care that no template was prescribed. The functional and economic analysis should be assembled and updated while the year's facts are still fresh.

When is ZATCA most likely to ask?

ZATCA uses risk indicators to decide where to focus. General documentation is more likely to be requested where certain features are present.

Professional interpretation, drawn from how the regime operates in practice: the higher-risk situations tend to include:

• A counterparty sitting in a special economic zone.
• Arrangements that look artificial or lack commercial substance.
• A corresponding adjustment request after another authority has adjusted the other side of a transaction.
• International information exchange obligations being triggered.
• Losses or margins that sit outside what the functional profile would suggest.

Cross-border structures naturally attract more attention. A UAE group with Saudi operations and intercompany flows across the border should assume its Saudi entities are visible, and keep evidence current even where the Local File does not apply.

What are the penalties, and how does the disclosure form interact?

The documentation obligation does not stand alone. It connects directly to the disclosure form and to the penalty regime.

Confirmed legal fact: the disclosure form (CTDF) must be filed with the return and certified by a licensed local auditor. Weak or missing documentation lets ZATCA make its own transfer pricing adjustment, which increases the tax or zakat liability before any penalty is added. The penalty framework for late disclosure, misrepresentation, and late payment is set out in the Saudi income tax rules, and we cover it in detail in our article on KSA transfer pricing penalties for non-compliance.

The chain from documentation to cost is direct. A thin or missing general documentation file leaves the arm's length nature of a transaction unproven. ZATCA can then adjust the taxable base, and the penalties attach to the adjusted liability. In effect, poor documentation converts a paperwork gap into a tax cost.

Practical advisory observation: the disclosure form and the underlying documentation must tell the same story. If the method disclosed on the CTDF does not match the analysis in the general documentation, that inconsistency is exactly the kind of flag that prompts a request and, potentially, an adjustment.

Why should UAE headquartered groups with Saudi operations care?

For a UAE group, Saudi general documentation is not a distant compliance item. It sits inside the same intercompany flows the group already manages for UAE purposes, and it carries its own Saudi rules on top.

Several practical issues stand out for UAE headquartered groups.

First, the same intercompany transaction can be documented on both sides of the border. A management fee charged by a UAE parent to a Saudi subsidiary needs a UAE position and a Saudi position. The functional analysis should be consistent, but the documentation tier and the local rules differ. Our UAE transfer pricing compliance guide covers the UAE side.

Second, related-party identification has to be complete on the Saudi side too. A relationship that the UAE team maps for UAE purposes may also drive Saudi documentation duties. The tests are not identical, but the discipline is the same. See our guidance on identifying related parties and on reporting related-party transactions.

Third, payments to owners, directors, and officers deserve attention in both jurisdictions. The UAE treats these as connected person payments, tested against market value, as explained in our article on connected persons under UAE Corporate Tax. Saudi rules apply their own arm's length testing to related-party dealings, and general documentation is where a below-threshold Saudi entity would evidence them.

Fourth, consistency across the group protects the whole structure. A Saudi entity that is characterised as a routine service provider in its general documentation should not be described as an entrepreneur in the group's UAE Master File. Cross-border inconsistency is one of the fastest ways to invite scrutiny.

A practical example for a UAE group

Consider a UAE holding company with a Saudi subsidiary that provides marketing support to group entities. The Saudi subsidiary's controlled transactions total less than SAR 6 million a year, so it is exempt from the Local File. It is not exempt from the arm's length principle.

The group prepares general documentation for the Saudi subsidiary: a short functional analysis showing routine marketing support with limited risk, a cost-plus method with a documented mark-up, benchmarking to support that mark-up, and a reconciliation to the disclosure form. If ZATCA requests the file, it can be produced within the window. Without that file, ZATCA could adjust the subsidiary's margin upward and apply penalties on the additional tax.

Common mistakes to avoid

• Assuming a Local File exemption removes the documentation duty entirely. It removes the format, not the arm's length obligation.
• Treating "no prescribed template" as "no file needed." General documentation still has to prove arm's length pricing.
• Waiting for a ZATCA request before preparing the file. The production window is too short to build a defensible analysis from scratch.
• Skipping the functional analysis. Without it, the chosen method and margin have no foundation.
• Relying on stale benchmarks. Outdated comparables are a common trigger for challenge.
• Letting the general documentation contradict the disclosure form or the audited accounts.
• Overlooking small Saudi entities, funds, or natural persons that quietly carry a documentation duty.
• Failing to keep the Saudi and UAE characterisations of the same entity consistent.

Practical recommendations for UAE groups with Saudi operations

1. Map every Saudi entity in the group and identify which ones have related-party transactions, regardless of size.
2. For each below-threshold Saudi entity, confirm that general documentation applies and prepare a proportionate file.
3. Build the functional analysis first, then select the method, then support it with current benchmarking.
4. Reconcile the general documentation to the disclosure form and the financial statements before the return is filed.
5. Refresh comparable data each year and re-run the full search when functions or markets change.
6. Keep the Saudi and UAE positions on the same intercompany transaction consistent in substance.
7. Treat contemporaneous preparation as the deadline, so any ZATCA request can be met within the window.
8. Where structures are complex or cross-border adjustments arise, get specialist support early through SBC's transfer pricing services.

Frequently asked questions

Who must prepare general documentation in Saudi Arabia?

Any taxpayer or zakat payer with related-party transactions that is exempt from the Local File and Master File. This includes taxpayers and mixed entities below the SAR 6 million Local File threshold, zakat payers below the phased thresholds, natural persons in business, zakat-exempt entities, and investment funds. It is the fallback record that keeps below-threshold taxpayers within the arm's length principle.

Does general documentation have a required format?

No. Article 19 of the KSA Transfer Pricing Bylaws does not prescribe a template, and any format that meets the requirements is acceptable. The file must, however, contain enough to verify the arm's length nature of each controlled transaction, especially the functional analysis and the economic or benchmarking analysis.

How quickly must general documentation be provided to ZATCA?

Within a set period of a formal ZATCA request, measured in calendar days. Because the window is short and no template is provided, the practical approach is to prepare and keep the analysis contemporaneously rather than waiting for the request.

How is general documentation different from the Local File?

They share the same purpose and the same production timeline, but the Local File is a prescribed, OECD-style document required above the thresholds, while general documentation is a format-free record required below them. Both must demonstrate that controlled transactions are at arm's length.

Do UAE groups with small Saudi entities really need general documentation?

Yes, where those Saudi entities have related-party transactions and fall below the Local File threshold. The trigger is having controlled transactions, not being large. A modest Saudi service company or fund vehicle can carry a real documentation duty.

What happens if a Saudi entity has no general documentation when ZATCA asks?

ZATCA can make its own transfer pricing adjustment because the arm's length nature of the transaction is unproven. That increases the tax or zakat liability, and penalties then attach to the adjusted amount. Missing documentation effectively converts a paperwork gap into a tax cost.

Conclusion

Saudi general documentation is easy to underestimate. It has no template, it is not filed with the return, and it applies mostly to smaller entities. None of that reduces its importance. Under Article 19 of the KSA Transfer Pricing Bylaws, a below-threshold Saudi entity still has to prove that its related-party pricing was at arm's length, and it has to do so quickly once ZATCA asks.

For UAE headquartered groups, the message is practical. The Saudi entities you treat as small can still carry a documentation duty, the file has to exist before a request arrives, and the Saudi position has to stay consistent with the group's UAE documentation. Building a proportionate functional and economic analysis while the facts are fresh is far cheaper than reconstructing one under pressure, and it protects the wider structure from adjustments and penalties.

If you want support preparing general documentation for your Saudi entities, aligning it with your UAE positions, or reviewing your cross-border transfer pricing risk, explore SBC's Transfer Pricing and Corporate Tax services, browse our full services overview, read more analysis on the SBC insights hub, or contact the SBC team to review your Saudi and UAE documentation together.

15/6/26 Zakat vs Corporate Income Tax

Page Title: Zakat vs Corporate Income Tax in Saudi Arabia: A Guide for UAE Groups
Meta Title: Zakat vs Corporate Income Tax in Saudi Arabia Explained
Meta Description: Understand Saudi zakat at 2.5% versus corporate income tax at 20%, how ownership drives the split, and what it means for UAE groups with Saudi operations.
Primary Keywords: zakat vs corporate income tax Saudi Arabia, Saudi zakat and corporate tax
Secondary Keywords: mixed ownership company KSA, ZATCA corporate income tax, GCC ownership tax, Saudi Arabia tax for UAE groups, zakat base calculation
Slug: zakat-vs-corporate-income-tax-saudi-arabia-uae-groups