Calculation Only vs. Filing and Remittance
Choose sales tax software by the workflow it covers: some products calculate tax at checkout, while others also file returns and remit payments.[1][3][6] A calculation engine determines tax based on factors such as location and product taxability. Filing tools prepare returns, track deadlines, submit payments, and produce compliance reports.[1][6] 
| Product | Calculation and nexus | Filing and remittance | What to confirm |
|---|---|---|---|
| Numeral | Real-time calculation and nexus functions.[1] | Automated returns and remittance.[1] | Exact plan inclusions |
| Avalara | Calculation, nexus, and exemptions.[1][3][6] | Returns, remittance, and notice management.[3] | Quoted modules and limits |
| Sovos/Taxify | Tax determination and real-time liabilities.[1][8] | Automated filing is documented.[1][8] | Payment and notice scope |
| Lovat | Nexus alerts and real-time calculation.[1] | Filing and remittance.[1] | Plan eligibility |
| TaxJar | Calculation, nexus tracking, and reporting.[1][2][6][8] | AutoFile is available.[1][2][8] | Remittance and notice handling |
| Stripe Tax | Calculation and reporting for Stripe transactions.[1][6][8] | Does not file returns.[1][8] | A separate filing process |
| TaxCloud | Calculation, exemptions, and reports.[1][7][8] | Filing and remittance capabilities are documented.[1][7][8] | Service, state, and integration eligibility |
| Vertex | Sales-tax and VAT/GST determination.[1][4][6][8] | Return preparation and validation are documented.[4] | Submission and remittance |
| Quaderno | U.S. sales-tax and VAT/GST tools, invoices, and reports.[8] | Submission and remittance are not confirmed.[8] | The complete filing workflow |
For each quote, require written confirmation of who handles registration, return submission, tax payment, amended returns, and government notices. The sources do not verify exact plan scope across these products, even when filing is advertised.[1][2][3][4][7][8]
Best Fit by Ecommerce Operating Model
After confirming workflow coverage, compare products against the business’s channels, geographic reach, transaction complexity, and existing systems.
| Option | Best-fit operating model | Workflow level | Main qualification |
|---|---|---|---|
| TaxJar | U.S. small-to-mid-market, multichannel ecommerce using Amazon, Shopify, or WooCommerce.[1][2][6][8] | Calculation, nexus tracking, reporting, and AutoFile.[1][2][8] | International support is described as limited; automatic tax invoices are not included.[1][2][6][8] |
| Stripe Tax | Stripe-native SaaS, subscriptions, invoices, and digital products.[1][6][8] | Calculation and reporting.[1][6][8] | It does not file returns, and reporting is confined to Stripe transactions.[1][6][8] |
| TaxCloud | Budget-focused U.S. merchants.[1][7][8] | Calculation, reporting, filing, and remittance.[1][7][8] | Confirm state coverage, integration eligibility, filing scope, and usage limits.[1][7][8] |
| Lovat | Sellers prioritizing proactive nexus monitoring across channels.[1] | Calculation, filing, and remittance.[1] | Listed connections include Magento, eBay, WooCommerce, Shopify, Amazon, and PayPal.[1] |
| Numeral | Ecommerce businesses, particularly Shopify sellers.[1] | Calculation through automated returns and remittance.[1] | Verify support for every store, marketplace, entity, and jurisdiction. |
| Avalara or Sovos/Taxify | Mid-market, high-volume, or complex operations.[1][3][6][8] | Broad determination and compliance automation.[1][3][8] | Consider them when exemptions, notices, dispute documents, broader integrations, or regulatory coverage drive the decision.[1][3][6][8] |
| Vertex | Global or high-volume omnichannel commerce.[1][4][6][8] | Sales-tax and VAT/GST determination plus return preparation and validation.[4] | Vertex supports product rules, invoicing, ecommerce, and major ERP integrations; it also says its cloud products can scale from small businesses.[1][4][6][8] |
| Quaderno | Global ecommerce, SaaS, and digital products.[8] | U.S. sales-tax and VAT/GST tools, invoices, and reports.[8] | The sources do not confirm filing and remittance.[8] |
The sources do not confirm account-specific transaction suitability, complete country and state coverage, or required add-ons across these products.[1][2][3][4][6][7][8] Ask each vendor to demonstrate the intended mix of channels, entities, products, and jurisdictions using representative account data.
Pricing and Contract Questions
Published evidence is insufficient for a credible monthly-cost comparison. Sovos/Taxify uses custom pricing based on features and complexity. Vertex pricing may reflect transaction volume, jurisdictions, company size, and other needs. Lovat offers a free nexus-tracking tier, while TaxCloud’s free availability depends on the service, state, and integration.[1][4][7][8]
The sources do not verify most plan prices, transaction caps, filing limits, or overage charges.[1][2][3][4][5][6][7][8] Require an itemized written quote covering:
- Implementation, migration, and state-registration charges
- Return fees by state and filing frequency
- Transaction and API caps and overage rates
- Amended-return costs and notice handling
- Exemption-certificate services and premium support
The contract should state the initial term, renewal rules, permitted price increases, cancellation deadline, refund policy, data-export rights, and transition assistance. Ask about uptime and filing commitments and remedies for missed deadlines. These commercial terms are not consistently confirmed in the sources.[1][2][3][4][5][6][7][8]
Compare quotes using the same annual scenario: expected transaction volume, active states, filing frequencies, entity and channel counts, likely registrations, and support requirements.
Check Integrations and Compliance Gaps
Test each proposed integration with the actual data flow. A demonstration should show whether the engine determines jurisdiction, product taxability, shipping treatment, customer exemptions, and nexus—not merely whether it applies a rate.[6]
Map every store, marketplace, payment platform, subscription system, accounting package, and ERP. Identify which system owns product codes, exemption status, refunds, and marketplace-facilitator transactions. Confirm the final transaction record retains the tax rate and basis, jurisdiction, product-taxability status, and any exemption or certificate reference needed for returns and audit support.[6]
- Entity and customer logic: Test each legal entity, B2C transaction, and B2B resale-certificate workflow. B2C sales generally require tax unless exempt, while B2B transactions may depend on valid resale documentation.[6]
- Marketplace handling: Verify how facilitator-collected transactions are identified because marketplace obligations vary by state law.[6]
- Implementation fit: Assess industry expertise, ecosystem integration, tax and e-invoicing capabilities, implementation flexibility, support, communication, assigned responsibilities, and update schedules.[5]
How to Build a Two-Vendor Shortlist
- Define the required workflow. Decide whether the business needs monitoring and calculation only or also registration, returns, filing, remittance, notice handling, and exemption management. Crossing a nexus threshold may trigger registration, collection, and return obligations.[6]
- Eliminate coverage gaps. Remove products that cannot support the required channels, jurisdictions, tax types, product-taxability rules, entities, transaction types, or ERP connections. Product mapping, certificates, multiple channels, and filing workload can complicate compliance.[6]
- Score the survivors. Compare workflow coverage, integration fit, implementation effort, support ownership, and scenario-based annual cost. Selection should also address communication, assigned responsibilities, and an agreed update schedule.[5]
- Run the same demonstration. Ask each finalist to process a taxable sale, exempt transaction, marketplace order, refund, nexus alert, return, and accounting export. Require comparable written quotes and a responsibility matrix showing what is automated, what requires approval, and what remains with an accountant or filing provider.
A Stripe-native seller may accept separate filing, while a multistate business facing return deadlines may prefer integrated filing and remittance.[1][6][8]
Set Ownership Before Implementation
Assign nexus review, registrations, product mapping, exemption certificates, return approval, remittance funding, notices, reconciliation, and deadline monitoring to the vendor, the business, or its accountant. Filing schedules vary by state, while inadequate documentation and incomplete returns create compliance exposure.[6]
Agree in writing on implementation support, assigned responsibilities, support contacts, escalation procedures, direct communication, and an update schedule.[5] Before relying on automation, document how the parties will reconcile transactions and address refunds, late transactions, amended returns, and corrected data.
References
- 10 Best Sales Tax Software for Ecommerce in 2026 (numeral.com, 2026)
- TaxJar: Sales Tax Compliance for Modern Commerce (taxjar.com, 2026)
- Sales and use tax compliance software | Avalara (avalara.com)
- E-commerce Tax Solutions & Sales Tax Software for Global Compliance | Vertex Inc. (vertexinc.com)
- How to choose the right sales tax automation software | Thomson Reuters (thomsonreuters.com)
- eCommerce Sales Tax Features for Your Business (clarity-ventures.com, 2026)
- Sales Tax Software for Ecommerce – 3dcart (shift4shop.com)
- 10 Best Sales Tax Software for Small Businesses (2026) (quaderno.io)
