You are upgrading to the most current version of Sage X3. Everything is going well; however, you are having some issues getting Sage Sales Tax (SST) up and running. What can you do to troubleshoot? Here are a few items to check out:
- When you are setting up SST, use the most current instructions, not ones that you may have previously downloaded. Go to the Online help center, How to (1) tab, Distribution (2) menu, Implement Sage Sales Tax (3).
- Java Bridge is not required on versions v11 and higher for batch processing.
- Is Avalara having issues? It may not be your system! Check out https://status.avalara.com. Avalara’s service status dashboard provides product updates in real time. You can receive all status notifications by clicking Subscribe to updates on this page and choose your notification preferences to be via text or email.
- As of 2021R4 (12.0.28) or Syracuse 12.13, the Test URL and Production URL changed. These URL values must be correct, or you will receive an Information message “Connection error: sstPing:500” when you click Ping Sage Sales Tax. The ping must be successful to process SST.
- Verify REST V2 URLs are defined in Setup, Usage, Sage Sales Tax connection (LTPAR)
- New V2 REST Test URL: https://sandbox-rest.avatax.com
- New V2 REST Production URL: https://rest.avatax.com
- Be sure the URL doesn’t end with a forward slash (/) or doesn’t have a blank space at the beginning or end.
- If you have custom URLs, check with your Avalara representative.
- While we are in Sage Sales Tax connection, verify that the Account and License key values are correct.
- Eliminate blanks at the beginning and end of the Account and License values.
- Check with your Avalara representative if you are unsure of the correct values.
- Verify that Activation is selected on the Others tab under Setup, Organizational structure, Companies (GESCPY). Sage Sales Tax Company should be completed. It should match the company in the Avalara dashboard. Again, ensure that there are no pesky blank spaces either at the beginning or end of the tax company value.
- Customizations can interfere with SST. Did SST work before or without the customization? You can use the Object Difference Analyzer (ACOMPOBJ) to identify customizations. See thisa Sage X3 Support blog for instructions on how to use the function: How to find what I changed in a folder (aka what did I break this time) https://www.sagecity.com/us/sage_x3/b/sageerp_x3_product_support_blog/posts/how-to-find-what-i-changed-in-a-folder-aka-what-did-i-break-this-time. It is a handy tool and not just for SST troubleshooting.
- Miscellaneous
- It is highly recommended you request separate test and production accounts. Although this is not required, it gives you the flexibility to continue testing (if desired) after the credit card process has been moved to production. Contact your Avalara representative to obtain a separate test account.
- SST uses the United States Postal Service (USPS) database of Validated addresses, as well as the Postal Addressing Standards used by the USPS in addition to the Canada Post Service.
- Validating the address may change the address format to conform to USPS requirements.
- If the address does not exist in the USPS database, contact your Avalara representative.
- Example: business park management creates its own streets and addresses within the park.
- Error: “Invalid country code.”
- Avalara uses only two-character ISO 3166 country codes.
- ISO stands for International Organization for Standardization.
- Sage and Avalara no longer support TLS 1.0 and 1.1 effective December 31st, 2022.
- If you start doing business in a new state, it must be setup in Avalara.
Hope these tips help you as you work with Sage Sales Tax.
Take care my X3 friends. Stay safe!