- How this works
- How is it configured?
- What if I don't see a matching tax code from my accounting system?
- Limitations
How This Works
Each time an Order is synced, the tax code applied to each product in the order is matched to a corresponding tax code in the accounting service.
How Is It Configured?
Simply navigate to the Manage menu, then scroll down to the heading reading Map Tax Codes. If you've already configured your settings, you'll need to select Edit on the workflow for the integration of orders
On this screen, the tax codes that have been found in BigCommerce are displayed to the left and on the right are drop-down fields that allow you to select the corresponding tax code from those that have been found in your accounting system.
All you'll need to do here is select the corresponding tax code from your accounting system. Once completed, save your changes.
What if I don't see a matching tax code from my accounting system?
If you do not see a corresponding tax code from your accounting system, you will need to navigate to your QuickBooks Online account and setup the correct tax rate.
Once this has been done, navigate to your integration configuration to select the appropriate tax. In case this is still not available, please try the Refresh button to update the list of available taxes.
Once saved, you can click on the Sync Now link to run another sync and see the sale(s) go through to your accounting system.
Limitations
Changing tax settings in BigCommerce
Consider the following scenario..
- You've setup your own taxes in BigCommerce
- You then map your tax codes to your accounting system
- After configuring tax, you start using Avalara instead
You will now be prompted to re-map your tax codes within your integration configuration.
2 Comments
I have checked this multiple times, mapped the codes and still it fails.
12 Product can't be created in QuickBooks Online. Product is using an inactive Account or Tax Code.
The 12 products are using the same tax setting in BC as the other 80 or so products.
The same scenario can also happen in reverse, where we're unable to push an item if invoices containing the item already exist