SOP Management & Workflow Documentation3 min readUpdated September 2026

The Multi-State Nexus Review Checklist Firms Reconstruct Too Late

A client expands into a new state, hires a handful of remote employees, and nobody on the engagement runs a fresh nexus review, because the client's tax situation seemed settled after last year's return. Eighteen months later, a notice arrives from a state the client didn't know they owed anything to, and the firm is now explaining why that exposure wasn't caught sooner.

Multi-state corporate tax advisory has more moving parts than a single-jurisdiction return, and the moving part that causes the most expensive surprises is nexus: whether a client's activity in a given state has crossed the threshold that creates a filing obligation there.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Triggering a Nexus Review on Actual Business Changes, Not the Calendar

A nexus review that happens once a year, on a fixed schedule, misses the client who adds a remote employee in a new state in month four or opens a warehouse in month nine. A checklist tied to specific trigger events, a new employee's work location, a new physical location, a new significant customer base in a state, that requires a nexus review whenever one of those events is reported, catches the exposure close to when it started rather than at the next scheduled check-in.

This depends on the client actually telling the firm about these changes, so the checklist should include a recurring prompt asking the client directly, rather than assuming they'll think to mention it.

Events that should trigger a fresh nexus review include:

  • A client hires a remote employee whose work location is in a state where the client had no presence before.
  • A client opens or leases a new physical location, such as a warehouse or office, in another state.
  • A client builds a significant new customer base in a state where it has not previously filed.
  • The client answers a recurring prompt from the firm that asks directly about staffing, locations and customers in new states.

Collecting Apportionment Data Per State, Not Once for the Whole Return

A multi-state return needs sales, payroll, and property data broken out by state, and collecting that data as one undifferentiated bucket from the client, then trying to apportion it later, invites errors and rework. A checklist requiring apportionment data to be requested and confirmed on a per-state basis, with a specific data owner named for each state's figures, produces cleaner data going into preparation instead of a reconciliation project after the fact. Note which figures came directly from the client versus which were estimated or carried forward from a prior year, so a reviewer can tell the difference later.

Tracking Deadlines Across States That Don't Share a Calendar

State filing and extension deadlines don't line up with each other or with the federal deadline, and a firm managing filings across a dozen states for one client needs every one of those dates tracked individually, not folded into a single 'tax deadline' on a calendar. A workflow with one tracked instance per state filing, each with its own due date and status, makes a state that's about to be missed visible well before the deadline arrives. Group the view by client rather than by state alone, so a preparer managing several clients across several states can see everything due that week in one place instead of checking a dozen separate lists.

Keeping the E-File Authorization Chain Clean Across Multiple Returns

A corporate client with filings in several states generates several signed authorizations, and losing track of which one is outstanding for which state is a common way a filing gets delayed at the last minute. A checklist requiring the specific signed authorization to be attached to each state's filing record before that filing moves forward keeps the authorizations from being confused with each other.

What a Missed Nexus Signal Actually Costs a Client and the Firm

Accountants and auditors nationally earn a median of $83,6801, and the value a multi-state tax advisor provides well above that pay level is precisely catching a nexus obligation before a state catches it first, with penalties and back taxes attached. A firm that can show a documented, triggered nexus-review process, rather than an annual check that happened to miss a mid-year change, is in a much stronger position if a client ever questions why an exposure wasn't caught sooner.

Responding to a State Notice Before It Escalates

A notice from a state taxing authority has its own response deadline, often shorter than a typical filing deadline, and a notice that sits in a client's mail pile or a firm's inbox for even a couple of weeks can turn a routine inquiry into a penalty situation. A checklist triggered the moment any notice is received, requiring it to be logged, assigned an owner, and routed toward a response within a set number of days, keeps a notice from being the one thing that falls through the cracks during an already busy filing season. Confirm the specific response window with the notice itself rather than assuming a standard timeline, since it can vary by state and by the type of issue raised.

Executive Capability Standard

What Good Looks Like

A disciplined multi-state tax practice triggers a nexus review on actual client business changes rather than a fixed calendar, and tracks every state's filing deadline and authorization as its own item with visible status.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Review the last several clients who had a late-discovered nexus exposure, and trace each back to the business change that should have triggered a review sooner.
2. Do Manually:Run nexus reviews annually as part of the standard engagement, relying on the client to separately mention any business changes during the year.
3. Delegate:Assign an engagement lead to prompt clients quarterly about nexus-triggering changes and to track apportionment data collection per state.
4. Automate:Run nexus-review triggers, apportionment data collection, and per-state deadline tracking as tracked workflows with visible status and recurring client prompts.
5. Buy:Connect the nexus-trigger workflow to the client's own HR or payroll data feed where available, so a new work location in a new state surfaces automatically instead of waiting for the client to report it.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Process Street

Use it to trigger nexus reviews on actual client changes and track per-state apportionment data and deadlines as tracked workflows.

Visit Process Street→
Every

Use it to keep firm payroll and contractor payments organized through multi-state filing season.

Visit Every→

Frequently Asked Questions

How often should a client be prompted to report a nexus-triggering change?

Often enough that a mid-year change doesn't sit unreported for months, which usually means a recurring prompt rather than relying solely on the client to remember to mention it during the next scheduled review. Quarterly check-ins work well for clients actively expanding into new states.

Who should own apportionment data collection for a specific state?

Whoever on the engagement is responsible for that state's return should own requesting and confirming its specific data, rather than one person collecting an undifferentiated total for the client to sort out later. Naming an owner per state is what actually gets clean, state-specific figures.

What's the most common cause of a missed state filing deadline?

A deadline that was tracked as part of a general 'tax season' calendar rather than as its own dated item, so it got deprioritized behind the federal deadline everyone was focused on. Tracking each state filing as its own item with its own due date is what prevents that.

Sources

Where we quote a benchmark, we show its source. Other figures in this guide are estimates or general guidance, so check them against your own numbers.

  1. Annual wage, Accountants and Auditors (SOC 13-2011), US all industries. BLS OEWS May 2025, 2025.

Related Guides