Hotel Lodging Tax Compliance: Transient Occupancy Taxes, Tourism Districts, and OTA Marketplace Rules

A single hotel already has to track state, county, city, and sometimes tourism-district occupancy tax on every room night, and the hotel occupancy tax and transient lodging compliance guide covers those foundational rules: what counts as taxable, how the stacking works, filing frequency, penalties, and exemptions. The moment a hotel group grows past one property, or operates across state lines, the compliance problem stops being about one property’s registrations and becomes a portfolio-level exercise: a different assessment structure in each tourism district, a different marketplace facilitator statute in each state, and an OTA reconciliation process running across every property. This article picks up at that scale: tourism improvement districts and convention taxes, how marketplace facilitator laws actually work state by state, and what a real multistate reconciliation calendar looks like.

How does lodging tax compliance scale across a portfolio?

A single hotel’s occupancy tax compliance is fundamentally a registration checklist: identify every state, county, city, and district layer that applies to that one address, register at each one, and file on each one’s schedule. A portfolio of properties across multiple states turns that checklist into a matrix, every property against every jurisdictional layer that applies to it, and the matrix does not simplify just because several properties share a state.

• Two properties in the same state can face entirely different local layers, since a hotel in a county with a tourist development tax and a city hotel tax faces layers a property twenty miles away, outside both boundaries, never has to register for.
• Filing calendars do not align across properties even within the same state, because county and city filing frequency is usually set by that property’s own revenue volume, not by the portfolio’s aggregate size.
• A management company running properties in ten states is effectively running ten separate compliance calendars, registration renewals, and exemption documentation rules, none of which necessarily share terminology or definitions for what counts as a taxable charge.

The practical answer is a centralized jurisdiction map, maintained at the portfolio level rather than reconstructed property by property, that tracks every registration, filing deadline, and rate change across the whole portfolio. Properties that are individually compliant but managed without that central view are the ones where a rate change or a new district assessment gets missed, because no one is watching all of them at once.

How are tourism improvement districts created and assessed?

A tourism improvement district (TID) is a geographically defined area where hotel and lodging properties fund a dedicated assessment, typically for destination marketing, though some fund broader area improvements (streetscaping, security, event programming). Unlike a general municipal hotel tax, which a city council simply enacts, most TIDs are formed through a petition and majority-vote process among the affected property owners, then made mandatory for every property within the boundary once adopted, including properties whose owners voted against formation or opened after the vote.

• The assessment method varies by district: some assess a flat percentage of room revenue (commonly 1% to 2%, on top of the general occupancy tax layers), others a flat per-room, per-night fee, and a few a hybrid formula weighted by room count and average rate.
• Governance typically sits with a nonprofit tourism marketing district corporation, not the city or county’s general revenue department, even though the same agency often collects the assessment alongside the general hotel tax on the same combined return.
• TIDs almost always have a renewal or sunset provision, commonly 5 to 10 years, requiring a new petition and vote to continue, so a portfolio operator needs to track upcoming renewal votes that could change or eliminate an assessment, not just current boundaries and rates.

How are convention center taxes structured and administered?

Convention center taxes are a narrower category than TIDs: a dedicated percentage or flat assessment on hotel rooms within a defined county or city, imposed to finance the construction, expansion, or operation of a convention facility, and administered directly by the city or county finance department rather than a separate marketing district corporation.

• Because convention center taxes frequently back municipal bond debt, they are almost always mandatory rather than subject to periodic reauthorization votes, with the rate set by ordinance rather than by a property-owner petition.
• The tax base typically mirrors the general municipal occupancy tax base (room rate plus mandatory fees), but the registration and return are usually separate, even when both are filed with the same finance office on the same due date.
• Some cities layer a convention center tax on top of an existing TID and a general municipal hotel tax, all three administered by different offices, which is precisely the kind of stacking that makes a property’s effective occupancy tax rate look nothing like the state’s published sales tax rate.

A portfolio operator’s practical task mirrors the TID one: confirm the convention center tax registration is separate from the general municipal registration, confirm its filing calendar independently, and re-verify both on any change of ownership, since some jurisdictions require fresh registration on a change of control even when the property itself does not change.

What’s a marketplace facilitator law, and which OTAs apply?

A marketplace facilitator law is a state statute that shifts the legal obligation to collect and remit a transaction tax, sales tax originally and in most adopting states now also lodging tax, from the underlying seller (the hotel) to the platform that facilitates the transaction and processes payment (the OTA). Most states adopted these statutes for general sales tax between 2018 and 2021, largely in response to the Supreme Court’s South Dakota v. Wayfair decision, and a majority have since extended the same framework, or a lodging-specific variant, to occupancy tax.

