Avalara review: sales tax compliance software for finance and accounting teams

Avalara is one of the few tax tools that publishes a price: Core Compliance at $79 per state per month, or $69 with SST Services, checked 25 September 2026. Buy it if your exposure is US sales and use tax and revenue is under $50M. Above that, you are quoted.

Rajat GuptaEditorial LeadReviewed 25 September 2026Pricing checked 25 September 2026 against the Avalara sales tax pricing page

Avalara in brief

Avalara is one of the few tax tools that publishes a price: Core Compliance at $79 per state per month, or $69 with SST Services, checked 25 September 2026.

Price: $69 per state/month (Core Compliance + SST Services) · Per state where you collect tax, billed monthly or annually
Best for: Mid-market companies with multi-state US sales tax nexus
Watch out for: The published price stops at $50M in revenue, and that is a harder edge than it looks.

The short answer

Buy Avalara if you have triggered economic nexus in several US states, your transaction systems are the ones Avalara has mature connectors for (NetSuite, QuickBooks, Sage Intacct, Microsoft Dynamics 365, SAP Business One), and your revenue sits under $50M so the published per-state plans apply. Calculation, nexus monitoring and Managed Returns in one $79 per state per month line is the cleanest budget story in indirect tax.

Skip it if your revenue is over $50M, because the published plans stop applying and you negotiate like everyone else. Skip it too if your exposure is mostly European VAT or APAC GST, or if your ERP is SAP S/4HANA or Oracle Cloud and you want the tax engine wired in at the transaction layer rather than through a connector. Those are Vertex evaluations.

Where Avalara fits

Avalara fits the company that has crossed economic nexus thresholds in more states than a spreadsheet can honestly track. The trigger is rarely one large event. It is the slow accumulation of remote sales until someone in finance realises the business is registered in four states, probably liable in another six, and nobody can prove which. Avalara answers that with three things sold as one subscription: AvaTax calculating at the point of transaction across more than 12,000 US jurisdictions, nexus monitoring across all 50 states, and Managed Returns handling filing, remittance and the notices that come back.

The published pricing tells you who Avalara built this packaging for. Core Compliance is priced per state where you collect tax, and the plans are for businesses under $50M in revenue. That is a deliberate mid-market product with a self-serve price tag, and it is why Avalara is usually the first name on a shortlist assembled by a controller rather than a tax director. Cross the $50M line and you move to a custom plan with the full product range, multi-entity management and a 1-hour response SLA: a different buying process with different questions.

Connector breadth is what makes a short implementation plausible. Avalara maintains pre-built integrations across ERPs, billing systems, e-commerce platforms and point of sale, and for the mid-market stack those connectors are configuration work rather than development work. A company running NetSuite or QuickBooks with Shopify in front of it can usually get calculation live without a systems integrator. That is a real cost difference from Vertex, where implementation is a formal project with a partner attached, and it shows up in the first-year total rather than the subscription line.

The second thing Avalara absorbs is research. Rate and taxability changes land constantly at state and local level, and a company selling software, digital goods or medical devices across thirty states cannot maintain its own taxability matrix without dedicating a person to it. You are paying for someone else to track legislative change. AvaTax Exemptions is included in Core Compliance rather than sold separately, which matters to B2B sellers whose resale certificates live in a shared drive.

Where Avalara stops being the obvious answer is control. It is a configured service, not a tax engine you tune. If your product taxability is genuinely contested, or your tax team wants to own the rules rather than map to someone else's taxonomy, the configuration model will feel like a ceiling rather than a convenience. Teams in that position should price Vertex alongside, and should expect that comparison to be a comparison of implementation projects as much as of software.

Avalara pricing

Avalara publishes a price, which puts it in a small minority of the tax and compliance tools on this site. Checked on 25 September 2026, Core Compliance is $79 per state per month or $799 per state per year, and Core Compliance + SST Services is $69 per state per month or $699 per state per year. Both plans are for businesses under $50M in annual revenue; above that you get a custom quote, and paying annually saves 15%. The structural point is in the unit: you buy states, not seats, so the bill tracks your nexus footprint.

What Avalara publishes

