Skip to content

Sales tax and VAT software for Salesforce

Salesforce is where the quote and the order are agreed, which makes the tax on them a commercial number rather than a reporting one. Salesforce calls that figure an estimate, supplies no rate data, and leaves registration, filing, and remittance to something else. Commenda covers all three, across all 50 states and 70+ countries.

Integration connection between platform and Commenda

Quote the tax your customer will actually pay

Salesforce calls quote and order tax an estimate and treats the invoice as the final figure. Commenda calculates from the ship-to address and the product tax code, so the figure on the quote is the figure that bills.

Monitor your global exposure

In Salesforce a tax rate is a record you create for one jurisdiction. Commenda measures the same revenue against economic and physical thresholds in all 50 states and 70+ countries, and notifies you at 80% of a threshold.

Register, file, and remit

Salesforce hands reporting to your tax engine or to a separate process. Commenda registers you, files across all 50 states and 70+ countries, and tracks remittance per jurisdiction.

Coverage comparison

What Salesforce is scoped to do, and what it hands back

Salesforce is a CRM and a quote-to-cash suite, so registering and filing were never in its scope. Calculation is, and CPQ and Billing do it differently. Its figures come from Salesforce Help on CPQ versus Billing tax, choosing a tax engine, standard engine considerations, standard engine guidelines, and applying taxes, checked on July 30, 2026.

SalesforceCommenda
Tax on the quote your customer signsNeeds an outside engine. Only AvaTax ships pre-packaged for CPQCalculated from the ship-to address and the product tax code
Rates for each jurisdictionNot supplied. Salesforce states it does not provide tax rate dataMaintained across all 50 states and 70+ countries
Knowing where you oweNot in scope. It taxes where you built a rate, and measures no thresholdsEconomic and physical thresholds in 50 states and 70+ countries, with alerts at 80%
Registrations for collecting taxNot in scope. It is a quote-to-cash suite, not a filing agentPermits in all 50 states, EU VAT with OSS and IOSS, and GST across APAC and Canada
Returns, in the US and abroadNot in scope. On its own engine, reporting is a separate processFiled in all 50 states and 70+ countries, amendments included
Remitting what you collectedPassed to your tax engine, and unposted invoices are ignored by itTracked per jurisdiction, every filing
Exemption certificatesNot documented as a record. Exemptions feed the order calculationCollected, validated, stored, and applied automatically where valid

Calculate taxes globally on Salesforce using Commenda

Salesforce Billing needs one tax rate record for every jurisdiction or address you tax in, and Salesforce states it does not supply the rate data. Commenda resolves state, county, city, and district rates from the ship-to address, and applies the product tax code for what you actually sell. Nothing has to be maintained by hand.

global indirect tax calculation software product shot commenda

Track your global exposure from Salesforce

Salesforce taxes where you configured a rate and a legal entity. It does not measure whether you owe there. Commenda reads your revenue against economic and physical thresholds in all 50 states and 70+ countries, and tells you at 80%, before you cross. A short questionnaire covers physical presence, because a warehouse or a remote employee never shows up on an order.

global indirect tax exposure tracking software product shot commenda

Automatically remit transactions around the world

Salesforce documents reporting as a separate process on its own tax engine, and notes that third-party engines are where reporting tends to come from. Commenda builds the return from your transaction data instead. Returns go out across all 50 states, plus EU VAT with OSS and GST in APAC and Canada, with amendments where a period needs correcting. The liability and the filing confirmation post back to your ledger.

global indirect tax remittance software product shot commenda

Manage your customers and exemptions in one place

Salesforce lists exemptions as an input its order tax calculation can read. Getting the certificate is the harder half. Your customers upload through a portal that can carry your branding, each one is validated on upload, and it applies automatically in the states where it is valid. Expiries are tracked and chased, including the annual refreshes states like Florida require.

global indirect tax exemption certificate software product shot commenda

Consolidation

Why quote-stage tax is the expensive kind to get wrong

