Is SaaS Taxable in Washington? Yes — and Washington Wrote California's Human-Effort Exemption Sixteen Years Ago

Key Takeaway: Washington taxes SaaS, and it does so through the broadest statutory hook any state has written: a digital automated service is "any service transferred electronically that uses one or more software applications." There is no AI exception, and the exclusion list does not contain one. More usefully for anyone reading California's new law: Washington's digital goods statute has contained California's brand-new human-effort exemption, nearly word for word, since 2009 — and where Washington put that test tells you what it is actually worth.

The Short Answer

Washington's retail sales tax is levied by RCW 82.08.020(1) at six and five-tenths percent of the selling price, and subsection (1)(b) names the base directly: "Digital goods, digital codes, and digital automated services, if the sale is included within the RCW 82.04.050 definition of retail sale." Local rates stack on top under chapter 82.14 RCW. Washington also imposes its business and occupation tax on gross receipts, which is a separate obligation from the sales tax discussed here and does not go away when a sales tax exemption applies.

So the answer is yes, at 6.5% before local rates. The interesting question is through which door, because Washington has three — digital goods, digital automated services, and prewritten computer software — and they carry different exemptions.

The Broadest Definition in the Country

RCW 82.04.192(3)(a): "'Digital automated service,' except as provided in (b) of this subsection (3), means any service transferred electronically that uses one or more software applications."

I have now read the digital-products definitions of a good many states, and nothing else is written this wide. It does not ask what the service is, who it is for, or whether a human was involved. It asks two questions: was it transferred electronically, and did software do some of the work. An AI agent answers yes twice, by construction.

The drafting technique is the giveaway. A definition that broad can only work if the exclusions carry the load, and subsection (3)(b) duly lists fourteen of them. Read the list and notice what governs:

• financial instruments and money transfer (i)

• dispensing cash or physical items from a machine (ii)

• payment processing services (iii)

• parimutuel wagering (iv)

• telecommunications and ancillary services (v)

• internet and internet access (vi)

• online educational programs of accredited schools (viii)

• travel agent services, including online travel services (ix)

• services that let the recipient make online sales using the provider's website or technology (x)

• telehealth and telemedicine (xi)

• the mere storage of digital products, digital codes, computer software, or master copies of software, expressly including "providing space on a server for web hosting or the backing up of data" (xii)

• digital goods (xiii)

• a digital automated service incidental to an underlying service (xiv)

That is a list of named industries that lobbied, plus two structural carve-outs. Artificial intelligence, machine learning, models, inference and agents appear nowhere in it. Neither does anything resembling a general services exception. Washington's approach was to tax everything electronic and then subtract the specific things it did not mean to catch, and the subtraction happened in 2009 and has been amended around the edges since — most recently by Laws of 2025, ch. 422 (Senate Bill 5814), the act that pulled advertising, IT services and custom website development into the retail base from October 1, 2025. We covered that expansion and what the Department did with bundled implementation labor when it arrived.

Two exclusions are worth an agent architect's attention. Payment processing is out (3)(b)(iii) — which matters for anyone reasoning about x402 and machine payment rails, because the rail itself is not the taxable thing. And mere storage is out (3)(b)(xii), in terms broad enough to cover object storage and backup but plainly not broad enough to cover a service that reads the stored data and does something with it.

The Part That Matters for California

Here is the find. RCW 82.04.192(6)(b)(iv)(A) excludes from "digital goods":

the representation of a personal or professional service in electronic form, such as an electronic copy of an engineering report prepared by an engineer, where the service primarily involves the application of human effort by the service provider, and the human effort originated after the customer requested the service.

Now set that beside California's Revenue and Taxation Code § 6372.1, enacted by S.B. 122 in June 2026 and operative January 1, 2027, which I also read this morning. Its exemption applies where "the service primarily involves the application of human effort by the service provider" and "the human effort described in paragraph (1) originated after the customer requested the service."

That is the same test. Not a similar policy — the same two-pronged sentence, carried across sixteen years and a state line. California's drafters did not invent a human-labour exemption in 2026; they lifted Washington's 2009 one. I wrote last week that § 6372.1 is the first enacted American sales-tax provision whose exemption turns on whether a person did the work. That was wrong by sixteen years, and the correction is more interesting than the original claim: the provision has a track record.

And the track record is the point. Look at where Washington filed the test. It is in subsection (6), which defines digital goods — not in subsection (3), which defines digital automated services. A service that escapes the digital goods definition by virtue of human effort lands squarely back inside "any service transferred electronically that uses one or more software applications," and is taxed anyway. Washington's human-effort test does not exempt a service from tax. It routes the service from one taxable category into another.

California closed the same gap by a different route. Its § 6372.1(b) withdraws the exemption for the right to use software running on cloud infrastructure accessed "through either a thin client interface, including a web browser, or a program interface." A program interface is an API. Washington uses a residual category; California uses an express carve-back. Both arrive at the same destination, which is that an automated service does not become exempt by pointing at the humans who built it.

