Avalara vs Vertex: Tax Engine Comparison for 2026

Key Takeaways

• Avalara publishes a per-state price for calculation plus filing below a stated revenue line. Vertex's indirect-tax products are quote-based, and Avalara's tier above that revenue line is quote-based too.

• The published Avalara plans name a short connector list aimed at commerce platforms and smaller accounting systems. SAP, Oracle, NetSuite, and Microsoft Dynamics are described with the custom tier, not with that list-price package.

• Avalara is named on the Streamlined Sales Tax certified-provider list that offers state-funded services. Vertex is not named on the list opened for this article.

• The latest Avalara ownership pages opened here still describe Vista as the majority shareholder after a confidential IPO filing. Vertex is a public company.

• Local U.S. sales-tax rates moved sharply in the first half of 2026, so the rate file is a selection criterion, not a brochure claim.

• A connector that posts tax is not a finished return. Someone still has to clear bad addresses and exemption gaps before money is remitted.

What you are actually choosing

A tax determination engine rates a transaction from the place of supply, the product, and the buyer's exemption status, then either prepares the return or hands a file to the team that does. Avalara and Vertex both sell that job. They do not sell the same package, and neither name was retired in the pages opened for this comparison. Avalara's calculation product is still AvaTax. Vertex's determination product is still O Series.

The useful split is narrower than a brand bake-off. Below a published revenue line, Avalara sells calculation and managed returns at a per-state list price, including a lower price when a seller qualifies for state-funded Streamlined Sales Tax services. Above that line, Avalara moves the buyer to a custom contract. Vertex documents determination, certificates, returns, and e-invoicing, and it does not publish a dollar price for those products. If your invoices start in Shopify, Amazon, Stripe, or QuickBooks and you are under the revenue line, price the Avalara list and test SST eligibility before you book a Vertex scoping call. If the system of record is SAP, Oracle, or a broad Microsoft estate with many entities, treat Vertex as a real finalist and make Avalara's custom tier bid the same scope, because the cheap Avalara plan does not claim those ERPs.

The invoice the engine rates often starts in another system. A clinic that bills recurring care through in-house dental membership plans still has to decide which of those charges are taxable. A software company whose product pages are drafted with AI writing tools for SaaS still needs a human tax category on the SKU, because marketing copy does not set taxability. An agency that runs a month-end pacing check so campaign invoices go out on time is working in the same window in which sales-tax returns are built. Those guides cover the upstream systems. They do not rate tax.

Who this is for

This guide is for a tax or finance lead at a mid-size company who already knows a spreadsheet will not survive the next nexus state or the next ERP project. You are comparing Avalara and Vertex because a shortlist meeting is close, not because you need a definition of sales tax. You have more than one selling channel, or you are about to, and someone on your team can review exceptions.

Red flags: nobody will review address failures and exemption mismatches before a return is filed; you collect in a single state only through that state's portal and you are not adding channels; you want filing done for you but you will not allow an API connection or a scheduled export from the billing system.

How we evaluated these tax engines

The weights below are a buying screen for this reader. They are not a score assigned to either vendor, and they are not a ranking from a review site. Rate and rule maintenance is 20% because a stale jurisdiction rate becomes a wrong invoice the day the city changes it. Returns, filing, and remittance are 20% because a correct calculation that nobody files still leaves the company exposed. Fit with the system that creates the invoice is 15%, because a low list price that cannot see your ERP is a second project. Exemption-certificate handling is 15%, because a calculation that ignores a valid certificate creates tax you should not have charged and a file you cannot defend. A price you can read before the sales call is 15%, because a quote-only comparison hides the first-year cost until late in the process. A required human review before filing is 15%, because an unattended connector will remit tax on bad addresses. The pass marks are the minimum we would want before a product stays on a shortlist. They are not measured results.

Factual claims in the tables and sections that follow come from vendor pricing pages, vendor product and research pages, a review comparison, a company release, a news report, and the Streamlined Sales Tax registration page. Judgments about who should buy which product are marked as analysis. Where a dollar figure was not on a vendor pricing page, the cell says Quote-based.

Who owns the products, and what is still for sale

Neither product has been folded into the other. You are still buying two separate companies with two different ownership stories, and that matters when you ask who will support the contract in three years.