Salesforce is where revenue is agreed. That makes the tax on a quote a number your customer accepts, not a number you can quietly restate later. Getting it right needs rates you do not maintain, thresholds Salesforce does not measure, and a filing path it does not have.

  • A quote is a promise. An invoice is where the correction lands

    Salesforce is explicit that quote and order tax are only estimates, and that Billing performs the final calculation on the invoice. It even recommends calculating quote tax on quotes with subtotals of $1 million or greater, because a large tax figure moves the total price. If the estimate was low, someone absorbs the difference. That is either a credit note or your margin.

  • Salesforce taxes the jurisdictions you configured

    A tax rate in Salesforce Billing is a record for one jurisdiction, and Salesforce documents that a mismatched or null legal entity means no tax is calculated at all for that order product. Nothing in the system asks whether you should have been collecting there. Thresholds move, and they differ by state (see the state-by-state thresholds). Our sales tax calculator gives you the rate for an address, but the rate is the easy part.

  • Enterprise deals close in Salesforce. Self-serve revenue does not

    Most Salesforce shops bill enterprise contracts through Salesforce and run self-serve through a payments or subscription platform. Each system measures its own share, so neither one knows the number that matters. Exposure has to be measured once, across every channel, against one threshold per state.

  • One ledger behind every channel

    Every source connects to one ledger, across 100+ supported integrations. Each transaction carries its origin, product tax code, and any tax already collected, so marketplace revenue stays separate from revenue that still needs tax. The result is one exposure figure per state, one return per period, and every line traceable back to the order it came from (how global indirect tax works at Commenda).

What it takes

What global indirect tax takes in Salesforce

Salesforce publishes no list price for Salesforce Billing or its tax features, so there are no dollar figures here. What it does publish, in detail, is what each capability depends on. Its own tax engine costs nothing extra. The cost of growth is the rate data, the configuration, and the reporting.

What you needWhat Salesforce requiresSource
Tax on a quote your customer signsA third-party tax engine or a custom configuration. Salesforce states your org must integrate with one, and that only AvaTax is available pre-packaged for CPQCPQ vs Billing tax
A rate for a city or a ZIP codeOne tax rate record per jurisdiction or address, with every address level above the one you use filled in. A ZIP-level rate needs the ZIP, city, state, and countrySet up tax rates
Rates that stay currentManual maintenance. Salesforce states that admins must update tax rate records when rates change, and that Salesforce does not provide tax rate dataStandard engine considerations
Any tax at all on an order productMatching legal entities on the tax treatment and the tax rate. Salesforce states that if they do not match, or one is null, it does not calculate tax for that order productStandard engine considerations
Anything past simple taxationA third-party engine. Salesforce strongly recommends its own engine only for simple use cases, and does not support customizations made to its behaviourStandard engine guidelines
Reporting you can file fromA third-party engine, or a separate process you run yourself. Salesforce notes third-party integrations often provide reporting services and its own engine does notChoosing a tax engine
Remittance out of your invoice dataA posted invoice and an external engine. Salesforce notes most tax services use the posted data to remit or to drive remittance, and that external engines ignore unposted transactionsCPQ vs Billing tax
Line volume in a single calculationUp to 1,000 quote lines per API call on the internal engine, and up to 2,200 invoice lines with Avalara. Each tax calculation is an independent callCPQ vs Billing tax
Correct tax in a multicurrency orgYour own check. Salesforce states a 10% GBP tax rate applies 10% to a USD invoice line as well, because the rate's currency is ignoredStandard engine guidelines

Figures verified on July 30, 2026.

From the field

Trusted by businesses across the globe

TRX
TRX
“The platform works exactly the way I need it to. I have one team member who manages all of our exemption certificates, and that functionality has been particularly efficient for us. It allows him to handle everything seamlessly, making the handoff significantly easier.”
Matt Preston, CPA

VP of Finance, TRX

Read the full story

Compare Commenda sales tax software with competitors

Salesforce names Avalara and Vertex in its own tax documentation, and both publish AppExchange connectors. We compare the alternatives on coverage, ratings, and real pricing, and we say where each one wins.

Vertex Alternatives and Competitors (2026)

Frequently asked questions

What revenue and finance teams running Salesforce ask before they move their indirect tax to Commenda.