Core Compliance: $79 per state/month, or $799 per state/year (Monthly or annual, per state (annual saves 15%))AvaTax calculation across more than 12,000 US jurisdictions, Managed Returns covering filing, remittance and notices, nexus monitoring in all 50 states, and AvaTax Exemptions for exempt customers.
Core Compliance + SST Services: $69 per state/month, or $699 per state/year (Monthly or annual, per state (annual saves 15%))Everything in Core Compliance, plus state-funded calculation and filing in up to 25 Streamlined Sales Tax states for qualifying sellers, audit liaison support, and a single SST ID across participating states.
Custom: Quote-based (Custom contract)For businesses at $50M or more in annual revenue. Full Avalara product range, multi-entity management, and a 1-hour response SLA.

Prices as published on the Avalara sales tax pricing page and checked on 25 September 2026. They are scoped to businesses under $50M in revenue, so treat them as a ceiling on what a mid-market deal should cost rather than a rate card that applies to everyone.

Even on a published plan, two companies paying per state can end up with different bills. Avalara's own pricing FAQ names the variables.

Your state count, which is the published unit and the one that moves on its own. Each additional state where you collect adds $69 to $79 per month depending on your plan, and nexus expansion follows your sales rather than your decisions. Use Avalara's nexus monitoring to forecast next year's state count before you pick a billing term, because an annual commitment priced on today's footprint does not cover tomorrow's.
Whether you qualify for the Streamlined Sales Tax programme, the biggest lever on the published price. The SST plan is cheaper at $69 per state per month, and for qualifying remote sellers the states fund calculation and filing in up to 25 SST states. Eligibility turns on whether you have a significant physical presence there, so it is a question for your tax advisor rather than a checkbox on a quote.
The factors Avalara's FAQ lists beyond state count: which products and services you buy, how many business applications you integrate, how many sales transactions you process a month, and the number of jurisdictions in scope. Transaction volume is the one that surprises growing companies, because nothing on the published plans says what volume they assume. Ask for that number, ask what happens when you exceed it, and get the answer in the contract.

What costs extra

Sales tax registration at $403 per location, which is a real line item during a catch-up project. A company registering in six new states pays registration fees before a single return is filed, separately from the per-state subscription.
Business License Guidance from $119, which matters to businesses with physical locations or regulated products rather than to remote sellers.
Implementation help, which carries no published fee but is usually a real cost. Avalara sells services directly and through certified partners, and product code mapping is where mid-market projects consume the most time. Get the partner's scope and fee quoted alongside the subscription.
Capabilities outside the Core packaging. Cross-border compliance and the wider product range sit in the custom plan, so a company expecting international obligations should price that path rather than assume a later bolt-on.

Implementation and commercial terms

These rows are what Avalara publishes as of 25 September 2026. Anything absent was not published, which means it is negotiable and should be settled in writing before signature.

Published price: Yes, for Core Compliance and Core Compliance + SST Services. The custom plan is quoted.
Who the published plans cover: Businesses under $50M in annual revenue. $50M and above is custom.
Billing basis: Per state where you collect tax, monthly or annually. Annual saves 15%.
Implementation fee: None published for the Core plans. Custom plans are quoted.
Free trial: None listed on the pricing page.
Registration fees: $403 per location, charged on top of the subscription.
Support SLA: A 1-hour response SLA is published only for the custom plan.

Budget Avalara as three numbers. Your state count multiplied by $79, or $69 if SST genuinely applies, gives a subscription you can defend to a CFO today. Registration at $403 per location covers every state you have still to register in. Third is the implementation and tax advisory work to classify your catalogue, which Avalara does not publish and which is the number most often missed. Then add a state or two for next year, because per-state pricing turns growth into a recurring increase rather than a renegotiation.

Source: the Avalara sales tax pricing page, checked 25 September 2026. Confirm current prices with the vendor before you budget.

What Avalara gives up

The published price stops at $50M in revenue, and that is a harder edge than it looks. A company growing through that threshold does not keep its per-state rate and add features; it moves to a custom plan negotiated like any enterprise contract. If you are approaching that revenue, the published figures are an anchor and nothing more. Ask for custom pricing early, so you learn its shape before your renewal becomes the forcing function.

