Stripe Tax vs Vertex 2026: Sales Tax Automation Compared

The short answer: choose by where your transaction data lives

Sales tax automation is software that works out the tax due on each sale, tracks where you owe it, and, in some products, registers you with states and files the returns. Stripe Tax and Vertex both do the first part. They differ sharply on who they are built for, how they are priced and how much of the compliance chain they cover.

TL;DR: If your orders run through Stripe, you sell mostly in the US, and you want one vendor to calculate, register and file, Stripe Tax is the simpler and more transparent purchase. If your orders and purchases flow through an ERP such as SAP, Oracle, NetSuite or Dynamics, or you need purchase-side tax, on-premise deployment or very large jurisdiction coverage, Vertex is the engine built for that and you should budget for a quote and a project.

One naming point settles a common confusion before you compare anything. Neither product in your search has been renamed or discontinued as of this guide's research date, but Stripe's US filing is run by a related company. Stripe's own documentation says Stripe files your US sales tax through TaxJar, a Stripe company, and that automated US filing is available in 46 US locations with a state-level sales and use tax according to Stripe's filing documentation (2026). So if you see TaxJar mentioned next to Stripe Tax, that is the filing arm, not a separate competitor. On the Vertex side, this guide covers the O Series tax engine plus the separate Vertex Indirect Tax Returns product, because Vertex sells calculation and filing as distinct pieces.

The legal backdrop explains why the decision matters. All 45 states with a statewide sales tax, plus Washington, D.C., have adopted economic nexus, and most set the trigger at $100,000 in sales over the current or previous calendar year, according to Kintsugi's state guide (2026). The same tracker, last updated in September 2026, shows rules still moving: Kentucky removed its transaction test effective August 1, 2026. Kintsugi sells sales tax software, so treat its table as a convenient summary and confirm your states with each revenue department. For a wider field that includes other vendors, see the sales tax nexus automation comparison.

Key Takeaways

• Stripe Tax publishes its prices and bundles registration and filing into its Complete tiers, so you can model total cost before talking to sales. Vertex's pricing is Quote-based, so budget time for procurement.

• Vertex wins on ERP depth, purchase-side tax and deployment choice. An independent head-to-head lists Vertex ahead on 13 of 22 differing capabilities and Stripe Tax ahead on 9.

• Stripe Tax wins on speed to value for Stripe-based sellers: nexus alerts, a "Register for me" option and dashboard-based filing sit in one product.

• Filing is a separate decision on both sides. Stripe files through TaxJar and requires a Complete subscription; Vertex files through a separate returns product.

• Neither tool removes your review duty. Someone must reconcile collected tax to the general ledger each period, and that step is where most errors surface.

• The deciding question is not features. It is whether tax determination must live inside your ERP or inside your payment flow.

Who this is for

This guide is for a controller or finance lead at a company that sells online into many US states and is close to choosing between a payments-native tax product and an enterprise tax engine. It assumes you already know what economic nexus is and need a straight comparison of cost, coverage and effort.

Red flags that should stop you from choosing Stripe Tax: your tax determination must run inside SAP, Oracle or Dynamics for both sales and purchases; you need on-premise or hybrid deployment; your auditors expect an ERP-certified tax engine. Red flags that should stop you from choosing Vertex: you have no one to own an implementation project; you need a published price to get budget approval this quarter; you want a vendor to register you in new states on your behalf and see no such service described on Vertex's product pages.

How we evaluated these tools

This is a buyer's guide built from public information. It uses each vendor's pricing and product pages, Stripe's technical documentation, Vertex's SEC filing, and independent write-ups, several of them from competing vendors, which is flagged where relevant. Nothing here comes from hands-on testing, and no vendor paid for placement. The criteria below are weighted for a company selling online across many states.

Analysis: the weights favor sellers whose pain is filing workload and budget predictability. If you run a large ERP estate with purchase-side tax, move 10 points from price transparency to ERP fit and Vertex looks stronger. The weights are a starting point, not a verdict.

Side-by-side feature matrix

This table separates what the vendors and reviewers state from our analysis. "Not stated" means the pages reviewed did not say, which is different from "unsupported."

