Skip to content

Sales tax and VAT software for Campfire

Campfire closes the month fast and books your tax liability cleanly. It does not set the rate, watch a state threshold, register you, or file a return, and its own integrations directory lists five vendors for that. Commenda is one of them and the rest of it too, across all 50 states and 80+ countries.

Integration connection between platform and Commenda

Trusted by global businesses

Storii
Storii
Mpl
Mpl
Cloudsek
Cloudsek
Razorpay
Razorpay
Assembled
Assembled
WilsonLearning
WilsonLearning
GmLighting
GmLighting
Isochem
Isochem
ProlongLash
ProlongLash
Mystifly
Mystifly
Seismic
Seismic
Fairs
Fairs
Remote
Remote
PineLabs
PineLabs
Jhana
Jhana
Avea
Avea
Wetstone
Wetstone
Pharmapac
Pharmapac
Composio
Composio
LoulouLollipop
LoulouLollipop
Passes
Passes
Aestus
Aestus
Frex
Frex
Aspire
Aspire
RifaAi
RifaAi
Skydo
Skydo
Trx
Trx
Npw
Npw
Mojo
Mojo
CleanAir
CleanAir
CoxLondon
CoxLondon
SportsHeads
SportsHeads
Skydesk
Skydesk

One vendor instead of five options

Campfire lists five sales tax vendors in its Sales Tax integration category and leaves the choice to you. Commenda does calculation, exposure, registration and filing itself, so you pick once.

Know about a threshold before you cross it

Campfire does not track nexus. The word appears nowhere in its published API, and every mention on its site describes a partner capability. Commenda measures your Campfire invoices against thresholds in all 50 states and 80+ countries and tells you at 80%.

Campfire books the tax. We calculate and file it

In every Campfire tax integration the partner calculates, Campfire books the liability, and the partner remittance clears it. Commenda does the calculating, the registering and the filing, across all 50 states and 80+ countries.

Coverage comparison

What Campfire handles, and what it hands to a partner

Campfire routes tax to an integration rather than a module, so most rows below turn on which partner you picked. Its figures come from Campfire's own Anrok announcement, Avalara integration page, January 2026 product update, and core accounting page, checked on September 16, 2026.

CampfireCommenda
Calculating tax on an invoiceThrough a partner. Campfire states that Anrok applies the rates to invoices created in CampfireRates maintained per jurisdiction and applied per transaction
Booking the tax to the right accountHandled, and handled well. A journal entry for tax payable by jurisdiction, cleared when the partner remitsCalculated per transaction and reconciled against what you filed
Applying a rate without a partnerManual. Rates a person selects, applied in bulk across selected transactionsApplied automatically, per jurisdiction and per product
Knowing where you oweNot handled. Nexus belongs to whichever of the five tax partners you pickEconomic and physical thresholds in 50 states and 80+ countries, with alerts at 80%
Registrations for collecting taxNot handled. Registration happens in the partner's dashboardPermits in all 50 states, EU VAT with OSS and IOSS, and GST across APAC and Canada
Filing your US sales tax returnsNot handled. The partner files, on its own subscriptionFiled in all 50 states, amendments included
Filing VAT and GST outside the USNot handled. International VAT is described as the partner engine's capabilityFiled across 80+ countries from one platform
Exemption certificatesNot handled. Certificates live in the partner, and are tested in its sandboxCollected, validated, stored, and applied automatically where valid
Product and service taxabilityNot handled. Campfire stores the partner's tax code on the product and hands it overApplied per jurisdiction, per product, on every transaction

Calculate tax on your Campfire invoices

Campfire is clear about who does this. Its own announcement of the Anrok integration says the partner applies the correct rates to every invoice created in Campfire. Natively you get tax rates a person selects and can apply in bulk, which Campfire frames as useful when importing from systems that do not calculate tax automatically. Commenda holds the rate per jurisdiction and applies it per transaction.

global indirect tax calculation software product shot commenda

Track your global exposure from Campfire