• A covered OTA (Expedia, Booking.com, and similar platforms operating as merchant of record) registers directly with the state, collects occupancy tax from the guest as part of the total charge, and remits it under its own registration, rather than passing that obligation to the hotel.
• The statute typically defines “marketplace facilitator” broadly enough to capture any platform that processes payment and facilitates a booking, regardless of how the platform brands itself, which matters for hotels using smaller regional booking platforms that may not obviously look like a traditional OTA.
• Airbnb and VRBO are covered in some states and not others, and coverage can differ from what applies to a traditional hotel OTA booking even within a single state, because short-term rental platforms often built jurisdiction-by-jurisdiction agreements before relying on the general statute.

How do marketplace facilitator rules vary by state?

This is where portfolio-level compliance gets genuinely difficult, because “marketplace facilitator” is not one uniform national rule. It is 50 separate state statutes, plus separate rules in home-rule cities that administer their own tax independently of the state, each with its own scope, effective date, and definition of what is actually covered.

• Scope of tax covered. Some states’ statutes cover only the state-level occupancy or sales tax, leaving county and city lodging taxes entirely outside the statute and still the hotel’s own obligation. Others extended the statute to cover local taxes administered by the state on the locality’s behalf, but not those a home-rule city administers directly.
• Effective dates. States adopted these statutes on different timelines, so a booking made before a state’s effective date, even on the same platform, was not covered the way a booking made after is, which matters for any multi-year reconciliation.
• Registration and reporting visibility. Some states require the OTA to report gross booking data broken out by property, letting the hotel verify what was remitted on its behalf. Others allow aggregate reporting, leaving no property-level visibility at all.

A portfolio spanning several states needs this analysis done state by state, not assumed uniformly from whichever state the ownership group knows best. A rule of thumb that works in one state (“Expedia handles all of it”) can be flatly wrong next door, where the same platform’s coverage stops at the state tax line and leaves the county and city layers with the hotel.

What does OTA reconciliation look like across a portfolio?

A reconciliation process that works at portfolio scale needs to answer three questions for every booking channel, at every property, every filing period: what was the guest actually charged, what tax was actually collected, and was that tax actually remitted, by the hotel or the platform, to the correct jurisdiction.

• Pull channel-level revenue and tax data from the property management system, broken out by direct bookings, each OTA, and any short-term-rental channel, for the filing period.
• Match it against each platform’s remittance report, where available, to identify which specific jurisdictional layers the remittance actually covers for that property and period, not assumed coverage based on the state’s general statute.
• Flag the gap layers, the jurisdictions the platform does not cover, and confirm the hotel’s own filings include tax on those bookings for the uncovered layers.
• Escalate discrepancies before the filing deadline, not after, since correcting a filed return is materially more work than catching a mismatch before it’s filed.

Doing this manually across a dozen properties and half a dozen OTAs, every month, is why most portfolio operators build it into their revenue management or accounting system rather than a spreadsheet exercise; the hotel bookkeeping and USALI chart of accounts guide and the hotel revenue management and RevPAR accounting guide cover how channel-level revenue gets coded to support this instead of fighting it.

How do filing calendars work across multiple jurisdictions?

Every jurisdictional layer, state, county, city, district, and convention authority, sets its own registration process and filing frequency, and none coordinate with each other or with a portfolio operator’s other properties. The result, at scale, is a calendar with dozens of distinct filing dates across even a modest portfolio.

• Filing frequency is generally volume-driven: a new registration typically defaults to monthly filing, with a downgrade to quarterly or annual available once the property shows lower, stable tax volume, but the threshold differs by jurisdiction.
• A property that changes ownership, adds a building, or crosses a revenue threshold can trigger a re-registration or a filing frequency change at one layer without triggering the same change at another layer for the same property.
• Missing a deadline at one layer does not pause the others; each jurisdiction runs its own delinquency clock, and at portfolio scale, one missed deadline usually signals a calendar or ownership gap that affects more than one property.

The only reliable way to manage this at scale is a single master calendar, one row per property per jurisdictional layer, showing the next filing date, the last rate change, and current registration status, reviewed on a fixed schedule rather than reconstructed from memory.

When should a hotel use a voluntary disclosure agreement?