The facts behind the matrix: Vertex states that O Series supports 19,000 jurisdictions with continually updated rules and rates according to Vertex's O Series page (2026), and its returns product supports "over 1600+ returns" according to Vertex's returns page (2026), with direct transmission for California and Illinois. The independent capability count comes from an ERP software directory: Vertex leads on 13 of 22 capabilities; Stripe Tax leads on 9 according to ERPResearch (2026). That page grades both tools identically on 18 further capabilities, and it credits Stripe Tax with the stronger economic nexus tracking and tax ID validation while crediting Vertex with purchase-side determination and configurable custom tax rules.

Analysis: the matrix shows two products aimed at different centers of gravity. Stripe Tax is a payments-adjacent product that happens to reach into registration and filing. Vertex is a tax engine that plugs into many transaction systems and sells filing as an adjacent module.

Pricing and total cost, checked October 8, 2026

Pricing checked October 8, 2026. Stripe publishes its prices; Vertex does not. The Stripe figures below come from the vendor's pricing page and are monthly prices on a one-year contract for the Complete tiers.

Those figures come from Stripe's pricing page (2026). The same page warns that additional fees may apply for registrations and filings outside the US, or if you exceed plan limits, and it does not list registration or filing fees for the pay-as-you-go option. A useful anchor for the API route: Stripe Tax Basic API fee: 50¢ per registered-location transaction according to Stripe's pricing page (2026). Pay-as-you-go also makes the first-year cost easy to forecast because nothing recurs when volume is zero.

Vertex is the opposite. Vertex's own product pages state no price, and the description of what drives the quote comes from competitors. TaxCloud, which competes with Vertex, says costs depend on company size, headcount, solution scope and modules, that consulting and implementation services are usually billed separately, and that its Certificate Center sells for an additional monthly fee, according to TaxCloud's Vertex pricing explainer (2026). Treat that as a checklist of line items to ask for, not as a price. For vendor viability, Vertex's own SEC filing reports Vertex gross revenue retention: 95% at June 30, 2026 according to Vertex's August 2026 SEC filing (2026). That is a company-wide retention figure, not a price, and it says customers tend to stay, which also means switching costs are real.

The second cost table converts Stripe's published rates into monthly cost at different volumes. It shows when the subscription beats the per-transaction fee. Basic covers calculation only; the Complete tiers also bundle the registration and filing counts listed above.

Analysis: at every volume shown, the Complete subscription costs less than the per-transaction API fee, and it adds registrations and filings that Basic does not bundle. The catch is the other limits. A Complete tier can also run out of registrations or filings before it runs out of transactions, and Stripe's filing documentation says you need a Complete subscription for TaxJar to file for you. Vertex cannot be placed in this table until you have a quote, so ask for a written proposal that itemizes the engine license, returns, certificate management, support tier and implementation services.

Worked example: what the math looks like for a mid-sized online seller

This is an illustration, not a measured result. Suppose a seller has 1,500 taxable transactions a month in five states where it is registered, and files quarterly in each, which is 5 states × 4 filings = 20 filings a year. Through the Stripe API, each tax.calculation response returns a tax_breakdown array that the finance team maps to a state tax payable account. On the Basic API route the fee is 1,500 × $0.50 = $750 a month, or $9,000 a year, with 15,000 included calculation calls (1,500 × 10) and registration and filing priced separately through partners. The smallest Complete tier covering 1,500 transactions is the $1,000 tier, which costs $1,000 × 12 = $12,000 a year and includes 6 registrations, 20 filings and 25,000 calculation calls. The gap is $12,000 − $9,000 = $3,000 a year, which is effectively what the bundle charges for 20 filings and up to 6 registrations. If outsourced filing plus internal staff time for 20 returns would cost more than $3,000, the bundle wins; if less, Basic wins. The same seller cannot get a comparable Vertex number until it receives a quote, so the useful test is to ask Vertex to price the same 1,500 transactions and 20 filings and compare the three-year total including implementation.

Stripe Tax: profile

Best fit: companies that already bill through Stripe Payments, Checkout, Billing or Invoicing, sell mostly in the US, and want calculation, registration and filing from one vendor. Stripe also states that its API works with other payment processors, so a non-Stripe seller can integrate, but the value drops once data has to be pushed in.

