Scenario: How are research and development costs treated under this regime — here, for tax incentives for new projects by? — the opening question most companies face on this topic, with reference transactions of around 613,000 USD per period. Every assessment in this article follows the law as it stands on 20 October 2026, from source instrument to application and action.
1. The current legal basis
The instruments governing this topic directly are Investment Law 143/2025/QH15 on investment incentives and Corporate Income Tax Law 67/2025/QH15 on separate accounting for each project’s income.
The substantive point to grasp first: A new project by an existing investor is assessed for incentives independently by the new project’s own location and sector; incentives cannot be pooled across projects, and income must be accounted separately — failing that, allocation by revenue ratio applies under close tax scrutiny. Keep that point in view throughout the sections that follow.
Against the backdrop of the current framework, treatment decisions are tested against documents created at the same time as the 613,000 USD transaction, the basis relied on for the 613,000 transaction should be filed alongside, so the argument never has to be rebuilt. Reading the file as an auditor would, the bottleneck usually sits in evidence retention for the 613,000 USD transaction rather than in legal theory, the basis relied on for the 613,000 transaction should be filed alongside, so the argument never has to be rebuilt.
2. How the authority applies this in practice
Viewed from the file itself, the authority builds its view from samples and extends it to the 613,000 USD transaction only if the sample fails, recording it early around the 613,000 transaction keeps the company on the front foot in every later meeting. At the level of daily operations, the treatment chosen for the 613,000 USD transaction becomes the silent benchmark for similar transactions, this belongs in the file of the 613,000 transaction from the period it arises, not at finalisation time. Placed in the period’s transaction chain, treatment decisions are tested against documents created at the same time as the 613,000 USD transaction, this is also the basis for the company’s own review of the 613,000 transaction before each next filing period. Once the authority starts its review, the internal approval chain for the 613,000 USD transaction forms part of the file rather than an annex, the figures of the 613,000 transaction must agree exactly with the financial statements of the same period.
3. Working through the questions companies actually ask
How are research and development costs treated under this regime — here, for tax incentives for new projects by?
The scope of this question must be read narrowly against the actual transaction — “How are research and development costs treated under this regime — here, for tax incentives for new projects by” — because changing a single element (the performing party, the timing, or the value around the 613,000 USD mark) changes the applicable conclusion. Viewed from the file itself, the company should answer for the 613,000 USD transaction as it was documented at the time, not as it is understood today, and this is the point to settle before the company signs any commitment around the 613,000 transaction. At the level of daily operations, the dispute narrows once the company separates the evidenced part from the missing part around the 613,000 USD transaction, the basis relied on for the 613,000 transaction should be filed alongside, so the argument never has to be rebuilt. Placed in the period’s transaction chain, the argument only stands when the independent comparison source was kept in the same period as the 613,000 USD transaction, this is what separates an explanation-ready 613,000 transaction file from a patched-together one.
Can incentives from an old project extend to a new one — here, for tax incentives for new projects by?
The scope of this question must be read narrowly against the actual transaction — “Can incentives from an old project extend to a new one — here, for tax incentives for new projects by” — because changing a single element (the performing party, the timing, or the value around the 613,000 USD mark) changes the applicable conclusion. Viewed from the file itself, the right reading cross-checks contract, invoice and cash flow of the 613,000 USD transaction at the same time, this belongs in the file of the 613,000 transaction from the period it arises, not at finalisation time. Placed in the period’s transaction chain, the answer here must anchor in the evidence of the 613,000 USD transaction instead of industry custom, every related figure must trace back to the source documents of the 613,000 transaction itself. Viewed from the file itself, the answer improves once the 613,000 USD transaction is separated from group-wide generalisations, the basis relied on for the 613,000 transaction should be filed alongside, so the argument never has to be rebuilt.
Which documents prove the incentive conditions are still met — here, for tax incentives for new projects by?
The scope of this question must be read narrowly against the actual transaction — “Which documents prove the incentive conditions are still met — here, for tax incentives for new projects by” — because changing a single element (the performing party, the timing, or the value around the 613,000 USD mark) changes the applicable conclusion. In audit practice, the answer improves once the 613,000 USD transaction is separated from group-wide generalisations, this needs written internal confirmation, for the 613,000 transaction, from the officer responsible for compliance. Against the backdrop of the current framework, a persuasive answer names who owned the 613,000 USD transaction and under which decision, this is the part of the 613,000 transaction file that decides the outcome of the first explanation round. Once the authority starts its review, credibility rises visibly when the company presents both sides of the 613,000 USD transaction, the conclusion taken on the 613,000 transaction becomes the benchmark for later transactions of the same kind.
4. Procedure and the file to prepare
- Archive test: test that the full file can be produced within one working day of a request — this is the part of the 613,000 transaction file that decides the outcome of the first explanation round.
- Basis check: remove every citation to a replaced instrument from the file and substitute the provision currently in force — careful work on the 613,000 transaction shortens the inspection timetable materially.
- Document review: test that the full file can be produced within one working day of a request — this belongs in the file of the 613,000 transaction from the period it arises, not at finalisation time.
- Archive test: remove every citation to a replaced instrument from the file and substitute the provision currently in force — and this is the point to settle before the company signs any commitment around the 613,000 transaction.
- Basis check: place the topic on the annual compliance calendar with its own deadline per task instead of bunching into finalisation — this needs written internal confirmation, for the 613,000 transaction, from the officer responsible for compliance.
5. Risks and action conclusion
When the matter reaches an inspection table, the company’s compliance reputation suffers long after a single assessment on the 613,000 USD transaction, the conclusion taken on the 613,000 transaction becomes the benchmark for later transactions of the same kind. From comparable cases handled in practice, an adjustment on the 613,000 USD transaction usually extends the review into neighbouring periods, the basis relied on for the 613,000 transaction should be filed alongside, so the argument never has to be rebuilt. Seen from the authority’s side of the table, limitation periods mean older files can still be reopened around the 613,000 USD transaction, the workstream around the 613,000 transaction needs one continuous owner rather than handovers mid-stream.
Conclusion: Against the backdrop of the current framework, the treatment chosen for the 613,000 USD transaction becomes the silent benchmark for similar transactions, this is what separates an explanation-ready 613,000 transaction file from a patched-together one. Once the authority starts its review, consistency of pricing logic across the 613,000 USD transaction and its neighbours is what is really being tested, this is the first thing the tax authority will ask when the 613,000 transaction file is opened.
6. A worked illustration
To make the order of operations concrete, take a transaction in scope worth USD 728,750 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 14,575 — before any treaty relief, incentive or credit is considered. The illustration shows why classification must precede computation: on the same USD 728,750 value, misclassifying the nature of the transaction moves that USD 14,575 figure away from what is actually payable.
Recent finalisation cycles show that the disputed point usually shrinks to one document in the 613,000 USD transaction file, the conclusion taken on the 613,000 transaction becomes the benchmark for later transactions of the same kind. Against the backdrop of the current framework, preparing the counter-argument for the 613,000 USD transaction in advance changes the tone of the meeting, this point, on the 613,000 transaction, should be revisited whenever new guiding instruments are issued. When the matter reaches an inspection table, credibility rises visibly when the company presents both sides of the 613,000 USD transaction, this belongs in the file of the 613,000 transaction from the period it arises, not at finalisation time.
Frequently asked questions
1. How are research and development costs treated under this regime — here, for tax incentives for new projects by?
On “How are research and development costs treated under this regime — here, for tax incentives for new projects by”: Reading the file as an auditor would, a persuasive answer names who owned the 613,000 USD transaction and under which decision, the basis relied on for the 613,000 transaction should be filed alongside, so the argument never has to be rebuilt. For the finance team preparing the file, the immediate task is to freeze the evidence set of the 613,000 USD transaction in its current state, careful work on the 613,000 transaction shortens the inspection timetable materially. Once the authority starts its review, framing the 613,000 USD transaction by its business purpose first makes the pricing discussion shorter, this should sit in the recurring compliance calendar for the 613,000 transaction rather than wait for an incident. When the matter reaches an inspection table, framing the 613,000 USD transaction by its business purpose first makes the pricing discussion shorter, this is also the basis for the company’s own review of the 613,000 transaction before each next filing period.
2. Can incentives from an old project extend to a new one — here, for tax incentives for new projects by?
On “Can incentives from an old project extend to a new one — here, for tax incentives for new projects by”: Placed in the period’s transaction chain, this point should be settled before finalisation season to avoid retroactive fixes on the 613,000 USD transaction, this should sit in the recurring compliance calendar for the 613,000 transaction rather than wait for an incident. Recent finalisation cycles show that a persuasive answer names who owned the 613,000 USD transaction and under which decision, the basis relied on for the 613,000 transaction should be filed alongside, so the argument never has to be rebuilt. Seen from the authority’s side of the table, this point should be settled before finalisation season to avoid retroactive fixes on the 613,000 USD transaction, recording it early around the 613,000 transaction keeps the company on the front foot in every later meeting. For the finance team preparing the file, the right reading cross-checks contract, invoice and cash flow of the 613,000 USD transaction at the same time, skipping it on the 613,000 transaction leaves the company explaining from a defensive position at inspection.
3. Which documents prove the incentive conditions are still met — here, for tax incentives for new projects by?
On “Which documents prove the incentive conditions are still met — here, for tax incentives for new projects by”: When the matter reaches an inspection table, the argument only stands when the independent comparison source was kept in the same period as the 613,000 USD transaction, every related figure must trace back to the source documents of the 613,000 transaction itself. Recent finalisation cycles show that the disputed point usually shrinks to one document in the 613,000 USD transaction file, every later adjustment must be reconciled against the decision recorded on the 613,000 transaction. Against the backdrop of the current framework, framing the 613,000 USD transaction by its business purpose first makes the pricing discussion shorter, this is what separates an explanation-ready 613,000 transaction file from a patched-together one. Viewed from the file itself, the dispute narrows once the company separates the evidenced part from the missing part around the 613,000 USD transaction, this needs written internal confirmation, for the 613,000 transaction, from the officer responsible for compliance.
4. Which conditions decide whether this project keeps its incentives — here, for tax incentives for new projects by?
On “Which conditions decide whether this project keeps its incentives — here, for tax incentives for new projects by”: For the finance team preparing the file, the disputed point usually shrinks to one document in the 613,000 USD transaction file, and this is the point to settle before the company signs any commitment around the 613,000 transaction. From comparable cases handled in practice, credibility rises visibly when the company presents both sides of the 613,000 USD transaction, this is the part of the 613,000 transaction file that decides the outcome of the first explanation round. Recent finalisation cycles show that the company should answer for the 613,000 USD transaction as it was documented at the time, not as it is understood today, and this is the point to settle before the company signs any commitment around the 613,000 transaction. Against the backdrop of the current framework, the dispute narrows once the company separates the evidenced part from the missing part around the 613,000 USD transaction, recording it early around the 613,000 transaction keeps the company on the front foot in every later meeting.
This article has been quality-reviewed by the FLAW AI Legal Council
