Scenario: Which thresholds or exemptions could apply to this documentation duty — here, for transfer pricing risk while enjoying tax? — the opening question most companies face on this topic, with reference transactions of around 353,000 USD per period. This article answers under the law as it stands on 20 October 2026, from the source instrument to application and action.
1. The current legal basis
The directly governing framework is Decree 255/2026/ND-CP on tax administration for related-party transactions (replacing Decree 132/2020/ND-CP from 1 July 2026) and the Tax Administration Law 108/2025/QH15 (replacing Law 38/2019/QH14 from 1 July 2026).
The substantive point to grasp first: Incentive periods attract the closest transfer pricing scrutiny because every unit of shifted profit directly reduces the tax being relieved; conversely, once incentives end, the incentive years remain within the audit limitation period and can still be reassessed with penalties. Keep it as the axis for everything below.
Reading the file as an auditor would, small unexplained gaps around the 353,000 USD transaction invite disproportionately deep follow-up, preparing early keeps the company in control when explanations are requested. Placed in the period’s transaction chain, small unexplained gaps around the 353,000 USD transaction invite disproportionately deep follow-up, the file should show this reasoning without a separate request.
2. How the authorities apply it in practice
Viewed from the file itself, the file is compared against third-party data the company does not control for the 353,000 USD transaction, this needs an internal written record in the period it arises. In audit practice, treatment decisions are tested against documents created at the same time as the 353,000 USD transaction, and this is the point to settle before filing anything. Viewed from the file itself, the treatment chosen for the 353,000 USD transaction becomes the silent benchmark for similar transactions, this factor decides most of the explanation outcome later. From comparable cases handled in practice, the topic is read through the document chain of the 353,000 USD transaction in true chronological order, this should be minuted alongside the underlying figures.
3. Working through the questions companies actually ask
Which thresholds or exemptions could apply to this documentation duty — here, for transfer pricing risk while enjoying tax?
The scope of this question must be read narrowly against the actual transaction — “Which thresholds or exemptions could apply to this documentation duty — here, for transfer pricing risk while enjoying tax” — because changing a single element (the performing party, the timing, or the value around the 353,000 USD mark) changes the applicable conclusion. Viewed from the file itself, the disputed point usually shrinks to one document in the 353,000 USD transaction file, this needs an internal written record in the period it arises. In audit practice, the argument only stands when the independent comparison source was kept in the same period as the 353,000 USD transaction, and this is the point to settle before filing anything. Viewed from the file itself, the dispute narrows once the company separates the evidenced part from the missing part around the 353,000 USD transaction, this factor decides most of the explanation outcome later.
How should the company prepare before the audit team arrives — here, for transfer pricing risk while enjoying tax?
The scope of this question must be read narrowly against the actual transaction — “How should the company prepare before the audit team arrives — here, for transfer pricing risk while enjoying tax” — because changing a single element (the performing party, the timing, or the value around the 353,000 USD mark) changes the applicable conclusion. For the finance team preparing the file, the right reading cross-checks contract, invoice and cash flow of the 353,000 USD transaction at the same time, and this is the point to settle before filing anything. Placed in the period’s transaction chain, preparing the counter-argument for the 353,000 USD transaction in advance changes the tone of the meeting, preparing early keeps the company in control when explanations are requested. Viewed from the file itself, what persuades here is a short evidence chain rather than a long narrative about the 353,000 USD transaction, this needs an internal written record in the period it arises.
What documentation proves this transaction was priced at arm’s length — here, for transfer pricing risk while enjoying tax?
The scope of this question must be read narrowly against the actual transaction — “What documentation proves this transaction was priced at arm’s length — here, for transfer pricing risk while enjoying tax” — because changing a single element (the performing party, the timing, or the value around the 353,000 USD mark) changes the applicable conclusion. For the finance team preparing the file, framing the 353,000 USD transaction by its business purpose first makes the pricing discussion shorter, preparing early keeps the company in control when explanations are requested. Recent finalisation cycles show that what persuades here is a short evidence chain rather than a long narrative about the 353,000 USD transaction, this is where preparation time earns its return. Viewed from the file itself, the answer here must anchor in the evidence of the 353,000 USD transaction instead of industry custom, this factor decides most of the explanation outcome later.
4. Procedure and the file to prepare
- Compliance calendar: build a tracing table for the 353,000 USD transaction from contract to payment record and reconcile it with the period return — this needs an internal written record in the period it arises.
- Archive test: remove every citation to a replaced instrument from the file and substitute the provision currently in force — this needs an internal written record in the period it arises.
- Internal sign-off: record the owner, the basis used and the points still disputed in the chosen treatment — and this is the point to settle before filing anything.
- Internal sign-off: record the owner, the basis used and the points still disputed in the chosen treatment — this factor decides most of the explanation outcome later.
- Compliance calendar: place the topic on the annual compliance calendar with its own deadline per task instead of bunching into finalisation — this should be minuted alongside the underlying figures.
5. Risks and action conclusion
From comparable cases handled in practice, an underestimated risk is late-payment interest accumulating on the tax of the 353,000 USD transaction, the related figures must agree with the audited financial statements of the same period. At the level of daily operations, insurance and indemnity clauses rarely cover the tax cost of the 353,000 USD transaction, the file should show this reasoning without a separate request. In audit practice, timing risk arises because the 353,000 USD transaction may be reviewed under guidance issued after it closed, this is where preparation time earns its return.
Conclusion: Placed in the period’s transaction chain, the depth of the explanation file must match the 353,000 USD value of the transaction being explained, the related figures must agree with the audited financial statements of the same period. When the matter reaches an inspection table, treatment decisions are tested against documents created at the same time as the 353,000 USD transaction, the file should show this reasoning without a separate request.
6. A worked illustration
To make the order of operations concrete, take a transaction in scope worth USD 426,250 in the period. If the related obligation is measured at a reference rate of 20% of the transaction value, the amount to compute for this transaction alone is USD 85,250 — before any treaty relief, incentive or credit is considered. The illustration shows why classification must precede computation: on the same USD 426,250 value, misclassifying the nature of the transaction moves that USD 85,250 figure away from what is actually payable.
Seen from the authority’s side of the table, the conclusion flips if a single element of the 353,000 USD transaction changes, so the answer must attach to the specific file, this needs an internal written record in the period it arises. At the level of daily operations, framing the 353,000 USD transaction by its business purpose first makes the pricing discussion shorter, this is also what the audit team reconciles first against the return. For the finance team preparing the file, a persuasive answer names who owned the 353,000 USD transaction and under which decision, this needs an internal written record in the period it arises.
Frequently asked questions
1. Which thresholds or exemptions could apply to this documentation duty — here, for transfer pricing risk while enjoying tax?
On “Which thresholds or exemptions could apply to this documentation duty — here, for transfer pricing risk while enjoying tax”: Placed in the period’s transaction chain, the argument only stands when the independent comparison source was kept in the same period as the 353,000 USD transaction, preparing early keeps the company in control when explanations are requested. Viewed from the file itself, a persuasive answer names who owned the 353,000 USD transaction and under which decision, the same logic will be applied to the next period unless documented otherwise. Against the backdrop of the current framework, the authority tests this point on a small transaction sample before extending it across the period around the 353,000 USD mark, the file should show this reasoning without a separate request. Seen from the authority’s side of the table, what persuades here is a short evidence chain rather than a long narrative about the 353,000 USD transaction, and this is the point to settle before filing anything.
2. How should the company prepare before the audit team arrives — here, for transfer pricing risk while enjoying tax?
On “How should the company prepare before the audit team arrives — here, for transfer pricing risk while enjoying tax”: At the level of daily operations, the answer here must anchor in the evidence of the 353,000 USD transaction instead of industry custom, this workstream needs a clearly named owner inside the compliance function. Viewed from the file itself, the conclusion flips if a single element of the 353,000 USD transaction changes, so the answer must attach to the specific file, the file should show this reasoning without a separate request. Seen from the authority’s side of the table, what persuades here is a short evidence chain rather than a long narrative about the 353,000 USD transaction, the file should show this reasoning without a separate request. When the matter reaches an inspection table, framing the 353,000 USD transaction by its business purpose first makes the pricing discussion shorter, every later adjustment must trace back to the decision taken at this point.
3. What documentation proves this transaction was priced at arm’s length — here, for transfer pricing risk while enjoying tax?
On “What documentation proves this transaction was priced at arm’s length — here, for transfer pricing risk while enjoying tax”: From comparable cases handled in practice, a persuasive answer names who owned the 353,000 USD transaction and under which decision, the related figures must agree with the audited financial statements of the same period. Viewed from the file itself, the disputed point usually shrinks to one document in the 353,000 USD transaction file, every later adjustment must trace back to the decision taken at this point. Recent finalisation cycles show that the dispute narrows once the company separates the evidenced part from the missing part around the 353,000 USD transaction, the file should show this reasoning without a separate request. Placed in the period’s transaction chain, the answer improves once the 353,000 USD transaction is separated from group-wide generalisations, every later adjustment must trace back to the decision taken at this point.
This article has been quality-reviewed by the FLAW AI Legal Council