What is stated: Stripe's product page describes threshold monitoring by volume and transaction count, 600+ product tax categories, tax ID validation, and no-code, low-code and full API setup. Its US documentation says Stripe monitors economic nexus only for sales outside the state where your business is based, and it recommends consulting a tax advisor about where to register.

Limitations: an independent directory lists no stated ERP integrations for Stripe Tax, and Stripe Tax is cloud only. Automated filing needs a Complete subscription, a US bank account for remittance, and state details such as tax ID and filing frequency. Stripe only files transactions where automatic tax was enabled, so manual invoices without Stripe Tax and sales processed before enablement are excluded unless you import them by CSV.

Implementation: the lightest path is a dashboard configuration. The filing documentation describes a monthly summary email, processing that starts as early as the 7th of the month, and change requests due before the 6th at 6 PM ET. That calendar is a control point your team must own.

Primary evidence: Stripe pricing, filing documentation, Tax Calculation API reference.

Vertex: profile

Best fit: mid-market and enterprise sellers with an ERP, multiple transaction systems, purchase-side tax needs or a tax team that wants configurable rules. Vertex describes a single tax engine connected to ERP, procurement, e-commerce and billing systems.

What is stated: O Series provides tax content licensable by industry, a customizable calculation engine, US address cleansing with USPS ZIP+4 enrichment and Tax Area ID assignment, and edge containers that put the engine at the point of transaction. The returns product runs as a desktop install or hosted cloud, with role-based access and SOX audit logs, and supports more than 100 standard reports.

Limitations: no public price, and the sources reviewed describe implementation, certificate management and higher-tier modules as separate cost lines. Reviewers cited by competitors raise cost and support responsiveness; treat those as signals to probe in references, not as verdicts. The O Series page reviewed does not describe return filing, so filing is a second product and a second contract conversation.

Implementation: expect an ERP-connected project: data mapping, taxability configuration, testing and rollout, with your IT or an integrator involved. No source reviewed gave a reliable duration, so ask Vertex for a reference customer with your ERP and a comparable number of systems.

Primary evidence: O Series, Indirect Tax Returns, Vertex's SEC filing.

Where the work actually lands: reconciliation, alerts and the DIY question

Whichever engine you choose, three jobs stay with your team: confirming that collected tax ties to the ledger, acting on nexus alerts, and keeping evidence for an audit. This is where a proposed workflow from US Tech Automations fits, and the following describes a configurable design, not a live deployment or measured result. In the Stripe case, the trigger is a scheduled run in the first days of each month, ahead of the 6th-of-month change-request cutoff. The action pulls the itemized transaction export that Stripe's dashboard produces for each location, reads the per-state totals, and compares them with the sales tax payable balance in your accounting system through its API. The output is a variance report by state, with any difference above a threshold you set routed to the controller. Prerequisites are API or export access to Stripe and to the ledger (QuickBooks Online and NetSuite both expose APIs), a named reviewer, and a documented tolerance. The human review point is mandatory: the controller approves or files a change request in Stripe before the cutoff, and the workflow never files or alters a return itself.

The same design can be pointed at a Vertex estate. The trigger is month-end close; the action collects the standard reports and data extracts Vertex says it provides for compliance, audit and reconciliation, matches invoice-level tax to the ERP tax liability accounts, and flags orphaned or zero-tax lines in states where you are registered. The output is an exception queue with the source document attached and an approval log. Prerequisites are a read-only report or database extract from the tax engine, ERP access and agreed account mappings. Review points are the controller's sign-off on exceptions and a tax manager's decision on any taxability disputes. For CRM-originated B2B orders, a connector such as the one in how to connect Salesforce to Stripe is a prerequisite, so that tax-exempt status is captured before an invoice is created.

Many readers will ask whether Zapier, Make or n8n can do this instead. They can. Configured well, those tools support run histories, retries, error branches and audit evidence, and building a Stripe-to-spreadsheet feed is a well-trodden path, as the guide on connecting Stripe to Google Sheets shows. The tradeoff is ownership: you must design and maintain observability, idempotency so a retry does not double-count a transaction, escalation when a scenario fails silently, access controls on tax data, and ongoing maintenance when an API changes. A proposed US Tech Automations design would configure those pieces as defaults for a finance workflow, namely an immutable run log, approval steps with named approvers, and an exception queue. It still needs your API access, your account mappings and your reviewers, and it does not replace the tax engine, calculate tax or file a return. If you have a capable operations engineer and a low-volume workflow, the DIY route may be the cheaper answer.