Avalara went public in June 2018 and was taken private in 2022 in a Vista deal valued at $8.4 billion including debt, and on July 21, 2025 Reuters reported a confidential U.S. IPO filing with no share count and no price range disclosed, according to Reuters (2025). On November 12, 2025 a BlackRock-led group invested $500 million to purchase shares from existing holders, Vista remained the majority shareholder, and the release said Avalara supports over 43,000 businesses and government entities in more than 75 countries, according to PR Newswire (2025). This article does not treat Avalara as a listed company. No page opened here shows a completed later offering or a trading ticker.

Vertex, Inc. (NASDAQ: VERX) said on October 1, 2026 that it is trusted by Fortune 500 share: more than 60% according to Vertex (2026). The same announcement describes Vertex as a global indirect-tax company covering determination, e-invoicing, reporting, filing, and audit defense. Public-company status does not tell you the license cost. It does tell you that financial disclosures exist for Vertex in a way they do not, on these pages, for Avalara.

On scope, Avalara's published sales-tax plans bundle AvaTax calculation, managed returns, nexus monitoring, and exemption records for companies under the revenue line, and the pricing page points international work, e-invoicing, property tax, consumer use tax, 1099 and W-9, and excise to the wider product set or the custom tier. Vertex's cloud description covers determination, e-invoicing, global compliance reporting, and file-and-pay. Vertex's calculation docs add a seller call, a buyer call, and an owner call, so procurement accruals and inventory movements are in the engine design, not only customer invoices. Analysis: if your pain is U.S. sales-tax filing for a commerce stack, Avalara's list-price bundle is the package that matches the sentence you searched. If your pain is one determination standard across order management, procurement, and several ERPs, Vertex's documented shape matches that sentence, and you should price it as a project.

The rate file these engines have to absorb

City sales-tax rate increases outnumbered decreases by City rate ratio: 4.5 to 1 according to Vertex (2026), and that August 13, 2026 report also counts 463 combined rate changes and new rates from January 1 through June 30, 2026, a county increase-to-decrease ratio of 5 to 1, 63 new taxing cities in the half year, a combined average U.S. rate of 10.1881% in data dated June 30, 2026, and 12,566 new and updated sales and use tax jurisdictions as of that date, split on the page into 7,183 city, 1,972 county, 3,365 district, and 46 state. That 12,566 figure is Vertex's count of new and updated jurisdictions in the rate file. It is not Avalara's product-coverage claim, and it is not a statement that the country has only that many taxing places.

Analysis: both vendors live or die by how fast this file reaches your invoices. A mid-size team cannot read 463 changes by hand and push them into every channel. The buying question is not "does the vendor have content." Both say they do. The question is whether your channels actually call that content on each committed invoice, and whether a quotation that was never stored can still be reconciled to the return. Ask each vendor how a city change on a Tuesday reaches an order taken that night, and ask what you see when it does not.

The review and registration rows are cited in the sections below. They are repeated here so the rate-file shock and the buyer evidence sit in one view. They are not a combined score.

Head-to-head on seven buying questions

Price clarity comes first because it changes who is even allowed to buy the list-price product. Avalara prints per-state prices under its revenue line and withholds a printed enterprise price above it. Vertex withholds a printed price for the indirect-tax products reviewed here. A finance lead who needs a budget number this week can model Avalara's published plans with a calculator. That lead cannot model Vertex without a sales conversation. Analysis: do not let a Vertex proposal arrive in a different shape from the Avalara custom proposal. Ask both for first-year fees, renewal basis, implementation, exemption-certificate volume, returns, and extra entities, as one number.

System fit is the disqualifier most teams discover too late. The Core Compliance connector list on Avalara's pricing page names Amazon, BigCommerce, Campfire, DualEntry, eBay, Etsy, Miva, QuickBooks Desktop, QuickBooks Online, Rillet, Sage 50, Shopify, Shopify Marketplace Connect, Stripe, Tabs, TikTok, Walmart, and WooCommerce. The same page describes SAP, Oracle, NetSuite, and Microsoft Dynamics with the broader integration story and puts full access to the signed partner catalog on the custom plan. Vertex's real-time calculation page says Vertex Cloud connects to SAP, Oracle, and Microsoft. Analysis: a company on QuickBooks Online or Shopify can stay on Avalara's published plan and test it. A company on NetSuite or SAP should assume the Avalara conversation is custom, and should put Vertex in the same round rather than "trying the cheap plan first."