You give up control of the determination logic. Avalara maintains tax content centrally and has you map your catalogue onto its taxability categories. That is what you want if your products are ordinary and your tax team is one person with other duties. It is a constraint where taxability is contested, because a wrong mapping produces wrong tax on every transaction until someone notices. Budget tax advisory time for the mapping, not only implementation time.

Deep ERP integration on SAP S/4HANA and Oracle Cloud is not Avalara's strength. The mid-market connectors are mature and configuration-driven; the enterprise ones need more implementation effort and often a systems integrator. If your system of record is one of those two, the connector layer that makes Avalara cheap to deploy elsewhere becomes the thing you work around, and that is the clearest technical reason to put Vertex on the list.

International indirect tax is thinner than the US story. Avalara does sell cross-border compliance, but it sits outside the published Core packaging, and companies whose main exposure is European VAT or APAC GST generally find more depth in specialist platforms. Treat Avalara as a US sales and use tax product with international options rather than a global indirect tax engine.

Support quality is uneven below the enterprise tier, and the published SLA says so by omission: the 1-hour response commitment appears only on the custom plan. That matters here more than in most software, because a configuration error in tax calculation compounds silently across every transaction until a notice arrives. Ask what the response commitment is on a Core plan.

How Avalara compares

There are two serious indirect tax engines in the set of products we cover, and only one publishes a price. The third row is not an alternative to the first two: it is the compliance platform that sits next to them in a public company, where the sales tax controls Avalara runs are the controls your audit team has to evidence. Every price comes from that vendor's own site, checked on 25 September 2026, and where nothing is published we record that rather than estimate.

Tool	Best for	Price	Where it breaks
Avalara	US sales and use tax at mid-market scale, on mainstream ERPs	$79 per state/month, or $69 with SST Services	Published plans stop at $50M revenue, and determination logic is not yours to tune
Vertex	Enterprise indirect tax across VAT and GST, inside SAP or Oracle	Not published, quote only	Implementation is a multi-month project with a partner attached
Optro (formerly AuditBoard)	Evidencing the SOX controls around tax, not calculating tax	Not published, quote only	Adjacent purchase rather than a substitute, priced per product licensed

What to test in an Avalara demo

No free trial is listed on Avalara's pricing page, so this is a demo and sandbox exercise. The upside of published pricing is that you can model the cost before the demo instead of during it, which frees the conversation to test the two things that decide the outcome: taxability mapping and your filing footprint.

Settle your nexus position before you look at software. Avalara's nexus monitoring is a starting point, not a determination, and configuring filing frequencies on a wrong nexus analysis builds the error into every return. If no tax advisor has validated a nexus study recently, do that first. It also fixes your state count, the number your subscription is priced on.
Take your twenty most awkward SKUs, not your twenty biggest, and have Avalara map them to its taxability categories in front of you. Digital goods, bundled services and anything with a state-specific exemption are where mapping gets contested. This step decides whether the implementation runs short or long, and it is checkable in a demo rather than discoverable in month three.
Decide the SST question explicitly. Ask Avalara to confirm in writing whether your physical presence profile qualifies you for the plan at $69 per state per month and which of the up to 25 SST states it would cover. A cheaper plan with state-funded filing is worth an hour of your tax advisor's time.
Connect the real ERP, not a demo instance, and watch a transaction calculate end to end. Confirm the rate applied, the jurisdiction resolved, the exemption honoured and the audit trail written. If your system of record is SAP S/4HANA or Oracle Cloud, make the integrator's scope and fee concrete here.
Price the whole first year on paper: state count at $79 or $69 per state per month, registration at $403 per location for each state still to register, Business License Guidance from $119 if locations apply, plus the implementation partner's quote. Then add the states you expect to trigger next year. Compare that against a quote-only competitor and remember you can verify your half of the comparison and not theirs.

Frequently asked questions about Avalara

How much does Avalara cost?

Avalara does not publish list pricing. All plans are custom-quoted based on transaction volume, number of filing jurisdictions, and modules included (AvaTax, Returns, ECM, cross-border). Transaction volume is the primary cost driver. Finance teams should request quotes for the full compliance workflow, not just AvaTax in isolation, to get an accurate total cost picture. See /software/avalara/pricing for a cost framework and questions to ask sales.

What ERP systems does Avalara integrate with?

