Your Tax Software Just Got an AI Middle Manager — What Avalara Avi Actually Does for Accounting Firms

There's a category of news that looks like a software update but is actually a liability shift. Avalara Avi belongs in that category.

Avalara made Accounting Today's 2026 Top New Products list. The reason wasn't a new interface or a smarter tax chatbot. The reason was that Avi has been rebuilt from scratch as a multi-agent AI orchestration layer — a system that doesn't just answer compliance questions, but executes compliance tasks by coordinating specialized AI agents in the background.

If your clients use Avalara, autonomous AI agents may already be running compliance workflows in their accounts. The question isn't whether this matters to your firm. It does. The question is what to do about it.

---

What Is Avalara Avi? (From Chatbot to AI Agent Orchestrator)

Most accounting firm owners who've encountered Avalara Avi know it as a chatbot. You could type a tax question — "What's our nexus exposure in Colorado?" — and get an answer. That version of Avi was useful in the same way a knowledgeable junior employee is useful: available, fast, and reasonably accurate on known issues.

The new Avi is different in kind, not just degree.

A chatbot answers questions. An agent executes tasks. Avi has crossed that line.

The current Avi is an orchestration layer: give it a compliance workflow goal, and it delegates subtasks to specialized AI agents — one for sales tax nexus research, one for exemption certificate validation, one for audit documentation prep. Each agent handles its piece of the task autonomously. Avi coordinates the results and delivers an output.

In plain English: instead of asking Avi a question and getting an answer you then act on, you can assign Avi a workflow goal and have the AI complete the steps on its own.

That's not a chatbot anymore. That's an AI middle manager — one that's running inside your client's Avalara account whether you know it or not.

---

What Avi Does in Practice — The Workflows It Runs

The three core workflows Avi can execute autonomously:

Sales tax nexus analysis. Avi can research a client's nexus exposure across states based on their transaction data, identify new nexus thresholds crossed, and surface the results without requiring the accountant to initiate each step manually. For a client with multi-state sales activity, this used to mean hours of manual research or an expensive consulting engagement. Avi compresses that into an automated workflow.

Exemption certificate validation. Outstanding or expiring exemption certificates are a chronic risk management problem for accounting firms that manage Avalara for clients. Avi can run automated checks on the status of certificates by account — flagging gaps, expiries, and missing documentation. This previously required someone to pull a report and review it line by line.

Audit response support. Avi can route relevant documentation and prepare summary responses when a client faces a sales tax audit inquiry. The agent assembles what's in the Avalara system — transaction records, exemption certificates, nexus positions — into a prepared response packet.

The common thread: all three are multi-step workflows that used to require a human (your staff or the client's) to initiate each step manually. Avi now runs those steps. In the background. On its own.

---

Why This Matters for Your Firm (Even If You're Not the One Using Avi)

Here's the nuance most accounting firm owners miss: many accounting firms don't use Avalara for their own operations. They manage Avalara for clients — configuring it, troubleshooting it, advising on nexus questions. The client owns the Avalara account. The firm is the professional advisor.

In that relationship, when Avi's agents execute a compliance decision inside the client's account — say, validating an exemption certificate that a human reviewer would have flagged for follow-up — where does your firm's advisory relationship to that decision stand?

This is not a theoretical question. It has three practical implications:

1. You may not know Avi is running. Clients don't call to say "hey, we turned on the AI agent workflows in Avalara." They accept a product update or click through an in-app prompt. The agents start running. The compliance positions start forming. You don't know until you look.

2. Autonomous outputs may not be reviewed before positions are taken. A human reviewing an exemption certificate has a chance to catch something questionable. Avi's agent validation runs on its own timeline, without a required human checkpoint. The compliance position may be set before anyone at your firm sees it.

3. Your engagement letter probably doesn't address this. Most engagement letters were written when the tools of record were human-operated software. They specify what work your firm will do and how decisions will be reviewed. They don't contemplate AI agents running compliance workflows inside the client's own software — workflows that your firm had no hand in initiating.

---

Three Things Accounting Firms Should Do Before Clients Rely on Avi Agents

1. Inventory your Avalara-using client accounts.

Identify which clients use Avalara, and for each one, find out whether Avi is enabled and what automated workflows are active. This is a client outreach task, not a technical one — call, email, or ask on the next client call. You're looking for one answer: is Avi running agent workflows in this account, and if so, which ones?

You will find that some clients have no idea what Avi agents are. That conversation itself is valuable — it positions your firm as the one that noticed and asked.

2. Update your engagement letter.

Add a clause that clarifies the following: AI-assisted compliance decisions generated by third-party software (including client-owned tools like Avalara) remain subject to your firm's professional review before any compliance position is taken. This language protects you when an Avi agent produces an output that turns out to be wrong — and it sets client expectations that autonomous agent outputs don't substitute for your review.

If you don't have an attorney-drafted engagement letter, this is a good time to get one. If you have an existing template, this is a single addendum.

3. Ask Avalara about agent action logs.

Before you can review Avi's work, you need a record of what Avi did. Ask Avalara — either through their support channel or your account rep — what audit logging is available for Avi agent actions. Specifically: can you pull a log of agent-executed workflows, the inputs they used, and the outputs they produced?

If a client faces a sales tax audit inquiry that touches on a compliance position Avi's agents helped form, that log is your documentation. If it doesn't exist or isn't accessible, that's a gap in your engagement with that client that needs to be addressed now.

---

What This Signals for the Rest of the Tax Tech Stack

Avi is first, but it isn't unique.

Intuit is building agent capabilities into QuickBooks and its professional accountant tools through its Anthropic partnership. Thomson Reuters is upgrading Checkpoint AI with agentic features. Canopy has AI workflow automations in active rollout. Digits — as covered recently in our analysis of the Xero OS launch — is connecting live financial data to AI agents directly.

"Agentic" is the word that will define tax and accounting technology in 2026–2027. Not "AI features" — agents that act autonomously, run multi-step workflows, and produce outputs without waiting for human prompts at each step.

Avalara Avi is the clearest current example because it's in production, in client accounts, running now. But the same capability is arriving across the entire tax tech stack over the next 12 to 18 months.

The accounting firm owners who understand this transition — who can explain to a client what an AI agent is doing in their Avalara account and what review is appropriate — are positioned to lead on AI governance in their client relationships. That's not a small thing. Clients who encounter these tools without guidance will make decisions based on their own understanding, which may or may not account for the compliance risk.

The firm that shows up with a clear framework is the one that gets trusted with the next conversation. The firm that shows up without one becomes reactive.

---

The Practical Next Step

This week, do one thing: make a list of every client account where Avalara is in use. For each one, note whether your firm has visibility into what Avi is or isn't doing in that account.

That list is the start of your Avi governance posture. It tells you where you're exposed and where you need to have a conversation. Most accounting firm owners who do this exercise will find at least one client account where Avi may be running workflows they've never discussed.

That's the conversation to have — before Avi runs a workflow that ends up in an audit.

Related: Digits MCP and Xero's AI OS: What Accounting Firms Need to Know | Agentic AI: The Year of Agents for Professional Services Firms

---

The Crossing Report covers the arrival of agentic AI in professional services software every week — translated for firm owners, not tech buyers. Subscribe here.