This article is for informational purposes only and does not constitute tax, legal, or accounting advice. Consult a qualified tax professional before making compliance decisions.

Industry & Opinion

KPMG and Anthropic Ship Managed Agents Into Tax Workflows. The Sales Tax Layer Underneath Is Not Settled.

Beardsley Rumble|2026-05-31|6 min read

On May 19, 2026 KPMG and Anthropic announced a global alliance and launched KPMG Digital Gateway Powered by Claude, integrating Claude Cowork and Anthropic's Managed Agents API directly into KPMG's client delivery platform. The initial focus, per the press release, is tax clients and private equity firms. The 276,000-person professional services firm will use Managed Agents to handle "autonomous, multi-step task execution" against client data hosted on KPMG's Microsoft Azure environment, with KPMG's U.S. arm designated a preferred consultant for deploying Anthropic capabilities into PE portfolio companies. KPMG describes the result as collapsing "weeks" of agent-build time into "minutes."

That is a genuinely significant operational story. It is also, for sales and use tax purposes, an interesting one — because the thing KPMG just put inside its tax delivery wrapper is a product that state revenue departments have not yet decided how to classify. The Big Four is not exempt from that question. If anything, the alliance forces the question into the open.

What KPMG is actually selling

A KPMG tax engagement has historically been a professional service. The deliverable is the judgment of credentialed tax professionals, supported by software tools that are incidental to the advice. In the great majority of states, professional services delivered by licensed professionals are outside the sales and use tax base — sometimes expressly exempted, more often simply not enumerated. That is the framing the firm has lived inside since the New York Sales Tax Bulletin TB-ST-690 era.

Digital Gateway Powered by Claude is a different animal. The press materials describe Managed Agents performing the actual work — analyzing client data, surfacing exceptions, drafting outputs, executing multi-step tax-rule traversals — and KPMG professionals supervising, reviewing, and stamping the result. The labor mix shifts. The deliverable still carries a KPMG signature, but the substantive computation that produces the deliverable runs in Anthropic's infrastructure against client data residing inside KPMG's Azure environment.

That shift matters because state revenue departments do not classify by what the seller calls a product. They classify by what is actually being delivered.

Three classifications a state will reach for

The same set of facts can support at least three different sales tax characterizations, and the choice of characterization can produce dramatically different outcomes within a single state.

Professional service. This is the frame KPMG would prefer and the one that most closely matches the pre-alliance arrangement. In states that exempt professional services delivered by a credentialed firm — and that recognize tax preparation, audit, and advisory work as falling inside the exemption — the engagement remains outside the base. The risk is that the more autonomously the agent acts, and the less the human supervision tracks traditional review, the harder this frame is to maintain. State auditors will ask how many hours of credentialed-professional time stand behind each deliverable. That is a fact question, not a legal one.

Data processing service. Texas Tax Code section 151.0035 defines data processing to include "word processing, data entry, data retrieval, data search, information compilation, [and] payroll and business accounting data production." The state taxes data processing at 80 percent of the price (the long-standing partial exemption). Several other states — Ohio, Connecticut, Pennsylvania within specific categories — apply analogous treatment. A Managed Agent pulling, transforming, and presenting client tax data fits the data-processing definition far more cleanly than a human partner reviewing a return. If a state revenue auditor reaches for the data-processing characterization, the underlying agent-delivered work becomes taxable in those jurisdictions, regardless of whether the firm wrapping the work is licensed.

Software as a service. Digital Gateway is a hosted platform. Clients access it. The Managed Agents do the work inside the platform. In the seventeen-or-so states that treat SaaS as taxable prewritten software — New York after the Beeline appellate ruling earlier this year, Pennsylvania, Washington, Texas, Tennessee, South Carolina, and others — the characterization question is whether the access fee is the actual revenue event or whether the engagement fee is. If a client pays KPMG an engagement fee and receives Digital Gateway access as part of it, the bundled-transaction rules in each state will determine whether the entire fee, the access portion, or none of it is taxable. New York's recent Beeline holding — that a bundled SaaS-plus-services transaction is fully taxable when the software component is central rather than incidental — is the cautionary case.

None of these three positions is plainly wrong. Reasonable practitioners can argue any of them, and the answer will vary state by state, possibly client by client depending on the engagement structure. The unsettled categorization is exactly the kind of question the AgentTax Tax Policy Registry tracks under saas_vs_information_service and bundled_service_classification — both currently flagged as unsettled or watch, with no plain statutory winner.

Why this matters beyond KPMG

KPMG is the visible case because of the scale and the press release, but the same fact pattern will repeat any time a service-business operator embeds an autonomous agent into a workflow it used to deliver with employees. A boutique tax practice routing client K-1 work through a Managed Agent faces the same three-way classification question. A bookkeeping firm running QuickBooks data through an agent-mediated reconciliation pipeline faces it. A law firm deploying Claude on diligence work faces a version of it. The Anthropic alliance with Intuit announced in February of this year — making TurboTax, QuickBooks, Credit Karma, Mailchimp, and Intuit Enterprise Suite available inside Claude — pushes the same question downstream to every small business operator who runs tax workflows through that integration.

In each of these cases, the operator's incentive is to maintain the professional-service or non-taxable-service characterization. The state's incentive, given the budget pressures driving the 2026 wave of digital tax base expansion (Washington SB 5814, Newsom's May Revise SaaS proposal in California, Utah's October excise, Maryland's data-processing extension), is to reach for the broader characterization. The disagreement is not academic. It determines whether the operator owes tax on what it is actually selling, and whether the buyer owes use tax on what it is actually consuming.

What AgentTax users should do

For operators building agent-delivered services into a previously human-delivered offering, three steps are appropriate now:

Unbundle the invoice. Where the engagement letter can separately identify professional-judgment hours, platform access, and agent-executed computation, the line items support the classification argument later. A single lump sum invites the state's broadest reading.

Document the human-supervision layer. State revenue departments give weight to the credentialed-professional involvement that distinguishes a traditional professional service from a packaged data product. Time entries, review logs, and sign-off records are the evidence.

Register where the agent meaningfully operates. Agent activity on a client's data inside a state can create economic-nexus exposure for the operator even when no human partner ever set foot in that state. The Managed Agents pattern is fundamentally a remote-execution pattern, and the nexus analysis follows the execution, not the firm's office locations.

What to watch

The first state revenue ruling addressed directly to agent-delivered professional services will reset the conversation. The candidates most likely to produce it are Texas (because of the existing data-processing infrastructure under section 151.0035), Washington (because the post-SB 5814 base expansion already pulled software, IT, and advertising into the base), and New York (because the appellate Beeline framework on bundled SaaS-plus-services is now precedent). None of those three states has issued direct guidance on agent-mediated tax engagements yet. Operators should not wait for them. The Tax Policy Registry's positions on these questions remain neutral while the law is forming — but the operational decisions an operator makes today will determine which characterization the operator can credibly defend later.

KPMG and Anthropic have shipped impressive plumbing. The classification layer underneath is the operator's problem, and it does not arrive solved in the box. That is what AgentTax is built to answer. Try the calculation at agenttax.io.

This analysis is for informational purposes only and does not constitute legal or tax advice. Consult a licensed tax professional for compliance decisions.