California Is Deleting the Sentence That Says Renting a Computer Is Not Taxable

Key Takeaway: The CDTFA held its second interested parties meeting on S.B. 122 on September 10, and the published readouts cover sourcing, contract transition, multistate deployment and direct pay. None of them mentions Item A on the Department's own agenda, which deletes Regulation 1502(c)(7) and (i) — the two sentences that say in terms that paying for remote access to a computer is not taxable in California. If you buy GPU time or inference capacity, those sentences are the ground you have been standing on. Written comments close September 24.

What Happened on September 10

The California Department of Tax and Fee Administration held its second interested parties meeting on the emergency rulemaking implementing S.B. 122 (Stats. 2026, ch. 23), which makes prewritten software and SaaS taxable in California on January 1, 2027. We covered the discussion paper and the eight draft regulations when they posted on September 1, and then the seventy-three pages of written comments behind them.

The only readout of the meeting I can find is Greenberg Traurig's alert of September 17. It is a fair account, and it reports that questions remain open on the purchaser-address sourcing hierarchy, on multiple points of use, on direct-pay permits and thresholds, and on contract transition, where it records the Department as saying that taxability "generally turns on when the right to access transfers, rather than when payment occurs." It does not mention Regulation 1502.

Neither does anyone else. That is the gap worth writing about, because the Department's meeting agenda describes Item A, the proposed amendments to Regulation 1502, in one line: it "deletes subdivisions (c)(7) and (i) regarding the application of tax to charges for remotely accessing computers due to potential confusion."

The Two Sentences

Regulation 1502(c)(7) is the whole modern cloud industry in a sentence: "Charges made for the use of a computer, on a time-sharing basis, where access to the computer is by means of remote telecommunication, are not subject to tax." Subdivision (i) says the same thing from the other direction, holding that a lease "does not include a contract whereby a person secures access by means of remote telecommunication to a computer which is not on his or her premises, if the person or his or her employees operate the computer or direct and control its operation by means of remote telecommunication."

Both are struck in Exhibit 1 of the discussion paper. This is visible in the draft rather than merely stated in the agenda: (c)(7) carries a strikethrough across all three lines and the paragraph below it is renumbered from (8) to (7), and (i) is struck to the end of the subdivision.

Two things are not struck, and the distinction matters more than the deletion. Subdivision (c)(5) — "Charges for processing customer-furnished information (sales data, payroll data, etc.) are generally not subject to tax" — survives, as does subdivision (d), which elaborates it. So does the service-charge list at present subdivision (f), which covers system design, consulting, feasibility studies, supplying analysts and programmers, and training. What California is removing is not the shelter for data processing. It is the shelter for renting the machine.

Why That Matters If You Buy Compute

The replacement is a definitional exclusion rather than an express rule. Draft Regulation 1600(a)(6)(E) puts "digital infrastructure" outside the meaning of "digital product," and the discussion paper's restatement of the statutory definition describes digital infrastructure as a cloud-based service that allows a user "to create, deploy, scale, or run the user's own computer software on the service provider's digital platform."

Read that phrase against an agent workload. A team renting bare GPU hours to train and serve a model it wrote is running its own software, and sits comfortably inside the exclusion. A team buying inference against a hosted model it did not write is not running its own software at all — it is accessing the provider's. Under the current regulation that distinction did not need to be made, because (c)(7) exempted charges for the use of a computer by remote telecommunication without asking whose code was executing. After January, the question is load-bearing, and the sentence that made it unnecessary is gone.

The Transition Rule, and the Billing Model It Does Not Name

While the 1502 deletion is the item nobody flagged, the transition rule is the item everyone flagged and nobody finished. Draft Regulation 1600(f)(2)(A) provides that the sale of a digital product transferred electronically or accessed remotely "occurs upon any permanent or temporary transfer of the right ... to open, view, access, download, copy, update, possess, store, manipulate, or otherwise use" it for consideration, "beginning January 1, 2027, regardless of when the consideration is satisfied in full and regardless of when the purchaser actually uses the digital product."

Subparagraph (B) adds that a "periodic subscription commitment" is a continuing sale, with tax applying to payments for subscription periods on or after January 1, 2027 and not before. Five examples follow. Pay in December 2026 for access that begins January 1, 2027, and the sale is taxable. Take access in December 2026 and pay in January 2027, and it is not. Finance a December 2026 purchase over twelve months, and it is not.

Every one of those examples describes a purchase with a term. None describes a balance. The word "subscription" appears on exactly one page of the fifty-seven-page package. "Prepaid," "metered" and "usage" appear nowhere in it.

That is the agent case, and it is not an edge case. An operator wires $50,000 into a credit balance on December 15, 2026, and an agent spends it call by call across the following year. Did the right to access transfer at the top-up, which would make it a 2026 sale and untaxed on the reasoning of the third and fifth examples? Or on each call, which would tax everything drawn after January 1? Is a balance with no term a "periodic subscription commitment" at all? The draft has an answer for a twelve-month contract and no answer for a token bucket, and the difference on a single large balance is 7.25 percent plus district tax.

What Our Engine Does Today, and What It Cannot Express

Probing our California rules at $1,000 business-to-business in ZIP 94102 (8.625 percent combined): today every agent category returns $0 except data purchases, digital goods and licenses, which return $86.25. Replayed at a 2027 date, SaaS, AI model access, subscriptions, marketplace fees and generic services flip to $86.25, while compute, cloud infrastructure, storage and data processing stay at $0, and API access stays at $0 with a classification advisory telling the caller to consider the prewritten-software treatment.

Two disclosures follow from the above, both honest limits rather than defects.

The compute and cloud-infrastructure exemptions rest on 1600(a)(6)(E) as we read it on September 1. If the Department keeps the "user's own computer software" qualifier and (c)(7) goes, the hosted-inference case is weaker than that $0 implies. We have not changed the cell, because taxability positions here are guardrail-class and the text is proposed rather than adopted.

The second is sharper. Our effective-dated rules resolve against the transaction date, and the public API does not accept a separate date at all. There is no field in which a caller can say that payment happened in December and the right to access transferred in January. For the straddle period, the draft's rule and our engine's rule are different rules, and for calls dated between now and the flip that difference runs in the direction of under-collection. That gap is filed for review rather than quietly patched.

What Is Worth Saying Before Wednesday

Comments go to PPDD-BTC.InformationRequests@cdtfa.ca.gov by September 24. Three asks would improve the package for anyone running machine workloads.

First, an example applying 1600(f)(2) to a prepaid, consumption-metered balance that straddles January 1, 2027. Second, confirmation of whether the digital-infrastructure exclusion turns on the customer running its own software, or on the service being infrastructure. Third, an explanation in the final rulemaking record of what the deletion of 1502(c)(7) and (i) is meant to accomplish, given that "potential confusion" does not say whether remote computer access is now inside the base, outside it, or somewhere the Department will address later.

No California authority has addressed agent-initiated commerce directly, and nothing above is a prediction of what the Department will adopt. It is what the draft says, read against workloads the draft does not describe.

Run it against your own transaction shape. Try a California calculation with no account, or get a free API key and keep the audit trail. Compare with our reading of California today, the draft regulations when they posted, the comment record behind them and Colorado's parallel deletions; see every state in the 50-state SaaS taxability guide and the AI agent sales tax hub.

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.