When a CPA Firm Needs Its Own Sales Tax Answer

Start where you would start for any client: list every state where you have customers, and for each one, note whether your revenue there is purely advisory and preparation work, or includes something else, a resold software subscription, a licensed template library, a white-labeled portal fee. Most firms find the advisory and preparation revenue is exempt everywhere, and the software-adjacent revenue is the only piece worth tracking closely.

This is the same exercise your own team runs for clients constantly. Applying it internally usually takes an afternoon and answers whether either Anrok or Avalara is even necessary yet.

Firms increasingly resell or mark up a bookkeeping platform, offer a proprietary dashboard for tracking client financials, or license a compliance tool they built internally to other firms. Each of those, billed as a recurring subscription or license fee separate from hourly advisory work, tends to be treated as taxable software revenue in states that tax SaaS, even though the firm's core accounting work sitting right next to it is exempt.

Median pay for a staff accountant is $83,680 a year, with the top quartile above $109,810¹, which is worth keeping in mind before assigning a senior accountant to manually track this instead of billable client work.

Outsourced controller and fractional CFO engagements complicate this further when they come bundled with a reporting dashboard the firm built and maintains. If the dashboard access continues even in a month where no advisory hours are billed, that is a sign the fee has become its own product rather than a byproduct of advisory time, and it is worth pricing and taxing it that way rather than folding it quietly into the retainer.

If your firm bills a client portal, dashboard, or resold software subscription through a modern billing tool, Anrok applies SaaS taxability logic to that specific revenue line and tracks nexus as it grows, while your advisory and preparation invoices stay entirely outside that process. For a firm where this is a small but growing side revenue line, that clean separation matters more than raw feature breadth.

A regional or national firm running multiple offices, multiple entities, or a broader mix of services beyond core accounting, think valuation work, technology consulting, or outsourced controller services with embedded software tools, tends to fit Avalara's wider coverage and ERP integrations more comfortably as complexity grows.

Burn multiple discipline still applies to a growing practice the same way it does to any other business², and a messy internal tax process is exactly the kind of quiet inefficiency that shows up in that number eventually.

Pull your last twelve months of revenue and separate it into three buckets: advisory and preparation hours, resold or licensed software, and everything else. Confirm the second bucket's size, since a firm with a genuinely small software line may not need either platform yet, while one where that bucket has grown into real recurring revenue should treat this the same way it would tell a client to.

• Advisory and preparation revenue: typically exempt, confirm state by state
• Resold or licensed software revenue: typically taxable where the state taxes SaaS
• Passed-through reimbursements: typically exempt if documented as a pass-through

If you are unsure how your own state treats a specific line, apply the same standard you would hold a client to and get a second opinion rather than assuming.

Do this review annually at minimum, and sooner if you have just launched a new service line. A firm that starts white-labeling a portal for five clients as a pilot can find that number tripled within a year, and the point where it becomes worth automating is usually earlier than most partners expect.