Operators routinely ask for “sales tax like the big suites.” That phrase hides two different products: calculation on transactions and compliance automation up to filing. The first belongs in your ledger; the second is a regulated service category with its own vendors, registrations, and liability. Conflating them produces RFPs that no single tool answers honestly.
The calculation layer (belongs in your books)
Solid operational software lets you define tax codes, tie them to rates (basis points or decimal equivalents), and apply them per invoice line where mixed taxable and non-taxable work is common — fleet repair invoices are a classic example. The output you want is deterministic: given these lines, these codes, and these rounding rules, the tax total matches what you print and what you book to liability accounts.
The filing layer (often separate)
- Jurisdiction sourcing: Where a sale is taxed can depend on destinations, exemptions, and entity nexus — tables change; counsel interprets.
- Registrations and credentials: Filing access is not a generic API shim.
- Remittance and penalties: Deadlines and corrections carry real money risk — beyond “software says so.”
Buying criteria that survive audit conversations
Ask vendors to separate claims: Can you show me the ledger postings for a mixed-tax invoice? Can you export the detail? If the answer is fuzzy, “tax automation” marketing is covering weak bookkeeping. Privbooks is explicit: line-accurate math with codes you own — not e-file, not jurisdiction autopilot.