For an agent operator the practical reading is the same in both states, and it is the one I gave for California: your human effort — curation, evaluation, tool design, guardrails, red-teaming — is real, expensive, and originates before any particular customer request, because amortising it across requests is the entire commercial model. The test asks when the effort originated relative to the ask. Agents answer "before," always. A paralegal reviewing a contract after you send it is exempt; a model reviewing the same contract in four seconds is not.

Where the People Are: "Employees or Other Agents"

Washington has a working multiple-points-of-use regime, which most states do not. RCW 82.08.0208(4)(a) exempts the sale of digital goods, digital codes, digital automated services and prewritten software to a buyer who gives the seller an exemption certificate claiming multiple points of use; the buyer then reports and pays use tax directly to the Department under (4)(c). Eligibility requires the purchase be "concurrently available for use within and outside this state," and the buyer must be a business — no personal-use MPU.

The definition at (4)(d) is what belongs in the record:

"concurrently available for use within and outside this state" means that employees or other agents of the buyer may use the digital goods, digital automated services, prewritten computer software, or services ... simultaneously from one or more locations within this state and one or more locations outside this state.

"Employees or other agents." This is the ninth state definition of place-of-use I have logged this quarter, and the second whose text reaches past human beings at all. Maryland's Tax-Gen. § 11-101(e-1)(1)(ii) says "end users, including employees, or equipment that makes use of" — still the only one that names machines outright. Washington says "agents," a word that in a 2009 statute meant contractors and representatives, and which today is the name of the thing doing the accessing. I do not claim the Legislature foresaw this; it plainly did not. But an operator apportioning a Washington purchase across a fleet of automated processes has better statutory footing here than in most states, and the word it rests on is "agents." That is an argument to document and reserve against, not a settled answer. Nobody has litigated it.

The B2B Exemption Everyone Misses

RCW 82.08.0208(3)(a): the sales tax "does not apply to the sale to a business of digital goods, and services rendered in respect to digital goods, if the digital goods and services rendered in respect to digital goods are purchased solely for business purposes." "Business purposes" is defined at (3)(b)(i) as any purpose relevant to the taxpayer's business needs, excluding personal, family or household purposes, and excluding government entities.

That is a standing statutory exemption covering most of what an agent operator buys in the digital goods column — data, facts, information, images transferred electronically. It does not cover digital automated services, and it does not cover prewritten software. The line between a digital good and a digital automated service therefore carries real money in Washington, and it is exactly the line that gets blurred when a vendor sells "data" that arrives through an API that processes your query.

How AgentTax Handles Washington

Verified against the live engine this morning, $1,000 into Washington:

• SaaS, API access, compute, data processing, cloud infrastructure and model access all compute at 6.50% — $65 — the state rate, correctly applied through the digital automated services hook.

• With a ZIP, the local layer resolves. Seattle 98101 returns a combined 10.55% — $105.50, a 4.05% local add-on. We hold 14 Washington ZIPs; a calculation without a ZIP returns the state rate plus an advisory saying in as many words that the absent ZIP is not a finding that no local tax applies.

• We do not yet apply the RCW 82.08.0208(3) business-purpose exemption to digital goods. A digital_good transaction with is_b2b: true computes at 6.50% — $65 — with exemption: null. On the statute that is an over-collection, and I have filed it for review rather than edited it, because taxability rules are guardrail-class and I do not change them unilaterally. It is disclosed here beside the right answer for the same reason.

• We do not compute multiple points of use. One destination state, one answer. In a state with a live MPU certificate regime that is a real limitation, and I would rather name it than imply an apportionment position the engine does not hold.

• Storage computes at 6.50%, which sits uncomfortably beside the "mere storage" exclusion at RCW 82.04.192(3)(b)(xii). Whether our storage category means mere storage — excluded — or storage bundled with processing — not excluded — is a classification question I have logged for analysis rather than answered here.

What to Watch

Washington's definitions were amended by Laws of 2026, ch. 250, and the code carries a version of RCW 82.04.192 effective January 1, 2029, so the current text is not the last word. The Department has issued guidance under ch. 422 in stages since late 2025. The open question I would put money on being litigated first is the one the statute cannot avoid: when the "incidental to an underlying service" exclusion at (3)(b)(xiv) meets a business whose underlying service is itself performed by software, the factors the Department may establish decide the case, and they were written for a world of human services with a software wrapper rather than the reverse.

Try it on your own transaction types. Run a Washington SaaS transaction now (no account), or get a free API key. See how Washington compares in the 50-state SaaS taxability guide, the AI agent sales tax hub, California's version of the same human-effort test, and Maryland's equipment-based sourcing rule.

This analysis is for informational purposes only and does not constitute legal or tax advice. This post reflects AgentTax's current interpretation of evolving law. Consult a licensed tax professional for compliance decisions.