Since South Dakota v. Wayfair (decided 21 June 2018), a US state can require you to collect sales tax based on how much you sell into it, with no shop, warehouse or staff there. Cross a state's economic-nexus threshold, most often $100,000 in sales, and the obligation starts. The problem for an ERPNext user: the system has no engine to work out the rate for each jurisdiction, and nothing that tells you when you've crossed a threshold. This guide covers where thresholds sit in 2026, when hand-set rates are workable, and when to hand rate lookup to a tax engine such as TaxJar or AvaTax. It describes the system setup, not tax advice: confirm your obligations with a US sales-tax adviser.
US sales tax goes wrong quietly: you cross a threshold, keep invoicing without collecting, and the exposure grows until a state notice arrives with back tax and penalties. I lead ERPNext and Frappe programmes at MithTech, a team of Frappe specialists in Bengaluru. Nexus tracking and rate lookup, usually handed to a tax engine, are what keep it from becoming a surprise.
Do your sales create nexus?
Economic nexus is a per-state test, and thresholds differ. Before anything in ERPNext, work out where you have an obligation.
Calculator
Economic Nexus Threshold Checker
Pick a state threshold profile and enter your annual sales and transaction count to see whether you've crossed the economic-nexus threshold.
Most states use $100,000 in annual sales. California and Texas use $500,000, New York $500,000 and more than 100 sales, and Alabama and Mississippi $250,000. The trend is away from transaction counts: Alaska (2025), Utah (2025), Illinois (2026) and Kentucky (August 2026) dropped the 200-transaction test. Fifteen states, DC and Puerto Rico still had one on the chart when we checked, and Connecticut requires both $100,000 and 200 transactions. The checker illustrates representative states; check each state you sell into.
Hand-configure, or delegate?
The right approach depends mostly on how many states you have nexus in, and whether a marketplace already collects for you.
Interactive
Manual vs Delegate Decider
Set your number of nexus states and whether you sell only through marketplaces to see whether manual configuration or a tax engine fits.
ERPNext's tax setup (Tax Categories, Item Tax Templates, Sales Taxes and Charges Templates and Tax Rules) can hold rates by hand for one or two states. It doesn't scale: the US has thousands of taxing jurisdictions, a state rate isn't a local rate, and rules change often. Past a couple of states, the upkeep outweighs the saving and you hand rate lookup to an engine.
How does handing rates to a tax engine work in ERPNext?
The tax engine, not ERPNext, owns rate lookup by jurisdiction, product taxability and, on fuller plans, nexus tracking and filing. ERPNext calls it at invoice time and writes the returned tax lines back.
Code recipe
Manual · Delegate · Track · Prevent
Copy-paste the native tax surface and its limits, the delegation hook pattern, the nexus-tracking job ERPNext won't do for you, and the controls that keep an un-tracked threshold from becoming an assessment.
0 of 4 steps done
Tick a step’s number when it is done; the ticks stay on this device.
Decide manual vs delegated by footprint
For a small, stable footprint (one or two states), hold the rates in ERPNext's Tax Rules. Past that, use an engine. If every sale runs through a marketplace facilitator, the platform generally collects the tax; every sales-tax state and DC has a facilitator law (Missouri's, the last, from 1 January 2023). You may still owe registrations and returns.
Wire the delegation hook
On Sales Invoice validation or submit, collect the ship-from and ship-to addresses and the line items, call the tax engine's REST API, and write the returned amounts back as tax lines. TaxJar is the separate frappe/taxjar_integration app; AvaTax uses the same shape through a custom app against its REST API. Check the exact hook and fields against the integration you adopt.
Track nexus, not just rates
Rate lookup is half the job. Track sales and transaction counts per state, over the period each state uses, against its current threshold, and alert at around 80% so you register before you cross. Late registration means uncollected back tax plus penalties. Physical presence still creates nexus: inventory in a third-party fulfilment warehouse counts.
Reconcile and re-check annually
Reconcile what you collected against what you must remit, per state and filing period. Recheck thresholds each year; states keep changing dollar limits and dropping transaction tests.
When sales, fulfilment and finance each move the needle
The whole business creates nexus, not one desk. Sales drives the volume that trips economic nexus; fulfilment can create physical nexus when inventory lands in a new state's warehouse; finance holds the liability when a state notice arrives. Each acts without seeing the others' tax consequences.
Centralise nexus monitoring. Feed per-state sales, transaction counts and inventory locations into one view measured against current thresholds, and alert before a line is crossed. Let the tax engine own rates so nobody hand-picks local rates, and reconcile collected against remitted every period. Crossing a threshold should open a registration task, not be discovered two years later.
Draft policy for your finance and operations leads to ratify. Per-state sales, transaction counts and inventory locations are tracked continuously against each state's current economic-nexus threshold, with an alert at ~80% so registration happens before the threshold is crossed. Rate and jurisdiction determination is delegated to a tax engine, not hand-maintained beyond a minimal footprint. Collected sales tax is booked to a liability account and reconciled against remittances per state and period. Physical presence, including third-party warehouse inventory, is treated as nexus-creating. Thresholds and marketplace-facilitator duties are re-checked annually. Confirm current rules with a US sales-tax adviser before adoption.
Manual rates or a tax engine?
| Delegate to a tax engine | |
|---|---|
| Correct rate at the exact jurisdiction (state, county, city, district) | A state-level rate that misses local jurisdictions |
| Scales to many states without per-rate upkeep | Only workable for one or two states |
| Can track nexus and (fuller plans) file returns | No nexus tracking: you must build it |
| Rules and taxability maintained by the engine vendor | You chase every rate and rule change yourself |
| TaxJar via its own app (frappe/taxjar_integration); AvaTax via a custom app | Native Tax Categories, Templates and Tax Rules |
At a glance
| Aspect | What to know |
|---|---|
| Rule | Economic nexus by state since Wayfair (2018) |
| Common threshold | $100,000 in sales; CA and TX $500,000; NY $500,000 and 100+ sales |
| In ERPNext | Hand-set Tax Rules for one or two states; a tax engine beyond that |
| What ERPNext won't do | Track nexus thresholds |
FAQ: what do people ask most?
What is economic nexus after South Dakota v. Wayfair?
Economic nexus means a state can require you to collect sales tax based on your sales or transaction count into that state, with no physical presence. The 2018 Wayfair decision overturned the earlier physical-presence rule, so remote sellers can be obliged on economic activity alone, most often $100,000 in annual sales.
How do I calculate US sales tax in ERPNext?
For a very small footprint you can hold rates in ERPNext's Tax Categories, Item Tax Templates and Tax Rules by hand. For anything larger, a tax engine is called at invoice time and ERPNext writes the returned amounts back as tax lines. For TaxJar, Frappe maintains a separate app, frappe/taxjar_integration.
Does ERPNext have an AvaTax integration?
Not an official one. TaxJar has a separate Frappe app (frappe/taxjar_integration), out of ERPNext core since v15. AvaTax works through the same pattern, a custom Frappe app calling the AvaTax REST API at invoice time. With no Frappe-maintained AvaTax connector, treat it as a build.
What are the US economic nexus thresholds in 2026?
Per the Sales Tax Institute chart (as of 1 August 2026), most states use $100,000 in sales; California and Texas use $500,000; New York $500,000 and more than 100 sales; Alabama and Mississippi $250,000. Many states have dropped the 200-transaction test. Thresholds change, so check each state with its revenue department before relying on it.
What happens if we don't track nexus and cross a threshold?
You keep invoicing without collecting the tax you were obliged to collect, and the liability grows unseen. When a state finds it, you face assessment for the back tax plus interest and penalties, often paid out of your own pocket, since collecting from customers afterwards is hard. That is why continuous nexus tracking matters.
Do marketplace sales count toward my nexus obligation?
If you sell through a marketplace facilitator, the platform is generally responsible for collecting and remitting the tax; every sales-tax state and DC has a facilitator law. Whether facilitated sales count toward your own threshold varies by state, and you may still need to register and file. Confirm the per-state rules with a US sales-tax adviser.
What related issues might you also hit?
- ZATCA Phase 2 clearance vs reporting: a clearance model, where the document is stamped before it is valid.
- ERPNext multi-currency and multi-company setup: running a US entity inside a wider group.
What is the bottom line?
Wayfair turned US sales tax into a volume problem, and ERPNext solves neither half on its own: not the local rate, not the threshold tracking. Hand rates to a tax engine, run nexus monitoring as a proper job, and book the tax as the liability it is. Then a crossed threshold becomes a registration task, not an assessment.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 3 August 2026
Worked with us? Leave a Google review