Time constraints surrounding sales and use tax
Your online business is painfully aware of tax deadlines for income, payroll, property and other...
Automation can play an important role in sales tax compliance. It can monitor sales activity, calculate tax, track economic nexus thresholds and alert your team when something changes.
But not every step in sales tax compliance should happen automatically.
Sales tax registration is a good example.
Some sales tax technology can automatically register a business with a state once its system determines that an economic nexus threshold has been crossed. On the surface, that sounds efficient. Turn on the feature, let the technology monitor your thresholds and automatically register wherever necessary.
The problem is that crossing a threshold doesn't always mean the next step should automatically be registration.
A nexus threshold is a trigger for a decision. It shouldn't necessarily make the decision for you.
What happens when you cross an economic nexus threshold?
Economic nexus laws generally require businesses to evaluate their sales activity in a state and determine whether they have established a sales tax obligation.
Technology can be extremely helpful here. When you're selling into dozens of states, automatically monitoring sales against state thresholds can reduce a significant amount of manual work.
But identifying that you've potentially crossed a threshold is only the first step.
Before registering, there are questions worth answering:
Those aren't questions a threshold notification alone can answer.
Economic nexus rules aren't identical from state to state
One of the challenges with economic nexus is that a "$100,000 threshold" doesn't necessarily mean the same thing everywhere.
States can differ in which transactions are included in their economic nexus calculations, the period used to measure sales and when an obligation begins after a threshold is crossed.
Marketplace activity can add another layer of complexity. So can exempt transactions, resale transactions and businesses selling a mix of taxable and non-taxable products or services.
Consider a company whose technology reports $105,000 of sales into a state with a $100,000 economic nexus threshold.
The automated answer might be:
Threshold crossed. Register.
A practitioner is more likely to ask:
What's included in that $105,000?
That distinction matters.
If transactions have been categorized incorrectly, sales channels are missing or the state's threshold rules haven't been applied correctly, the registration decision may be based on an incomplete picture.
Registering creates an obligation. It doesn't just complete a task.
A sales tax registration isn't the end of a process.
It's the beginning of one.
Once your business is registered, you may be responsible for filing returns on an established schedule, remitting tax, maintaining records and responding to state notices. Depending on the jurisdiction, returns may still be required during periods when no tax is due.
That means an unnecessary registration can create unnecessary compliance responsibilities.
It can also create another opportunity for something to go wrong.
Miss a return because you didn't realize an account had been established? There may be a notice or penalty.
Forget to file because there was no tax due? Depending on the jurisdiction, you may still have a problem.
Register first and figure out the compliance process later? Now you may have an active account without the systems and processes needed to support it.
Registration should be coordinated with the broader compliance process, not treated as an isolated administrative task.
Are you ready to collect sales tax?
Even when registration is clearly required, when and how you register should be part of a larger plan.
Before collection begins, your business may need to determine:
Automatically obtaining a permit doesn't answer any of those questions.
Your company can technically be registered while still being operationally unprepared to comply.
What if nexus actually began before the system says it did?
This is one of the biggest reasons to review a nexus determination before automatically registering.
Economic nexus isn't the only way to establish sales tax nexus.
Physical presence can still matter.
Employees, inventory, offices, warehouses, contractors and other business activities can potentially create an obligation depending on the circumstances and jurisdiction.
There can also be gaps in the data being monitored.
Maybe the nexus software only received transactions from one ERP, but your company has multiple sales channels.
Maybe you recently acquired another business.
Maybe inventory is being stored by a third party.
Maybe historical transactions weren't loaded into the system.
If your actual nexus date was 18 months ago, registering today doesn't make those previous 18 months disappear.
Before registering, you may need to understand the historical exposure and determine the appropriate way to address it.
That could include evaluating prior transactions, determining potential tax liability and considering whether remediation options such as a voluntary disclosure agreement (VDA) make sense.
Automatically registering first can take that evaluation out of sequence.
Registration can require sensitive information
Sales tax registrations can also require more information than some businesses realize.
Depending on the state and business structure, applications may request information about owners, officers or other responsible individuals. That can include Social Security numbers and other sensitive identifying information.
There is a reason states ask for this information.
Sales tax collected from customers is generally considered a trust tax. Depending on the jurisdiction and circumstances, individuals responsible for collecting and remitting those funds can potentially face personal liability for unpaid trust taxes.
Submitting a registration isn't the same as clicking "accept" on another software setting.
The company, its finance or tax team and potentially its officers should understand what is being submitted and why.
What about income tax and other state registrations?
A new sales tax obligation can also be a signal that it's time to evaluate the company's broader state footprint.
Sales tax nexus, income or franchise tax nexus, Secretary of State registration requirements and other state obligations don't necessarily follow the same rules.
Having one obligation doesn't automatically mean you have all of the others.
But business activity significant enough to trigger a sales tax review can warrant a broader conversation.
For example:
Why are we crossing the threshold in this state?
Has the company simply increased sales there? Did it hire employees? Add inventory? Open a location? Acquire another business? Change how products or services are delivered?
The facts behind the nexus determination may have implications beyond sales tax.
That's context a threshold-monitoring tool may not have.
What if you're only slightly over the threshold?
This is another situation where judgment matters.
Suppose your technology identifies that you've crossed a state's economic nexus threshold by a relatively small amount.
The answer may ultimately be that you need to register.
But before doing so, it is worth validating the calculation.
Are all the transactions being counted supposed to be included?
Is there a return or credit affecting the total?
Are marketplace transactions being handled correctly?
Are exempt or resale transactions treated correctly under that state's rules?
Is the sales data assigned to the correct state?
Is this the correct legal entity?
The goal isn't to find a reason not to register.
It's to make sure the business is making the decision based on accurate information.
Automation only knows the data it can see
This is an important limitation of any sales tax technology.
A system only knows what you give it.
For a business with one entity, one ecommerce platform and straightforward transactions, that may provide a fairly complete picture.
For a larger or more complex organization, it may not.
Your company might have multiple entities, ERPs, ecommerce platforms, marketplace channels, acquired businesses, offline transactions or revenue streams that aren't connected to the same system.
Technology can process the data remarkably efficiently.
But someone still needs to ask whether the data represents the complete business.
Where should automation fit into sales tax registration?
None of this means registration itself has to be a manual, time-consuming process.
Technology should absolutely be used to make sales tax compliance more efficient.
The distinction is where automation stops and judgment begins.
Technology can:
Monitor. Track sales activity against state economic nexus thresholds.
Alert. Tell your team when you're approaching or potentially exceeding a threshold.
Organize. Bring the relevant data together so the situation can be reviewed.
Support. Help prepare and submit registrations once the appropriate course of action has been determined.
But between "threshold crossed" and "registration submitted," there should be an opportunity to review the facts.
Should sales tax registration be automatic?
For most businesses, we'd argue that the better question is:
Should registration be automatic, or should the technology automatically tell you when it's time to make a decision?
Those aren't the same thing.
Automation is extremely good at repeatable tasks. Sales tax professionals are there for the situations where context, judgment and business-specific facts matter.
Economic nexus often requires both.
Use technology to monitor the thresholds.
Use automation to reduce the administrative work.
But before creating a new tax account, make sure someone understands your business, validates the obligation and considers what happens next.
Because in sales tax:
A threshold notification is data. A registration is a decision.
Your online business is painfully aware of tax deadlines for income, payroll, property and other...
Copyright © 2026 TaxConnex, LLC