Troubleshooting Guide for SuiteTax

The nexus on the sales transaction is not from the country you expect. For example, the nexus shows "California" instead of "Texas".

NetSuite determines the nexus to use based on the following information:

• location

• shipping address

• subsidiary address

• entity tax registration

For more information about the nexus determination logic, see Nexus Determination Lookup Logic in SuiteTax.

Review the nexus determination logic and compare it against the transaction details, such as location or shipping address.

For more information, see Nexus Determination on Sales Transactions.

If you are working on a purchase transaction, see Nexus Determination on Purchase Transactions.

The tax codes available on the transaction are not from the country you expect. For example, the tax code list on your transaction shows the UK tax codes instead of the German ones.

• On a transaction, only the nexuses associated to the subsidiary can be used.

• The tax code list is based on the transaction nexus.

• The tax code list on a transaction contains the tax codes that are in the same country as the transaction nexus.

Review the relevant tax code lookup logic and compare it against the transaction details, such as location or shipping address.

For more information, see:

• Tax Code Lookup Logic for United States.

• Tax Code Lookup Logic for VAT Countries.

• One Stop Shop (OSS) for SuiteTax Lookup Logic.

The default tax code set on the customer record is not used on the transaction.

• You can set a default tax code or tax group on your entity records under the Tax Registrations subtab.

• The tax code set as default is then used on the transaction. Select your customer or vendor tax registration number matching your transaction nexus. For example, you define your default tax codes on the customer Tax Registrations subtab for nexus 1 and nexus 2. After that, when you create an invoice with nexus 2, the SuiteTax Engine then uses the default tax code for nexus 2.

Check if the customer or vendor tax registration number is filled under the Tax Details subtab on the transaction.

You are receiving these error messages when trying to set a "Valid Until" date on your subsidiary tax registration:

"The tax registration () cannot be saved because there are existing transactions later than the Valid Until date. Make sure that the new Valid Until date is later than the date of the last transaction." OR

"There are existing transactions before the date you entered. Make sure that the new Effective From date is earlier than the date of the first transaction."

Ensure that the "Valid Until" date is later than the date of the last transaction for the relevant subsidiary tax registration.

Create a report to find out the date of the last transaction for the relevant subsidiary tax registration.

1. Go to Lists > Search > Saved Searches > New.

2. Select "Transaction"

   .

3. Add the following filters:

   1. Subsidiary: set the value for subsidiary where you want to set the "Valid Until" date.

   2. Nexus: set the nexus for which you want to set the "Valid Until" date.

   3. Date: specify the "Valid Until" date in the Date field. When you are editing the field, select the "after" filter.

4. Go to the Results subtab.

   1. Sort by date.

   2. Check the Descending box next to the Sort By field.

5. Save your search.

Adjust the "Valid Until" date based on the date of the last transaction. For example, the date set as "Valid Until" is "09/30/2024" and the date of the last transaction is "09/30/2024". You should adjust the "Valid Until" date to "10/01/2024".

You are receiving this error message when trying to create a transaction (for example, invoice, vendor bill, and some other taxable transaction):

"The tax registrations setup for the subsidiary associated with the transaction is incomplete. If you want taxes to be calculated for the relevant nexus, you must select a tax engine. Otherwise, mark the nexus as tax-exempt. Go to the subsidiary to complete the setup. You may need to contact your administrator to perform this action."

The subsidiary tax registration setup must be completed before you can create a transaction. If you want your taxes to be calculated for the related nexus, you need to select a tax engine. Otherwise, mark the subsidiary tax registration as tax exempt to skip the tax engine assignment and disable the tax calculation on transactions.

Go to the subsidiary record and check the nexuses on the subsidiary tax registrations to ensure that one of these is true:

• a tax engine is selected.

• the Tax-Exempt box is checked.

If neither configuration setting has been set, you need to configure one before you can proceed in the transaction creation.

"Unable to save the transaction due to an error being reported by the tax calculation engine: Tax Calculation Plugin error: NetSuite was not able to estimate the correct Nexus for this transaction. Based on the Nexus Determination Lookup Logic in SuiteTax, NetSuite has determined the Ship From country country A, Ship To country country B and the Subsidiary country country C, these countries do not match any Subsidiary Tax Registration. You must have an active nexus that matches one of the countries identified in the nexus lookup logic. If you want taxes to be calculated for the nexus, set up the nexus and assign a tax engine. Otherwise, mark the nexus as tax-exempt. Go to the subsidiary to complete the setup. You may need to contact your administrator to perform this action."

This error is displayed when NetSuite cannot match the countries or the U.S. states to the nexus associated to the subsidiary.

For example, on the transaction, you have "New York" as shipping address, and "Arizona" as location. Then, on the subsidiary, the address is "California". The nexus associated to the subsidiary is "Florida".

In this situation, you get the mentioned error. The reason is that NetSuite cannot match the relevant addresses to the nexus associated to the subsidiary.

Check the following:

1. Shipping address, location address of the transaction.

2. Go to the subsidiary record, and check if any of the addresses matches to the nexuses on the subsidiary tax registration.

The subsidiary tax registration should have at least one nexus that matches to the addresses that were used in the nexus determination.

For more information about nexus determination, see Nexus Determination Lookup Logic in SuiteTax.

You have enabled the Multiple Shipping Routes (MSR) feature and the Enable Item Line Shipping preference on your sales transaction. You are receiving this error when trying to add another item line on your sales transaction:

"NetSuite doesn't support multiple nexuses within one transaction. The nexus determined for this line is not the same as the nexus determined for the first item line. See Nexus Determination Lookup Logic in SuiteTax. Create a separate transaction for this line."

When the nexus determined for the new item line is the same as the nexus of the first item line, you can select different addresses. For more information, see Nexus Determination Lookup Logic in SuiteTax.

The error appears if the nexus determined for the new item line is different from the nexus determined for the first item line. NetSuite supports a single nexus on the transaction.

For more information about the single nexus validation, see Multiple Shipping Routes, specifically the section on "To add multiple shipping routes on a transaction" for SuiteTax.

You need to create a separate transaction for the line that triggers the single nexus validation.