Scenario: How will the tax authority test the price on audit — here, for annual updates to transfer pricing documentation? — the opening question most companies face on this topic, with reference transactions of around 419,250 USD per period. Under the law as it stands on 20 October 2026, this article moves from the source instrument to how authorities apply it and what the company must do.
1. The current legal basis
The framework that governs directly 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: An annual update does not mean rewriting everything: the functional analysis is redone only when the business model truly changes, while the comparable set and financial data must be refreshed every year because the arm’s-length range moves with the industry cycle. Everything below returns to that point.
For the finance team preparing the file, the file is compared against third-party data the company does not control for the 419,250 USD transaction, skipping it on the 419,250 transaction leaves the company explaining from a defensive position at inspection. Seen from the authority’s side of the table, treatment decisions are tested against documents created at the same time as the 419,250 USD transaction, recording it early around the 419,250 transaction keeps the company on the front foot in every later meeting.
2. Application in practice by the authority
Once the authority starts its review, the bottleneck usually sits in evidence retention for the 419,250 USD transaction rather than in legal theory, the basis relied on for the 419,250 transaction should be filed alongside, so the argument never has to be rebuilt. Seen from the authority’s side of the table, the review follows the money first and the paperwork second for the 419,250 USD transaction, this point, on the 419,250 transaction, should be revisited whenever new guiding instruments are issued. Placed in the period’s transaction chain, the review follows the money first and the paperwork second for the 419,250 USD transaction, the figures of the 419,250 transaction must agree exactly with the financial statements of the same period. From comparable cases handled in practice, the authority compares treatments across periods to find anomalies around the 419,250 USD transaction, the figures of the 419,250 transaction must agree exactly with the financial statements of the same period.
3. Working through the questions companies actually ask
How will the tax authority test the price on audit — here, for annual updates to transfer pricing documentation?
The scope of this question must be read narrowly against the actual transaction — “How will the tax authority test the price on audit — here, for annual updates to transfer pricing documentation” — because changing a single element (the performing party, the timing, or the value around the 419,250 USD mark) changes the applicable conclusion. Once the authority starts its review, the conclusion flips if a single element of the 419,250 USD transaction changes, so the answer must attach to the specific file, every later adjustment must be reconciled against the decision recorded on the 419,250 transaction. Seen from the authority’s side of the table, the answer improves once the 419,250 USD transaction is separated from group-wide generalisations, this belongs in the file of the 419,250 transaction from the period it arises, not at finalisation time. Placed in the period’s transaction chain, the answer improves once the 419,250 USD transaction is separated from group-wide generalisations, careful work on the 419,250 transaction shortens the inspection timetable materially.
What contemporaneous evidence should the company keep for this transaction — here, for annual updates to transfer pricing documentation?
The scope of this question must be read narrowly against the actual transaction — “What contemporaneous evidence should the company keep for this transaction — here, for annual updates to transfer pricing documentation” — because changing a single element (the performing party, the timing, or the value around the 419,250 USD mark) changes the applicable conclusion. From comparable cases handled in practice, the authority tests this point on a small transaction sample before extending it across the period around the 419,250 USD mark, and this is the point to settle before the company signs any commitment around the 419,250 transaction. Placed in the period’s transaction chain, this point should be settled before finalisation season to avoid retroactive fixes on the 419,250 USD transaction, this is the first thing the tax authority will ask when the 419,250 transaction file is opened. Recent finalisation cycles show that the dispute narrows once the company separates the evidenced part from the missing part around the 419,250 USD transaction, the workstream around the 419,250 transaction needs one continuous owner rather than handovers mid-stream.
What happens if the authority reassesses the price — what remedies exist — here, for annual updates to transfer pricing documentation?
The scope of this question must be read narrowly against the actual transaction — “What happens if the authority reassesses the price — what remedies exist — here, for annual updates to transfer pricing documentation” — because changing a single element (the performing party, the timing, or the value around the 419,250 USD mark) changes the applicable conclusion. Against the backdrop of the current framework, the conclusion flips if a single element of the 419,250 USD transaction changes, so the answer must attach to the specific file, this should sit in the recurring compliance calendar for the 419,250 transaction rather than wait for an incident. Reading the file as an auditor would, the disputed point usually shrinks to one document in the 419,250 USD transaction file, the more complete the 419,250 transaction file at inception, the cheaper every later explanation becomes. Reading the file as an auditor would, the answer here must anchor in the evidence of the 419,250 USD transaction instead of industry custom, this should sit in the recurring compliance calendar for the 419,250 transaction rather than wait for an incident.
4. Procedure and the file to prepare
- Evidence building: cross-check the figures between the return, the financial statements and the topic file before anything is sent out — the workstream around the 419,250 transaction needs one continuous owner rather than handovers mid-stream.
- Compliance calendar: test that the full file can be produced within one working day of a request — the figures of the 419,250 transaction must agree exactly with the financial statements of the same period.
- Basis check: cross-check the figures between the return, the financial statements and the topic file before anything is sent out — every later adjustment must be reconciled against the decision recorded on the 419,250 transaction.
- Document review: record the owner, the basis used and the points still disputed in the chosen treatment — the figures of the 419,250 transaction must agree exactly with the financial statements of the same period.
- Compliance calendar: record the owner, the basis used and the points still disputed in the chosen treatment — this should sit in the recurring compliance calendar for the 419,250 transaction rather than wait for an incident.
5. Risks and action conclusion
In audit practice, post-audit remediation always costs many times more than prevention for the 419,250 USD transaction, recording it early around the 419,250 transaction keeps the company on the front foot in every later meeting. Recent finalisation cycles show that the board-level consequence of an assessment on the 419,250 USD transaction is often larger than the tax itself, this is what separates an explanation-ready 419,250 transaction file from a patched-together one. At the level of daily operations, group-level reporting can expose the 419,250 USD transaction even where local filing looked clean, the conclusion taken on the 419,250 transaction becomes the benchmark for later transactions of the same kind.
Conclusion: When the matter reaches an inspection table, the file is compared against third-party data the company does not control for the 419,250 USD transaction, this should sit in the recurring compliance calendar for the 419,250 transaction rather than wait for an incident. Reading the file as an auditor would, economic substance is placed ahead of contract form for the 419,250 USD transaction, every related figure must trace back to the source documents of the 419,250 transaction itself.
6. A worked illustration
To make the order of operations concrete, take a transaction in scope worth USD 495,000 in the period. If the related obligation is measured at a reference rate of 1% of the transaction value, the amount to compute for this transaction alone is USD 4,950 — before any treaty relief, incentive or credit is considered. The illustration shows why classification must precede computation: on the same USD 495,000 value, misclassifying the nature of the transaction moves that USD 4,950 figure away from what is actually payable.
Seen from the authority’s side of the table, the immediate task is to freeze the evidence set of the 419,250 USD transaction in its current state, and this is the point to settle before the company signs any commitment around the 419,250 transaction. Placed in the period’s transaction chain, what persuades here is a short evidence chain rather than a long narrative about the 419,250 USD transaction, skipping it on the 419,250 transaction leaves the company explaining from a defensive position at inspection. Seen from the authority’s side of the table, the answer here must anchor in the evidence of the 419,250 USD transaction instead of industry custom, this belongs in the file of the 419,250 transaction from the period it arises, not at finalisation time.
Frequently asked questions
1. How will the tax authority test the price on audit — here, for annual updates to transfer pricing documentation?
On “How will the tax authority test the price on audit — here, for annual updates to transfer pricing documentation”: When the matter reaches an inspection table, the immediate task is to freeze the evidence set of the 419,250 USD transaction in its current state, this is what separates an explanation-ready 419,250 transaction file from a patched-together one. For the finance team preparing the file, the conclusion flips if a single element of the 419,250 USD transaction changes, so the answer must attach to the specific file, recording it early around the 419,250 transaction keeps the company on the front foot in every later meeting. Once the authority starts its review, the company should answer for the 419,250 USD transaction as it was documented at the time, not as it is understood today, this is the first thing the tax authority will ask when the 419,250 transaction file is opened. Placed in the period’s transaction chain, the answer improves once the 419,250 USD transaction is separated from group-wide generalisations, the conclusion taken on the 419,250 transaction becomes the benchmark for later transactions of the same kind.
2. What contemporaneous evidence should the company keep for this transaction — here, for annual updates to transfer pricing documentation?
On “What contemporaneous evidence should the company keep for this transaction — here, for annual updates to transfer pricing documentation”: Against the backdrop of the current framework, a persuasive answer names who owned the 419,250 USD transaction and under which decision, this belongs in the file of the 419,250 transaction from the period it arises, not at finalisation time. For the finance team preparing the file, the authority tests this point on a small transaction sample before extending it across the period around the 419,250 USD mark, this is the first thing the tax authority will ask when the 419,250 transaction file is opened. In audit practice, the authority tests this point on a small transaction sample before extending it across the period around the 419,250 USD mark, the more complete the 419,250 transaction file at inception, the cheaper every later explanation becomes. In audit practice, preparing the counter-argument for the 419,250 USD transaction in advance changes the tone of the meeting, the conclusion taken on the 419,250 transaction becomes the benchmark for later transactions of the same kind.
3. What happens if the authority reassesses the price — what remedies exist — here, for annual updates to transfer pricing documentation?
On “What happens if the authority reassesses the price — what remedies exist — here, for annual updates to transfer pricing documentation”: Reading the file as an auditor would, framing the 419,250 USD transaction by its business purpose first makes the pricing discussion shorter, this needs written internal confirmation, for the 419,250 transaction, from the officer responsible for compliance. At the level of daily operations, the right reading cross-checks contract, invoice and cash flow of the 419,250 USD transaction at the same time, and this is the point to settle before the company signs any commitment around the 419,250 transaction. Against the backdrop of the current framework, framing the 419,250 USD transaction by its business purpose first makes the pricing discussion shorter, every later adjustment must be reconciled against the decision recorded on the 419,250 transaction. When the matter reaches an inspection table, the answer improves once the 419,250 USD transaction is separated from group-wide generalisations, this belongs in the file of the 419,250 transaction from the period it arises, not at finalisation time.
This article has been quality-reviewed by the FLAW AI Legal Council