Campfire closes the month three to ten days faster, and none of that speed tells you which state your billing just created an obligation in. Commenda measures the same revenue against economic thresholds in all 50 states and 80+ countries and tells you at 80%, before you cross. A short questionnaire covers physical presence too, because an office or a remote employee never shows up on an invoice.

global indirect tax exposure tracking software product shot commenda

Register and file everywhere you owe

In every Campfire tax integration the pattern is identical. The partner calculates, Campfire creates the journal entry for tax payable by jurisdiction, and when the partner remits, that syncs back and clears the liability account. The booking is Campfire's. The registration, the return and the remittance are not. Commenda registers you in all 50 states, across EU VAT including OSS and IOSS, and for GST in APAC and Canada, then files on each jurisdiction's frequency.

global indirect tax remittance software product shot commenda

Manage your customers and exemptions in one place

Campfire stores your partner's keys on its own records, including an Avalara tax code on each product and an Anrok customer ID on each invoice. Certificates themselves live in the partner. Commenda holds a verified tax ID on the customer record with the system it came from, and certificates work the same way: your customers upload through a portal, each one is validated on upload, and it applies automatically where it is valid.

global indirect tax exemption certificate software product shot commenda

Consolidation

Why the journal entry is not the whole job

Campfire closes the books fast and books tax liability properly while doing it. Indirect tax is a different job. It needs a rate for each jurisdiction, a threshold counted across every sales channel, a registration, and a return filed on each state and country schedule. Commenda does that work on top of your Campfire data.

  • Campfire treats tax as an integration, not a product

    Campfire's product menu is core accounting, revenue automation, Ember AI, accounting intelligence, and implementation. Tax is not on it. Instead its integrations directory carries a Sales Tax category with five partners. That is a reasonable decision for an ERP to make. It also means picking the tax vendor was always going to be your job, and the ledger is neutral about which one.

  • Campfire books the tax a partner calculated

    Every Campfire tax integration reads the same way. The partner calculates, Campfire creates the journal entry, and the partner's remittance clears the liability account. The accounting is clean. The tax decision, the registration and the return all happened somewhere else, on a separate subscription, with a separate support queue.

  • A tax partner only sees Campfire invoices

    A partner connected to Campfire calculates on the invoices that pass through Campfire. Revenue from a marketplace, a reseller, an app store or a second billing system counts toward the same state threshold and none of it appears. Physical presence never appears on an invoice at all. One office or one remote employee creates an obligation with no revenue threshold to cross first.

  • One number per state, whatever it came through

    Campfire is one of 100+ systems Commenda reads, and each transaction keeps its origin, its product tax code, and any tax already collected. An app store sale that was never yours to tax stays separate from a direct invoice that needs it. You get one exposure figure per state and one return per period.

What it requires

What Campfire hands to a tax partner

Every row below is Campfire describing its own role. Two are easy to miss. The rate on an invoice comes from the partner, and Campfire part of the filing cycle is the journal entry that the partner remittance later clears.

What you needWhat Campfire requiresSource
A rate applied to an invoice automaticallyA tax partner. Campfire's own announcement states that Anrok applies the correct rates to every invoice created in CampfireCampfire, Anrok integration
A rate applied without a partnerYou, manually. January 2026 added bulk application of a sales tax or VAT rate across selected transactions, which Campfire frames as useful when importing from systems that do not calculate tax automaticallyCampfire, January 2026 update
Tax on an invoice through the APIA number you supply. The documented line item field is a plain tax amount, with no address, jurisdiction or tax code in the request and no rate-lookup endpointCampfire developer docs
To know when you crossed a state thresholdThe tax partner. Nexus appears nowhere in Campfire's published API schema, and multi-state nexus tracking is listed as an Anrok capabilityCampfire, Anrok integration
A registration in a new stateThe tax partner. Campfire's Anrok page describes registering in new jurisdictions from the Anrok dashboard, not from CampfireCampfire, Anrok integration
A return filed and the money remittedThe tax partner. Campfire's role is the journal entry: the partner calculates, Campfire books the liability, and the partner's remittance syncs back to clear itCampfire, Avalara integration
Exemption certificates kept and validatedThe tax partner. Campfire describes validating exemption certificate flows in Avalara's sandbox, and resale exemptions as something applied through its Anrok integrationCampfire, August product update
Product taxability decidedThe tax partner, from keys you map. Campfire stores an Avalara tax code on each product, giving SW052000 for SaaS as its example, plus Avalara and Anrok item IDsCampfire, Avalara integration
A price you can compare before talking to anyoneA conversation. Campfire publishes no pricing page, and none appears in its sitemapCampfire

