Washington Rejects the 'It's Just Professional Services' Argument for Digital Automated Services

Washington's Department of Revenue has published a determination that should worry any operator hoping to keep an AI service off the tax base by wrapping it in professional labor. In Determination No. 23-0004, 45 WTD 013, the Administrative Review and Hearings Division held that implementation charges and even reimbursed travel costs are subject to retail sales tax when they are provided in connection with a taxable digital automated service. The reasoning matters more than the dollars.

What the taxpayer sold, and what it argued

The taxpayer was a software provider offering cloud-based solutions to state and local governments — a platform for public-facing interactions like permitting and licensing, plus a payment-processing application. Because those applications are transferred electronically and use software to perform tasks for the customer, the Department classified the core offering as a "digital automated service," or DAS, under RCW 82.04.192. That classification was not the fight.

The fight was over two line items the taxpayer wanted to treat as non-taxable. First, "Time and Materials" charges for implementing the platform — the professional labor of configuring and standing up the software for each government client. Second, "Time and Expense" charges: reimbursements for airfare, lodging, and similar out-of-pocket costs the taxpayer incurred while doing that implementation work. The taxpayer's theory was familiar and, on its face, reasonable. Implementation is human labor. Washington law excludes "customization of prewritten computer software" from the taxable base. Travel reimbursements are just pass-through costs the taxpayer already paid tax on. Three separate arguments, all pointing the same direction: only the software subscription should be taxed, not the services around it.

The Department rejected all three.

Why the customization exclusion did not save the labor

Washington does exclude customization of prewritten software from tax. But the ARHD found the implementation work here was not sold as a standalone service — it was provided exclusively in connection with the digital automated service. The customer could not buy the implementation without buying the DAS. Because the labor existed only to deliver the taxable digital product, it was treated as part of that taxable transaction, not as an independent, excludable service.

Notice what the Department did not do. It did not run a classic true-object test weighing whether the customer "really wanted" software or services. It asked a narrower, more mechanical question: were these services offered independently, or only as an adjunct to the taxable DAS? When the answer is "only as an adjunct," the exclusion for standalone customization never engages. That is a meaningfully lower bar for the state than a true-object inquiry, and a meaningfully harder one for the taxpayer to clear.

Why travel reimbursements were taxable too

The travel-cost holding is the one that surprises people. The ARHD relied on Washington's definition of "sales price," which includes all consideration received by the seller with no deduction for the seller's own costs of doing business — even costs on which the seller already paid tax. Airfare and lodging that the taxpayer bought, paid sales tax on, and then billed through to the government client were still part of the taxable sales price of the DAS. There is no "we already paid tax on this" carve-out. Consideration is consideration.

Why this lands on AI agent operators

If you operate an AI agent, an agentic workflow, or any autonomous software service, the structure in this determination is your structure. Very few agent products are sold as pure, self-serve API access. There is onboarding. There is integration work. There is a solutions engineer who configures the agent for the customer's systems, and sometimes travels to do it. Operators routinely assume that this wrapper of human labor is non-taxable professional services, taxed — if at all — under different rules than the software itself.

Washington just said: not if the labor exists only to deliver the taxable digital service. The "we mostly sell services, the software is incidental" framing does not survive when the services are not sold independently of the software. And the removal of the "human effort" exclusion from the DAS definition under ESSB 5814, effective October 1, 2025, closed one of the last doors an agent operator might have used to argue that a human-mediated service escapes DAS classification entirely.

Three concrete implications:

Bundled onboarding is presumptively taxable. If your implementation, integration, or professional-services fees are only available to customers who buy the agent product, expect Washington to treat them as part of the taxable DAS sale. Pricing them as a separate SKU on the invoice does not change the analysis if they cannot be purchased separately in substance.

Pass-through costs are not deductible from the base. Travel, third-party fees, and reimbursed expenses billed to the customer are part of the sales price. Build that into your tax calculation, not around it.

Separately-offered services need to be genuinely separate. If you want implementation labor to qualify for the customization exclusion, it has to be a real, standalone offering — available for purchase, priced, and sold on its own to customers who are not buying the DAS. A line item is not a separate service; an independently sellable product is.

The broader pattern

This is a published determination, not a court decision, and Washington Tax Determinations reflect the Department's interpretation rather than binding precedent. But the direction is unmistakable and it rhymes with what we are seeing elsewhere — Utah's seller-hosted software rule, Vermont taxing prewritten software "however accessed," California's SB 122. States are steadily narrowing the paths by which a software-plus-services offering can be recharacterized as mostly-services and taxed lightly or not at all. Washington's contribution is to attack the recharacterization at the bundling seam: the question is not what the customer wanted, but whether the services could have been bought without the taxable product.

For AI agent operators, the compliance move is to know, per state, whether your onboarding and integration labor rides along with a taxable digital service — and to compute tax on the full consideration when it does.

See how AgentTax resolves per-state digital-service and bundling treatment for AI agents so the Washington answer — and the other forty-something — is computed on the full transaction, not guessed at line by line.

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