Sales tax and VAT software for Campfire

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.