Figures verified on September 16, 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

Campfire lists five sales tax vendors and stays neutral between them. We compare the options on coverage and ratings, and say which buyer each one suits.

Best AI Tax Software for Campfire (2026)

More sales tax resources

Guides from the Commenda team on nexus, permits, remittance, and switching vendors.

See all articles

Frequently asked questions

What finance teams running Campfire ask before they move their indirect tax to Commenda.
Read our FAQ library

Through a partner, yes. Campfire's own announcement of its Anrok integration says the partner applies the correct rates to every invoice created in Campfire, and its Avalara page describes the same flow. Natively, Campfire gives you tax rates a person selects, with a bulk-apply tool added in January 2026 that Campfire frames as useful when importing from systems that do not calculate tax automatically. Its API takes a plain tax amount on a line item, with no address or jurisdiction in the request. So the rate comes from somewhere, and that somewhere is the decision. Commenda is one platform for the rate, the exposure, the registration and the return.

The number of vendors, and what the exposure figure is measured on. A tax engine connected to Campfire calculates on the invoices that pass through Campfire, and files on its own subscription. Commenda reads your Campfire ledger and every other channel you sell through, across 100+ integrations, into one ledger tagged by ship-to state, then registers and files from that. Teams usually move because they were holding a ledger, an engine, and a filing relationship, and wanted one accountable vendor instead of three.

No. Nexus appears nowhere in Campfire's published API schema, and multi-state nexus tracking is listed as a capability of the partner rather than of the ledger. That matters because sales tax liability starts on the day you cross a threshold, not on the day you notice. Commenda notifies you at 80% of a registration threshold so the registration can go in while you are still under it, and a questionnaire covers physical presence as well, since an office or one remote employee creates an obligation with no revenue threshold to cross first.

Partly, and the split is worth knowing. Campfire supports 180+ currencies and unlimited entities, it lets each entity relabel a tax ID as a VAT or GST number on invoices, and a 2024 post describes VAT automation in its global reporting. What its current product pages describe is international VAT as a capability of the partner engine you connect. No VAT return, One Stop Shop, or Import One Stop Shop filing is published anywhere on its site. Commenda registers and files VAT across the EU including OSS and IOSS, and GST across APAC and Canada.

The tax partner. Campfire describes validating exemption certificate flows in Avalara's sandbox environment, and applying resale exemptions through its Anrok integration, so the certificates themselves live in whichever engine you chose. Commenda collects them through a portal your customers upload to, validates each one on upload, stores it against the customer record, and applies it automatically on future transactions where it is valid. During an audit the certificate is already on file, which is the point at which the difference is felt.

It is enough for the books and not for the obligation. Campfire creates a journal entry for tax payable by jurisdiction and clears it when the partner remits, which is exactly what a general ledger should do. None of it answers where you are required to register, what your product is taxable as in each state, or which return is due next week. Those are the parts that produce an assessment when they go wrong. Commenda covers them on top of the same Campfire data.

Your invoices and credit memos, the ledger behind them, and the entity each one belongs to. That one connection feeds three things: sales tax and VAT calculation, your monthly close, and the intercompany testing behind transfer pricing. You choose which entities and which data models sync, and what Commenda can read and write, and those scopes stay visible and editable after setup. Access runs per user and per entity, so auditors get read-only access without shared credentials.

Custom integration support for your business

Campfire setups differ in what feeds them. Some teams bill through Stripe, some through Chargebee or Orb, some raise invoices from Salesforce. We map how yours works, including which revenue arrived already taxed and which entities need VAT, 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