Sales tax and VAT software for Chargebee

Partly, and the answer turns on which region you mean. Chargebee's tax overview gives exactly two routes: configure taxes manually for every taxable region and have Chargebee apply those rates, or connect a third-party provider and have the rates applied through the integration. For the United States and Canada, Chargebee states it currently offers only manual CSV tax upload, with up to four rates against one row per ZIP code, and if neither the shipping nor the billing address matches your file, tax is not applied. Automatic rate determination comes from one of the eight providers Chargebee lists: Avalara, Anrok, Vertex, Taxamo, Vertex Validator, Kintsugi, ONESOURCE Indirect Tax, and Sphere. Commenda maintains the rates and calculates on the invoice, so there is no rate file to keep current.

No. Chargebee describes its tax integrations as automating tax filing and reporting, and the filing itself happens in the partner product rather than in Chargebee. What Chargebee gives you is reporting: tax and exemption summaries segmented by jurisdiction name and jurisdiction type, downloadable per jurisdiction. Chargebee also notes that jurisdiction codes can come back empty for some jurisdiction types because that data comes from the provider. Commenda files and remits across all 50 states and 70+ countries on each jurisdiction's required frequency, tracks remittance per jurisdiction, and files amendments where a period needs correcting.

No to both. SaaS taxability varies state by state, and within a state by delivery model and customer type. Some states treat B2B SaaS as tangible personal property, New York being the classic example, and others exempt it. Chargebee's tax profiles are what separate digital from non-digital products, and Chargebee documents tax profile support for the EU, Australia, New Zealand, and the United Kingdom. That list does not include the United States, which is exactly where the SaaS answer splits by state. Commenda maintains a state-by-state SaaS matrix and assigns the correct product tax code to each transaction, so the same subscription resolves differently in New York and California without you keeping a rules matrix.

It depends on how your rates are configured, and this is the case most tax pages skip. Chargebee calculates tax on the invoice date by default. Its transitional taxation feature will split a single invoice across two rates when a rate changes inside the service period, and Chargebee states plainly that this is supported only for manual taxes configured in Chargebee, is not supported in any tax integration, and is not supported for any accounting integration. Without it, Chargebee's own documented workaround is to update the rate yourself, issue a credit note for the remaining service period, and raise a one-time charge at the new rate. Commenda maintains rate history centrally and calculates from the invoice and the credit note as Chargebee records them, so a rate change does not need a manual credit-and-recharge before the next bill run.

A good part of the invoice mechanics, and none of the compliance. Chargebee validates a customer's VAT number against VIES, can request and store a VIES consultation number as proof that the check happened, and collects location evidence for digital sales by matching the billing country against the customer's IP address or card BIN, blocking the order where neither matches. Its published EU rate list carries a note that rates were last updated on May 29, 2019 and recommends you review them yourself. Its registration guidance describes VAT MOSS, and Chargebee states that its Brexit changes require your action and will not be updated on your behalf. Commenda registers you for EU VAT, files under OSS, and covers the UK and the non-EU European countries as separate registrations.

Because Chargebee's own reverse charge compares two countries, not two tax IDs. Chargebee states that reverse charge is supported only for cross-border transactions and not for domestic transactions under its manual taxation, and that it checks only whether the buyer's country differs from the country in your organization address. Its documentation is explicit that reverse charge is applied even where there is a tax registration number in the buyer's country. Inside the EU the rule is different: Chargebee drops VAT when the buyer holds a valid VAT number and sits in a different member state. Where a third-party provider categorises a transaction for reverse charge, Chargebee applies that irrespective of the setting. Commenda breaks each transaction into its component figures and maps them to the treatment and the return format each jurisdiction requires.

Chargebee cancels it at renewal. Both the Avalara and the Anrok integration pages state that for customers who signed up before the integration was enabled, Chargebee will cancel their subscriptions during renewal if tax cannot be determined, and both ship a validation tool for finding those subscriptions before they lapse. There is a separate setting that generates the invoice without applying tax instead of blocking the renewal, and Chargebee notes it applies only to renewals processed through third-party providers. Commenda reads the transaction after Chargebee has recorded it, so an address it cannot resolve surfaces as a data exception on the ledger rather than a cancelled subscription.

In some states, yes. A meaningful minority of states include exempt sales when calculating whether you crossed the economic nexus threshold, so you can owe a registration obligation in a state where the underlying sale is not taxable. Chargebee reports the non-taxable amount by jurisdiction name and jurisdiction type, which tells you the size of it but not whether it has put you over a line. Commenda surfaces it state by state and counts it against the right threshold for each one.