Sphere
Sales tax determination, registration and filing, kept separate from the ledger that records it.
What it does
Sphere determines sales tax on transactions, monitors where selling activity has created a filing obligation, and handles registration and returns.
Why it matters next to an AI-native ERP
Sales tax exposure is created by selling, not by accounting, and it accumulates quietly until somebody looks. The ledger records the liability but does not work out where it exists.
It is worth saying plainly that this model is specific to the United States. In Mexico, Colombia, Chile, Panama and the Dominican Republic, tax is not something you determine and file afterwards. The invoice is not legally valid until the tax authority has validated it in advance and returned an authorisation code. That is a different architecture, and it belongs inside the transaction path rather than in a filing tool.
How we implement it
We start with a nexus review, map product taxability, handle exemption certificates in the customer master, and reconcile the liability accounts against what is actually filed. For entities operating under a clearance regime we design the certified provider integration instead, which is a different piece of work and we scope it separately.
We implement this alongside Campfire, Rillet and DualEntry. If you are working out how it should connect to your ledger, that is the conversation we have every week.