Sales Tax in Ecommerce ERP Integrations: Nexus, Tax Engines, and Data Flow

Sales tax is where ecommerce integrations quietly create the most expensive problems: a few cents of rounding on every order, marketplace tax reported twice, refunds that never reverse their tax, or nexus that crept up in a state nobody was watching. This guide covers how tax data should flow between the store, a tax engine, and the ERP. It’s written for the people building and running the integration. It is not tax or legal advice — your obligations depend on your products, states, and facts, so confirm the design with a qualified tax professional. As on every page, documented marks statements from official sources, and recommendation marks our guidance.

Why nexus is now an integration problem

Documented: in South Dakota v. Wayfair (2018), the US Supreme Court held that physical presence is not necessary for a state to require a seller to collect sales tax, overruling the prior physical-presence rule. The South Dakota law at issue applied to sellers that delivered more than $100,000 of goods or services into the state, or engaged in 200 or more separate transactions there, in a year.

Documented: states adopted their own economic nexus rules. Thresholds and measurement periods vary by state — Shopify’s US tax reference lists, for example, different thresholds and periods such as the previous or current calendar year, a rolling twelve months, or the previous four quarters. Many states also have marketplace facilitator rules that require marketplaces to collect and remit tax on sales they facilitate, and states differ on whether marketplace sales count toward a remote seller’s own threshold.

Recommendation: because nexus depends on sales into each state across all channels — your store, wholesale, marketplaces, phone orders — the data has to come from wherever every channel meets. In most integrated stacks, that’s the ERP or a tax engine that receives every transaction, not the storefront alone.

Rule 1: one system calculates tax

Recommendation: choose a single tax authority for each channel:

Channel	Typical calculator	ERP receives
Shopify store (D2C)	Shopify’s tax calculation or a tax engine (such as Avalara, Vertex, or TaxJar) connected at checkout	Tax lines as calculated, by jurisdiction
B2B / wholesale	Tax engine called by the ERP or B2B storefront, honoring exemption certificates	Same, plus certificate reference
Marketplaces	The marketplace, where it’s the facilitator	Tax marked as collected and remitted by the marketplace

The ERP then records tax; it doesn’t recalculate it. Recalculation causes penny differences on thousands of orders and, more seriously, different answers on exempt customers, shipping, or product taxability than the customer was charged.

Rule 2: keep tax at jurisdiction level

Documented (Shopify): each Shopify order exposes tax lines with a title, rate, amount, and a channelLiable flag that indicates whether the channel that submitted the tax is liable for remitting it.

Recommendation: map each tax line to an ERP tax code and liability account by jurisdiction rather than posting one “sales tax” total. A typical mapping record:

{
  "source": "shopify",
  "orderId": "gid://shopify/Order/5551234",
  "taxLines": [
    { "title": "CA State Tax", "rate": 0.0725, "amount": "3.63", "channelLiable": false,
      "erpTaxCode": "CA-STATE", "liabilityAccount": "2310-CA" },
    { "title": "Los Angeles County Tax", "rate": 0.0025, "amount": "0.13", "channelLiable": false,
      "erpTaxCode": "CA-LA-CNTY", "liabilityAccount": "2310-CA" }
  ]
}

Illustrative only. Rates, titles, and jurisdictions here are examples, not current rates. Maintain the mapping as data so finance can update it without a code release, and alert on any tax line that has no mapping instead of posting it to a default account. See data mapping.

Rule 3: marketplace tax is not your liability

Recommendation: when a tax line is marked as channel-liable — or an order comes from a marketplace that is the facilitator in that state — record the tax so it’s clearly collected and remitted by the marketplace. Include those sales in nexus tracking where the state counts them, but keep them out of the tax you remit yourself. Double-reporting marketplace tax is one of the most common reconciliation errors.

Rule 4: refunds reverse tax

Recommendation: refunds must carry their own tax lines, reversing tax in the same jurisdictions and in the same period logic your returns use. A refund posted as a single negative amount with no tax breakdown leaves the liability overstated. Partial refunds, refunds of shipping only, and returns of exempt items each need a test case. See refunds and cancellations.

Rule 5: exemptions live with the customer record

Recommendation: for B2B buyers, store exemption certificate details (state, certificate reference, expiry) on the customer in the ERP or tax engine and sync the exemption status to the B2B storefront. Expired certificates should block exemption — not silently keep it — and every exempt sale should reference the certificate used.

Reconcile every period

Recommendation: before each filing period closes, reconcile three numbers per state:

1. Tax collected according to the store’s (or tax engine’s) tax report.
2. Tax recorded in the ERP liability accounts.
3. Tax filed on the return.

Differences usually trace back to refunds, cancelled orders posted late, channel-liable tax, or unmapped tax lines. Investigate them while the period is still open. The same discipline as inventory reconciliation applies: automate the comparison, route exceptions to a person.

Nexus monitoring

Documented (Shopify): Shopify’s US tax liability insights mark states as “Action required” where potential liability has been identified and “Monitoring” where sales reached at least 80% of a state’s economic nexus threshold, calculated on net sales. External sales that aren’t imported into Shopify may be excluded, depending on the state.

Recommendation: if you sell through more than one channel, make sure the system tracking nexus sees all of them — import wholesale and marketplace sales or track nexus in the tax engine or ERP. Review the report monthly and decide on registration before crossing a threshold, not after.

Common pitfalls

• Tax recalculated in the ERP, creating differences from what customers paid.
• One “sales tax” account with no jurisdiction detail, making returns a manual exercise.
• Marketplace tax reported as your own and remitted twice.
• Refunds without tax lines, leaving liabilities overstated.
• Nexus tracked on the storefront only while wholesale and marketplace sales grow elsewhere.
• Expired exemption certificates still honored at checkout.