Is Your Lodging Tax Is Sitting in the Wrong Account Right Now?

This post is drawn from a recent HostAllies webinar on STR accounting and tax clarity. Lodging tax came up as one of the areas where even experienced operators have gaps and where the consequences hit hardest.

Most property managers know lodging tax is complicated. What they don't always see is how much of the chaos missed filings, unexpected back taxes, owner confusion traces back to one mistake: treating tax money like operating money.

Here's how to fix that, and how to build a system where tax season is a report, not a scramble.

One Booking. Three Separate Obligations.

When a guest checks in, three financial events happen simultaneously:

• A lodging tax obligation is created. The correct amount must be calculated, held separately, and remitted to the right jurisdiction by the right deadline.

• An owner's financial event occurs. Nightly rent is earned, the owner's portion is calculated, and the transaction feeds into their year-end statement and Schedule E, the IRS form where rental income and expenses are reported.

• An operator revenue event occurs. Your management fee is earned, cleaning margin is recognized, and pass-through costs are logged for your Schedule C, your business income and expense report.

  
  

Each of these lands on a different party, with different deadlines, and different consequences if something goes wrong.

Lodging tax is the one that bites hardest, because in most jurisdictions, the property manager is the one on the hook to collect it, hold it, and remit it. Not the owner. Not the platform. You.

Note: In some management structures, the owner holds the STR license and retains tax liability. Check your management agreement and confirm with your CPA.

The Year-Round Rhythm (Start Here)

Lodging tax compliance isn't a once-a-year event. Build these checkpoints into your operations:

• Weekly: Audit new bookings for correct tax configuration. A rate error caught before checkout is fixable. One caught after the guest has left, and the funds are gone, usually isn't.

• Monthly: Run a lodging tax collected vs. remitted report. Confirm platform remittance in every market where you're relying on Airbnb, Vrbo, or any OTA to file on your behalf.

• Quarterly: Review jurisdiction rule changes across your markets. Update your tracker to reflect current rates and filing frequencies. Mid-year rate changes happen; cities like Nashville and Phoenix have adjusted rates with little lead time.

• Year-end: Confirm all lodging tax filings are closed before issuing owner year-end packages. Your CPA can't produce a clean picture until this is done.

Where Things Break Down

The most common failure isn't fraud or negligence. It's infrastructure. Here's what goes wrong:

• Tax money lives in the wrong account. When the lodging tax gets deposited into the operating account, it gets spent. Remittance time comes, and the cash isn't there. This is the most common and most painful version of this problem.

• OTA remittance is assumed, not confirmed. Airbnb collects lodging tax in many markets, but not all, and not always completely. In California, for example, Airbnb may remit certain state-level taxes but not every local jurisdiction's levy. Partial remittance is common. If you're not confirming platform remittance by market every month, you likely have gaps you don't know about yet.

• VCAs are misunderstood and create double-payment risk. Some platforms have formal agreements with certain states to collect and remit tax entirely on your behalf. These are called Voluntary Collection Agreements. If that arrangement is in place in your market and you're also remitting independently, you're likely paying twice. Confirm VCA status before filing anything in a new market.

• The wrong rate is configured in the PMS. Collecting too little means the shortfall comes out of your margin. Collecting too much creates owner confusion and potential refund issues.

• The jurisdiction tracker is treated as a one-time setup. Tax rules change at the local level sometimes retroactively, sometimes immediately, sometimes with advance notice. A tracker built last year may already be wrong.

What a Clean System Actually Looks Like

• A dedicated liability account. Lodging tax should be separated at the moment of collection. It should never sit in your operating account or commingle with owner funds.

• A jurisdiction tracker that's a living document, not a spreadsheet you set up at onboarding and never touch again. At minimum, track: Market, Tax Rate, Filing Frequency, Who Remits, VCA Status, and Last Verified. Review it quarterly. When you take on a new market, this is the first thing you build. 

• Pre-booking verification on every new property. Before the first booking goes live, confirm the correct rate is configured in your PMS, and you have the owner's Tax ID for any required STR filings.

• Monthly collected vs. remitted reporting. Every month, compare what you collected against what was remitted. Confirm platform remittance in every market where you're relying on an OTA to handle it.

  
  

When this system is working, there are no surprises at year-end. You know what was owed, what was paid, and every jurisdiction is closed out.

A Note on Multi-Market Complexity

If your portfolio spans multiple states, your lodging tax exposure compounds. Different states define "lodging tax" differently. Some include sales tax on accommodations. Some have county and city layers on top of state rates. Operating across state lines without a per-market compliance process isn't a gap; it's a liability.

How HostAllies Handles This 

Lodging tax is one of the most jurisdiction-specific, operationally complex parts of running an STR property management company. It's also one of the easiest things to get wrong when you're scaling.

If your lodging tax process needs work, we'll clean it up and keep it clean.

Ready to put this into practice? Book a free consultation with HostAllies.