A multinational's Saudi entity based in KAFD can have a perfectly reasonable pricing decision and still fail a ZATCA review if the documentation behind it doesn't exist.

Any Saudi entity with related-party transactions above the applicable thresholds, whether that's management fees charged from a foreign parent, intercompany services, goods transferred between related entities, or intercompany financing, falls under these rules. This sits alongside, and often intersects directly with, both corporate income tax exposure on foreign ownership and withholding tax on the underlying cross-border payments themselves.

The three-tier documentation structure

ZATCA's framework, aligned with OECD guidance, expects a master file covering the group's global operations and transfer pricing policies, a local file specific to the Saudi entity's actual transactions, and country-by-country reporting for larger multinational groups above the relevant revenue threshold. Many Saudi subsidiaries have access to a group-level master file prepared elsewhere but no properly localized file addressing their specific Saudi transactions, which is the gap ZATCA most often flags.

Where regional group structures run into trouble

A Riyadh-headquartered holding company charging a management fee to a manufacturing subsidiary, or a trading arm buying and selling goods to a related party outside Saudi Arabia, both need that pricing benchmarked against what unrelated parties would charge. Without a benchmarking study behind the number, ZATCA can challenge the pricing and reassess taxable income upward, which affects both the Zakat or tax base and potentially triggers withholding tax questions on the same transaction.

Benchmarking as the analytical foundation

Documentation without a proper benchmarking study behind it is largely just an assertion. A benchmarking exercise, comparing your related-party pricing against comparable transactions between independent parties, is what actually supports the documentation rather than just describing the arrangement. This is a distinct piece of work covered under transfer pricing benchmarking, and the two are almost always commissioned together for a defensible file.

What preparing a local file actually involves

We start from your actual intercompany agreements and transaction data, not a generic template, and build the local file around what your Saudi entity really does with its related parties. Where a benchmarking study is needed to support the pricing, we coordinate that analysis so the final file tells one consistent, defensible story rather than a policy document sitting apart from the numbers that don't quite match it.

Local context

Groups with a Riyadh head office and multiple related entities, whether manufacturing, trading or services, carry more transfer pricing exposure than a single-entity business, simply because more related-party transactions exist to document. This is worth reviewing whenever a group adds a new entity in a different city, not just at year-end.