Is dock installation taxable? Sales tax on lake work
It depends on your state — install, removal and repair can each get a different answer. Here are the traps that catch lake-country operators: stacked jurisdictions, the lake that touches two counties, and why the rate has to lock to the job forever.
· 6 min read
Is dock installation taxable? The honest answer is: it depends on your state, and sometimes on your county, and the difference is real money. In some states, installing a dock is a taxable service like any other labor. In others it counts as an improvement to real property and is exempt. Repairs are often treated differently from installs in the same state, and removal can be different again.
So the first move isn’t software — it’s a conversation with your accountant, or an hour with your state revenue department’s guidance for contractors. What this piece covers is the part after that conversation: the handful of traps that catch lake-country operators specifically, and how to set the answer up once so every job from then on charges, records and reports the right tax without anyone doing arithmetic in a truck.
The question your accountant will actually ask
“Are you performing a taxable service, or improving real property?” That one distinction drives most states’ answers. A dock that stays seasonally and comes out every fall looks like a service arrangement; a permanent pier can look like construction. Some states tax the labor, some tax only materials, some tax neither, and a few tax repairs but not new installation. Get the ruling for each service you offer — install, removal, repair — not one ruling for the company. They can genuinely differ.
This is also why LakeOps never decides what’s taxable. You mark which of your services carry tax, and every service starts unmarked — off isn’t an opinion about your state’s law, it’s software declining to have one. A confident wrong answer about tax would be worse than no answer.
A lake is where jurisdictions pile up
The rate on a job is almost never one number. It’s a stack — state plus county plus maybe a city or a special district — and a working lake routinely touches two counties. The same service, performed from the same barge on the same afternoon, can owe a different stack on the north shore than on the south. Whoever does your books needs each layer separately, because each one is filed on its own return.
That’s the trap in entering one combined figure. “7.375%” can’t be split back into 4% plus 2.375% plus 1% after the fact — the sum doesn’t tell you the parts, and the parts are what you file. In LakeOps, each taxing authority gets its own rate, with its own registration number, and the authorities that tax one area are grouped and matched to properties by postal code. The whole stack applies, and every layer stays reportable on its own.
Postal codes have their own edge case: some straddle a county line. For those properties — your accountant will know where they are — the group is set directly on the property, and that choice wins outright. No lookup second-guesses a decision a person made about a boundary.
The rate must lock to the job, forever
Here’s the trap that surfaces a year later. Rates change — a county adds a quarter percent, a transit district appears — and a customer calls in September asking about the tax on a job from March. If your system reruns today’s rates over old work, you have no answer, and worse, your filed returns quietly stop matching your records.
So in LakeOps, tax is worked out the moment a job closes and every component rate is stamped onto it, permanently. Change a rate next season and finished work is untouched. “Why was I charged that in March” is answered by opening the job — not by reconstructing what the rate used to be.
When there’s no answer, an unpriced job beats a guess
One behavior worth understanding before it surprises you: a taxable job at a property whose postal code no group covers finishes without a price, rather than being taxed at zero. Taxing at zero would be the software quietly ruling the work exempt. An unpriced job is visible and fixable in an afternoon — add the missing group, price it again — where tax you failed to collect gets discovered by an auditor two years later, with interest. The tax settings page flags postal codes on your properties that nothing covers, so you can close those gaps before a crew finishes a job inside one.
What filing season needs from you
When returns come due, the sales tax report groups by authority — never by how you happened to configure groups — and shows tax charged and tax collected side by side, because states differ on which basis you file. It also lists what it excluded: completed work that carried no tax because the service wasn’t marked taxable. That’s the first thing an accountant asks about a return, and the answer is already written down. The whole thing exports to CSV for whoever files.
One small thing so it never worries you: each authority’s tax is rounded on its own, because each line is filed on its own and has to be exact. On a small job the components can add to a cent either side of what the combined rate would give. That’s the correct answer, not a rounding bug.
Do the homework once
Sales tax on lake work is a genuinely local question, and there’s no way around the hour it takes to get your state’s answer. But it’s one hour, once — get the ruling per service, enter each authority’s rate on its own, mark the services that carry tax, and from then on every job prices itself with the right stack, locks it, and files clean. The alternative is doing that arithmetic by hand, per job, all season, and hoping the September phone call never comes.