A voluntary disclosure agreement (VDA) is a program, offered by most state and many local revenue departments, that lets a taxpayer come forward proactively about unfiled returns or underpaid tax, in exchange for a limited lookback period (commonly 3 to 4 years, instead of an unlimited period an auditor could otherwise reach) and, in most programs, a waiver of penalties, though interest is still generally due.

• A VDA makes the most sense once a portfolio review, prompted by an acquisition, a new registration project, or an OTA reconciliation gap, surfaces a jurisdiction where a property should have been filing and was not.
• Most programs are anonymous at the initial inquiry stage, letting a hotel group (usually through counsel or its accountant) confirm the lookback period and penalty treatment before disclosing the taxpayer’s identity, and walk away if the terms are not favorable.
• Waiting for an audit to find the same gap instead almost always costs more: audits typically reach further back, assess full penalties, and often extrapolate a sample-period error rate across the entire audit period.

A multistate group expanding through acquisition should build a VDA review into due diligence itself, since the seller’s compliance gaps become the buyer’s exposure at closing; the hotel acquisition due diligence and purchase price allocation guide covers that broader process.

There is a federal wrinkle worth knowing here. Back tax and interest paid under a VDA or an assessment are generally deductible as an ordinary business expense under IRC 162. A civil penalty, which is what a late-filing occupancy tax penalty legally is, is generally not deductible under the fines-and-penalties disallowance in IRC 162(f). A VDA’s penalty waiver avoids creating that nondeductible line item.

How does nexus work for a hotel management company?

Nexus, the connection to a state sufficient to trigger a filing obligation, is usually straightforward for lodging tax itself: a property physically located in a state obviously has nexus there for that tax. The harder question is what other obligations a management company picks up simply by having staff, a regional office, or a centralized reservations function touching multiple states.

• A management company with employees traveling into a state to oversee a property, or a regional office in a state where it owns no hotels, can trigger corporate income or franchise tax nexus there, independent of the lodging tax question entirely.
• Centralized functions, a shared reservations center, a corporate team processing payroll for properties in several states, can create payroll withholding and unemployment insurance obligations in states where the company has no hotel at all.
• This nexus analysis runs separately from the property-level occupancy tax registration project, since the two questions depend on different facts and statutes, even though both get triggered by the same multistate expansion.

What mistakes show up in multistate lodging tax compliance?

The recurring failure at portfolio scale is not usually a single wrong calculation. It is a structural gap between how the compliance work is organized and how the tax obligations are actually layered.

• Managing occupancy tax property by property instead of through a portfolio-level jurisdiction matrix, so a rate change or a new district assessment is caught only if someone happens to be watching that property that month.
• Assuming marketplace facilitator coverage is uniform across states, when a rule that holds in one state is frequently wrong next door, where the same platform’s coverage stops at the state tax line.
• Never reconciling OTA remittance data against actual bookings, property by property, the single biggest source of undetected exposure across a portfolio.
• Treating an acquisition’s prior-period compliance gaps as the seller’s problem, when those liabilities usually transfer to the buyer, or at minimum create escrow and indemnification questions that need resolving before closing.
• Waiting for an audit instead of using a voluntary disclosure agreement, once a gap is identified, which turns a limited, penalty-free lookback into a full-scope, fully penalized assessment.

What should I do next?

If you operate more than one lodging property, the first deliverable worth building is a single jurisdiction matrix across the portfolio: every state, county, city, district, and convention tax layer that applies to each property, current registration status, and the actual filing calendar, not the assumed one.

• If any property sits inside a TID or a convention center tax zone, confirm those registrations and calendars separately from the general municipal hotel tax, since they are almost never on the same schedule.
• If you have never run a property-by-property OTA reconciliation, start with your highest-OTA-volume property and your state with the least favorable marketplace facilitator coverage, where exposure accumulates fastest.
• If the reconciliation turns up a gap where a property was never registered, evaluate a voluntary disclosure agreement before an audit finds it for you.

Related reading: the hotel occupancy tax and transient lodging compliance guide for the foundational rules on what is taxable, exemptions, and single-property filing mechanics; the hotel acquisition due diligence and purchase price allocation guide for building this review into a deal before closing; the hotel real estate ownership structure and REIT guide for how occupancy tax obligations flow through a REIT-TRS structure across a portfolio; and the FICA tip credit, Form 8846, and restaurant tax savings guide for the payroll-side multistate exposure a hotel’s food and beverage operation carries alongside its lodging tax obligations.

This guide is general information, not tax advice for your specific situation. Which points apply, and how, depends on your facts.