Stripe Tax vs Avalara for Filing and Tax Rates 2026

Stripe Tax vs Avalara comes down to who files

Sales tax automation is software that applies the rate on a taxable sale and, on some plans, prepares the return and sends the tax you collected to the state. The choice between Stripe Tax and Avalara is which of those jobs you are buying. Calculation tells the invoice what to charge. Filing closes the period with the state. A finance lead who prices only the rate, then discovers nobody is sending the return, has bought the smaller product.

Neither name has been retired. Stripe's current pricing page still sells Stripe Tax in two shapes, Tax Basic for calculation and collection, and Tax Complete for monitoring, registration, calculation, and filing. Avalara's calculation product is still AvaTax. The published small-business bundle on Avalara's sales-tax pricing page is Core Compliance, and that bundle includes AvaTax plus Managed Returns. Core Compliance is a plan name, not a rename of AvaTax. What has changed inside Stripe's US filing path is the operator of the return. Stripe's US filing guide states that Stripe files US sales tax through TaxJar, a Stripe company, and that TaxJar files on your behalf only after you are on a Tax Complete subscription. Tax Basic does not include that filing step.

TL;DR: use the Tax Basic plan on Stripe when every taxable sale already runs through Stripe and someone else will file. Use Tax Complete when you want Stripe's filing allowance and your return count fits a tier. Use the Core Compliance plan on Avalara when invoices also start outside Stripe, you want managed returns in the states where you are registered, and annual revenue is under $50 million. Above that revenue, or off the named connector list, Avalara's Custom plan is quote-based.

The rate environment is why the product choice is not a coin flip. Retail sales taxes account for 32 percent of state tax collections, 45 states levy a state sales tax, and the Average combined rate: 7.53% according to Tax Foundation (2026), with Louisiana's combined state and average local rate at 10.13 percent and California's state rate at 7.25 percent, while Alaska, Delaware, Montana, New Hampshire, and Oregon have no statewide sales tax. Local add-ons are the gap between a state rate and the combined rate. A tool that stops at a state code will miss districts.

Registration pressure is wider than a handful of headquarters states. Active SST registrations: 36,132 according to Streamlined Sales Tax Governing Board (2026), and 28.6 percent of the businesses registered through that system contract with a certified service provider, as of September 30, 2026. The same page records the Supreme Court's South Dakota v. Wayfair decision on June 21, 2018, which let states require collection from sellers without a physical presence. Economic-nexus thresholds still differ by state, which is why a rate engine and a multi-state nexus comparison answer different questions. The engine applies a rate where you are already registered. It does not decide whether you should register.

Key Takeaways

• The Tax Basic plan on Stripe calculates and collects tax where you are registered, at 0.5% per transaction on no-code Stripe tools or 50¢ per API transaction. Filing is not in that plan.

• Tax Complete lists at $90, $430, $1,000, and $1,500 per month on a one-year contract. The $90 tier includes 200 transactions a month, 4 filings a year, and 2 registrations a year. A US filing past the allowance is a $55 overage.

• The Core Compliance plan on Avalara is $79 per state per month or $799 per state per year for companies under $50 million in annual revenue, and it includes AvaTax calculation plus managed returns.

• The SST services plan on Avalara is $69 per state per month or $699 per state per year, and only qualifying sellers get the state-funded treatment. It is not a discount on every state.

• The Custom plan on Avalara has no printed dollar price. It is the path at $50 million and above, and it is also the path when your billing system is outside the named connector list.

• Combined rates are not the state rate. The average combined rate is 7.53%, and Louisiana's combined rate is 10.13%. A person still reviews the draft return before tax money moves.

How we evaluated these tools

The weights below are review weights for one buyer: a finance lead at an online or SaaS company selling into more than one US state and close to a purchase. They are not scores from either vendor, and they are not a ranking of brand quality. Filing and calculation each take 25% because this search is about whether the product stops at the invoice or also sends the return. Channel coverage takes 15% because many SaaS invoices are born in a billing tool or an accounting file, not only in a card checkout. A readable public price takes 15% because a quote you cannot see is not yet a comparable cost. Registration and nexus signals take 10% because the rate is only owed where you are registered or about to be. A human review before money moves takes 10% because both products can prepare a number that is still wrong if the source data is wrong.