Filing is bundled differently. Avalara's published plans include managed returns: preparation, filing, remittance, and notice handling, plus a state-funded path for qualifying volunteer sellers. Vertex describes file-and-pay on Vertex Cloud and describes returns preparation in its sales and use tax materials, without a public package price. As of September 30, 2026 the Streamlined Sales Tax registration system showed 36,132 active registrations, 28.6% of those businesses contracted with a certified service provider, 23 full member states were listed plus Tennessee as an associate, and five providers were named as offering the service, Avalara, TaxCloud, Sovos, AccurateTax, and Avior, while Exactor is listed as certified but not currently offering the free service, and Vertex is not named, according to Streamlined Sales Tax Governing Board (2026). Analysis: SST status is a reason to keep Avalara on the shortlist when you are a remote seller with little property and payroll in participating states. It is not a reason to ignore Vertex if your footprint is physical, international, or tied to a large ERP the list-price plan does not name. State-funded service does not cover every state you might owe.

Exemption handling is included by name on Avalara's published plans through AvaTax Exemptions. Vertex's sales and use tax pages describe certificate collection and storage as part of the sales-tax process, including Certificate Center. Analysis: either way, the certificate is useless if the calculation call does not receive the customer tax identifier. A checkout flow that drops that field will charge tax to an exempt buyer and store a clean-looking invoice that is wrong.

Reviewer evidence is thinner on Vertex and wider on Avalara, which is what a 75-review sample versus a 365-review sample usually means. Reviewers give Avalara Avalara review score: 4.0 of 5 according to Software Advice (2026) across 365 reviews, with ease of use at 3.8, value for money at 3.6, customer support at 3.4, and functionality at 3.9, and 63% would recommend it, while the reviewed base is described as often small-business, with retail, consumer goods, and services at 34%, IT and software at 15%, manufacturing at 10%, and sales tax as the top use case at 37%. The same page scores Vertex at 4.3 of 5 across 75 reviews, with ease of use at 4.0, value for money at 4.1, customer support at 4.0, and functionality at 4.2, and 68% would recommend it. Analysis: Vertex's higher marks sit on a much smaller review set, and Avalara's support score is the weak spot in that comparison. Use the scores to plan reference calls, not to skip the connector test.

The API store-or-not rule is a practical Vertex point from the calculation docs. A seller calculation is a POST to /v2/supplies, and the sale message type may be Quotation, Invoice, or Distribute Tax. The docs say the message type decides whether the calculation is kept for reporting and remittance. Avalara's create-transaction model makes a similar split between an order, which is an estimate, and an invoice, which is stored. Analysis: if your checkout only sends quotes, neither engine will build a return from those calls. The committed invoice has to be sent again under the document type that is stored.

Human review is the gap neither pricing page closes for you. Both vendors can be wired so tax appears on the order with no one looking. That is how bad ship-to addresses and expired certificates reach a state portal. The review question belongs in the contract and in the integration design: who sees the lines the engine will not rate, and what happens if that person is out on filing day.

Pricing and a worked filing cost

Pricing checked October 10, 2026.

An illustrative company under $50 million in annual revenue that files in 8 states extends the Annual list price: $799 per state according to Avalara (2026) to 8 × $799 = $6,392 a year, against $79 per state per month × 8 states × 12 months = $7,584, or $699 per state × 8 = $5,592 a year on the SST annual rate when the seller qualifies, while that page also lists $69 per state per month on the SST plan, calls the yearly Core Compliance figure a 15% savings, describes AvaTax as covering 12,000+ U.S. tax jurisdictions and nexus monitoring across all 50 states, offers state-funded services in up to 25 states for qualifying volunteer sellers, sets volunteer tests that include less than $50,000 of in-state property, less than $50,000 of in-state payroll, less than 25% of total property or payroll, and no fixed place of business for more than 30 days, says this package covers Canadian GST/HST, PST, and QST for U.S. and Canada selling, describes broader coverage across 190+ markets, and reserves 1,400+ signed partner integrations for the custom tier at $50 million and above. If the invoice is created in QuickBooks Online, the tax figure still has to be written to TxnTaxDetail.TotalTax on the QuickBooks Online sales-tax workflow and a reviewer has to accept it before anyone treats the return as final.

The 15% label is the pricing page's description of annual billing versus monthly billing. The dollar gap in the illustration is straight multiplication of the published rates for 8 states, not a second discount. The SST totals apply only if the seller qualifies. They are not a coupon on the standard plan. No Vertex pricing page opened in this session listed a dollar amount, so Vertex is Quote-based. Avalara above the revenue line is Quote-based as well.

License guidance on Avalara is listed for as low as $119, and sales tax registration on Avalara is $403 per location, according to Avalara (2026). "As low as" means the guidance fee can be higher. Registration is stated per location, so eight new locations are not one fee.

