Texas Short-Term Rental Taxes and Hotel Occupancy Tax

A Texas host who starts the year with a clean tax setup saves hours every month that follows. That setup has three parts. First, confirm state hotel occupancy tax registration for the host's situation and local hotel occupancy tax arrangements for each property's city, using official state and city sources. Second, confirm for each platform used whether that platform collects state tax, local tax, both, or neither for stays in that city. Third, create a tax folder per property, with subfolders per month, ready to receive statements as they arrive. Hosts who create that structure in January work with it all year; hosts who improvise in December reconstruct it under pressure.

January is also the moment to separate tax money mentally from income. Taxes collected from guests, or collected by a platform on the host's behalf, are not the host's spending money. Hosts who move tax amounts into a separate account, or at least track them as a separate line, never face the familiar shortfall of having spent tax money before remittance day. That separation is a habit, not a software feature, and it works with a simple spreadsheet as well as with accounting tools.

Spring brings the first payout statements of the year, and with them the first chance to test whether platform collection matches expectations. For each property, compare the statement's tax lines with the setup note from January: did the platform collect the state layer, the local layer, or neither, as expected? A mismatch in spring, investigated while the stays are fresh, is a short query to the platform. The same mismatch discovered in December, across dozens of stays, is a reconstruction project. File each statement in its month folder on arrival, with a one-line note recording what was collected and what remains for the host to remit.

Direct bookings in spring need the same attention, with an extra step: the host is the collector. Add the correct state and local charges to the guest invoice, hold them separately, and record them in the same month folder as platform statements. A direct stay without a tax line on its invoice is not a tax-free stay; it is a stay whose tax the host must still account for, now without having collected it. Catching that omission in spring, for one stay, teaches a host to fix invoicing before summer volume arrives.

Summer volume tests every tax routine. More stays mean more statements, more refunds, more alterations, and more chances for a tax line to be missed. Refunds deserve particular care: a guest refunded in full should not generate tax for the refunded nights, while a partial refund or an alteration that shortens a stay changes the tax base for that stay. Record each refund and alteration in the month it occurs, with the original booking reference, so the tax adjustment traces to its cause. Hosts who file refunds without tax notes create year-end puzzles that no statement alone can solve.

Summer is also when a host first sees whether annual totals are tracking as expected. A mid-year totals check, total income per property, total tax collected per layer, total tax remitted, takes an afternoon and reveals drift early: a platform that stopped collecting local tax in one city, a direct-booking invoice template missing a tax line, or a property whose local tax was never set up. Fixing drift in summer costs a few hours. Fixing it after year end costs a professional fee and a possible late filing.

Autumn reconciliation is the host's last calm opportunity to fix the year. For each property, total the year's stays, income, tax collected by platforms, tax collected by the host, and tax remitted, per layer, and list every difference with an explanation: timing, refund, alteration, or collection gap. Where a difference has no explanation, investigate it while platform dashboards still show the year's data and guest messages are still retrievable. Platforms archive and rotate data, and a difference that is investigable in autumn may be unprovable by spring.

Autumn is also the right time to seek advice if the year has become complex: a new city added, a pattern changed from hosted to whole-home, a company structure introduced, or direct bookings grown sharply. Advice sought in autumn can still shape the year's final filings and next year's setup. Advice sought after a tax notice arrives must defend a completed year, which is harder and more expensive.

Winter filing should be an assembly task, not a discovery task, if the monthly folders are complete: totals from monthly notes, remittance references already recorded, refunds already adjusted. File through the correct state and local channels for each property, keep filing confirmations with the year's folder, and note any amount still outstanding with its due date. Then archive the year's folder intact, statements, invoices, remittance confirmations and advice notes together, rather than scattering them across email and platform dashboards.

Reset for the next year before the first January booking: confirm tax rules have not changed for any city, confirm platform collection coverage has not changed, update the setup note, and create fresh month folders. A reset that takes an hour in winter prevents a year of drift. Hosts who skip the reset carry last year's assumptions into a new year where a city or platform may have changed its arrangements.

Keep state and local tax records per property per year, with stay-level detail, for as long as official guidance requires, and longer where a host's own records allow it cheaply. Digital copies, backed up, beat paper scattered across properties. For multi-city portfolios, mixed channels, or company hosting, professional tax advice tailored to the actual pattern is worth its cost, and advice notes should be filed with the tax year they concern. This guide gives general information only, last verified on 26 October 2026, and states no tax rate, since rates and filing details must be checked on official state and city portals at the time of filing.