Factual product claims in the tables below come from the vendor pages and the public sources linked in this piece. The pass marks are ours. A product can be a sound engine and still miss a pass mark for this buyer. Missing the filing mark means you still need a filer. Missing the channel mark means you still need a second feed. Missing the public-price mark means you stop and ask for a quote before you treat a blog estimate as a cost.

Calculation, filing, and the channels that feed them

Read the rows as jobs, not as stars. Tax Basic on Stripe is a calculation and collection product on Billing, Checkout, Invoicing, and Payment Links, plus an API path the pricing page describes for transactions from Stripe's payment APIs or any payment processor. Tax Complete keeps that calculation and adds obligation monitoring, registrations, and filings. The Core Compliance plan on Avalara bundles AvaTax calculation, Managed Returns filing and remittance, notice handling, nexus monitoring across all 50 states, and AvaTax Exemptions. The Custom plan on Avalara is the wider catalog, with no printed price.

The channel row is the one that surprises Stripe-first teams. No-code calculation follows Stripe Billing, Checkout, Invoicing, and Payment Links. The API rate is there when the charge is created somewhere else. Filing is a third door. The US filing guide says Stripe includes transactions where automatic tax is enabled, and it also says you can import transactions from another platform into the filing period you are reviewing. A Shopify order that never touched Stripe can still be part of a Stripe filing if you import it, and it will not be part of that filing if you forget. Avalara's pricing page names the connectors that sit on the published per-state plans, including QuickBooks Online, Shopify, Stripe, Amazon, Walmart, and WooCommerce. NetSuite, SAP, and Oracle show up as connectors on Avalara's AvaTax product page, and they do not appear in that Core Compliance name list. If your system of record is one of those, ask whether you are being quoted Core Compliance or Custom before you multiply a per-state price.

Exemption certificates are a separate drawer from the rate. AvaTax Exemptions is included in the Core Compliance description. Stripe's pricing page does not describe a certificate vault on Tax Basic or Tax Complete. Firms that already store resale certificates in a document system should keep that system. A tax document software comparison is the right place to judge the certificate drawer. Do not assume the tax engine you pick for rates is also the system of record for exemption files.

SST member states: 24 according to Streamlined Sales Tax Governing Board (2026), representing over 31 percent of the population. Full members on the remote-seller page are Arkansas, Georgia, Indiana, Iowa, Kansas, Kentucky, Michigan, Minnesota, Nebraska, Nevada, New Jersey, North Carolina, North Dakota, Ohio, Oklahoma, Rhode Island, South Dakota, Utah, Vermont, Washington, West Virginia, Wisconsin, and Wyoming, with Tennessee as an associate member. Avalara's pricing page says qualifying sellers may receive state-funded calculation, filing, remittance, and certificate handling in up to 25 states, and it mentions Pennsylvania through an analogous program. Those are different counts. Twenty-four is the Governing Board's member count. Up to 25 is Avalara's description of where state funding can apply. States such as California, Texas, Florida, and New York are outside the member list, so an SST price does not cover a national filing footprint.

Pricing checked against the public pages

Pricing checked October 9, 2026.

The Tax Complete plan on Stripe lists at $90, $430, $1,000, and $1,500 per month on a one-year contract. The $90 tier includes 200 transactions a month, 2,000 calculation API calls, 2 registrations a year, and 4 filings a year. The $430 tier includes 1,000 transactions, 10,000 calculation calls, 4 registrations, and 12 filings. The $1,000 tier includes 2,500 transactions, 25,000 calculation calls, 6 registrations, and 20 filings. The $1,500 tier includes 5,000 transactions, 50,000 calculation calls, 10 registrations, and 32 filings. A further tier is described only as 10 or more registrations, 5,000 or more transactions, 50,000 or more calculation calls, and 32 or more filings, with no extra dollar figure on the page. Tax Basic is 0.5% per transaction where you are registered, on Billing, Checkout, Invoicing, and Payment Links, or 50¢ per API transaction with 10 calculation calls included and 5¢ for each calculation call above 10. The same page describes tax calculation on 600+ product and service types, collection in 100+ countries, and filings in 90+ countries, according to Stripe (2026).