These rows are arithmetic on published Avalara rates for a made-up 8-state footprint. They are not a quote, they omit implementation and overage fees, and they do not include Vertex because Vertex did not publish a rate to multiply. A total cost comparison is unfinished until both vendors answer the same volume, entity count, and connector list in writing.

Who should choose Avalara, and who should choose Vertex

Choose the published Avalara plans when the company is under the revenue line, the billing systems are on the named connector list, and the work is U.S. sales tax plus Canadian GST/HST, PST, and QST as that page describes it. The best version of that choice is the SST plan when you truly meet the volunteer tests. You supply registrations, product tax categories, and exemption data. Avalara's managed-returns description covers preparation, filing, remittance, and notices. You should still name an employee who approves exceptions. Limitation: the moment you add NetSuite, SAP, or a complex exemption population, you have left the price you could calculate from the public page.

Choose Avalara's custom tier when you want AvaTax content and managed returns but your stack or entity count is outside the published plans. Treat that choice as Quote-based and bid it against Vertex on the same worksheet. Limitation: you lose the ability to budget from the website, and the review-site support score is the item to test with references before you sign a multi-year custom agreement.

Choose Vertex when indirect tax has to be determined the same way in a large ERP, in procurement, and on customer invoices, and when e-invoicing mandates sit on the same roadmap as U.S. sales tax. Implementation means mapping each financial event to the message type that is actually stored, loading taxability categories, and deciding whether returns are in scope or only determination. The calculation docs show a host address pattern under vertex-ws as well as cloud deployment, so ask whether your security review is for a vendor-hosted tenant, a server you run, or both. Limitation: without a public price, a mid-market team can spend a quarter in scoping and still not know if the license fits the year. Vertex is also the wrong tool to "try for one Shopify store" if the published Avalara plan already covers that store and you qualify for SST.

Choose neither enterprise engine when you have one state, one simple rate, and the state portal is enough. Adding a determination vendor, and then a workflow around it, creates logins and mappings you will not use.

When NOT to use US Tech Automations: skip that layer when the native Avalara or Vertex connector already posts tax into the only billing system you use and a person already reviews exceptions inside that vendor's portal; when you file one simple return from the state site; or when the ERP's own reminder is enough and you do not need a separate queue. In those cases another system is another login, another credential, and another place for a failed call to hide.

A review step between the invoice and the return

The engine rates the line. It does not, by itself, prove that the invoice which left your billing system is the invoice which was filed. That gap is where a configurable workflow earns its keep, and it should be designed as a proposal with prerequisites, not described as a finished deployment.

A proposed configuration, not a live customer: when QuickBooks Online commits an invoice, US Tech Automations can pull that invoice, send the ship-to address and the product tax category to the engine you licensed, and write the returned tax onto TxnTaxDetail.TotalTax for a reviewer to accept or reject before the month-end file is built. Prerequisites are a QuickBooks Online connection or a scheduled export, Avalara or Vertex credentials, and a maintained map from item to tax category. A person still approves address failures, exemption mismatches, and any line the engine will not rate. Nothing in that design is a measured saving.

On filing week, the same design can watch for a completed return package, compare the summed tax on approved invoices with the amount about to be remitted, and open a review task when the difference crosses a dollar limit you set. US Tech Automations does not file the return by itself in this design. The tax lead approves the variance note, and the filing step stays inside Avalara's managed returns or the Vertex returns service you contracted. The output is a stored approval tied to the period, plus a list of invoices that were held back. If the source system cannot export the invoice, or the engine credentials are not available, the workflow should stop and wait rather than guess a rate.

Zapier, Make, n8n, or a configured review path

The real alternative for many teams is not "no automation." It is a chain they build in Zapier, Make, or n8n, or a job their own developers run. Those tools can support run histories, retries, error branches, and audit evidence when someone configures them. A Make scenario can catch an HTTP error from a tax call and try again. An n8n flow can branch when the engine returns an address fault. Zapier can post a message when a run fails. That is real operations work, and for a single QuickBooks company with one reviewer it can be enough.

