US sales tax nexus for UK businesses: When you’ve already crossed the line

• U.S. sales tax nexus is triggered automatically. U.K. businesses can create obligations before they realise thresholds have been exceeded, even without a U.S. entity or physical presence.
• The problem is operational, not theoretical. Once nexus is triggered, liability begins immediately and can expand across multiple states through penalties, interest, and ongoing noncompliance.
• Structured remediation reduces risk. State-by-state exposure analysis, controlled registration strategy, and voluntary disclosure evaluation help contain financial and audit exposure.
• Prevention depends on continuous monitoring. Automated threshold tracking, real-time tax calculation, and scalable filing processes stop exposure from compounding as U.S. operations grow.

Crossing the line means your business has triggered sales tax nexus in a U.S. state and should already have been registered there.

Nexus is triggered by activity, not by registration. A business does not become liable when it decides to register. Liability begins when the threshold is exceeded.

For most U.K. ecommerce businesses, this happens through economic nexus — where sales revenue or transaction volume into a state exceeds the threshold defined by that state.

The South Dakota v. Wayfair decision confirmed that physical presence is no longer required for states to impose sales tax obligations. This means a U.K. business can trigger obligations:

• Without a U.S. entity
• Without employees in the state
• Without a warehouse or office

Revenue alone can be enough.

Revenue thresholds vs. transaction thresholds

Most states apply a threshold of around:

• $100,000 in annual sales
• Or 200 transactions

Some states use revenue only. Others apply both tests.

The measurement window also varies. Some states look at the previous calendar year, while others use a rolling 12-month period. This is why nexus analysis must be done state by state.

Nexus is triggered automatically

There is no application process that confirms nexus.

No state approval is required before obligations begin. Once the threshold is exceeded, the obligation exists automatically. The fact that the business discovers the issue later does not change the liability period.

This is why retrospective exposure builds quietly — and why detection timing matters operationally, not legally.

Once you suspect nexus may already exist, the priority is to confirm where and when thresholds were exceeded.

This is a diagnostic exercise. The objective is to build a defensible, state-by-state view of exposure so finance teams can decide what action to take next.

Step 1: Segment U.S. revenue by state

Start with transaction-level data.

Pull at least the last 24 months of U.S. sales activity from ecommerce platforms, ERP systems, marketplaces, and payment providers. Revenue must be segmented by:

• Ship-to state
• Sales channel
• Transaction count

Marketplace sales and direct ecommerce sales should be separated immediately. This matters because marketplace collection rules may affect whether tax was already collected and whether those transactions count towards thresholds in specific states.

Businesses already selling into the U.S. often discover that state-level visibility was never built into reporting from the outset.

Step 2: Compare against each state’s measurement period

Threshold analysis must be performed individually for each state. This includes:

• Revenue thresholds
• Transaction thresholds
• Measurement window rules

Some states use the previous calendar year. Others use rolling 12-month calculations.

The goal is to identify:

• Whether the threshold was crossed
• The first date of exceedance
• Whether nexus still exists today

This date becomes critical because it defines the potential retroactive liability period.

Step 3: Confirm marketplace collection status

Next, identify which states had marketplace tax collection in place. This requires reviewing:

• Amazon marketplace reports
• Shopify or direct ecommerce sales
• Marketplace facilitator tax reports
• 1099-K reporting data

Understanding Form 1099-K reporting is important because states increasingly use reported marketplace and payment processor revenue to identify unregistered sellers.

The key point is avoiding double counting. Marketplace sales may:

• Count towards nexus thresholds
• Already have tax collected by the marketplace
• Still create registration obligations in some states

Direct sales exposure must therefore be separated clearly from marketplace-collected transactions.

Step 4: Document the trigger date

Once thresholds are identified, record the exact date each state threshold was first exceeded. This date determines:

• The start of potential liability
• Lookback periods
• Voluntary disclosure eligibility
• Financial exposure calculations

Without documented trigger dates, remediation becomes difficult to defend.

The objective is not perfect precision. It’s a clear, supportable timeline that finance leaders can use to make decisions confidently.

Once nexus has been identified, the objective is to stop exposure growing, quantify the problem accurately, and choose the right remediation path for each state.

The earlier this happens, the more options remain available.

Do not ignore the exposure

Liability does not disappear because registration was delayed. States increasingly use:

• Marketplace reporting
• Payment processor data
• 1099-K filings
• Nexus questionnaires
• Data matching between jurisdictions

Once a business has crossed the threshold, exposure continues to build until the issue is addressed.

For businesses already evaluating late registration exposure for U.K. sellers, the key is acting before states initiate contact directly. Ignoring the issue usually increases:

• Tax liability
• Interest
• Penalty exposure
• Audit complexity

Decide between immediate registration and voluntary disclosure

The next decision is remediation strategy.

In some states, immediate registration may be appropriate to stop future exposure from increasing. In others, a voluntary disclosure agreement (VDA) may provide a better outcome by limiting lookback periods and reducing penalties.

The Multistate Tax Commission voluntary disclosure program provides a coordinated framework used by many states for structured remediation. The right path depends on:

