Most online sellers do not learn about the Streamlined Sales Tax Project until their accountant says something like, "You crossed economic nexus in seven states last quarter — here are the seven separate registration packets you have to fill out by Friday."
That moment is when the cost of Wayfair stops being theoretical. Since the 2018 Supreme Court ruling in South Dakota v. Wayfair, every state with a sales tax can require remote sellers to collect once they cross an economic threshold — typically $100,000 in in-state sales. The result is roughly 11,000 taxing jurisdictions, 46 different state portals, dozens of forms, and a compliance bill that can run into five figures a year for a business doing $2 million in revenue.
The Streamlined Sales Tax (SST) Project is the one piece of infrastructure designed to soften that blow. Twenty-four states accept a single registration through one portal, and if you qualify as a "CSP-compensated seller" (the term that replaced "volunteer seller" in the SST agreement), the states themselves will pay a Certified Service Provider to calculate, collect, and remit your sales tax for free.
Here is how the program actually works in 2026, who it helps, who it hurts, and how to decide whether to opt in.
What the Streamlined Sales Tax Project Actually Is
SST is a multistate compact, not a federal law. It started in 2000, long before Wayfair, when states realized that the only way Congress would ever let them tax remote sellers was to first simplify sales tax themselves. The Streamlined Sales and Use Tax Agreement (SSUTA) standardizes the parts of sales tax that drove sellers crazy — uniform definitions for what counts as "candy" or "clothing," uniform sourcing rules, uniform exemption certificates, a single registration system, and a process for certifying tax software vendors.
The Governing Board reports 34,073 active registrations as of April 30, 2026, with 28.3% of those sellers using a Certified Service Provider. The next Governing Board annual meeting is scheduled for October 13, 2026.
The 24 Member States in 2026
Twenty-three states are full members, and Tennessee is an associate member that has adopted most of the agreement but not all of it:
Arkansas, Georgia, Indiana, Iowa, Kansas, Kentucky, Michigan, Minnesota, Nebraska, Nevada, New Jersey, North Carolina, North Dakota, Ohio, Oklahoma, Rhode Island, South Dakota, Tennessee, Utah, Vermont, Washington, West Virginia, Wisconsin, and Wyoming.
That list is worth memorizing if you sell across state lines. Notice what is not on it: California, Texas, Florida, New York, Illinois, Pennsylvania, Massachusetts, and Virginia. Roughly half of U.S. retail sales happen in states that are not SST members, which means SST is a powerful tool — but never a complete solution.
How the SSTRS Portal Works
The Streamlined Sales Tax Registration System (SSTRS) lives at sstregister.org. The user experience is simple by sales tax standards:
- Create an account with an email and a password.
- Provide the business legal name, entity type, FEIN, NAICS code, contact information, and the date you want each state's registration to take effect.
- Pick which states you want to register in. You can pick all 24 or a subset.
- Submit. The system issues an SSTID (your Streamlined ID) and forwards your information to each state.
Sellers who have done this report registering for 15 state permits in about 20 minutes. The registration itself is free. By contrast, registering directly with each Department of Revenue can take an hour per state and sometimes requires a notarized application, a bond, or a power of attorney.
One subtlety: once you have an SSTID, each state still mails physical confirmation and account credentials. For roughly ten of the SST states, that mail can take seven to fourteen business days. If you need to start filing immediately — say because nexus was triggered last quarter — you may want to register directly with those states alongside SSTRS so you can access their portals within 24 to 48 hours.
Certified Service Providers and the "Free CSP" Benefit
This is the part of SST that changes the math for most small sellers.
A Certified Service Provider (CSP) is a tax software vendor whose system has been audited and certified by the Streamlined Sales Tax Governing Board. Four CSPs are currently active: Avalara, TaxCloud, Sovos, and AccurateTax. The CSP plugs into your e-commerce platform, calculates tax in real time at checkout, files returns in every SST state, and responds to state tax notices on your behalf.
The remarkable part is the funding model. In SST states, if you qualify as a "CSP-compensated seller," the state pays the CSP — not you. The compensation is a percentage of the tax remitted, so the state effectively takes a small fee off the top of each collection in exchange for the CSP doing the work.
To qualify as a CSP-compensated seller in a given SST state, you must meet all of these tests during the 12 months before you register in that state:
- No fixed place of business in the state for more than 30 days.
- Less than $50,000 of property in the state.
- Less than $50,000 of payroll in the state.
- Less than 25% of your total property or total payroll in the state.
- You were not already collecting sales or use tax in that state as a condition of selling to the state government.
If you pass those tests, you qualify for free CSP services in that state. You can pass in some SST states and fail in others — qualification is per-state, not all-or-nothing.
The Audit Liability Shield
This benefit gets less attention than the "free" one, and it is arguably more valuable.
When you use a CSP and provide accurate information about your products and customers, the Streamlined agreement transfers responsibility for tax calculation errors away from you. If the CSP applies the wrong rate or misclassifies a product, the CSP and the state — not your business — handle the consequences during an audit. For a seller pushing tens of thousands of transactions a month across multiple states, that shield is worth substantially more than the cost of the software it replaces.
You do still owe the correct amount of tax. You also still owe the tax on transactions the CSP processed if the underlying data was wrong (for example, you misclassified your products in the CSP's catalog). The shield covers calculation, not classification.
The Drawbacks: Why SST Is Not Always Right
The agreement makes three trade-offs that bite some sellers.
You must register in all 24 SST states, or accept that registering in a subset still means the same set of obligations everywhere you pick. If you only have nexus in three SST states, registering through SSTRS in all 24 voluntarily creates filing obligations in all 24, even where you collect zero tax. You can register in only those states where you actually have nexus, but doing so trades away one of the main reasons sellers like the system — set-it-and-forget-it coverage.
You give up vendor compensation in most states. Many states pay a small "vendor discount" (typically 0.5% to 1.5% of tax collected) to sellers who file on time. CSP-compensated sellers generally do not receive that discount; the state is already paying the CSP. For a high-volume seller, the vendor discount can outweigh the CSP value.
The state Department of Revenue access is slower at first. Roughly ten SST states require physical mailings to issue account credentials. If you need to access a state portal immediately to file or respond to a notice, the direct-registration path is faster.
Filing frequency may be wrong out of the gate. SSTRS does not ask you for projected annual liability. States then assign filing frequency from internal defaults, which often means monthly filing even when quarterly would be appropriate. Sellers report fixing this with a phone call to the state, but it is an avoidable annoyance.
SST does not cover non-member states. If most of your sales are in California, Texas, Florida, or New York, SST barely touches your compliance burden.
Economic Nexus Thresholds Are Still Shifting in 2026
The other moving piece in 2026 is what triggers nexus in the first place.
Most states adopted the post-Wayfair default: $100,000 of sales or 200 separate transactions in the current or prior calendar year. That second prong — 200 transactions — has been the bane of subscription companies and small-ticket sellers. A $4 digital product hitting 200 customers in a state triggers full compliance.
Sixteen states have now dropped the 200-transaction prong entirely. Illinois did so effective January 1, 2026; nexus there now requires only $100,000 in Illinois sales. New York remains the strict outlier — you need both $500,000 in sales and 100 transactions before nexus attaches.
The practical effect: small sellers with high transaction volume but low average ticket size are slowly being released from compliance obligations in states they should never have been pulled into. Re-check your nexus map every quarter; the answer in 2024 is not the answer in 2026.
SaaS and Digital Goods: A Separate Headache
For software companies, the SST decision is layered on top of a deeper question: is your product even taxable?
Around 25 U.S. jurisdictions tax some form of Software-as-a-Service in 2026, and the rules are not uniform. Texas, New York, Pennsylvania, Washington, Ohio, Massachusetts, and South Carolina generally tax SaaS at the full state rate. California, Virginia, Florida, and Missouri exempt it. Hawaii and Washington treat SaaS as a taxable digital service under separate definitions. Maine joined the taxing-states club in 2026 by adding digital audiovisual and digital audio services to its taxable list, which catches streaming and subscription businesses.
SST helps SaaS companies in the member states because the agreement defines digital products and digital services consistently. It does not, however, override a state's underlying choice about whether SaaS is taxable. The SST agreement makes taxability predictable; it does not make it favorable.
When SST Is the Right Choice
SST tends to be worth the trade-offs when:
- You sell physical or digital goods to customers across most of the country.
- A material share of your customers are in SST states (especially Indiana, Ohio, Michigan, Washington, or New Jersey).
- You are a small or mid-size seller without a dedicated tax team.
- Your average transaction value is low and your transaction count is high — the CSP automation pays for itself.
- You care more about audit-shield protection than the small vendor discount.
SST tends to be the wrong choice when:
- Almost all your customers are in non-SST states.
- You have a complex product taxability situation that the CSP's catalog cannot model accurately.
- You have nexus in only one or two SST states and want to avoid creating registration obligations in 22 more.
- Your largest cost is the lost vendor discount in high-volume states.
A Practical Multistate Sales Tax Workflow
Once you decide on SST, the operational sequence looks like this:
- Map nexus first. Pull the prior twelve months of revenue and transactions by ship-to state. Build a sortable table. Apply each state's current threshold.
- Register through SSTRS only in states where you have nexus or expect to within ninety days. Resist the urge to "voluntarily" register everywhere to feel covered. Each registration is a filing obligation.
- Pick a CSP. Compare Avalara, TaxCloud, Sovos, and AccurateTax on integration with your platform (Shopify, WooCommerce, BigCommerce, Stripe, NetSuite, etc.), product-taxability mapping, and exemption certificate management.
- Onboard your product catalog. Misclassified items are the single biggest source of CSP errors. Spend the time on this once.
- Reconcile monthly. Match what the CSP collected to what hit your bank account and what is sitting in your sales tax payable accounts. The first month is always ugly; by month three it should be clean.
- Keep direct registrations open in non-SST states with nexus. California, Texas, Florida, New York, and others still require separate filings.
Where Bookkeeping Makes or Breaks This
The single most common sales tax bookkeeping mistake is treating collected tax as revenue. It is not. It is a liability — money you are holding for the state until you remit it.
A clean chart of accounts for a multistate seller separates:
- Sales — taxable, by state if you want margin analysis by region.
- Sales — exempt, with exemption certificate references.
- Sales tax payable, one liability account per state (or per CSP remittance, if you reconcile in bulk).
- Sales tax expense, only if you are absorbing tax you should have collected.
- CSP fees, separately from sales tax expense, so you can see the true cost of the program.
When the CSP files a return, the journal entry debits the per-state sales tax payable account and credits cash. When you reconcile, the per-state payable should run to zero after each filing — anything left over is a sign of a timing mismatch or a calculation error you need to chase down.
Plain-text accounting tools make this kind of granular liability tracking trivial because you control the chart of accounts directly. If your bookkeeping system collapses all sales tax into one bucket, you lose the ability to reconcile per-state remittances against per-state collections — and that is exactly the reconciliation an auditor will ask you to produce.
Keep Your Multistate Tax Records Clean From Day One
Sales tax compliance is one of those areas where the books either save you in an audit or hang you. Beancount.io provides plain-text accounting that gives you complete transparency and version-controlled history over every per-state liability — no black boxes, no vendor lock-in, no surprises when the state of Washington sends a notice asking why their numbers do not match yours. Get started for free and see why developers and finance professionals are switching to plain-text accounting.