Overview
One of the most common use-cases for NetSuite is the functionality to support multiple sales channels, all flowing into NetSuite.
For example, if I am an E-Commerce and B2B seller, I have a combination of my E-Commerce platform sales and transactions originating out of NetSuite.
Why does this matter?
Zamp needs to fully understand your quote-to-cash process, and where transactions originate to:
Ensure there are no duplicate transactions being posted to your Zamp account.
Zamp is not recalculating tax on transactions that you have already charged a customer for.
Common Workflow
The below diagram outlines a business selling on an E-Commerce platform, a marketplace platform, and also creating invoices out of NetSuite:
How does the Integration with NetSuite handle this?
Standard Tax
If SuiteTax is NOT enabled, Zamp determines whether Zamp should be calculating tax on Cash Sales, Invoices, Sales Orders, and Credit Memos based on the Tax Item configured for a customer.
Note: The Tax Item is the Zamp Tax Code configured during the installation of the bundle. It would be configured in this step of Zamp's Standard Tax Configuration Guide.
Is Tax Item Zamp Tax at time of transaction creation? | Zamp Tax Calculation | Transaction Posted to Zamp? |
No | No | Yes |
Yes | Yes | Yes |
The Tax Item will be configured as such within a customer record
Integration Connector Responsibility
If you are using a connector such as Celigo to push transactions from external platforms (e-commerce or marketplace), you will need to ensure the mapping that determines how transactions are generated in NetSuite set the customer's Tax Item set as a non-Zamp code.
How to Verify
You can verify a transaction was posted without Zamp Tax calculations via the Zamp Tax Steps on a given transaction. Look for External Tax Codes Detected. Confirm the tax amount imported from the integration connector matches what was posted in Zamp.
SuiteTax
For SuiteTax enabled accounts, the tax configuration within NetSuite is altered significantly. Instead of determining if Zamp should be calculating tax at the customer-level, the integration will determine this at the transaction-level.
Is the Skip Calculation setting enabled when the transaction is saved? | Zamp Tax Calculation | Transaction Posted to Zamp? |
No | Yes | Yes |
Yes | No | Yes |
The "ZAMP | SKIP CALCULATION" setting is a mappable field at the transaction-level
Integration Connector Responsibility
If you are using a connector such as Celigo to push transactions from external platforms (e-commerce or marketplace), you will need to ensure the mapping that determines how transactions are generated in NetSuite have Zamp | Skip Calculation enabled for each transaction.
How to Verify
You can verify a transaction was posted without Zamp Tax calculations via the Zamp Tax Steps on a given transaction. Look for User Skip Calc Override. Confirm the tax amount imported from the integration connector matches what was posted in Zamp.