The buyer owns the rest. Observability is yours: you decide where run logs live and who is paged. Idempotency is yours: the same invoice must not be sent twice and filed as two sales. Escalation is yours: an address error on day 28 of the month needs a person, not another retry. Access control is yours: the Avalara license key or the Vertex credential should not sit in a shared scenario that every operator can export. Maintenance is yours when a vendor changes a payload or when QuickBooks changes how tax is written. A proposed US Tech Automations design could configure the review gate, the hold on unrated lines, and the period-end variance check as named steps, with the same prerequisites: an export or API from the billing system, engine credentials, and a human approver. It does not remove the tax judgment, and it should not be bought when the native connector plus one reviewer already closes the period.

Mistakes that blow up the shortlist

• Comparing Avalara's per-state list price with a hallway rumor of a Vertex enterprise fee. Vertex is Quote-based until the proposal arrives, and Avalara's custom tier is Quote-based too.

• Assuming the published Avalara plan includes SAP, Oracle, or NetSuite because the brand is on a logo wall. The named list for those plans is the commerce and smaller-accounting set.

• Treating SST state-funded service as free filing in every state where you have economic nexus. The volunteer tests are about property, payroll, and physical presence, and non-participating states are outside that funding.

• Buying calculation and forgetting returns, or buying returns and sending only quotations. If the stored document type is never sent, the return has nothing honest to file.

• Letting a connector post tax with no exception queue. The rate file can be current and the ship-to address can still be wrong.

• Talking about Avalara as if it were still a New York Stock Exchange company. The pages opened here show a 2022 take-private, a July 2025 confidential filing with no terms, and a November 2025 release that still names Vista as majority shareholder.

Glossary

• Determination is the calculation of tax on one transaction from place, product, and customer status.

• Nexus is a connection to a state that can require you to register and collect.

• Economic nexus is a selling threshold, such as sales into a state, that can create that duty without an office there.

• Exemption certificate is the buyer's document that says a sale should not be taxed, and it has to reach the calculation call.

• Use tax is the tax a buyer may owe when the seller did not charge sales tax on a taxable purchase.

• CSP means certified service provider, a company the Streamlined Sales Tax Governing Board allows to calculate, file, and remit for participating states.

• SST is the Streamlined Sales Tax agreement, the multi-state program behind that provider model.

• E-invoicing is a mandate to send invoice data to a tax authority in a set electronic format, which is a different project from U.S. sales-tax returns even when the same vendor sells both.

Questions before you ask for quotes

Which vendor publishes a price?

Avalara publishes per-state prices for companies under the revenue line on its sales-tax pricing page, and Vertex is Quote-based. Avalara's custom tier, for companies at or above that line, is Quote-based as well. A worksheet that shows a precise Vertex annual fee did not come from a public price page.

Will the published Avalara plan connect to SAP or NetSuite?

No. The pricing page's named connector list for the Core Compliance plans is the commerce and smaller-accounting set, including QuickBooks Online, Shopify, Amazon, and Stripe. SAP, Oracle, NetSuite, and Microsoft Dynamics are described with the custom tier. If those systems are your ledger, price the custom tier and price Vertex.

Did either product get renamed or discontinued?

No. The pages opened for this article still sell Avalara AvaTax and Vertex O Series under those names, alongside returns and exemption tools. You are not choosing a successor brand that replaced one of them.

Is Avalara trading on a stock exchange again?

Not on the evidence opened here. Reuters reported a confidential IPO filing on July 21, 2025 with no terms, and the November 12, 2025 release still called Vista the majority shareholder. Vertex is the company whose October 1, 2026 announcement uses the VERX ticker.

Is Vertex on the Streamlined Sales Tax provider list?

The registration page does not name Vertex among the providers offering that service. It names Avalara, TaxCloud, Sovos, AccurateTax, and Avior, and it lists Exactor as certified but not currently offering the free service. If state-funded filing is the reason you are shopping, Avalara is the one of these two that appears on that list.

Can Zapier, Make, or n8n replace the tax engine?

No. Those tools can move an invoice, retry a failed call, branch on an error, and keep a run history when you configure them. They do not maintain city rates, county rates, or exemption rules. The engine still has to do that work, or your staff does.

When is an extra workflow layer the wrong buy?

When NOT to use US Tech Automations, the simpler tool wins if the vendor's own connector already posts tax and a reviewer already works the exception list inside that portal, if you file one straightforward return on a state site, or if an ERP reminder is the only gap. Add a separate review path when invoices are born in one system, tax is rated in another, and nobody can see the difference before remittance.

A tax lead who has picked the engine, confirmed the connector, and still needs the invoice, the tax call, and the approval note in one place can see how US Tech Automations configures this after the vendor shortlist is done. The engine choice comes first. The review step is only useful once you know which API you are allowed to call and who signs the return.