The local transfer pricing report documents transactions between a company and its related parties and explains the analysis used to assess whether these transactions comply with applicable criteria. In Colombia, its requirement, scope, and thresholds depend on the regulations in force for each tax year; these must be verified before determining who is obligated to file or what information must be submitted.
What is the local report and what is it used for?
In practical terms, it is a technical document that compiles information about the analyzed transactions and explains the reasoning used to review them. Its purpose is to allow someone else to follow the sequence of events related to the transaction, the documentation consulted, the comparability analysis, and the conclusions. Therefore, it should not be limited to a general description of the group's policy or a disorganized collection of files.
For a company, this traceability facilitates internal review and helps connect the tax, financial, accounting, legal, and business areas. The report must correspond to the period and the transactions actually analyzed. If transactions, contracts, or policies have changed, the record must reflect these changes and not assume that information from a previous period remains relevant.
The local report must also be distinguished from other transfer pricing documents. The information statement, master file, country-by-country report, and CbC Report have their own names and purposes; they are not interchangeable terms. The company must separately verify which documents apply to it under current regulations. A general explanation of the topic can be found in the General guide to transfer pricing in Colombia; Here the focus is on the local report and its review.
A tax document, not a trade price guide
Transfer pricing relates to tax compliance in transactions between related parties. The local report is not a marketing study for setting a product's selling price, nor is it a commercial policy for the market. Its analysis refers to the intercompany transactions reviewed and the evidence that explains the conditions considered.
Nor should it be treated as an automatic conclusion regarding the obligation to submit documents. The existence of a relationship between companies is a fact that must be evaluated in conjunction with the criteria and conditions in force for the taxpayer and the corresponding tax year.
Obligation in Colombia: thresholds and documents that must be verified
Before drafting the report, the company must determine which rules apply to its situation. The answer depends on the taxpayer's circumstances, transactions, and the criteria in effect for the tax year; it should not be assumed that all companies with related parties have the same obligations. It is also advisable to distinguish between regulatory obligations and recommended internal controls: the latter can strengthen the review, but they do not replace legal verification.
The audit must cover, at a minimum, the period under review, the conditions applicable to the taxpayer, the transactions included in the analysis, the relevant thresholds or criteria, and the documents that must be submitted, where applicable. The review of deadlines and formats must also be done for each obligation, rather than deducing it from documents prepared in previous years.
Note on validity: This guide does not specify amounts, due dates, or formats for 2026. These details should be confirmed in current regulations and official information from the DIAN (Colombian Tax Authority) applicable to the tax year being analyzed. It is not advisable to automatically transfer figures from previous periods.
| Checkpoint | What to confirm | Useful document control |
|---|---|---|
| Taxable year and applicable rule | What provisions and conditions apply to the reviewed period? | Record the official source consulted, its date, and the conclusion regarding its scope. |
| Taxpayer and operations | Which entity is being analyzed, with which related parties, and which transactions should be evaluated. | Maintain an inventory of parts and operations, compared with the information available in the company. |
| Thresholds and criteria | What values or current conditions determine the obligations that might apply? | Document the calculation used and the data that supports it, without reusing figures from another period by default. |
| Documents and dates | If applicable, local report, information statement, master report, country-by-country notification or CbC Report, in addition to their applicable deadlines and formats. | Maintain a matrix of obligations with responsible parties, verified dates, and readiness status. |
This matrix is a control tool, not a universal list of legal requirements. Its purpose is to allow the company to explain how it determined its obligations and what evidence supported that decision. If the applicable standard contains specific conditions, the matrix must be adjusted accordingly.
Content and supporting documentation: work structure
Once the scope is defined, the supporting documentation must allow the analysis to be reconstructed without relying on informal explanations. The specific structure should be checked against current requirements, but a practical organization might include the following components:
- Scope and identification: Specify the entity reviewed, the period, the related parties considered, and the scope of the analysis. Record which transactions were included and how the reviewed universe was defined.
- Description of transactions: Explain the nature of each transaction analyzed, the relevant conditions, and the supporting information. The level of detail should help to understand what was done and between whom, not remain within a generic accounting category.
- Contracts and policies: Organize the applicable agreements, transfer pricing policies, and any relevant changes. Identify any discrepancies between what was stipulated in the documents and what actually occurred in practice, and explain how these discrepancies were addressed in the analysis.
- Comparability analysis: Describe the approach used, the data reviewed, the elements of comparison, and the relevant limitations. If adjustments are made or information is discarded, document the reason.
- Conclusion and traceability: Explain how the conclusions were reached and link them to the supporting financial, contractual, and operational evidence. Outstanding observations or relevant assumptions should not be left implicit.
The file can be organized with contracts, policies, transaction records, financial reports, and other supporting documents relevant to the case. The goal is not to accumulate files, but to establish a clear relationship between each document and the part of the analysis it helps to explain. Reconciling the documents with available records also allows for identifying discrepancies before closing the review.
The page of Amezquita's transfer pricing services It describes an offering that includes studies, information statement, local report, master report, country-by-country notification, CbC Report, diagnostics, and analysis of contracts and policies.
Comparability analysis: review of intercompany transactions
Comparability analysis seeks to assess whether the information used provides a useful benchmark for reviewing the terms of a related-party transaction. It does not require that the transactions being compared be identical; rather, it requires explaining why the selected information is relevant and how any differences that could affect the comparison were addressed. Selecting data without context, or without explaining its limitations, makes it difficult for a reviewer to follow the reasoning.
As a working guide, the review can proceed in this order:
- Define the scope of the operation: Identify the parties, the nature of the transaction, the period, and the relevant contractual conditions. Avoid overly broad descriptions that obscure differences between transactions.
- Compare documents and facts: Compare what is stipulated in contracts and policies with the available information on the execution of the operation. Record relevant changes and explain how they were addressed.
- Review the context: Assess, depending on the case, the economic and contractual conditions, the timing of the transaction, and other circumstances that may affect the comparison. Not all factors have the same relevance in every transaction.
- Justify the comparable information: Describe the source of the data, the period to which it corresponds, the selection criteria, and any known limitations. If internal or external comparables are used, explain why they are appropriate for the analysis.
- Connect analysis and conclusion: Document how the evidence supports the outcome and review its consistency with the financial information and documents submitted, where applicable. Investigate any discrepancies before closing the case.
A useful review is not about finding a similar figure and presenting it without explanation. It should show what was compared, why the comparison is reasonable, and what factors might limit its scope. When there is insufficient information to support a conclusion, it is preferable to acknowledge the limitation and avoid making a broader claim than the data allows.
Quality controls and recurring errors
Quality controls help ensure that the report is consistent, verifiable, and useful for decision-making. They can be organized into different stages, from data collection to final review:
Checks before closing the report
- Complete inventory: Compare the list of related parties and transactions with the records available in the responsible departments. Clarify any discrepancies before finalizing the scope.
- Information reconciliation: Verify that the data used in the analysis is consistent with the relevant financial and accounting records, and explain any discrepancies identified.
- Version control: Save the versions of contracts, policies, data, and analyses that served as the basis. Record the date of the regulatory review and the information used.
- Cross-review: Compare the local report with other applicable transfer pricing documents and check that documents with different purposes are not presented as equivalent.
- Independent review by the preparer: Ask another person to follow the thread from the evidence to the conclusion, identify unexplained assumptions, and confirm that the observations are resolved or recorded.
Mistakes that should be avoided
- Copying the report from the previous period without checking if operations, contracts, policies, information, or applicable rules have changed.
- Describing what was agreed in a contract without checking if it matches the information available about the transaction actually carried out.
- Omitting parts or operations of the inventory or describing them with categories that are too general to understand what was analyzed.
- Using data that cannot be reconciled with the company's records or leaving differences unexplained.
- Selecting comparables without documenting the criteria, time period, sources, or limitations of the analysis.
- Confusing the local report with the information statement, the master report or the CbC Report, or applying thresholds from a different year without validating them.
As a final test, someone who did not prepare the document should be able to trace the path from the transaction and its supporting documentation to the analysis and conclusion. If understanding a step requires explanations that are not recorded, the documentation may still need adjustments.