• Number of states involved
• Size of exposure
• Whether the state has already made contact
• Availability of historical data

Avoid backdating without strategy

One of the biggest mistakes is registering reactively without understanding the consequences. Backdated registration can:

• Expand filing obligations unnecessarily
• Confirm liability dates prematurely
• Remove VDA eligibility in some states

This is why remediation should be sequenced carefully. The goal is not just to become compliant going forward, but to reduce historical exposure in a controlled, defensible way while stabilising ongoing compliance operations.

Once nexus has been confirmed, the next step is quantifying exposure. Businesses should build a defensible estimate that allows finance teams to assess materiality, prioritise remediation, and understand potential downside.

Calculate uncollected tax

Start by identifying taxable revenue from the trigger date onward in each state. This requires:

• Separating taxable and non-taxable sales
• Removing marketplace-collected transactions where applicable
• Segmenting revenue by destination state

Once taxable revenue is isolated, apply an estimated blended state and local sales tax rate.

For businesses selling digital products or SaaS, understanding U.S. digital services sales tax treatment is important because taxability varies significantly by state. The output should be a state-by-state estimate of:

• Uncollected tax
• Exposure period
• Confidence level in the data

Estimate penalties and interest

Most states apply:

• Late registration penalties
• Failure-to-file penalties
• Failure-to-pay penalties
• Daily or monthly interest accrual

The methodology varies by state.

Assess multistate compounding risk

Exposure rarely exists in only one state. Once nexus has been triggered across several jurisdictions, liabilities compound:

• Different penalty structures
• Different interest calculations
• Different lookback periods
• Different filing frequencies

There is also escalation risk. Registration or remediation activity in one state may increase visibility elsewhere, particularly where sales volumes are high. For finance teams, this creates accounting and governance implications:

• Potential contingent liabilities
• Audit disclosure considerations
• Investor or due diligence scrutiny

The key is visibility. A quantified exposure model gives leadership a framework for making remediation decisions proactively rather than reacting under pressure.

Once exposure has been identified, the priority shifts from remediation to prevention. The objective is to stop new liabilities building while establishing a scalable compliance model going forward.

Implement ongoing state-level threshold monitoring

Economic nexus is dynamic. Thresholds can be crossed quietly as revenue grows across channels, products, and fulfilment models. Monitoring therefore needs to happen continuously, not once a year. A scalable approach includes:

• Automated state-level revenue tracking
• Transaction-count monitoring where relevant
• Alerts when thresholds are approaching
• Visibility across direct and marketplace channels

Without this, finance teams are forced into retrospective reviews instead of proactive control.

Standardise tax calculation and filing processes

As the number of states increases, inconsistency becomes the main operational risk. Standardisation should cover:

• Real-time sales tax calculation
• Product-level taxability mapping
• Filing calendar management
• Reconciliation between collected and remitted tax

This is particularly important where:

• Multiple ecommerce platforms are used
• Marketplace and direct sales overlap
• Inventory moves between fulfilment locations

The goal is not just compliance, but also operational predictability.

European businesses already managing U.S. sales tax are increasingly moving away from spreadsheet-based workflows towards structured, system-driven processes that support multistate scale.

The earlier monitoring and automation are introduced, the lower the likelihood that exposure compounds again in the future.

For many U.K. businesses, manual sales tax management becomes unsustainable once operations expand across multiple states. The tipping point usually appears when:

• Nexus has already been triggered in several states
• Historical exposure is unclear
• Marketplace and direct sales overlap
• Inventory is distributed across fulfilment networks
• Funding, acquisition, or audit preparation is approaching

At this stage, the challenge is not simply understanding the rules. It’s controlling operational risk consistently across jurisdictions. Manual processes break because they rely on:

• Spreadsheet-based threshold tracking
• Static tax rates
• Fragmented reporting
• Reactive correction workflows

As state exposure increases, those weaknesses become harder to manage internally.

Avalara provides a structured, scalable approach to U.S. sales tax compliance for U.K. businesses operating across multiple states. Instead of relying on fragmented manual processes, Avalara centralises:

• Economic nexus monitoring
• Real-time sales tax calculation
• Product-level taxability mapping
• Multistate registration support
• Automated filing and remittance
• Exemption certificate management
• Audit-ready reporting and documentation

Built on Avalara’s agentic AI platform for global tax and compliance, Avalara combines a certified compliance engine with AI-powered orchestration to help businesses manage compliance more efficiently at scale. AI capabilities support processes such as product classification, anomaly detection, threshold monitoring, and filing validation, helping finance teams identify potential issues earlier and reduce manual effort across workflows.

For businesses already dealing with retrospective exposure, Avalara supports both remediation and future-state compliance. Avalara can help evaluate nexus exposure, support voluntary disclosure agreement (VDA) processes where appropriate, and establish automated compliance workflows moving forward.

The outcome is greater operational control. Finance leaders gain visibility into where obligations exist, increased confidence that tax is being calculated more accurately, and a scalable compliance framework that supports continued U.S. growth without increasing operational burden.

Speak with Avalara to assess your current nexus exposure, evaluate remediation options, and build a sustainable multistate sales tax compliance model.