Troubleshooting in NetSuite

Tax codes

If you do not specify the tax code when verifying invoices, and you have a default tax code specified in NetSuite, invoices can be rejected with an error stating that the "transaction does not balance." To avoid this issue with NetSuite, make sure you specify the tax code when verifying invoices.

Location errors

If you receive an error about the location when sending a PO invoice to NetSuite, you can solve this issue by disabling the location validation for line items in NetSuite. To do this in NetSuite:

Navigate to Customization > Forms > Transaction Forms.
Select the form you want to edit.
Then click Edit and navigate to Screen Fields > Items.
Locate the Location field and deselect the box in the Show column.

Numeric EntityID instead of names

If you use a numeric EntityID for your NetSuite vendors, instead of names (the default NetSuite behavior), master data synchronization populates the Tungsten AP Essentials supplier name with the NetSuite vendor number instead of the actual name. You can change this behavior by using the Use Supplier Entity ID as supplier number setting.

Vendors shared between subsidiaries

If you share vendors between subsidiaries in NetSuite, these are not part of the master data synchronization due to limitations in NetSuite. You can work around this limitation by creating subsidiary-specific saved searches that have a criteria for Subsidiary Fields ... > Internal ID set to the specific subsidiary. When using this approach, you need to create one vendor saved search for each subsidiary.

Additional access is needed in order for a NetSuite user/role to query saved searches that span across multiple subsidiaries. To make sure it is working, you can try assigning the Administrator role to the integration user.

Errors after submission to NetSuite

Sometimes a document can be successfully sent to NetSuite, but receive an error in NetSuite after the document record is created. When this happens, the error is noted in the document history in AP Essentials along with the error from NetSuite.

Example

"The document (internal ID: XXXX) was created in NetSuite, but NetSuite replied with an error: Error message from NetSuite."

In this case, do not try to resend the document or correct the issue in AP Essentials. Instead, correct the error in NetSuite because the document has already been successfully created in NetSuite.

When AP Essentials sends documents to NetSuite, the internal ID of the document in NetSuite is used to identify the document and prevent duplicate records in NetSuite in the event of an error as described above.