Every STR investor eventually hears someone mention "the loophole." But if you've ever tried to actually read the regulation behind it, you probably hit a wall of legalese and cross-references that made your eyes glaze over.
That regulation is Temporary Treasury Regulation §1.469-1T(e)(3)(ii)(A) — and it's the entire legal foundation for why short-term rental losses can offset your W-2 income. If you're going to use this strategy (and you should), you need to understand exactly what this regulation says, why it exists, and how it applies to your property.
This isn't a "loophole" in the shady sense. It's a specific IRS classification rule that's been in the tax code since 1988.
- The 7-day average customer use rule comes from Treas. Reg. §1.469-1T(e)(3)(ii)(A), a regulation in force since 1988.
- If the average period of customer use is 7 days or less, the property is NOT a "rental activity" under IRC §469.
- That reclassification lets you apply the regular material participation tests — and treat losses as non-passive.
- The IRS does not contest the regulation. Audits focus on whether your records prove you meet it.
What Does the Regulation Actually Say?
Let's start with the regulation itself. Treas. Reg. §1.469-1T(e)(3)(ii)(A) provides an exception to the general rule that rental activities are automatically passive. Here's the relevant language, simplified:
An activity involving the use of tangible property is not a rental activity for a taxable year if the average period of customer use for such property is seven days or less.
That's it. That's the core of the entire STR loophole.
Under IRC §469, rental activities are generally classified as passive — meaning losses can only offset other passive income. For most W-2 employees, that makes rental losses essentially useless against their salary.
But this regulation creates an exception. If your average guest stay is 7 days or less, the IRS doesn't treat your property as a "rental activity" at all. Instead, it's classified as a regular trade or business activity. And that changes everything.
Why the 7-Day Threshold Exists
When Congress wrote the passive activity rules in the Tax Reform Act of 1986 and the Treasury issued these temporary regulations in 1988, they were thinking about hotels and motels. The logic was straightforward: if you're renting property for very short stays, you're operating more like a business than a passive landlord. You're dealing with constant guest turnover, cleaning, check-ins, maintenance calls — it looks and feels like a business.
The regulations weren't written with Airbnb in mind (the platform wouldn't exist for another 20 years). But the language is clear, and it applies equally to any property with short average stays — whether it's a boutique hotel in Manhattan or a cabin you rent out on VRBO.
This is why the strategy is called a "loophole." The regulation predates the short-term rental industry as we know it. The drafters likely envisioned commercial hotel operations, not individual investors managing a few vacation rentals from their iPhone. But the text of the regulation doesn't distinguish between the two.
How the 7-Day Average Is Calculated
The calculation uses only actual rental days, not calendar days. Here's how it works:
Average Period of Customer Use = Total Rental Days ÷ Number of Separate Rentals
If you had 200 total rental nights across 45 separate bookings in a year, your average is 200 ÷ 45 = 4.4 days. You qualify.
A few critical nuances:
- Days between bookings don't count. Only days a guest is actually occupying the property.
- Extended stays can blow your average. One 30-day booking mixed with short stays can push you above 7 days. This is why many STR investors set maximum stay limits.
- The calculation is per tax year. You recalculate every year. Qualifying last year doesn't guarantee you qualify this year.
- Partial-year conversions get tricky. If you convert a long-term rental to short-term mid-year, only the STR period counts — but consult your CPA on how the transition year is treated.
For a deeper breakdown of this calculation, see our 7-Day Rule guide.
The Second Requirement: Material Participation
Meeting the 7-day average gets you past the "rental activity" classification. But to make your losses non-passive, you also need to materially participate under Treas. Reg. §1.469-5T.
The two tests most STR investors use:
- The 500-Hour Test — You personally spend more than 500 hours on the activity during the tax year. This is the "safe harbor" because your hours stand alone.
- The 100-Hour Test — You spend more than 100 hours on the activity AND no other single individual spends more time than you. This is the most common path for STR investors who use cleaners, co-hosts, or property managers.
Both tests are legitimate. The difference is in how much scrutiny they attract and how much documentation you need. We break down the comparison in 100 Hours vs 500 Hours: Which Test Should You Use?
How It All Connects: The Legal Chain
Here's the complete legal chain that makes the STR loophole work:
- IRC §469(a): Passive activity losses can only offset passive income.
- IRC §469(c)(2): Rental activities are, by default, passive.
- Treas. Reg. §1.469-1T(e)(3)(ii)(A): BUT — if average customer use is 7 days or less, it's NOT a rental activity.
- Treas. Reg. §1.469-5T: The activity is non-passive if you materially participate (7 tests, any one of which works).
- Result: Your STR losses — including depreciation from a cost segregation study — directly offset your W-2 income.
This is not a gray area. It's black-letter regulation that's been in place for nearly four decades. The IRS doesn't challenge whether the loophole exists. They challenge whether individual taxpayers actually meet the requirements — specifically, whether the average stay is really 7 days or less and whether the taxpayer really materially participated.
That's why documentation is everything. Your booking records prove the 7-day average. Your hour logs prove material participation.
The "Temporary" Regulation Question
Sharp-eyed readers will notice that Treas. Reg. §1.469-1T is a temporary regulation (that's what the "T" means). Temporary regulations are issued under IRC §7805(e) and technically expire after three years.
So how is a "temporary" regulation from 1988 still in effect?
In practice, the IRS has never replaced it with a final regulation, and it's been cited, applied, and upheld in Tax Court for decades. The IRS treats it as authoritative. CPAs rely on it. Tax Court decisions reference it directly. For all practical purposes, it carries the same weight as a final regulation.
Could the IRS issue a final regulation that changes the 7-day rule? Theoretically, yes. But there's been no indication this is under consideration. The regulation has survived multiple major tax reform efforts — the 2017 Tax Cuts and Jobs Act, the 2025 OBBBA — without modification.
What This Means for Your Tax Strategy
Understanding the regulation matters because it tells you exactly what you need to prove:
- Average period of customer use ≤ 7 days. Keep your booking data clean. Set maximum stay limits if needed. Calculate your average quarterly so there are no surprises.
- Material participation under one of the seven tests. Track your hours contemporaneously — not from memory at tax time. The IRS has denied deductions in multiple cases (Almquist, Penley, Sezonov) specifically because the documentation was inadequate.
The STR Loophole app was built for exactly this. It tracks your hours against the 100-hour or 500-hour test in real time, logs third-party hours so you know if you're beating the "more than anyone else" threshold, and generates CPA-ready reports that align with IRS documentation standards.
The Bottom Line: The STR loophole rests on a specific, black-letter regulation — Treas. Reg. §1.469-1T(e)(3)(ii)(A) — that has been in force since 1988. The IRS does not dispute the exception exists; they audit whether you actually meet it. Keep clean booking records to prove the 7-day average, and contemporaneous hour logs to prove material participation.
Ready to see if you qualify? Try the free STR loophole calculator →
