A sales tax permit is not simply an account you open when checkout is ready. Registration should follow a documented nexus conclusion and should establish the legal entity, jurisdiction, collection start date, filing frequency, and owner of every ongoing obligation.
Key takeaways
Confirm why and when the business must register before submitting an application.
Prepare entity, ownership, location, product, and prior-registration data in one controlled file.
Do not collect tax before the permit or state procedure allows it.
Treat the permit as the beginning of filing, payment, notice, and recordkeeping duties.
Confirm the registration obligation first
Start with the event that created the obligation: physical presence, an economic nexus threshold, marketplace activity, acquisition, voluntary registration, or another state-specific rule. Save the official authority and the date the rule applies to the business.
A threshold warning is not always the legal registration date. Measurement periods, grace periods, and physical-presence rules can produce different effective dates. If earlier exposure exists, evaluate remediation before assuming a current application resolves the past.
- Identify the legal entity and nexus event.
- Calculate the trigger date from source transactions.
- Separate required, voluntary, and historical registrations.
- Obtain professional advice for material prior-period exposure.
Choose the right registration channel
Many states use their own revenue portal. Streamlined Sales Tax member states also provide the SSTRS, a free registration route that can cover selected member states. A centralized application simplifies entry, but each selected state still creates its own account and filing obligations.
Avoid creating a second account when the entity already has a permit from an acquisition, former channel, or prior voluntary registration. Search internal records and confirm the existing legal name, tax ID, and account status before applying.
- Check state and Streamlined registration options.
- Search for active, closed, or dormant accounts.
- Confirm whether local registrations are separate.
- Record who controls portal credentials and recovery methods.
Prepare the application data package
Typical applications request entity type, legal and DBA names, federal tax ID, formation state, business and mailing addresses, responsible-party information, NAICS code, products sold, locations, estimated sales, bank details, and the date collection will begin.
Use an approved source file rather than retyping from memory. Inconsistent names, addresses, ownership percentages, or dates can delay the permit and create mismatches across states. Streamlined guidance also notes that registration dates can differ by state.
- Validate legal names against formation documents.
- Use current responsible-party and contact details.
- Document products, channels, and business locations.
- Keep sensitive application data in an access-controlled location.
Set the collection start date carefully
The start date should reflect the state rule and the operational go-live plan. Choosing an earlier date can create unexpected returns; choosing a later date can create undercollection. Coordinate the application with checkout configuration, product mapping, invoice language, and customer support.
Do not assume submission means immediate authority to collect. Confirm whether the state has issued the permit, account number, or other required approval. Save the confirmation and communicate the approved date to every channel owner.
- Tie the requested date to the nexus analysis.
- Allow time for configuration and testing.
- Prevent collection in unapproved states.
- Retain the permit and submission confirmation.
Capture every post-registration duty
A permit can create monthly, quarterly, annual, or other filing duties, including zero returns. Record the first period, due date, payment method, prepayment requirement, local schedule, renewal, bond, and notice address.
Assign a primary owner and backup. Portal access should not depend on one employee or an adviser’s private email. Build a calendar that distinguishes return due dates, payment cutoffs, holidays, and internal review deadlines.
- Record filing frequency and first return.
- Add zero-return and prepayment requirements.
- Store account numbers without exposing credentials.
- Review every state notice for frequency changes.
Validate the registration end to end
Before the first taxable order, test real addresses, taxable and exempt products, shipping, discounts, marketplace orders, refunds, and invoice display. Confirm that collected tax posts to the correct legal entity and jurisdiction liability account.
After the first return, reconcile orders to the return and payment confirmation. Review the registration inventory quarterly so duplicate, inactive, or missing accounts do not accumulate as the business changes.
- Require tax and finance sign-off before activation.
- Reconcile the first filing at transaction level.
- Track notices through resolution.
- Close accounts formally when obligations truly end.
Frequently asked questions
Do I need a separate sales tax permit for every state?
Generally, registration is state-specific, and some local jurisdictions can require additional accounts. Streamlined registration can simplify applications for member states but does not create one nationwide permit.
Can I collect sales tax while my permit is pending?
Do not assume so. Confirm the state procedure and effective date before collection; unauthorized collection can create remittance and customer-refund problems.
Does a marketplace seller still need a permit?
Possibly. Direct sales, physical presence, state reporting rules, inventory, or marketplace-sales treatment can preserve a registration duty even when a facilitator collects tax.
What happens after registration?
The business must configure collection, file assigned returns, make payments, retain records, manage notices, and keep the account current until it is formally closed.
Official sources
Reviewed against the following primary sources on Aug 8, 2026.