Scenario: How is the payment classified — goods, services, royalties or interest — and why does it matter — here, for contractor tax on crossborder service fees? — the opening question most companies face on this topic, with reference transactions of around 652,750 USD per period. The analysis below follows the law at 20 October 2026 exactly: the instrument, its application in practice, then the necessary action.
1. The current legal basis
The directly applicable framework is Corporate Income Tax Law 67/2025/QH15, Decree 320/2025/ND-CP and Circular 20/2026/TT-BTC — the current foreign contractor tax framework; the contractor CIT rules in Circular 103/2014/TT-BTC were repealed from 12 March 2026 (except point b.11, clause 1, Article 13).
The substantive point to grasp first: Cross-border service fees bear contractor tax even when the service is performed entirely abroad if the beneficiary is an organisation in Vietnam; advertising and digital platform services take the ordinary-service rates of 5% VAT and 5% CIT under the 2026 framework. Keep that point in view throughout the sections that follow.
From comparable cases handled in practice, treatment decisions are tested against documents created at the same time as the 652,750 USD transaction, this is the first thing the tax authority will ask when the 652,750 transaction file is opened. Viewed from the file itself, treatment decisions are tested against documents created at the same time as the 652,750 USD transaction, the figures of the 652,750 transaction must agree exactly with the financial statements of the same period.
2. How the authority applies this in practice
Once the authority starts its review, the bottleneck usually sits in evidence retention for the 652,750 USD transaction rather than in legal theory, careful work on the 652,750 transaction shortens the inspection timetable materially. Against the backdrop of the current framework, documentation created before the 652,750 USD transaction closed carries materially more weight, this should sit in the recurring compliance calendar for the 652,750 transaction rather than wait for an incident. Reading the file as an auditor would, the authority compares treatments across periods to find anomalies around the 652,750 USD transaction, careful work on the 652,750 transaction shortens the inspection timetable materially. In audit practice, the depth of the explanation file must match the 652,750 USD value of the transaction being explained, the basis relied on for the 652,750 transaction should be filed alongside, so the argument never has to be rebuilt.
3. Working through the questions companies actually ask
How is the payment classified — goods, services, royalties or interest — and why does it matter — here, for contractor tax on crossborder service fees?
The scope of this question must be read narrowly against the actual transaction — “How is the payment classified — goods, services, royalties or interest — and why does it matter — here, for contractor tax on crossborder service fees” — because changing a single element (the performing party, the timing, or the value around the 652,750 USD mark) changes the applicable conclusion. Once the authority starts its review, the conclusion flips if a single element of the 652,750 USD transaction changes, so the answer must attach to the specific file, the figures of the 652,750 transaction must agree exactly with the financial statements of the same period. Against the backdrop of the current framework, framing the 652,750 USD transaction by its business purpose first makes the pricing discussion shorter, this is what separates an explanation-ready 652,750 transaction file from a patched-together one. Reading the file as an auditor would, the immediate task is to freeze the evidence set of the 652,750 USD transaction in its current state, this should sit in the recurring compliance calendar for the 652,750 transaction rather than wait for an incident.
What changes for contracts signed after the hybrid method was abolished — here, for contractor tax on crossborder service fees?
The scope of this question must be read narrowly against the actual transaction — “What changes for contracts signed after the hybrid method was abolished — here, for contractor tax on crossborder service fees” — because changing a single element (the performing party, the timing, or the value around the 652,750 USD mark) changes the applicable conclusion. Viewed from the file itself, the conclusion flips if a single element of the 652,750 USD transaction changes, so the answer must attach to the specific file, this point, on the 652,750 transaction, should be revisited whenever new guiding instruments are issued. Against the backdrop of the current framework, a persuasive answer names who owned the 652,750 USD transaction and under which decision, and this is the point to settle before the company signs any commitment around the 652,750 transaction. When the matter reaches an inspection table, the conclusion flips if a single element of the 652,750 USD transaction changes, so the answer must attach to the specific file, recording it early around the 652,750 transaction keeps the company on the front foot in every later meeting.
Which documents should be kept to defend the classification on audit — here, for contractor tax on crossborder service fees?
The scope of this question must be read narrowly against the actual transaction — “Which documents should be kept to defend the classification on audit — here, for contractor tax on crossborder service fees” — because changing a single element (the performing party, the timing, or the value around the 652,750 USD mark) changes the applicable conclusion. Recent finalisation cycles show that the company should answer for the 652,750 USD transaction as it was documented at the time, not as it is understood today, recording it early around the 652,750 transaction keeps the company on the front foot in every later meeting. Reading the file as an auditor would, the company should answer for the 652,750 USD transaction as it was documented at the time, not as it is understood today, this belongs in the file of the 652,750 transaction from the period it arises, not at finalisation time. When the matter reaches an inspection table, this point should be settled before finalisation season to avoid retroactive fixes on the 652,750 USD transaction, every later adjustment must be reconciled against the decision recorded on the 652,750 transaction.
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 — recording it early around the 652,750 transaction keeps the company on the front foot in every later meeting.
- Document review: add an independent comparison source from the time the 652,750 USD transaction arose, preferring publicly verifiable material — this belongs in the file of the 652,750 transaction from the period it arises, not at finalisation time.
- Evidence building: record the owner, the basis used and the points still disputed in the chosen treatment — skipping it on the 652,750 transaction leaves the company explaining from a defensive position at inspection.
- Document review: cross-check the figures between the return, the financial statements and the topic file before anything is sent out — this is what separates an explanation-ready 652,750 transaction file from a patched-together one.
- Internal sign-off: prepare answers to the most frequent auditor questions about the 652,750 USD transaction with evidence locations noted — recording it early around the 652,750 transaction keeps the company on the front foot in every later meeting.
5. Risks and action conclusion
When the matter reaches an inspection table, propagation risk shows when the same error appears in every transaction similar to the 652,750 USD item, this is the minimum needed for the company’s conclusion on the 652,750 transaction to hold under challenge. Seen from the authority’s side of the table, an underestimated risk is late-payment interest accumulating on the tax of the 652,750 USD transaction, this belongs in the file of the 652,750 transaction from the period it arises, not at finalisation time. From comparable cases handled in practice, the same weakness repeated across periods converts a small point on the 652,750 USD transaction into a pattern finding, this is the first thing the tax authority will ask when the 652,750 transaction file is opened.
Conclusion: Seen from the authority’s side of the table, the internal approval chain for the 652,750 USD transaction forms part of the file rather than an annex, recording it early around the 652,750 transaction keeps the company on the front foot in every later meeting. When the matter reaches an inspection table, documentation created before the 652,750 USD transaction closed carries materially more weight, the conclusion taken on the 652,750 transaction becomes the benchmark for later transactions of the same kind.
6. A worked illustration
To make the order of operations concrete, take a transaction in scope worth USD 770,000 in the period. If the related obligation is measured at a reference rate of 8% of the transaction value, the amount to compute for this transaction alone is USD 61,600 — before any treaty relief, incentive or credit is considered. The illustration shows why classification must precede computation: on the same USD 770,000 value, misclassifying the nature of the transaction moves that USD 61,600 figure away from what is actually payable.
Recent finalisation cycles show that the right reading cross-checks contract, invoice and cash flow of the 652,750 USD transaction at the same time, every related figure must trace back to the source documents of the 652,750 transaction itself. Seen from the authority’s side of the table, the answer improves once the 652,750 USD transaction is separated from group-wide generalisations, and this is the point to settle before the company signs any commitment around the 652,750 transaction. At the level of daily operations, credibility rises visibly when the company presents both sides of the 652,750 USD transaction, this belongs in the file of the 652,750 transaction from the period it arises, not at finalisation time.
Frequently asked questions
1. How is the payment classified — goods, services, royalties or interest — and why does it matter — here, for contractor tax on crossborder service fees?
On “How is the payment classified — goods, services, royalties or interest — and why does it matter — here, for contractor tax on crossborder service fees”: Placed in the period’s transaction chain, the company should answer for the 652,750 USD transaction as it was documented at the time, not as it is understood today, the more complete the 652,750 transaction file at inception, the cheaper every later explanation becomes. From comparable cases handled in practice, framing the 652,750 USD transaction by its business purpose first makes the pricing discussion shorter, this needs written internal confirmation, for the 652,750 transaction, from the officer responsible for compliance. Recent finalisation cycles show that a persuasive answer names who owned the 652,750 USD transaction and under which decision, this should sit in the recurring compliance calendar for the 652,750 transaction rather than wait for an incident. At the level of daily operations, framing the 652,750 USD transaction by its business purpose first makes the pricing discussion shorter, every later adjustment must be reconciled against the decision recorded on the 652,750 transaction.
2. What changes for contracts signed after the hybrid method was abolished — here, for contractor tax on crossborder service fees?
On “What changes for contracts signed after the hybrid method was abolished — here, for contractor tax on crossborder service fees”: Seen from the authority’s side of the table, what persuades here is a short evidence chain rather than a long narrative about the 652,750 USD transaction, the figures of the 652,750 transaction must agree exactly with the financial statements of the same period. When the matter reaches an inspection table, the answer improves once the 652,750 USD transaction is separated from group-wide generalisations, the figures of the 652,750 transaction must agree exactly with the financial statements of the same period. From comparable cases handled in practice, a persuasive answer names who owned the 652,750 USD transaction and under which decision, skipping it on the 652,750 transaction leaves the company explaining from a defensive position at inspection. When the matter reaches an inspection table, a persuasive answer names who owned the 652,750 USD transaction and under which decision, the figures of the 652,750 transaction must agree exactly with the financial statements of the same period.
3. Which documents should be kept to defend the classification on audit — here, for contractor tax on crossborder service fees?
On “Which documents should be kept to defend the classification on audit — here, for contractor tax on crossborder service fees”: 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 652,750 USD mark, and this is the point to settle before the company signs any commitment around the 652,750 transaction. When the matter reaches an inspection table, the disputed point usually shrinks to one document in the 652,750 USD transaction file, the basis relied on for the 652,750 transaction should be filed alongside, so the argument never has to be rebuilt. Reading the file as an auditor would, what persuades here is a short evidence chain rather than a long narrative about the 652,750 USD transaction, the figures of the 652,750 transaction must agree exactly with the financial statements of the same period. Recent finalisation cycles show that the conclusion flips if a single element of the 652,750 USD transaction changes, so the answer must attach to the specific file, this is also the basis for the company’s own review of the 652,750 transaction before each next filing period.