An owner in one state hears from a colleague in another state that security services aren’t taxed, relaxes, and never checks whether that’s true where they actually operate. Then a state auditor shows up two years later asking why sales tax was never collected on a service that, in that particular state, was taxable the whole time. This is not a hypothetical anxiety — it’s the exact trap that sales tax on services sets, because unlike income tax, which follows fairly consistent federal logic, sales tax on services is decided state by state, and the states do not agree with each other.
Are security guard services taxable? It depends entirely on which state you’re in
Most states that tax retail sales of physical goods do not extend that tax to most services, including security guard services — services have historically been taxed less broadly than goods in general sales tax law. But a meaningful number of states carve out specific services, including security services, and tax them anyway. Texas is a confirmed example: the Texas Comptroller’s own guidance states plainly that security services are subject to sales tax in Texas, with narrow exceptions for specific circumstances. That means a guard company billing a client in Texas has a sales tax obligation on that billing that a guard company billing a client in a neighboring state that doesn’t tax services simply does not have.
This is the trap in the framing of “are security guard services taxable” as if it had one national answer. It doesn’t. It’s a state-by-state determination, and the fact that Texas taxes it tells you nothing reliable about California, or Ohio, or wherever you actually operate — those states may tax it, may not, or may tax some categories of guard work (armed, unarmed, patrol, investigative) differently from others. Assuming your state follows a neighbor’s rule, in either direction, is how companies end up either overcharging clients for years or under-collecting a tax liability they were never told they owed.
Why this matters more than it looks like it should
For a services business, sales tax isn’t paid out of margin the way it often functions for a retailer selling goods — it’s supposed to be collected from the client and passed through. That only works if it’s on the invoice from the start. A company that discovers, mid-contract or after an audit, that it should have been charging tax all along faces an ugly choice: absorb the liability itself, or go back to a client and ask for retroactive payment on services already rendered, which is a conversation no account manager wants to have with a property manager who thought the bill rate was final.
The reverse mistake is just as costly in a different way — charging sales tax in a state that doesn’t require it on security services makes your bid look more expensive than a competitor’s for identical coverage, for no reason other than an administrative error nobody caught. Neither direction is a small clerical detail. Both change what a client actually pays, and both are avoidable with a five-minute check that most owners never make because the question of “are security guard services taxable” feels like it should have a simple, universal answer.
Where to actually get the answer, and what not to trust
The only reliable source is your own state’s department of revenue or equivalent tax authority — not a forum post, not a competitor’s invoice format, not what worked in the state where you used to operate. Some state revenue agencies publish specific guidance for security services the way Texas does; others require a direct inquiry because the taxability of a given service isn’t spelled out clearly in general sales tax statute. If you operate across multiple states, this is not a one-time lookup — it’s a state-by-state file you maintain and revisit whenever you sign a contract in a state you haven’t billed in before, because the same company can be taxable in one state and exempt in the next for the identical scope of work.
There’s a second layer to this that catches companies operating across state lines: a single company can owe sales tax on some of its contracts and not others, in the same month, depending purely on where each site sits. A mobile patrol contract that covers properties in two neighboring states isn’t one tax answer — it’s two, evaluated separately, and a company that assumes its whole book of business follows one rule because most of its revenue comes from one state is exactly the company that misses the exception sitting in a smaller contract three states over. This is also where the type of security work can matter within a single state’s rules — some states that tax guard services broadly still carve out narrower exceptions for specific categories of work, such as investigative services billed separately from guard coverage, and the only way to know which category your specific contract falls into is to ask the state directly rather than infer it from how a similar-sounding service was treated somewhere else.
This also isn’t a question your invoicing software can answer for you. Software can apply a tax rate consistently once you tell it what that rate should be for a given jurisdiction, and it can help you separate billing by site and by contract so a state-specific rate doesn’t get applied everywhere by mistake. But the determination of whether the service itself is taxable in that state has to come from the state, confirmed before the first invoice goes out under a new contract, not discovered afterward.
Building this into how you price and bid
Once you know a state’s answer, the practical fix is straightforward: build the tax treatment into your bill rate and quoting process for that state from the first proposal, not as a line item you add later. A client evaluating a bid wants to see the real total they’ll pay, and a bid that quietly omits an applicable tax will look artificially cheap right up until the first invoice corrects it — which is a worse first impression than pricing it correctly from the start. If you’re bidding across several states with a mix of taxable and non-taxable treatment, keep that distinction documented per contract so it doesn’t get lost when a new hire takes over billing.
None of this is tax advice, and it shouldn’t be treated as a substitute for a conversation with your state’s revenue agency or your own accountant — the rules genuinely vary, they change, and a guard company operating in several states needs a state-by-state answer rather than a single company-wide assumption. What you can control is not guessing. Confirm the treatment for every state you invoice in, document it, and build it into pricing before the contract starts, not after an audit finds it.
If you want a clearer picture of what a properly built-out bill rate and billing process actually looks like across a growing multi-state operation, explore CGuardPro’s guard payroll and billing tools or get in touch.