Only with an outside engine. Salesforce states that if your use case requires tax calculation on the quote, your org must integrate with a third-party tax engine or a custom configuration, and that only AvaTax is available pre-packaged for CPQ. Everything else is a custom integration. Salesforce also treats the result as provisional: quote and order tax are estimates, and Billing performs the final calculation on the invoice. Its own guidance is to calculate quote tax on quotes with subtotals of $1 million or greater, given how much a large tax figure moves the total. Commenda calculates from the ship-to address and the product tax code, so the same number holds from quote to invoice.

For simple, static rates, and Salesforce says so in those words. It recommends the standard engine for simple and static tax calculations such as VAT, strongly recommends it only for simple taxation use cases, and does not support customizations made to its behaviour. Three constraints matter in practice. Salesforce does not provide tax rate data, so you enter and update every rate yourself. It requires a tax rate record for every jurisdiction or address you tax in. And in a multicurrency org it ignores the rate's currency, so a 10% GBP tax rate applies 10% to a USD invoice line too. Commenda maintains the rates instead, across all 50 states and 70+ countries.

No, and it does not present that as its job. Salesforce Billing calculates tax on order products and invoice lines. On its own engine, Salesforce documents reporting as a separate process you handle, and notes that third-party integrations are often where reporting services come from. Remittance is the tax engine's, not Salesforce's: Salesforce states that most tax services use the posted invoice data to remit directly to a governing authority or to drive remittance through reporting, and that external engines ignore unposted transactions. Commenda files across all 50 states on each state's required frequency, files EU VAT with OSS and GST across APAC and Canada, tracks remittance per jurisdiction, and files amendments where a period needs correcting.

Check the legal entity first. Salesforce applies a tax treatment to an order product only when both records have matching legal entities, and states that if they do not match, or if one of the legal entities is null, it does not calculate tax for that order product. A tax treatment and its tax rate must also share a tax code. There is a second trap: an invoice line inherits its parent order product's legal entity and tax at creation, and Salesforce documents that later changes to the order product do not carry over. So a correction made after the fact can look applied and still bill the old figure.

No. Nexus is not a concept Salesforce Billing models. A tax rate is a record you create for a jurisdiction, and tax gets calculated where you created one. Nothing measures whether you should have registered somewhere you have not. Commenda measures your revenue against economic and physical thresholds in all 50 states, every EU member state, and 70+ countries, and notifies you at 80% of a registration threshold rather than after you cross it. Registering everywhere at once is not the answer either, because a registration starts a filing obligation whether or not you owe tax. We run the exposure analysis first and sequence registrations by liability size.

In a meaningful minority of states, yes. Some states include exempt sales when working out whether you have crossed the economic nexus threshold, so you can owe a registration obligation in a state where the underlying sale is not taxable. SaaS taxability itself varies state by state, and within a state by delivery model and customer type. New York is the classic example of a state treating B2B SaaS as tangible personal property. Each SKU is mapped to a product tax code that resolves to the right treatment per state, so a product taxable in one state and exempt in another is handled without you maintaining a 50-state matrix.

Yes, quite a lot. Salesforce documents them as two separate tax processes. CPQ calculates tax on the quote object and can only use an external engine, with AvaTax as the one pre-packaged option. Billing calculates on the order and invoice objects and can use its own internal engine. Tax rules and tax treatments, which is how Billing varies treatment by legal entity, are not part of CPQ at all. The internal engine also caps at 1,000 quote lines per API call. Commenda sits outside both, so the calculation, the exposure history, and the returns do not depend on which of the two you licence.

No engineering work on your side either way. Commenda supports 100+ integrations, with native connectors across accounting, billing, and commerce systems, a REST API for teams that want to call tax directly, and a mapped monthly CSV where no native connector exists. Where a native path is not already in place for your setup, we confirm the supported route rather than assume it works out of the box, and we scope which of your Salesforce records should feed tax before anything is switched on. The API covers calculation by product, tax code, and address, nexus determination, and exemption lookup, and it can be white-labelled so your customer never sees Commenda.

Custom integration support for your business

Every Salesforce org is configured differently, and those choices exist for good reasons. We map how yours works, including which records should feed tax and which revenue arrives already taxed, and build the integration to match.

Indirect Tax

Monitor nexus exposure, register, file, and remit sales tax and VAT in one platform. Commenda keeps you compliant across 100+ jurisdictions.

Explore the product