Avalara has pre-built connectors for NetSuite, QuickBooks Online, QuickBooks Desktop, Sage Intacct, Microsoft Dynamics 365, SAP Business One, Salesforce, Shopify, Magento, and over 1,200 other systems. Connector maturity varies: NetSuite, QuickBooks, and Sage Intacct connectors are well-tested and configuration-driven. SAP S/4HANA and Oracle Cloud integrations are more complex and typically require implementation services.

How long does Avalara implementation take?

For standard ERP connectors (NetSuite, QuickBooks, Dynamics 365, Sage Intacct), AvaTax implementation typically takes 2–8 weeks from contract to live calculation. Adding Returns configuration extends this by 2–4 weeks depending on filing jurisdiction count. Product code mapping for complex catalogs is the most common source of implementation delays and should be scoped explicitly before starting.

Does Avalara handle international VAT and GST compliance?

Avalara's cross-border module covers VAT, GST, and customs calculations for international transactions, but it is a separate module with additional cost. For companies with significant European VAT or APAC GST obligations, the cross-border capability is less mature than Avalara's U.S. sales tax offering. Sovos and Vertex offer stronger international indirect tax depth for finance teams with complex global compliance requirements.

How does Avalara pricing scale with transaction volume?

Avalara's primary billing metric is transaction count: every order line or invoice row processed through AvaTax increments the usage counter. As transaction volume grows, the annual cost increases. High-growth companies should model cost at projected volumes 2–3 years out before signing and negotiate committed pricing bands with cap provisions rather than accepting uncapped per-transaction overages.

What is the difference between Avalara and Vertex?

Avalara excels in connector breadth and is easier to deploy quickly across mid-market ERP and e-commerce environments. Vertex has a more configurable tax engine architecture suited to complex enterprise indirect tax workflows, deeper SAP and Oracle ERP integration, and stronger international VAT coverage. For enterprise organizations on SAP/Oracle or with complex manufacturing and distribution tax obligations, Vertex warrants direct evaluation. See /compare/avalara-vs-vertex.

Does Avalara automate sales tax return filing?

Yes. Avalara Returns automates return preparation, submission, and payment across filing jurisdictions on a configured schedule. The module supports all 50 U.S. states and many local jurisdictions. Filing status tracking, exception alerts, and a filing calendar are included. Returns is a separate module from AvaTax and must be included in the contract to access automated filing.

How does Avalara handle exemption certificates?

Avalara's Exemption Certificate Management (ECM) module provides a workflow for collecting, validating, and storing resale and exemption certificates from business customers. ECM integrates with AvaTax so exemptions apply automatically at calculation time without manual override. ECM is a separate module with per-seat pricing tied to the AR or tax team members who manage certificate workflows.

Is Avalara right for a small business?

Avalara's cost structure and contract complexity favor mid-market and enterprise buyers over small businesses. For companies with fewer than 1,000 transactions per month and nexus in 1–5 states, TaxJar or Stripe Tax typically deliver adequate coverage at lower cost and lower operational overhead. Avalara becomes the better choice when filing complexity, ERP integration requirements, or exemption certificate volume exceed what simpler tools handle.

What compliance certifications does Avalara hold?

Avalara is SOC 1 Type II and SOC 2 Type II certified. The platform maintains a complete audit trail of every tax calculation, rate applied, and exemption used, supporting both internal audit programs and external examiner documentation requests. For finance teams subject to external audit with tax system controls requirements, Avalara meets the standard documentation baseline.

What are the best alternatives to Avalara?

The main Avalara alternatives are: Vertex (strongest for enterprise and complex manufacturing tax scenarios with product-level taxability rules), TaxJar (acquired by Stripe, best for e-commerce businesses on Shopify/Amazon/WooCommerce), Sovos (strong for cross-border tax compliance and VAT in international scenarios), and native ERP tax engines (SAP Tax Engine, Oracle Tax for organizations with simple domestic tax requirements). For most mid-market US businesses with multi-state sales tax obligations, Avalara and Vertex are the two most commonly evaluated platforms. Vertex tends to be stronger for manufacturing and complex product taxability; Avalara tends to be more accessible for mid-market e-commerce and SaaS businesses. See the Avalara alternatives page for a full comparison.