Scenario: What contemporaneous evidence should the company keep for this transaction — here, for pricing technical support services from a? — the opening question most companies face on this topic, with reference transactions of around 530,750 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: Technical support services are usually priced on a cost-plus basis over the personnel and direct costs of the technical team, with a mark-up benchmarked against comparable independent technical service providers. Keep it as the axis for everything below.
Placed in the period’s transaction chain, the authority compares treatments across periods to find anomalies around the 530,750 USD transaction, this should be minuted alongside the underlying figures. Recent finalisation cycles show that consistency of pricing logic across the 530,750 USD transaction and its neighbours is what is really being tested, and this is the point to settle before filing anything.
2. How the authorities apply it in practice
Seen from the authority’s side of the table, documentation created before the 530,750 USD transaction closed carries materially more weight, the file should show this reasoning without a separate request. Against the backdrop of the current framework, consistency of pricing logic across the 530,750 USD transaction and its neighbours is what is really being tested, and this is the point to settle before filing anything. For the finance team preparing the file, the authority compares treatments across periods to find anomalies around the 530,750 USD transaction, this is where preparation time earns its return. Seen from the authority’s side of the table, economic substance is placed ahead of contract form for the 530,750 USD transaction, this factor decides most of the explanation outcome later.
3. Working through the questions companies actually ask
What contemporaneous evidence should the company keep for this transaction — here, for pricing technical support services from a?
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 pricing technical support services from a” — because changing a single element (the performing party, the timing, or the value around the 530,750 USD mark) changes the applicable conclusion. Seen from the authority’s side of the table, framing the 530,750 USD transaction by its business purpose first makes the pricing discussion shorter, the file should show this reasoning without a separate request. Against the backdrop of the current framework, what persuades here is a short evidence chain rather than a long narrative about the 530,750 USD transaction, and this is the point to settle before filing anything. For the finance team preparing the file, the immediate task is to freeze the evidence set of the 530,750 USD transaction in its current state, this is where preparation time earns its return.
What happens if the authority reassesses the price — what remedies exist — here, for pricing technical support services from a?
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 pricing technical support services from a” — because changing a single element (the performing party, the timing, or the value around the 530,750 USD mark) changes the applicable conclusion. In audit practice, the argument only stands when the independent comparison source was kept in the same period as the 530,750 USD transaction, preparing early keeps the company in control when explanations are requested. For the finance team preparing the file, the immediate task is to freeze the evidence set of the 530,750 USD transaction in its current state, and this is the point to settle before filing anything. From comparable cases handled in practice, the disputed point usually shrinks to one document in the 530,750 USD transaction file, the same logic will be applied to the next period unless documented otherwise.
How does this transaction interact with customs valuation or other filings — here, for pricing technical support services from a?
The scope of this question must be read narrowly against the actual transaction — “How does this transaction interact with customs valuation or other filings — here, for pricing technical support services from a” — because changing a single element (the performing party, the timing, or the value around the 530,750 USD mark) changes the applicable conclusion. Against the backdrop of the current framework, the immediate task is to freeze the evidence set of the 530,750 USD transaction in its current state, this needs an internal written record in the period it arises. Recent finalisation cycles show that the immediate task is to freeze the evidence set of the 530,750 USD transaction in its current state, this workstream needs a clearly named owner inside the compliance function. Reading the file as an auditor would, this point should be settled before finalisation season to avoid retroactive fixes on the 530,750 USD transaction, this needs an internal written record in the period it arises.
4. Procedure and the file to prepare
- Document review: test that the full file can be produced within one working day of a request — and this is the point to settle before filing anything.
- Archive test: test that the full file can be produced within one working day of a request — the file should show this reasoning without a separate request.
- Document review: test that the full file can be produced within one working day of a request — and this is the point to settle before filing anything.
- Compliance calendar: record the owner, the basis used and the points still disputed in the chosen treatment — this is where preparation time earns its return.
- Archive test: place the topic on the annual compliance calendar with its own deadline per task instead of bunching into finalisation — this factor decides most of the explanation outcome later.
5. Risks and action conclusion
Reading the file as an auditor would, the board-level consequence of an assessment on the 530,750 USD transaction is often larger than the tax itself, this is where preparation time earns its return. Recent finalisation cycles show that the same weakness repeated across periods converts a small point on the 530,750 USD transaction into a pattern finding, this is where preparation time earns its return. Reading the file as an auditor would, an underestimated risk is late-payment interest accumulating on the tax of the 530,750 USD transaction, this is where preparation time earns its return.
Conclusion: Once the authority starts its review, the bottleneck usually sits in evidence retention for the 530,750 USD transaction rather than in legal theory, this is also what the audit team reconciles first against the return. For the finance team preparing the file, risk grows with the distance between the booked price and the market range for the 530,750 USD transaction, 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 632,500 in the period. If the related obligation is measured at a reference rate of 10% of the transaction value, the amount to compute for this transaction alone is USD 63,250 — before any treaty relief, incentive or credit is considered. The illustration shows why classification must precede computation: on the same USD 632,500 value, misclassifying the nature of the transaction moves that USD 63,250 figure away from what is actually payable.
From comparable cases handled in practice, the right reading cross-checks contract, invoice and cash flow of the 530,750 USD transaction at the same time, this is where preparation time earns its return. Once the authority starts its review, this point should be settled before finalisation season to avoid retroactive fixes on the 530,750 USD transaction, this workstream needs a clearly named owner inside the compliance function. Seen from the authority’s side of the table, a persuasive answer names who owned the 530,750 USD transaction and under which decision, this is also what the audit team reconciles first against the return.
Frequently asked questions
1. What contemporaneous evidence should the company keep for this transaction — here, for pricing technical support services from a?
On “What contemporaneous evidence should the company keep for this transaction — here, for pricing technical support services from a”: Against the backdrop of the current framework, a persuasive answer names who owned the 530,750 USD transaction and under which decision, and this is the point to settle before filing anything. Against the backdrop of the current framework, this point should be settled before finalisation season to avoid retroactive fixes on the 530,750 USD transaction, the file should show this reasoning without a separate request. Reading the file as an auditor would, credibility rises visibly when the company presents both sides of the 530,750 USD transaction, the file should show this reasoning without a separate request. In audit practice, the company should answer for the 530,750 USD transaction as it was documented at the time, not as it is understood today, and this is the point to settle before filing anything.
2. What happens if the authority reassesses the price — what remedies exist — here, for pricing technical support services from a?
On “What happens if the authority reassesses the price — what remedies exist — here, for pricing technical support services from a”: For the finance team preparing the file, the immediate task is to freeze the evidence set of the 530,750 USD transaction in its current state, this factor decides most of the explanation outcome later. Reading the file as an auditor would, preparing the counter-argument for the 530,750 USD transaction in advance changes the tone of the meeting, the file should show this reasoning without a separate request. In audit practice, preparing the counter-argument for the 530,750 USD transaction in advance changes the tone of the meeting, this factor decides most of the explanation outcome later. At the level of daily operations, the authority tests this point on a small transaction sample before extending it across the period around the 530,750 USD mark, this workstream needs a clearly named owner inside the compliance function.
3. How does this transaction interact with customs valuation or other filings — here, for pricing technical support services from a?
On “How does this transaction interact with customs valuation or other filings — here, for pricing technical support services from a”: Seen from the authority’s side of the table, this point should be settled before finalisation season to avoid retroactive fixes on the 530,750 USD transaction, every later adjustment must trace back to the decision taken at this point. Recent finalisation cycles show that the argument only stands when the independent comparison source was kept in the same period as the 530,750 USD transaction, this is where preparation time earns its return. At the level of daily operations, the authority tests this point on a small transaction sample before extending it across the period around the 530,750 USD mark, this needs an internal written record in the period it arises. Seen from the authority’s side of the table, what persuades here is a short evidence chain rather than a long narrative about the 530,750 USD transaction, this needs an internal written record in the period it arises.
This article has been quality-reviewed by the FLAW AI Legal Council