When NOT to use US Tech Automations: skip it if you sell only through Stripe at modest volume and Stripe's dashboard totals plus a monthly spreadsheet check already give you comfort; if your ERP-native Vertex configuration already reconciles tax to the ledger inside the system; or if you have no one willing to review exceptions, because an alert nobody reads is only noise. In those cases the built-in reports or a simpler no-code flow are the better value.

Common mistakes in this decision

• Comparing Stripe's published monthly price with Vertex's license alone, and ignoring implementation, certificate management and returns on the Vertex side.

• Assuming that calculation means compliance. Registration, filing and payment remittance are separate tasks on both products.

• Choosing a tool before listing which systems must send it data. For Stripe Tax, manual invoices created without automatic tax are not filed.

• Treating a competitor's blog as a price list. Third-party estimates of Vertex cost are not a quote.

• Forgetting that thresholds change, which means alerts need an owner rather than a one-time setup.

Decision checklist

1. Where is tax determined today: in Stripe, a storefront, or an ERP? Pick the engine closest to that system.

2. Do you need purchase-side or use tax determination? If yes, shortlist Vertex.

3. Do you want one vendor to register and file? If yes, price the Stripe Complete tiers against Vertex plus its returns product.

4. Can you wait for a quote and fund an implementation project? If not, favor published pricing.

5. Do you require on-premise or hybrid deployment? If yes, only Vertex fits.

6. Who reconciles collected tax to the ledger each period, and who approves variances?

7. Which of your states have recently changed thresholds, and who watches them?

Glossary

• Economic nexus: a tax obligation created by sales volume or transaction count in a state, without physical presence.

• Remote seller: a business that sells into a state where it has no office, staff or inventory.

• Tax determination: the calculation of what tax applies to a specific line item, address and date.

• Registration: obtaining a permit from a state so you can legally collect its tax; separate from filing.

• Filing and remittance: submitting the return and paying the collected tax to the state.

• Use tax: tax owed on purchases where the seller did not charge sales tax, which is why purchase-side determination matters.

• Exemption certificate: a buyer-supplied document proving a sale is not taxable, which must be kept for audit.

Frequently asked questions

Is Stripe Tax cheaper than Vertex?

Stripe Tax is easier to price because it publishes tiers from $90 a month, while Vertex is Quote-based, so no honest cost comparison is possible until you have a written Vertex proposal.

Does Vertex file my sales tax returns?

Vertex offers filing through a separate product, Vertex Indirect Tax Returns, which prepares and e-files returns, while the O Series page reviewed describes determination and reporting rather than filing.

Can I use Stripe Tax if my payments run through another processor?

Yes, Stripe states that its API works with other payment processors, but you must send the transaction data yourself, which removes much of the convenience of the native integration.

Does Stripe Tax register me in new states?

Yes, for remote sellers Stripe documents a "Register for me" option with its Complete tiers, though it also advises consulting a tax advisor about where you need to register.

How long does a Vertex implementation take?

No source reviewed gave a reliable duration, so ask Vertex for a reference customer with your ERP and a comparable number of connected systems.

Was TaxJar discontinued when Stripe Tax launched?

No evidence of a discontinuation turned up in this research, and Stripe's documentation describes TaxJar as a Stripe company that files US returns on behalf of Stripe Tax customers.

Conclusion: pick the engine that matches your system of record

If your system of record is Stripe and your problem is US filing workload, Stripe Tax is the lower-friction choice, with tiers you can price today and a bundled path from alerts to registration to filing. If your system of record is an ERP and your problem is determination across sales and purchases, Vertex is the engine designed for it, and the real work is negotiating scope and funding implementation. Either way, someone must reconcile the output to the ledger every month. To see how that review step could be wired to your own exports and approvals, see how US Tech Automations configures this. For adjacent tax paperwork in client-facing accounting work, the guide to tax document software for accounting firms covers a related decision.