Guest & Occupancy Tax
Scaling Your Portfolio
Occupancy Tax Gaps Are Quietly Draining Your Owner Statements
If you run a single cabin in one county and never touch another jurisdiction, most of this won't apply. For everyone else, read on.
Occupancy-tax rules are fragmented by design. A single reservation can trigger tax obligations at the state level, the county level, the municipal level, and sometimes a special district level - all at different rates, with different remittance schedules, and different rules about who collects what.
When those layers don't reconcile cleanly on an owner statement, you end up with gaps: money collected that isn't accounted for, liabilities that never hit the books, or remittances that appear correct on the surface but are wrong when you check the underlying rates.
Those gaps are a liability for the operator, a source of confusion for owners, and a compliance risk that compounds over time.
How occupancy taxes are structured (and why that creates gaps)
Most U.S. jurisdictions layer at least two or three taxes on top of each other:
State lodging or sales tax - a baseline rate applied statewide
County tax: sometimes called a transient occupancy tax (TOT) or lodging tax
Municipal or city tax - an additional layer in incorporated areas
Special district levies - tourism improvement districts, convention center funds, and similar assessments
A reservation in a popular beach town might carry a 6% state sales tax, a 2% county TOT, a 3% city lodging tax, and a 1.5% tourism district surcharge - a combined 12.5% that has to be broken out, tracked, and remitted to four different authorities on four different schedules.
On top of that, large OTAs collect and remit some of these taxes directly in jurisdictions where they have marketplace facilitator agreements. But marketplace facilitator laws are not uniform. In some states the OTA covers all layers; in others it covers only the state portion; in a handful of markets it collects nothing and leaves full remittance to the operator. That patchwork is where most statement-level gaps originate.
What a gap looks like on an owner statement
Occupancy-tax gaps on owner statements typically fall into three patterns.
1. Taxes collected but not remitted
The gross reservation includes a tax line. The owner statement shows the tax as a deduction from the payout. But the actual remittance to the taxing authority either hasn't happened, happened at the wrong rate, or covered only one jurisdiction layer when several applied. The owner has already been debited; the liability hasn't been cleared.
2. Taxes missing entirely
A reservation comes through a channel that doesn't collect occupancy tax automatically. The tax isn't added to the reservation total, isn't deducted from the owner payout, and isn't remitted. The owner statement looks clean. The compliance obligation is invisible.
3. Rates applied from the wrong jurisdiction
A property moves from one short-term rental zone to another - a county annexation, a new city ordinance, a change in the property's tax classification - and the old rate keeps getting applied. No one flags it because the statement format hasn't changed, just the number.
Words in Action
Consider a property manager in a coastal Florida county running 12 units across two incorporated cities within the same county. Each city has its own additional lodging tax on top of the state and county layers.
Property A is in City 1. The applicable rate stack is:
Florida state sales tax: 6.0%
County tourist development tax: 5.0%
City 1 resort tax: 1.0%
Total: 12.0%
Property B is in City 2. The rate stack is:
Florida state sales tax: 6.0%
County tourist development tax: 5.0%
City 2 has no additional levy
Total: 11.0%
If the manager's system is set to a flat 11% across all units - perhaps because that's what the template defaulted to when City 2 properties were onboarded first - Property A reservations are being undercharged by 1 percentage point every booking.
On a $2,400 monthly revenue property, that's $24 per month in uncollected tax. Over a 12-month audit window, that's $288 per property. Across four units in City 1, it's $1,152 in cumulative gaps - plus any penalties and interest if the jurisdiction audits the operator.
The owner statements for those four units look perfectly normal. The error is in the rate table, not the statement format.
Common jurisdictional triggers that create new gaps
Gaps aren't just a setup problem. They reopen whenever something changes:
New city or county ordinances - many STR markets have added or increased lodging taxes in the last three years
Marketplace facilitator law changes - a state expands facilitator coverage and the operator keeps manually collecting taxes the OTA now remits, resulting in double collection
Property reclassification - a unit moves from a hosted to an unhosted classification, or crosses a nights-per-year threshold that changes its tax treatment
Cross-state portfolios - adding even one property in a new state introduces an entirely new tax code with different rates, definitions of taxable revenue, and remittance rules
For a deeper look at how these issues flow through your financial reporting, the STR property management accounting guide covers the full accounting lifecycle and how tax obligations connect to owner trust balances.
How gaps reach owner statements undetected
The statement itself is usually downstream of the problem. By the time a gap appears as a line item - or fails to appear when it should - the error has already been baked into the reservation total or the remittance logic. That's why reviewing owner statements at face value isn't enough to catch jurisdiction-level tax gaps.
What you need is a comparison between:
The tax rate that should apply to each property based on its physical address and current ordinances
The rate actually applied in each reservation
The amounts shown as tax deductions on owner statements
The amounts actually remitted to each taxing authority
When those four numbers don't reconcile, you have a gap. Most operators never run this comparison systematically because it requires pulling data from multiple places - reservation records, statement exports, remittance receipts, and current jurisdiction rate tables - and matching them property by property.
This is exactly the kind of multi-source discrepancy that a free owner statement audit is designed to surface. Rather than reviewing your statements manually, an audit flags where collected amounts, deducted amounts, and expected rates diverge across your portfolio.
Fixing gaps once you find them
Corrections fall into two buckets: prospective and retroactive.
Prospective fixes are straightforward. Update the rate table in your property management system, verify the correct rate for each property address, and confirm which tax layers the OTA is collecting on your behalf before adding manual collection on top.
Retroactive corrections are harder. If you've been undercharging guests, you generally can't go back and collect from them. You may owe the taxing authority the difference out of management revenue.
If you've been overcharging and over-remitting, you may be able to file for a refund, but the process varies by jurisdiction. In either case, the owner statement history needs a correcting entry so the records reflect what actually happened.
For properties held in trust under a property management agreement, retroactive tax corrections can also affect trust account balances. The owner trust accounting guide explains how to handle adjustments to owner funds without creating new compliance problems in the process.
Building a jurisdiction-rate audit into your routine
Occupancy tax rates change. Marketplace facilitator agreements change. Properties move between jurisdictions. A one-time fix isn't enough.
A practical cadence:
Quarterly: Pull a rate comparison for every property and verify it matches the current ordinances in each taxing authority
At onboarding: Confirm the full rate stack for every new property before the first reservation is processed
When an OTA notifies you of a policy change: Re-verify which layers they're now covering so you're not double-collecting or missing a layer
When a property crosses a state or city line: Treat it as a new onboarding even if it's just a short distance from an existing unit
You can also explore PX Accounting's features to see how automated cross-property statement auditing compares to manual rate-table reviews.
Next steps
Occupancy-tax gaps are systematic - once a wrong rate is in your setup, it applies to every reservation until someone catches it. The longer it runs, the larger the exposure.
If you haven't done a cross-jurisdiction rate review in the last year, start there. Pull the current rate for every property, compare it to what your system is applying, and check whether your OTA agreements match your remittance records.
If you want a faster path to finding what your current process is missing, submit your owner statements for a free audit and get a clear picture of where your tax lines, payouts, and deductions don't add up.
Frequently Asked Questions
What is an occupancy-tax gap on an owner statement?
An occupancy-tax gap is a discrepancy between the tax that should have been collected and remitted for a reservation and what was actually collected, shown on the statement, or remitted to the taxing authority. Gaps can be caused by incorrect rates, missing jurisdictional layers, or mismatches between OTA collection and operator collection.
Who is responsible when occupancy taxes are underpaid - the OTA or the property manager?
Responsibility depends on the jurisdiction and the terms of the marketplace facilitator agreement. Where an OTA has agreed to collect and remit specific taxes, the operator is generally not liable for those layers. For taxes outside the OTA's agreement, the operator - and sometimes the property owner - remains responsible. Always confirm in writing which layers your booking channels are covering in each market.
How do I find the correct occupancy tax rate for each property I manage?
Start with your state department of revenue for the state layer, then check the county assessor or treasurer's office for county levies, and the city finance department for any municipal tax. Many jurisdictions publish rate tables online, but they are not always current. When in doubt, call the authority directly or ask your CPA to verify before your next remittance cycle.
Can occupancy-tax gaps cause problems beyond back taxes owed?
Yes. Persistent gaps can trigger penalties and interest from taxing authorities. They can also create trust accounting problems if owner payouts were calculated on incorrect net amounts. In some cases, the gap surfaces only during a jurisdiction audit, at which point the lookback period may cover several years of under-remittance.
How far back should I review owner statements for occupancy-tax errors?
Most jurisdictions have a three-year statute of limitations for sales and lodging tax assessments, though some extend to five or six years if they suspect fraud or substantial non-compliance. A 12- to 24-month review is a reasonable starting point for most operators and will catch the majority of systematic rate errors without requiring a full historical reconstruction.
Jessica Hudson, CPA specializes in short-term rental tax, bookkeeping, and financial operations for vacation rental hosts and property managers. She also loves fresh chocolate chip cookies.