US filing overage: $55 according to Stripe (2026). On that support page the $90 tier lists an extra transaction at $0.50 and an extra calculation at $0.05, the $430 tier lists an extra transaction at $0.48, the $1,000 tier at $0.46, and the $1,500 tier at $0.35 with extra calculations at $0.04. A US registration past the allowance is a $150 overage, and the additional registration fee shown for the US is $0. The additional US filing fee shown beside the overage is also $0. The same table is much higher outside the US. Japan's additional monthly filing fee is $4,745 and the Japan filing overage is $4,800. A US SaaS company that also files abroad cannot copy the $55 figure into a foreign return.

The Core Compliance plan on Avalara lists at $79 per state per month or $799 per state per year, and the Core Compliance plus SST Services plan lists at $69 per state per month or $699 per state per year. The page calls the annual figure a 15% savings against monthly billing. Both published plans are for annual revenue under $50 million. The same page lists license guidance for as low as $119, sales tax registration at $403 per location, AvaTax calculation across 12,000+ U.S. tax jurisdictions, and 1,400+ signed integrations on the custom plan. It offers state-funded services in up to 25 states and names Avalara as one of five certified service providers. The Custom plan prints no dollar price. Volunteer tests on that page, measured over the 12 months before registration in each state, are no fixed place of business for more than 30 days, less than $50,000 of property, less than $50,000 of payroll, and less than 25% of total property or total payroll, according to Avalara (2026). The page also says transaction volume, the number of integrations, and the number of states still factor into what you pay. Treat $79 and $69 as the published per-state lists, not as a promise that volume never moves the invoice.

AvaTax, sold on its own rather than inside the per-state bundle, is described on Avalara's calculation page as usage-based annual tiers. That page does not print the dollar bands for those tiers. Where a dollar band is absent, write the price as quote-based. Do not paste an old tier chart from a third-party roundup into a budget.

What two states cost on the published lists

Here is an illustrative month, not a quote and not a customer result. A SaaS firm invoices 200 subscriptions at $149 each, all on Stripe Billing, in two states where it is already registered, and it files quarterly. Billed volume is 200 times $149, which is $29,800. The no-code Tax Basic rate is 0.5% of that volume, which is $149 for the month and $1,788 across 12 such months, and that amount does not include filing. The Tax Complete entry tier lists at $90 a month, so 12 months of that list is $1,080, and the tier includes 200 transactions a month plus 4 filings a year. Two states on a quarterly calendar produce 8 filings, so 4 filings sit past the allowance. The US filing overage is $55, and 4 times $55 is $220, which brings this filing-inclusive illustration to $1,300. Each finalized charge can be read from a tax.calculation, where tax_amount_exclusive is the tax added on top of the price and tax_breakdown splits that tax by jurisdiction. The Core Compliance plan on Avalara lists at $799 per state per year, so two states list at $1,598, and that list includes managed filing. On these published lists the two-state illustration is $298 lower on the Tax Complete path than on two Core Compliance states, before any volume adjustment Avalara's page says can still apply.

The six-state and ten-state rows are the same public unit prices, not a new rate card. They show why an entry tier that looks cheaper per month stops being the cheaper filing desk once the return count leaves the allowance. A ten-state monthly filer is comparing the $1,500 tier, plus US overages past 32 filings, with ten times the $799 annual list, and then asking whether those ten states are even on the named connector plan. If six of the ten invoices are created in NetSuite, the Avalara column may be the Custom plan, which is quote-based, and the Stripe column still needs an import or an API calculation for the NetSuite sales.

Who this is for

This comparison is for a finance lead at an online or SaaS business that already sells, or is about to sell, into more than one US state and wants a direct answer on calculation versus filing. You are in range if you can list the systems that create invoices, the states where you are registered, and how often each state wants a return.

Red flags: you want a law firm opinion on whether nexus exists, because neither product is that opinion. You want the vendor to become the seller of record for your revenue. Nobody on your team will look at a draft return before tax money leaves the bank account.

