Cyprus Local File vs SIT in 2026: What Groups Must Prepare

Cyprus Local File vs Summary Information Table (SIT) in 2026: thresholds, below-threshold documentation, filing responsibilities and practical controls.

The two obligations are not the same

Cyprus transfer pricing compliance is easier to manage when groups separate the Local File obligation from the annual Summary Information Table (SIT). The Local File is the detailed contemporaneous transfer pricing file that documents the relevant category of controlled transactions, the functional analysis, method selection, benchmarking and conclusions. The SIT is an annual disclosure summarising controlled transactions by category.

A group should therefore avoid treating the Local File threshold as a general exemption from transfer pricing. Controlled transactions remain subject to the arm’s-length principle even where a full Local File is not triggered. The practical question becomes how much evidence is proportionate to the size and complexity of the transaction.

2026 Local File thresholds

For tax years from 2026, the Local File thresholds are €10 million for financial transactions, €5 million for goods transactions and €2.5 million for other categories of controlled transactions. The threshold is considered by category for the relevant tax year and should be monitored using an arm’s-length view of the transaction values, not only whatever amount happens to be booked in the ledger.

Groups close to a threshold should not wait until year-end. A quarterly control that reconciles intercompany balances, interest, royalties, service fees and trading flows can prevent a late surprise.

What to retain below the threshold

Below-threshold does not mean no documentation. A proportionate file may include the agreement, business rationale, functional profile, pricing policy, calculations, evidence of third-party terms or market data, and a short explanation of why the selected method produces an arm’s-length result.

For recurring arrangements such as management services, software royalties and shareholder or group financing, a short annual refresh is usually more defensible than recreating the analysis only after a tax enquiry.

A practical year-end workflow

Start with the related-party ledger and map each transaction to the appropriate category. Reconcile the SIT population to the financial statements and tax computation. Identify threshold categories, confirm that agreements reflect actual conduct, refresh benchmarks where necessary and ensure the accounting entries agree to the transfer pricing analysis.

This workflow also helps the statutory audit: the audit team can see how related-party balances were identified, how pricing was supported and where judgement was applied.

Common errors

Common issues include using the wrong category, testing only the year-end balance instead of the annual transaction flow, relying on an old benchmark without checking whether conditions changed, and assuming that a low-value transaction cannot be challenged. Another frequent problem is a mismatch between the agreement, invoice narrative, accounting treatment and the actual functions performed.

The strongest file is not the longest. It is the one that reconciles cleanly to the books and explains the economics of the arrangement in a way that is consistent with what the parties actually do.