A nexus conclusion starts the coordination of permits, tax engines, orders, returns and the ledger. Registering too early creates unnecessary zero filings; registering too late can leave uncollected periods and penalty exposure.
1. Fix the first trigger date and registration scope
Physical nexus may arise from people, inventory, offices, installation or other in-state activity. Economic nexus requires the state's current sales and transaction rules. The start date on an application should follow the fact timeline, not software deployment or administrative convenience.
Before filing, confirm the selling entity, FEIN, legal name, responsible people, products, channels, expected sales, banking and existing state accounts. Streamlined registration covers participating states; it does not make their later returns identical.
2. Coordinate registration and collection deployment
After permit activation, configure the correct entity, state and effective date across ERP, Shopify, tax engines, marketplace settings and invoices. Test product taxability, customer location, local tax, certificates, refunds and freight—not only one standard order.
A permit without collection may leave the company funding tax or pursuing customers. Collection without a valid account can create entrusted-tax problems. Store the permit notice, configuration evidence and first taxed invoice in one implementation file.
- Permit and account effective date
- Product and service taxability mapping
- State, local, destination and rounding tests
- Exempt customers, refunds, discounts and freight
- Marketplace versus direct-channel responsibility
3. The state assigns filing frequency
Registration notices commonly assign monthly, quarterly, annual or prepayment requirements, and frequency can change. Enter the period, due date, prepayment and electronic-payment method in the calendar with both an owner and reviewer.
Confirm whether the first filing includes a short or historical period. Reconcile gross sales through taxable sales, deductions, tax collected and tax due. Uploading a tax-engine number without tying it to the ledger liability is not a completed filing control.
- Assigned frequency and first period
- Electronic filing, payment and authorization
- Gross sales, exemptions, taxable sales and tax bridge
- Tax engine, marketplace and ledger reconciliation
- Returns, credits and amended-return process
4. An active permit usually means zero returns
Many states expect every assigned return while an account is active, even with no sales, all marketplace-facilitated sales or no tax due. Missing a zero return can generate estimated assessments, notices or penalties.
A zero filing still requires review. Confirm no reportable activity and determine whether marketplace gross sales must appear before a deduction. Follow the account instructions and current return because state presentation varies.
5. End responsibility through formal closure
Falling below a threshold does not automatically cancel a permit or return requirement. Test continuing physical facts and state duration rules, then request cancellation rather than simply stopping filings.
Complete the final return, pay balances, archive certificates and retain state confirmation. If activity resumes, reassess registration instead of reusing a closed account.
