Your sales tax is a spreadsheet and a prayer

Somewhere in your company, sales tax is being handled by a heroic person and a spreadsheet. They update rate tables by hand when they remember to. Exemption certificates live in a filing cabinet, or an inbox, or a shared drive nobody's audited since the last administration. And ever since economic nexus became a thing, you technically owe tax in a growing list of states you've never set foot in, which everyone knows and nobody wants to think about too hard.

It works, in the sense that a system held together with good intentions works right up until an auditor asks a pointed question. Hand-maintained tax is a spreadsheet and a prayer — and the fix is to stop making Ross pretend it knows tax law and connect it to something that actually does.

Why Ross should not be your tax authority

Ross is a fine system of record. It is not, and was never meant to be, a live database of tax rules for every jurisdiction in the country. And that's what modern sales tax actually requires: thousands of jurisdictions, rates that change constantly, product taxability rules that vary by state, and the special joy of South Dakota v. Wayfair, which in 2018 decided you can owe sales tax in a state purely for selling enough into it — no office, no warehouse, no visit required.

Asking Ross to keep up with all of that through hand-maintained rate tables is asking your heroic spreadsheet person to lose. The rules move faster than any human can maintain them, and the penalty for falling behind isn't a warning — it's an assessment with interest.

What a tax engine actually does

This is a solved problem, and it's solved by a category of software whose entire job is knowing tax law so your ERP doesn't have to. The big ones are Avalara and Vertex; Taxware (now under Sovos) is the older, established name. They differ in the details, but the shape is the same, and it's genuinely good at three things.

They calculate tax at transaction time, using validated addresses and current rules, so the right rate is applied to the right line for the right jurisdiction without anyone maintaining a table. They manage exemption certificates — collecting, storing, and applying them — so a tax-exempt customer is handled by the system instead of by whoever remembers the cert is in a drawer. And they handle returns and filing, turning "how much do we owe where, and did we file it?" from a quarterly panic into a report.

The integration is the whole game

Buying Avalara or Vertex doesn't fix anything by itself. The value shows up only when Ross actually calls the engine at the right moments — when an order is quoted, when an invoice is cut — and applies the answer correctly.

That's the integration, and the interesting parts are where it usually goes wrong. Addresses have to be validated and mapped, because tax is jurisdiction-specific and "close enough" on an address means the wrong rate. Product taxability has to be right, because not everything is taxable the same way and a process manufacturer's catalog has real variety in it. Exemptions have to flow through so an exempt customer isn't charged and a non-exempt one isn't missed. And credits, returns, and adjustments have to reconcile back cleanly, because tax on a return that never gets reversed is its own small audit finding waiting to happen. None of this is exotic, but all of it has to be correct, because tax is the one area where being approximately right is a specific dollar amount you owe.

Don't forget the AP side

Sales tax gets the attention because it faces the customer, but use tax — what you owe on your own purchases when the vendor didn't charge it — is the quieter exposure, and it lives on the AP side of Ross. The same engine can help you get that right too, which matters because use tax is exactly the kind of thing that's invisible until an auditor finds a pattern of untaxed purchases and starts multiplying.

The audit is the point

Step back and the whole case is about one moment: the audit. When it comes — and for a multistate seller it's when, not if — you want to hand over a defensible, automated, consistent record of how every tax decision was made, instead of a spreadsheet, a filing cabinet, and a story. Connecting Ross to a real tax engine isn't about convenience. It's about being able to answer the question calmly. The convenience is just a bonus you get every day in between.

The bottom line

If sales tax at your company depends on someone's manual rate tables and a filing cabinet of certificates, you're carrying a risk that grows every time a rate changes or you cross a nexus threshold you didn't notice. Connect Ross to Avalara, Vertex, or Taxware, get the integration right where it counts — addresses, taxability, exemptions, reconciliation — and turn tax from a recurring dread into boring, defensible infrastructure. Your spreadsheet hero has better things to do.

If your Ross tax setup is one audit away from a bad quarter, connecting it to a real tax engine is a clean, high-relief project. Let's talk →. Related: the integration archetypes nobody names.