Shopify tax into Acumatica without Avalara.
If your Shopify orders are erroring out in Acumatica with a tax or jurisdiction message, this page explains why it happens and how to stop it. You do not need to buy a tax engine just to get Shopify's tax figure into your ERP.
It usually shows up the week you try to go live.
- · Orders place fine in Shopify, then fail to create in Acumatica
- · The error names a tax zone, tax category or jurisdiction that does not exist in your instance
- · A county you have never sold into before stops the whole order
- · Shopify and Acumatica disagree on the order total by a few cents
Both systems calculate US tax. They do not do it the same way.
Shopify calculates tax at checkout, at the rooftop level: state, county, city and special district, worked out from the delivery address at the moment of purchase. It does that everywhere you sell, without you configuring anything.
Acumatica calculates tax from tax zones and categories you configure in advance. It can only calculate tax for a jurisdiction it already knows about.
The gap between those two models is the problem. An order arrives from a county you have never sold into, Shopify prices the tax correctly, and Acumatica declines the order because it has no matching configuration. Every new jurisdiction becomes another piece of setup.
Configure every jurisdiction, or buy a tax engine.
Acumatica's own guidance is direct. On their community, an Acumatica moderator put the options to a merchant in exactly these terms:
“If user do not want to pay for Automatic Tax Engines, then they must setup the taxes with the correct tax IDs, tax rates in Acumatica.”
For a US seller that means creating and maintaining a tax ID for every jurisdiction you sell into. Which is why merchants in this position are so often told a tax engine is the only realistic option.
The usual recommendation is Avalara AvaTax inside Acumatica. It is a good product and it genuinely solves the jurisdiction problem. It is also a significant purchase. For a merchant with nexus in a single state and a new storefront, it frequently is not proportionate. You would be buying multi-state tax automation to solve a data-transfer problem between two systems that each already hold the right answer.
Send Shopify's tax figure straight through.
InSyncer for Acumatica has a setting called Tax Amount Override. Shopify calculates tax at checkout through Shopify Tax, Avalara, or another tax app. Tax Amount Override passes that amount to Acumatica against a nominated Tax ID, bypassing Acumatica recalc. Avalara may sit in Shopify or Acumatica; either way it is optional. InSyncer for Acumatica doesn't require, replace, or integrate with it. Refunds use the same mechanism.
Because the tax arrives already calculated, there is nothing to pre-seed per jurisdiction and the two systems cannot drift apart on the total. You keep Shopify's rooftop-level tax, which is what your customer was actually charged. InSyncer for Acumatica is not a tax engine and does not file returns; it carries Shopify's figure into your ERP.
Setup is two steps: enable the setting, then choose the Acumatica Tax ID to record it against. The right Tax ID depends on your tenant. Read the tax-handling guide for the full setup.
Avalara and InSyncer are not alternatives to each other.
Avalara may calculate tax in Shopify, or sit inside Acumatica as a Tax ID. Either way, Tax Amount Override works the same. Merchants running Avalara inside Acumatica point the setting at their Avalara Tax ID, and the Shopify figure is recorded against it.
InSyncer for Acumatica doesn't require, replace, or integrate with Avalara. If Avalara is the right product for your business, keep it.
Finish Line Technologies went live without Avalara.
Finish Line Technologies, the US bicycle lubricant brand, connected a new Shopify storefront to Acumatica. They had sales tax nexus in a single state, and the advice they were given was Avalara. A full tax engine was more than they needed at that stage.
Shopify Tax calculates the tax at checkout. InSyncer for Acumatica passes the total into a single Acumatica Tax ID with Tax Amount Override, and refunds follow the same path. Read the Finish Line case study.
The routes Acumatica documents, and the one InSyncer adds.
Acumatica's own Shopify connector can handle US tax. On the Acumatica community, an Acumatica moderator describes these routes for tax on imported orders:
- Create tax IDs and rates in Acumatica. Seed a tax ID for every jurisdiction you sell into, and keep adding them as orders arrive from new places.
- Tick External Tax Provider on the tax zone. The connector creates missing tax IDs, but per Acumatica, "only the Tax IDs are created but not the tax rate." It also assumes a tax engine is in place.
- Disable Automatic Tax Calculation (2023 R1+). Set on the order type. Acumatica notes it also stops invoices being sent to an external tax provider such as Avalara.
- InSyncer for Acumatica: Tax Amount Override. Pass the tax Shopify already calculated to one Tax ID you nominate. Nothing to seed per jurisdiction, no tax engine required.
Sources: Acumatica Community, Shopify Manual Tax Mapping (2021 to 2022) and preventing tax recalculation on imported orders (2022 to 2023).
Shopify tax and Acumatica, answered.
Can I sync Shopify Tax to Acumatica without Avalara?
Yes. InSyncer for Acumatica has a setting called Tax Amount Override. Shopify calculates tax at checkout through Shopify Tax, Avalara, or another tax app. Tax Amount Override passes that amount to Acumatica against a nominated Tax ID, bypassing Acumatica recalc. Avalara may sit in Shopify or Acumatica; either way it is optional. InSyncer for Acumatica doesn't require, replace, or integrate with it. Refunds use the same mechanism. Avalara is only worth adding if your business needs it for multi-state tax automation or filing.
How do I stop Acumatica recalculating tax on Shopify orders?
Enable Tax Amount Override in InSyncer for Acumatica and nominate an Acumatica Tax ID. InSyncer then sends the exact Shopify tax amount with the order and marks it as already calculated, so Acumatica records it against that Tax ID instead of working it out again.
Which Acumatica Tax ID should I use?
One that already exists in your Acumatica tenant. Tax ID names vary from tenant to tenant, so there is no single correct value. Merchants running Avalara inside Acumatica usually point the setting at their Avalara Tax ID; merchants without Avalara use a standard Tax ID. The tax-handling guide walks through the choice.
How does InSyncer for Acumatica compare with the native Acumatica connector for US sales tax?
Acumatica documents three routes for tax on imported Shopify orders: create tax IDs and rates in Acumatica yourself, use an external tax provider, or disable automatic tax calculation on the order type. InSyncer for Acumatica adds a fourth: pass the tax Shopify already calculated to a single Tax ID you nominate, so there is nothing to pre-seed per jurisdiction.
Does InSyncer for Acumatica work if I already use Avalara?
Yes. Avalara may calculate tax in Shopify or sit inside Acumatica as a Tax ID. Either way the setting works the same: the Shopify tax amount is passed through against the Tax ID you nominate. InSyncer for Acumatica does not integrate with Avalara, and you can keep using it.
Are refunds handled the same way?
Yes. Refund tax uses the same mechanism: the Shopify refund tax total is written onto the refund document in Acumatica. It is on by default.
Worth a look if any of these are true.
- · You sell in the US from Shopify with Acumatica as your ERP
- · Orders are failing to sync with tax or jurisdiction errors
- · You have been told the fix is a tax subscription you would rather not buy yet
- · You are seeing small tax discrepancies between the two systems
Step-by-step setup is in the docs: Tax handling in InSyncer for Acumatica.
Ready to connect your ERP to Shopify?
Tell us what you're working with. We'll let you know honestly whether InSyncer is the right fit.