Choose the Tax Basic plan on Stripe when the taxable sale is already on Stripe, an accountant or in-house filer will send the returns, and you want the rate without a monthly subscription. Choose Tax Complete when those sales stay on Stripe or you will import the rest, you have a US bank account the filing guide says TaxJar will debit for remittance, and your count of registrations and filings fits a tier after you add the $150 and $55 US overages. Choose the Core Compliance plan on Avalara when annual revenue is under $50 million, your billing and storefront systems are on the named connector list, and you want calculation and managed returns for orders that never touch Stripe. Choose the SST services plan only after you test the volunteer rules state by state. Choose the Custom plan when revenue is $50 million or more, you have several legal entities, or the system of record is outside that named list.

The Tax Basic plan's limit is the job it does not do. It will not file. The Tax Complete plan's limit is the allowance. Four filings a year on the $90 tier is a small drawer if you are monthly in several states, and non-US filing fees on the support page are a different price list. Implementation on the Stripe side is a dashboard path: turn on calculation, add registrations, subscribe to Tax Complete if TaxJar will file, connect a US bank account, and review the draft totals and the transactions in them before processing starts. Sales with automatic tax off, manual tax rates, and subscriptions that were never moved onto Stripe Tax stay out of the filing unless you fix them or import them. Primary evidence is the Stripe Tax pricing page and the US filing guide linked above.

The Core Compliance plan's limit is eligibility and scope, not the existence of a filing product. Managed Returns, as the pricing page describes it, prepares the return, files it, remits the tax, and helps with notices. The list price is per state, for companies under $50 million, on a named set of connectors. Volume can still change the bill. The SST price is lower because participating states pay the certified service provider for covered work, and Avalara says it takes on liability for calculation errors in qualifying SST jurisdictions. That liability shift does not extend to a state where you fail the volunteer tests or to a state outside the program. Returns filed in 2025: more than 6.6 million according to Avalara (2026). That AvaTax page also counts 1 invoice as 1 transaction whether the invoice has 1 line or 200 lines, says a single postal code can fall across more than one city, county, and district so jurisdiction matching is geospatial rather than ZIP-based, puts the median self-serve setup at 26 days including registration steps outside Avalara, and puts a typical managed implementation for SAP or Oracle at 4 to 6 months. Sandbox access is described for customers before go-live. Primary evidence is the Avalara sales-tax pricing page and the AvaTax page just cited.

When NOT to use US Tech Automations: if every taxable sale is already on Stripe and your accountant files from the itemized export, the Tax Basic plan plus that accountant is the smaller stack. If you qualify for state-funded SST service, the certified service provider arrangement can cover calculation and filing in those states without an extra layer. If you only need a reminder on the filing calendar, the task list in the accounting system is enough. The rate engine and the signature on the return stay inside Stripe Tax or Avalara.

The review step neither price tag replaces

A proposed US Tech Automations workflow starts when a finalized Stripe invoice export, or a committed Avalara transaction export, lands on a schedule. The action compares the ship-to state on each row with a registration list the finance admin maintains, and the output is an exception row for any state on a sale that is missing from that list. Prerequisites are the export itself, from Stripe's tax reports or from Avalara, and a registration file with state, tax id, and filing frequency. A person approves any new registration. The workflow does not register the company and it does not send money.

On filing week the trigger is the draft filing summary for that period. US Tech Automations can be configured to count the locations in the summary against the allowance stored for the plan, such as 4 filings a year on the $90 tier, and to open a packet when the count would cross into the $55 US overage. Prerequisites are the filing summary and that allowance saved as a setting, not a guess typed into a chat. The output is an approval record with the totals that were reviewed. A tax manager signs it before remittance. This is a proposed design, not a live deployment and not a measured result.

Zapier, Make, and n8n can download that same export, retry a failed run, branch when a file is empty, and keep a run history when you build those paths. They are a fair alternative. The buyer then owns observability, idempotency so the same invoice is not queued twice, escalation, access control, and maintenance when a column in the export changes. A proposed US Tech Automations design can store the source file id, skip a duplicate export, and assign the exception to a role, with the same export prerequisites and the same human approval before anyone registers or remits. A general model is not a substitute for either design. It does not hold the rate table or the filing signature, which is the limit described in what a newer model changes for an accounting firm.

Common mistakes that make the cheaper list price the wrong one

• Pricing the 0.5% no-code rate as if it included US filing. That rate is calculation and collection where you are registered. Filing starts on Tax Complete, through TaxJar.

