
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec rhoncus neque sed nibh sagittis, fringilla porttitor ipsum tristique. Nulla interdum ex et nisi vehicula, id laoreet nisl ultricies. Phasellus vitae magna ac lacus dictum tincidunt. Sed iaculis metus nec viverra pulvinar. Etiam id nisi eu turpis mattis imperdiet ac ac tortor. Aliquam at ipsum dui. Etiam pharetra consequat massa. Aenean nec lectus sit amet metus pharetra dapibus. Pellentesque interdum ex eget nisi fringilla, id semper erat rhoncus. Suspendisse lectus leo, malesuada pharetra commodo a, sollicitudin eu erat. Nullam justo nisl, tincidunt vel auctor id, luctus a tellus.
Pellentesque sollicitudin mauris sit amet enim volutpat, at faucibus sem laoreet. Morbi egestas ex non orci interdum, ut elementum orci faucibus. Maecenas et sem convallis erat dignissim facilisis. Quisque purus sapien, pellentesque euismod varius id, fermentum nec nibh. Integer commodo dignissim ipsum, ac accumsan metus fringilla sit amet. Aenean aliquam sem finibus tempor venenatis. Aliquam ac facilisis turpis, eu posuere ipsum.

In nisi dui, ultricies sit amet gravida vel, ullamcorper vel mauris. Aliquam nec sapien odio. Sed vitae suscipit felis. Nullam semper blandit lectus, eu finibus urna fermentum et. Aliquam vehicula ligula nibh, non efficitur massa iaculis et. Vestibulum vitae euismod odio, non maximus nulla. Sed viverra porta enim ac interdum. Maecenas auctor tristique auctor. Nullam et neque nec tortor malesuada ullamcorper. Pellentesque ac fringilla ante, non convallis est. Proin velit augue, rutrum vitae ipsum vel, malesuada dictum urna. Nunc vulputate sit amet odio vitae ullamcorper. Nullam suscipit ornare eros, et viverra sapien hendrerit quis. Donec odio eros, ultricies a risus quis, efficitur elementum turpis. Etiam interdum diam quis turpis ultricies.
Sed non sapien eros. Duis fringilla fringilla lectus sit amet aliquam. Aliquam erat volutpat. Vivamus molestie, felis rutrum luctus pulvinar, libero metus eleifend mauris, semper malesuada ante eros vitae eros. Phasellus vitae dolor faucibus, laoreet lectus quis, placerat nisi. Nam ornare nulla id est aliquet, quis fringilla neque congue. Duis facilisis sed massa vel bibendum. Curabitur sollicitudin tristique commodo. Vivamus facilisis venenatis nibh. Integer placerat elementum felis, id consequat lorem consectetur a. Duis laoreet sit amet nisl in eleifend. Interdum et malesuada fames ac ante ipsum primis in faucibus.
Proin eros lacus, pellentesque sed vehicula a, luctus non nibh. Nulla diam sem, posuere ac odio varius, ultrices tristique nibh. Morbi dictum scelerisque convallis. Praesent faucibus lorem lacus, id luctus justo feugiat et. Curabitur eget tellus non nisi interdum blandit. Maecenas pulvinar est sed ex elementum, ac commodo diam bibendum. Nulla auctor dolor felis, sit amet euismod ante eleifend non. Donec id neque magna.
Sales and use tax is the most boring compliance obligation your company has and it is the best first place to put AI to work, precisely because it is boring. The work is high-volume, it repeats on a calendar you cannot move, every output is checkable against something, and almost nobody on your team wants to own it. That combination is rare, and it is exactly the profile of a job you should be handing to a machine while the rest of the profession argues about whether AI is coming for the CPA.
The scale of the problem is genuinely absurd. In the Wayfair dissent, Chief Justice Roberts noted that over 10,000 jurisdictions levy sales taxes, each with different rates, different rules on what is exempt, different product category definitions, and different standards for when an out-of-state seller has enough presence to owe anything. Then the Court removed the physical presence rule anyway, and eight years later that complexity is a normal Tuesday for a mid-market controller with customers in twenty states.
Because there is no single American sales tax, there are thousands of them, and the harmonisation effort has only ever been voluntary. The Streamlined Sales Tax Governing Board has spent two decades trying to standardise definitions, rates and administration, and as of August 2025 it counts 23 full member states plus one associate member. That is real progress and it still leaves roughly half the sales-tax states doing whatever they want, which means the exceptions are the job.
And the exceptions are not exotic. A software subscription is taxable in one state, exempt in the next, and taxable only if it is downloaded rather than accessed in a third. A shipping charge is part of the taxable sale here and separately stated and exempt there. A customer hands you a resale certificate that expired in 2023 and nobody looked. Multiply that across your SKU list, your customer list and your filing calendar and you get the actual shape of the work, which is thousands of small determinations that each take ten seconds and collectively eat a person.
The frustrating part is how invisible this work is. Across the 80,000-plus accounting and finance postings we track at Audit Friendly, sales and use tax barely registers as a named skill next to close and reconciliation work, even though it is one of the most common sources of a surprise seven-figure assessment at a growing company. The profession has decided this is somebody else's problem, and the somebody is usually a controller doing it at 9pm on the 19th.
Start with taxability classification, because it is the highest-volume decision you make and it is genuinely repetitive. When you launch a new SKU or a new service line, something has to decide what tax category it falls into across every jurisdiction where you have registered. A model with your product catalogue and your existing classification history in front of it will get you a well-reasoned first pass in seconds, flagged by confidence, and your tax person reviews the flagged ones instead of all of them. That is a huge amount of time back and the downside is bounded because every determination is reviewable before it hits a filing.
Exemption certificate management is the second obvious one, and it is where most companies are quietly exposed. AI reads the certificate, pulls the entity name, state, certificate type, and expiry, checks it against the customer master, and tells you which ones are missing, mismatched, or dead. Your auditor is going to ask for exactly this file and most teams assemble it in a panic. Having a process that keeps it current all month is the same rolling-work logic we wrote about for the close, and it works for the same reason.
Then nexus monitoring. Economic nexus thresholds are just arithmetic against your revenue and transaction counts by state, but nobody watches them continuously, so companies cross a threshold in March and find out in November. Wiring a monthly check that reads your sales data and tells you which states you are approaching is not even sophisticated AI, it is a report nobody built, and it prevents the single most expensive mistake in this whole area.
Two more that pay off fast: use tax accrual review on the AP side, where a model scans vendor invoices for purchases that came in without tax and should have accrued some, which is tedious enough that most teams sample it rather than do it. And reconciling the filing back to the general ledger, where AI can explain the variance between what the tax engine says you collected and what the revenue accounts say, which is the exact tie-out that makes filings late.
Taxability is a legal conclusion, and a confident wrong one is worse than no answer, so the same discipline applies here that applies to any tax research: if the model gives you a determination, you want a citation to the actual statute, regulation or ruling, and you pull it and read it. Models invent authority that sounds right. In sales tax the invented answer is especially seductive because the real rules are so weird that a plausible fabrication is indistinguishable from a genuine oddity.
Sourcing rules are another trap. Whether a sale is taxed where it ships from or where it ships to, how a service performed in two states gets allocated, what happens with drop-shipments across three parties, these are exactly the questions where a general-purpose model will give you a clean confident paragraph that is wrong in your specific state. Treat sourcing as human territory until you have tested it against known answers repeatedly.
And be careful about registration. Once you register in a state you owe returns forever, including zero returns, and an AI that helpfully suggests registering everywhere is handing you a permanent compliance obligation you may not need. That is a business decision with a cost, and it belongs to a person.
The other thing I would hold onto: a tax engine and an AI assistant are two different products and you probably want both. Rate calculation at transaction time is a solved, deterministic problem that belongs in software wired into your billing system, while the AI layer sits above it doing classification, review and exception handling. Conflating the two is how teams end up disappointed. If you are working out which pieces you actually need, we score tools on features, support, value and security in the Audit Friendly software directory, and the broader framework in our guide on how to choose accounting software applies here with one override, which is that your billing system integration outranks every other feature on the list.
Because the feedback loop is fast and the blast radius is small. An income tax position sits unresolved for years, the judgment is dense, and you find out you were wrong on exam. A sales tax determination gets tested every single month when you file, so you learn quickly whether the workflow you built is any good, and a bad classification on one SKU is a fixable error rather than a restatement.
That is also why I would rather someone build here first. We mapped the broader picture in where AI actually fits in the tax workflow, and the pattern holds: put the model on the repeatable prep, keep the person on the call. Sales tax just happens to be the corner of tax where the repeatable prep is the biggest share of the work.
Pick the exemption certificate file, because it is the least glamorous and the most immediately useful. Point a model at your existing certificates, have it extract entity, state, type and expiry into a table, then reconcile that table against your customer list and see how ugly the gaps are. It will take you an afternoon and you will find something, I promise. Then decide whether you want that check running monthly, which is the whole game.
After that, run classification on new SKUs for a quarter with human review on every output, and measure how often the model was right before you loosen the review. Build the trust with evidence instead of vibes. And if this work is becoming a bigger part of your role, the market is quietly paying for it, so it is worth watching what shows up on the remote tax jobs board and pricing yourself accordingly.
It can produce a strong first pass with a rationale, and that pass needs human review before it drives a filing. Taxability is a legal conclusion that varies by state and by product definition, so treat AI output as a draft determination with a citation you verify, never as the final answer.
Exemption certificate management. Extracting entity, state, certificate type and expiry from a stack of certificates and reconciling that against your customer master is high-volume, entirely checkable, and it is the exact file an auditor asks for first, so the work pays off twice.
Yes, for most companies. Rate calculation at the point of transaction is deterministic and belongs in software wired into your billing system, while AI is better suited to classification, exception handling and review sitting above that engine. They solve different problems.
Since the Supreme Court decision in South Dakota v. Wayfair removed the physical presence requirement, states can require out-of-state sellers to collect once they exceed a revenue or transaction threshold in that state. Thresholds vary by state, so monitoring your sales by state continuously is the only reliable way to catch a crossing before it becomes a liability.
It depends entirely on the tool and its data handling terms. Purpose-built tax software with real controls is a different risk profile than a consumer chatbot, and transaction and customer data is sensitive enough that the security review should happen before any efficiency conversation.
The tools to take this off your plate exist right now, and most finance teams have not wired up even the easy piece. Go build the certificate check this week and see what falls out.