Are Managed IT Services Taxable? What Washington and Texas Say, and How to Check Last Quarter’s Invoices

Where a Washington sale happens, and when an out-of-state firm collects

Sourcing decides which location’s rate applies, and whether Washington’s tax applies at all. The interim guidance says IT services are taxed “based on the location where the services are received by the purchaser,” and sets a fallback order: the seller’s place of business if the client receives the service there; otherwise where the client receives it, if the seller knows; otherwise the client’s address in the seller’s records; otherwise an address obtained at the sale; and last, where the seller provided the service.

When a client receives services at several known locations, the department accepts allocation by the amount received at each or an equal split, or a reasonable and consistent method the client provides by the time of the invoice. One of the department’s worked examples reads like a managed services contract: a monthly fee for network support allocated across offices by headcount, and help desk tickets billed per ticket and sourced to the office of the employee who asked for help. Another warns that sourcing every monthly fee to an out-of-state address while users sit in Washington offices may be treated as bad faith. The guidance also says providers “should document in their contracts, invoices, or service agreements where they will be sourcing the services.”

A firm with no office in Washington is not automatically outside this. The guidance says a provider without physical presence may still need to collect and remit once it exceeds the economic nexus threshold of $100,000 in combined gross receipts sourced or attributed to Washington.

On bundling, the guidance says an IT service and a differently taxed service sold for one non-itemized price would generally be subject to retail sales tax as a bundle unless an exception applies, while separately itemized products can generally be treated by their own classification. A firm that bills one flat number per user should read that sentence with its CPA.

What the Texas text says about data processing services

Texas works from a list. The Comptroller’s publication 96-259, revised January 2026, names sixteen taxable services under Tax Code Section 151.0101. Data processing services is one of them; personal property maintenance, remodeling or repair services and security services are others. Which of those, if any, describes a given line on a managed services invoice is a classification question for the firm’s CPA.

The Comptroller’s rule, 34 Texas Administrative Code §3.330, defines a data processing service as “the computerized entry, retrieval, search, compilation, manipulation, or storage of data or information.” The publication’s examples include web hosting, website creation and maintenance, data storage including offsite backup, and conversion of data from one medium to another. It also draws a boundary: “Merely using a computer as a tool to help perform a professional service is not a data processing service.”

Then the arithmetic. Tax Code §151.351 reads in full: “There is exempted from the taxes imposed by this chapter 20 percent of the value of information services and data processing services.” Twenty percent of the charge is exempt and the tax applies to the rest, with one condition in the rule: “If the data processing service is also taxable as another type of taxable service other than an information service, the twenty percent exemption does not apply.”

Texas has a bundling rule as well. Under §3.330, where nontaxable related services and taxable services are sold for a single charge and the taxable portion represents more than 5.0% of the total, “the total charge is presumed to be taxable.” The rule lets the seller overcome that presumption by separately stating a reasonable charge for the taxable services to the customer at the time of the sale.

Why sales tax on managed IT services becomes a billing leak

Sales tax on managed IT services is a field on an invoice, and invoices are built from settings someone chose once. Wherever the PSA keeps the tax setting, on the client record, the site or each product line, it was set at onboarding, and the agreement template decides which lines are itemized. A firm that configured those fields before Oct. 1, 2025, for clients that all sat in an untaxed state at the time, has had no prompt to change them since.

Three things move a client into a taxing state without anyone touching billing: a law changes on a date, as Washington’s did; the client opens an office or hires remote staff in another state; or the firm signs a client headquartered in one state with users in another. In each case the service desk notices first, because the tickets change. The invoice does not, because no ticket edits a tax code. It is the same shape as seat drift on an agreement: the service moves through the technical side on its own, and billing moves only when a person edits a record.

Illustrative example: a client with a Washington office pays a flat $3,000 a month for managed services, invoiced with no tax line since the agreement began. Assume, for round numbers only, a combined rate of 10 percent at that office. Twelve months later the amount never collected is $3,600. Raising it after the fact is a harder conversation than adding it to the first invoice would have been. Whether tax was due on that agreement, and what to do about past periods, is the CPA’s answer, not the account manager’s.

The count: one quarter of invoices, by where clients receive service

The check needs no software and no tax knowledge: one quarter of invoices and a list of where each client’s users sit.

• Export last quarter’s invoices with client, bill-to address, service locations, each line item and any tax line.
• Next to each client, list every state where its users or offices receive support, from the PSA sites, the RMM device locations or the onboarding records. A headquarters address alone is not enough; the Washington guidance sources by where the service is received.
• Flag every client with users or offices in Washington or Texas, and in any other state the CPA names.
• For each flagged client, note whether any tax was charged, on which lines, at which location’s rate, and whether the managed services fee is one number or itemized.
• Mark the agreements signed before Oct. 1, 2025 that serve Washington users; those were built under the old rule.
• For a firm based outside Washington, total the year’s Washington-sourced receipts against the $100,000 economic nexus threshold the guidance names.

Three columns come out of it: the amount invoiced to clients in flagged states, the tax charged, and the difference. Zero is a good answer. A non-zero column is not a finding of tax owed; it is the list of invoices to put in front of a CPA, which is easier to do this quarter than after a notice arrives.

Questions to take to the CPA

None of these has one answer for every firm, which is why each goes to the CPA with the table from the count.

• In which of the states where our clients receive services are IT services, managed services, data processing or repair taxable, and which category does each of our invoice lines fall under?
• Do our Washington-served agreements signed before Oct. 1, 2025 carry tax from that date, and how should past invoices be handled?
• Have we crossed Washington’s economic nexus threshold, and do we need to register there?
• Should our flat monthly fee be itemized, given the Washington and Texas bundling rules?
• The Washington guidance has sections on non-profits and on state and local governments. Which of our clients do they touch, and what do we keep on file for them?

Rules change: Washington’s did in 2025, and the Texas data processing rule was amended effective April 2, 2025. A list of taxing states goes stale, which is why this guide quotes two texts and stops.

When not to hire anyone for this, and where the Review fits

If every client and every user the firm supports sits in a state the CPA has confirmed does not tax these services, there is nothing to count, and a consultant adds nothing. If the question is registration, voluntary disclosure or a notice from a state, that is work for a CPA or tax attorney from the first day, and it should not wait for an operations review.

Where the Revenue Review touches sales tax, it does so as a flag inside the Delivery → Invoice hand-off. While reading invoices, it notes which clients receive service in states the firm’s CPA has named and whether those invoices carry tax, and it hands that list to the owner and the CPA. It gives no tax opinion. The rest of the Review counts the other places money slips between the ticket and the invoice: seats that drifted, time never logged or never invoiced, invoices aging past terms. It takes two weeks, works read-only from the firm’s own exports, and ends in a written report the firm keeps.

The next step is a free 20-minute call, where we say whether the Review is worth the fee for this firm, or whether the table above and an hour with the CPA settle it.