Vertex review

The short answer

Buy Vertex if your indirect tax profile genuinely needs an engine rather than a service: product taxability complexity across many states, European VAT or APAC GST alongside US sales and use tax, and an ERP (typically SAP or Oracle) where tax has to be determined inside transaction processing rather than through an API connector. Buy it also if you have the internal indirect tax expertise to own the configuration, because that expertise is what the product assumes.

Skip it if you need automated sales tax compliance running inside a quarter, if your stack is NetSuite or QuickBooks with mostly US nexus, or if your tax function is one person with other responsibilities. Skip it too if automated multi-state returns filing is your primary requirement rather than calculation accuracy, because that is the part of Vertex you should verify hardest against your actual filing footprint.

Where Vertex fits

Vertex pricing

Vertex publishes nothing. There is no pricing page on vertexinc.com (the /pricing path returns a 404 as of 25 September 2026), no list prices, no published starting point and no published implementation fee. O Series and Vertex Cloud are both quoted after a demo, built from the tax content, jurisdictions and connected systems you need covered. That is normal for enterprise indirect tax, but it has a practical consequence: you cannot build a budget line for Vertex without a sales conversation, and you cannot compare it against a vendor that does publish without getting that quote first.

Since there is no price to read, the useful work is knowing what the quote is built from. These are the variables to raise in the first call, before scoping starts.

1. The tax content you license, which is the main dial. Vertex lets you take the content you need now and add more as you grow, so cost rises with each tax type (sales and use, VAT and GST, leasing, payroll) and each region you add. Price the regions you expect to enter next, not only the ones you are in, because content added mid-contract is rarely priced as generously as content in the original deal. Ask explicitly what a new country costs once you are a customer.
2. Transaction volume and the number of connected systems. Ask how volume is measured and what happens when you exceed the assumed band, and ask whether each additional connected system (SAP, Oracle, Microsoft, NetSuite, Workday, Shopify) carries a cost of its own. A company with one ERP and one commerce platform is a different quote from a company with three ERPs after two acquisitions, and the second is where unpleasant surprises live.
3. Whether compliance sits inside the quote or beside it. Vertex's core strength is determination. Returns, e-invoicing, exemption certificate management and outsourced sales and use tax returns are separate offerings, so a quote for the engine is not a quote for a compliance programme. Get the scope written as a list of what is included and what is not, and price the pieces you expect to add in year two at the same time.
4. Entity count and geographic scope, because that is how the contract is structured and therefore where change costs money. If your company has an active acquisition programme, a restructuring on the horizon or entities being wound down, negotiate what happens to the contract when the entity list changes before you sign, rather than discovering the answer during an integration.

What sits outside the core quote

• Returns filing, e-invoicing and exemption certificate management are separate offerings, as is outsourced sales and use tax returns. None are assumed to be in a determination quote.
• Implementation. No implementation fee is published, and Vertex works through systems integrators and accounting firms, so the professional services line comes from a partner rather than from Vertex. Get it quoted in parallel with the license, not after you have signed one.
• Internal and external tax expertise. Configuring taxability rules and exemption logic correctly takes indirect tax judgment. If you do not have that in-house, advisory support is a running cost rather than a one-off, and it belongs in the business case.
• ERP-side work. Deep integration into SAP or Oracle usually means change requests in the ERP programme as well as in the tax project, which often sits in a different budget and a different team's roadmap.

Implementation and commercial terms

Everything below reflects what Vertex published as of 25 September 2026, which is almost nothing. Where a row says nothing is published, that is the finding, and it is also the list of things to get in writing.

Published price

None. There is no pricing page; vertexinc.com/pricing returns a 404.

How it is sold

O Series and Vertex Cloud quoted after a demo.

Quote basis

Tax content licensed, jurisdictions and regions, and the systems connected.

Implementation fee

None published. Delivered with systems integrators and accounting firms.

Free trial

None listed. Vertex offers demos.

Compliance scope

Returns, e-invoicing and certificate management are separate offerings.

With nothing published, the only honest budgeting method is a three-line estimate built from quotes you request yourself: the license for the tax content and regions in scope, the integrator's fee for the ERP work, and the annual cost of the tax expertise to operate it. Ask for all three in the same week, because a license quote without the services number beside it will understate first-year cost by a margin that matters. Then ask the two questions that protect the later years: what a new country or tax type costs once you are a customer, and what happens to the contract when your entity list changes. Vertex may well be the right engine. It will not be the cheap one, and no page on its site pretends otherwise.

Source: the Vertex contact page, checked 25 September 2026. Confirm current prices with the vendor before you budget.

What Vertex gives up

How Vertex compares

Two indirect tax engines are covered on this site, and they split the market cleanly: Avalara sells a packaged compliance service at a published per-state price, Vertex sells an engine you configure and will not tell you what it costs. The third row is not a substitute for either: it is the compliance platform where a public company evidences the tax controls these engines operate, and it competes for the same budget. Prices come from each vendor's own site, checked on 25 September 2026, and nothing is estimated.

What to test in a Vertex demo

No free trial is listed; Vertex offers demos. With no published price and a long implementation, the demo has to do double duty: prove the engine handles your hardest tax questions, and extract enough commercial detail to build a budget. Go in with your own test cases rather than watching theirs.

1. Bring your five worst taxability problems and make Vertex configure them live. Not your highest-volume SKUs, your most contested ones: bundled software and services, leased equipment, anything with a state-specific exemption or a VAT place-of-supply question. The engine's configurability is the entire reason to buy it, so the demo should show it bending to your rules rather than demonstrating a clean catalogue.
2. Get the integration architecture drawn on a whiteboard for your specific ERP. Ask where determination happens, what is called at transaction time, what happens when the tax service is unavailable, and who maintains the integration after go-live. If you are on SAP or Oracle, this is the conversation that separates Vertex from connector-based alternatives, so make it concrete.
3. Ask for the license quote and the partner's services quote in the same week. Vertex publishes no implementation fee and delivers through systems integrators and accounting firms, so a license number on its own tells you little about first-year cost. Ask the partner directly how long a deployment of your shape takes and what their fee covers after go-live.
4. Draw the line between determination and compliance explicitly. Returns, e-invoicing, exemption certificate management and outsourced returns are separate offerings. Put your filing footprint in front of them and ask which parts the quote covers, which are extra, and what the filing automation does for your largest states. If returns automation is a primary requirement, test it rather than trusting the category reputation.
5. Price your next two years of footprint before signing. Ask what adding a tax type, a country or a connected system costs once you are a customer, and what happens to the contract if your entity list changes through acquisition or restructuring. Those answers are worth more than a discount on year one, because the modular licensing that makes Vertex flexible is also what makes expansion expensive if it is not priced up front.

Frequently asked questions about Vertex