Scenario: How should the company prepare before the audit team arrives — here, for preparing transfer pricing documentation for an? — the opening question most companies face on this topic, with reference transactions of around 406,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: The first year is not a documentation-free year: pricing policies and related-party contracts must be built from the very first transaction, because documentation prepared retroactively after an audit opens usually lacks contemporaneous evidence and is discounted. Keep it as the axis for everything below.
At the level of daily operations, the authority compares treatments across periods to find anomalies around the 406,000 USD transaction, the related figures must agree with the audited financial statements of the same period. From comparable cases handled in practice, economic substance is placed ahead of contract form for the 406,000 USD transaction, this is also what the audit team reconciles first against the return.
2. How the authorities apply it in practice
Viewed from the file itself, the authority builds its view from samples and extends it to the 406,000 USD transaction only if the sample fails, the file should show this reasoning without a separate request. For the finance team preparing the file, consistency of pricing logic across the 406,000 USD transaction and its neighbours is what is really being tested, this needs an internal written record in the period it arises. When the matter reaches an inspection table, the bottleneck usually sits in evidence retention for the 406,000 USD transaction rather than in legal theory, this needs an internal written record in the period it arises. From comparable cases handled in practice, the topic is read through the document chain of the 406,000 USD transaction in true chronological order, this should be minuted alongside the underlying figures.
3. Working through the questions companies actually ask
How should the company prepare before the audit team arrives — here, for preparing transfer pricing documentation for an?
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 preparing transfer pricing documentation for an” — because changing a single element (the performing party, the timing, or the value around the 406,000 USD mark) changes the applicable conclusion. Viewed from the file itself, the company should answer for the 406,000 USD transaction as it was documented at the time, not as it is understood today, the file should show this reasoning without a separate request. For the finance team preparing the file, what persuades here is a short evidence chain rather than a long narrative about the 406,000 USD transaction, this needs an internal written record in the period it arises. When the matter reaches an inspection table, the conclusion flips if a single element of the 406,000 USD transaction changes, so the answer must attach to the specific file, this needs an internal written record in the period it arises.
What documentation proves this transaction was priced at arm’s length — here, for preparing transfer pricing documentation for an?
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 preparing transfer pricing documentation for an” — because changing a single element (the performing party, the timing, or the value around the 406,000 USD mark) changes the applicable conclusion. In audit practice, what persuades here is a short evidence chain rather than a long narrative about the 406,000 USD transaction, this should be minuted alongside the underlying figures. At the level of daily operations, preparing the counter-argument for the 406,000 USD transaction in advance changes the tone of the meeting, this should be minuted alongside the underlying figures. Placed in the period’s transaction chain, preparing the counter-argument for the 406,000 USD transaction in advance changes the tone of the meeting, every later adjustment must trace back to the decision taken at this point.
Which transfer pricing method fits this transaction best, and why — here, for preparing transfer pricing documentation for an?
The scope of this question must be read narrowly against the actual transaction — “Which transfer pricing method fits this transaction best, and why — here, for preparing transfer pricing documentation for an” — because changing a single element (the performing party, the timing, or the value around the 406,000 USD mark) changes the applicable conclusion. Against the backdrop of the current framework, credibility rises visibly when the company presents both sides of the 406,000 USD transaction, this is also what the audit team reconciles first against the return. From comparable cases handled in practice, what persuades here is a short evidence chain rather than a long narrative about the 406,000 USD transaction, preparing early keeps the company in control when explanations are requested. Viewed from the file itself, framing the 406,000 USD transaction by its business purpose first makes the pricing discussion shorter, preparing early keeps the company in control when explanations are requested.
4. Procedure and the file to prepare
- Internal sign-off: record the owner, the basis used and the points still disputed in the chosen treatment — the file should show this reasoning without a separate request.
- Compliance calendar: build a tracing table for the 406,000 USD transaction from contract to payment record and reconcile it with the period return — the file should show this reasoning without a separate request.
- Evidence building: record the owner, the basis used and the points still disputed in the chosen treatment — this needs an internal written record in the period it arises.
- Evidence building: test that the full file can be produced within one working day of a request — this needs an internal written record in the period it arises.
- Archive test: cross-check the figures between the return, the financial statements and the topic file before anything is sent out — this should be minuted alongside the underlying figures.
5. Risks and action conclusion
Placed in the period’s transaction chain, timing risk arises because the 406,000 USD transaction may be reviewed under guidance issued after it closed, the related figures must agree with the audited financial statements of the same period. For the finance team preparing the file, the same weakness repeated across periods converts a small point on the 406,000 USD transaction into a pattern finding, this needs an internal written record in the period it arises. Seen from the authority’s side of the table, the largest risk is figures diverging between filing streams on the same 406,000 USD transaction, this should be minuted alongside the underlying figures.
Conclusion: When the matter reaches an inspection table, the internal approval chain for the 406,000 USD transaction forms part of the file rather than an annex, this needs an internal written record in the period it arises. Once the authority starts its review, small unexplained gaps around the 406,000 USD transaction invite disproportionately deep follow-up, this needs an internal written record in the period it arises.
6. A worked illustration
To make the order of operations concrete, take a transaction in scope worth USD 481,250 in the period. If the related obligation is measured at a reference rate of 2% of the transaction value, the amount to compute for this transaction alone is USD 9,625 — before any treaty relief, incentive or credit is considered. The illustration shows why classification must precede computation: on the same USD 481,250 value, misclassifying the nature of the transaction moves that USD 9,625 figure away from what is actually payable.
Seen from the authority’s side of the table, the argument only stands when the independent comparison source was kept in the same period as the 406,000 USD transaction, this is also what the audit team reconciles first against the return. For the finance team preparing the file, the conclusion flips if a single element of the 406,000 USD transaction changes, so the answer must attach to the specific file, this should be minuted alongside the underlying figures. Once the authority starts its review, this point should be settled before finalisation season to avoid retroactive fixes on the 406,000 USD transaction, every later adjustment must trace back to the decision taken at this point.
Frequently asked questions
1. How should the company prepare before the audit team arrives — here, for preparing transfer pricing documentation for an?
On “How should the company prepare before the audit team arrives — here, for preparing transfer pricing documentation for an”: Viewed from the file itself, a persuasive answer names who owned the 406,000 USD transaction and under which decision, this factor decides most of the explanation outcome later. When the matter reaches an inspection table, the right reading cross-checks contract, invoice and cash flow of the 406,000 USD transaction at the same time, this factor decides most of the explanation outcome later. Against the backdrop of the current framework, framing the 406,000 USD transaction by its business purpose first makes the pricing discussion shorter, this factor decides most of the explanation outcome later. Seen from the authority’s side of the table, the authority tests this point on a small transaction sample before extending it across the period around the 406,000 USD mark, this is where preparation time earns its return.
2. What documentation proves this transaction was priced at arm’s length — here, for preparing transfer pricing documentation for an?
On “What documentation proves this transaction was priced at arm’s length — here, for preparing transfer pricing documentation for an”: Viewed from the file itself, the immediate task is to freeze the evidence set of the 406,000 USD transaction in its current state, every later adjustment must trace back to the decision taken at this point. Placed in the period’s transaction chain, the disputed point usually shrinks to one document in the 406,000 USD transaction file, this factor decides most of the explanation outcome later. Reading the file as an auditor would, the disputed point usually shrinks to one document in the 406,000 USD transaction file, this is also what the audit team reconciles first against the return. From comparable cases handled in practice, preparing the counter-argument for the 406,000 USD transaction in advance changes the tone of the meeting, this needs an internal written record in the period it arises.
3. Which transfer pricing method fits this transaction best, and why — here, for preparing transfer pricing documentation for an?
On “Which transfer pricing method fits this transaction best, and why — here, for preparing transfer pricing documentation for an”: When the matter reaches an inspection table, the right reading cross-checks contract, invoice and cash flow of the 406,000 USD transaction at the same time, the file should show this reasoning without a separate request. When the matter reaches an inspection table, the immediate task is to freeze the evidence set of the 406,000 USD transaction in its current state, the file should show this reasoning without a separate request. Once the authority starts its review, preparing the counter-argument for the 406,000 USD transaction in advance changes the tone of the meeting, this is where preparation time earns its return. At the level of daily operations, the answer here must anchor in the evidence of the 406,000 USD transaction instead of industry custom, the file should show this reasoning without a separate request.