• Multiplying $79 by your state count when the invoice system is NetSuite, SAP, or another application missing from the Core Compliance name list. The wider AvaTax catalog and the published per-state plan are not the same offer. Off-list systems are quote-based.

• Taking the $69 SST price for a state where you have a fixed place of business, or $50,000 or more of property or payroll. The lower list is for qualifying volunteer sellers, and it does not cover non-member states.

• Assuming 4 included filings will carry a monthly calendar. Two states filed quarterly are already 8 returns. The US overage is $55 each past the allowance.

• Treating a ZIP code as the rate. Louisiana's state rate is 5.00 percent and its combined rate is 10.13 percent on the Tax Foundation table as of July 1, 2026. District-level rates are why the jurisdiction match matters.

• Letting an unreviewed export become a remittance. Both vendors describe a review step. Skipping it is how a missing invoice or a refund in the wrong period becomes a payment to the state.

A short list before you sign

1. Write down every system that creates a taxable invoice, including the one that is not Stripe.

2. List the states where you are already registered, and the filing frequency each state assigned.

3. Multiply states by frequency so you have a filing count for the year, then set that count next to 4, 12, 20, or 32.

4. Confirm whether annual revenue is under $50 million. If it is not, the Avalara column is quote-based.

5. Check the connector name against the Core Compliance list before you use $79 or $69.

6. If you want the SST price, test the 30-day, $50,000 property, $50,000 payroll, and 25% tests in each state.

7. Name the person who will review the draft return, and confirm the US bank account if TaxJar will remit.

8. Keep exemption certificates in the document system you already trust. Do not drop them because a rate engine was purchased.

Questions finance leads ask

Does Stripe Tax file US sales tax returns?

Tax Complete does, through TaxJar, and Tax Basic does not. The US filing guide says you need the Tax Complete subscription, a US bank account for remittance, and a review of the draft before processing. Included filings depend on the tier, from 4 a year on the $90 tier to 32 a year on the $1,500 tier, with a $55 US overage after that.

Is Avalara only a calculation engine?

AvaTax is the calculation engine, and Managed Returns is the filing and remittance service. The Core Compliance plan includes both for companies under $50 million in annual revenue. Standalone AvaTax usage tiers are described on the product page without printed dollar bands, so those bands are quote-based until a quote says otherwise.

What does the Tax Basic plan on Stripe cost?

The no-code price is 0.5% per transaction where you are registered, and the API price is 50¢ per transaction with 10 calculation calls included and 5¢ after that. There is no monthly subscription on Tax Basic. You are not buying filings at either of those rates.

What does the Core Compliance plan on Avalara cost?

The published list is $79 per state per month or $799 per state per year, and the SST services list is $69 per state per month or $699 per state per year. Sales tax registration is $403 per location, and license guidance is as low as $119. The Custom plan is quote-based.

Can Stripe file sales that were not charged on Stripe?

The US filing guide says you can import transactions from another platform into the filing period under review. Calculation on no-code tools still follows Stripe's own billing surfaces. The API rate is the published way to calculate tax on a sale from any payment processor, at 50¢ per transaction where you are registered.

When should a simpler tool win?

When NOT to use US Tech Automations: stay with the Tax Basic plan and your accountant when they already file from the export, stay with a certified service provider when SST funding already covers the states where you qualify, and stay with the accounting system's task list when all you need is a reminder. Add an orchestration layer only when the pain is mismatched registrations, duplicate exports, or an overage you want a person to approve before money moves.

The decision, then the layer above it

Buy calculation and filing as separate line items even when one vendor sells both. If the sales are on Stripe and the return count fits a Tax Complete tier after US overages, that tier is a coherent stack, with TaxJar doing the US filing and a person reviewing the draft. If the sales start in several systems, revenue is under $50 million, and the connectors are on the named list, the Core Compliance plan is the published per-state way to buy AvaTax and managed returns together. If revenue is $50 million or more, or the connector is not on that list, stop on quote-based and do not invent a price. If you qualify state by state, the SST services plan is the lower published list, and it still leaves non-member states on a normal bill.

The layer above either engine is the exception list and the approval on the draft. For that review queue, see how US Tech Automations configures this. The tax you charge still comes from the engine you select, and the payment to the state still waits on the person who signs the packet.