Some NetSuite settings can be enabled, tested, then disabled if the result isn’t right. SuiteTax isn’t one of them. Once it is enabled, there is no going back.
That’s why the question “SuiteTax or Legacy Tax?” deserves more than a quick answer. On one side, Legacy Tax, the older tax engine that many companies have used for years. On the other, SuiteTax, the modern engine on which NetSuite now focuses all its development.
At SuiteVise, our teams work with both engines every day. Here, in simple terms, is what you need to know: how each one works, their pros and cons, their real limitations and their impact on the rest of NetSuite.
Legacy Tax and SuiteTax in a nutshell
Legacy Tax is NetSuite’s original tax engine. It relies on manually configured tax codes and tax groups, supplemented by several bundles for international needs (international tax reports, tax audit files, supplementary tax calculations, withholding tax). It works, it is well known, and many older accounts still run on it.
SuiteTax is the next-generation tax engine. Instead of hard-coding tax logic into tax codes, it relies on a calculation engine: NetSuite’s own or that of a specialized provider such as Avalara. Rates are updated automatically, and international coverage is much broader.
Two key points to keep in mind right away:
- SuiteTax is enabled for the whole NetSuite account, not for a particular subsidiary.
- Enabling it is irreversible. You cannot go back to Legacy Tax once SuiteTax is enabled.
How the two engines work (without going into detail)
Legacy Tax: tax carried on the line
With Legacy Tax, the logic is straightforward. Each transaction line carries a tax code (or tax group) with its rate. The tax amount is calculated immediately on the line, and the line itself holds the tax information. What the user sees on screen is exactly what is stored.
It is easy to understand, easy to query in a saved search and easy to handle in a script.
SuiteTax: tax calculated by an engine
With SuiteTax, the logic changes. The transaction is sent to a tax engine, which determines the tax from several factors: the subsidiary, its tax registration, that of the customer or vendor, the item type, the ship-to location, and so on.
In the interface, this translates into a few new habits:
- Tax is calculated when the transaction is saved, or on demand with the Preview Tax button, which lets you see the tax before confirming.
- The result appears in a dedicated Tax Details subtab, no longer directly on the lines.
- The tax code shown on the transaction is no longer the starting point of the calculation: it mainly records the engine’s answer.
The real complexity: tax data that is no longer on the lines
This is the key point, and the most underestimated one. In SuiteTax, tax information is no longer carried on transaction lines as it is in Legacy Tax. It is stored in separate tables linked to the transaction: tax details, subsidiary and entity tax registrations, tax types, and so on.
For users, this change is almost invisible. For anything that reads or writes tax data, it’s another story:
- Saved searches and reports have to fetch tax from these new tables, with joins you need to know how to build.
- Scripts and workflows that read or changed tax on the lines have to be designed differently.
- Integrations (e-commerce, CRM, billing tools, data warehouses) have to get and send tax information in the right place.
- In SuiteAnalytics, SuiteTax information is exposed in the NetSuite2.com data source.
Key takeaway: SuiteTax requires real technical skills on top of tax expertise. A VAT report that “worked” in Legacy Tax can’t be rebuilt identically in SuiteTax just by changing a field.
SuiteTax vs Legacy Tax: the comparison
| Criterion | Legacy Tax | SuiteTax |
|---|---|---|
| Calculation logic | Tax code and rate on each line | Tax engine that calculates from the context |
| Where tax data is stored | On transaction lines | In separate tables (tax details) |
| Rate updates | Manual, country by country | Automatic, through the tax engine |
| Country coverage | About 40 preconfigured countries | About 180 countries |
| VAT numbers per entity | One per subsidiary, customer or vendor | Several tax registrations possible |
| Exemptions | At the general customer level | More granular, including by item |
| Reporting basis | Transaction date and tax periods | Tax point date and accounting periods |
| Third-party engines (Avalara…) | Older integrations | Certified engines can be plugged in |
| International bundles | Required | Replaced by compatible features and SuiteApps |
| Scope | — | The whole NetSuite account, permanent activation |
The advantages of SuiteTax
- Less maintenance: rates and rules change without your teams having to reconfigure everything.
- A true international tool: ideal for groups present in many countries.
- Several VAT numbers per entity: essential for a company registered for VAT in several countries.
- An open engine: you can plug in a specialized tax engine.
- Some module combinations depend on it, as we will see below with SuiteBilling.
The drawbacks of SuiteTax
- Permanent activation, for the whole account.
- A more complex data architecture: tax lives in separate tables, which complicates reports, scripts and integrations.
- Less intuitive logic: tax is no longer readable directly on the lines, and teams have to learn new habits (Preview Tax, tax details).
- Features still missing for some cases, detailed below.
- A greater need for technical skills, on top of tax expertise.
The pros and cons of Legacy Tax
Its main advantage: simplicity. Tax is visible and stored on the line, easy to check, extract and script. It covers the needs of a company with domestic or fairly simple taxation very well. Its drawbacks: manual rate maintenance, more limited international coverage, a single VAT number per entity, and reliance on several additional bundles as soon as you go beyond the domestic setting.
SuiteTax limitations to know about
SuiteTax is more powerful, but it isn’t complete yet. NetSuite itself publishes a list of known limitations. Here are the ones we check systematically:
- Partially deductible VAT. NetSuite’s tax engine does not yet natively handle partially deductible VAT, or reverse charge on those purchases. An important point for some French companies, especially those with a VAT recovery ratio.
- Withholding tax on payments. NetSuite’s tax engine only calculates it when the invoice or vendor bill is created, not at payment time. A sensitive issue for subsidiaries in Morocco, elsewhere in Africa or in other countries that apply withholding tax.
- Tax periods. They give way to the tax point date. Reporting habits need to be adjusted.
- Late charges. In Legacy Tax, tax on late charges was calculated automatically. In SuiteTax, it has to be added manually.
- Some transactions and features have no tax fields or aren’t supported yet, such as advanced intercompany journal entries or in-store pickup in the United States.
- Incompatible bundles. Tax bundles designed for Legacy Tax don’t work with SuiteTax and must be replaced by their equivalents.
Beware: for several of these cases, partners offer complementary solutions. But you need to know before activation, not after.
SuiteTax and other modules: what to anticipate
The choice of tax engine isn’t only about VAT. It has consequences for other NetSuite modules and features.
- SuiteBilling and multi-subsidiary customers. SuiteBilling and the Multi-Subsidiary Customer feature each work with Legacy Tax. But if you want to use them together, SuiteTax becomes necessary: tax lookup on a customer with several tax registrations only works correctly with SuiteTax. A key point for software companies and international groups.
- Tax bundles. Bundles designed for Legacy Tax (international tax reports, tax audit files, supplementary tax calculations, withholding tax) are not compatible with SuiteTax. They are replaced by equivalent features or SuiteApps, which need to be identified.
- Country localizations. Localization SuiteApps must be compatible with the engine you use. You need to check, country by country, what is available.
- Partner SuiteApps. A SuiteApp that handles tax data must support both engines. Before installing a third-party solution, check that it supports yours.
- External tax engines. Solutions such as Avalara plug into SuiteTax as certified engines. This is often the route chosen for complex US taxation.
- Reporting and integrations. As seen above, since tax data is no longer on the lines in SuiteTax, every report, extract or integration that involves tax must be designed to fetch it from the right place.
How to choose between Legacy Tax and SuiteTax?
There is no one-size-fits-all answer. Here are the questions we ask our clients:
- How many countries are you in, and do you plan to expand? The broader your international presence, the more sense SuiteTax makes.
- Do you have several VAT numbers for the same entity? If so, SuiteTax is practically unavoidable.
- Which modules do you use or plan to use? SuiteBilling combined with multi-subsidiary customers, for example, requires SuiteTax.
- Do you have specific tax cases? Partially deductible VAT, withholding tax: check that they are covered, natively or by a partner.
- How many reports, scripts and integrations involve tax? The more there are, the more SuiteTax’s data architecture needs to be taken into account.
- Do you have the technical skills to run it? SuiteTax requires a good command of NetSuite’s data model.
One rule applies in every case: since enabling SuiteTax is permanent, everything is tested first in a test environment (sandbox), never directly in production.
Frequently asked questions
What is the difference between SuiteTax and Legacy Tax?
Legacy Tax is NetSuite’s older tax engine, based on manually configured tax codes. SuiteTax is the modern engine: it relies on a calculation engine, updates rates automatically and covers many more countries.
Can you go back to Legacy Tax after enabling SuiteTax?
No. Enabling SuiteTax is permanent and applies to the whole NetSuite account.
Does SuiteTax handle every French VAT case?
Most of them, but not all. Partially deductible VAT, for example, is not yet handled natively by NetSuite’s engine. Check your specific cases before enabling SuiteTax.
Where is tax information stored with SuiteTax?
In separate tables linked to the transaction (tax details), no longer on the transaction lines as in Legacy Tax. That’s what makes reports, scripts and integrations more complex to build.
What is the Preview Tax button for?
It runs the tax engine’s calculation so you can see the tax before saving the transaction. The result appears in the Tax Details subtab.
Does SuiteBilling work with Legacy Tax?
Yes. However, if you combine SuiteBilling with multi-subsidiary customers, SuiteTax is required.
In short: SuiteTax is the future, but it takes preparation
SuiteTax brings more automated, more international and more open tax management. It is clearly the direction NetSuite is taking. But it is also a permanent change, with real limitations in some cases, such as partially deductible VAT or withholding tax.
Legacy Tax remains a simple, readable engine, suited to domestic or fairly simple taxation. SuiteTax is more powerful but more technically demanding, especially because tax data lives in separate tables. The right choice depends on your international footprint, your modules, your specific tax cases and the skills available to you.
Still on Legacy Tax, or wondering whether SuiteTax covers all your needs? SuiteVise offers a SuiteTax review: an analysis of your taxation, your customizations and the risks, with clear recommendations. Let’s take 30 minutes to talk it through.