Multi-Property STR Records: What Changes at 2, 5, and 10 Rentals

The short version

The IRS tests §469 material participation, average customer use, and §280A(d) personal-use days per property by default. That does not change with portfolio size. What changes is the operational work of keeping the records clean.

A §469 grouping election under Treas. Reg. §1.469-4 is one way to combine material-participation hours across multiple STR activities. Each property in the grouping must still independently satisfy the STR exception (average customer use of 7 days or less, or another Reg. §1.469-1T(e)(3)(ii) exception). Long-term rentals cannot be grouped with STRs. For most hosts with two or three properties, keeping separate per-property logs is the safest approach. Around five properties, purpose-built per-property tooling starts saving real time. At ten or more, entity structure and manager records become the audit-defense pinch point.

Not tax advice; general framework only. See your CPA for how any of this applies to your specific facts.

What stays constant regardless of property count

The IRS treats each rental property as its own §469 activity by default. That default does not change because you have two, five, or ten. The underlying record has to hold up per property before any grouping decision is on the table.

Material participation (100-hour threshold, 500-hour test, and the "more than anyone else" test from Reg. §1.469-5T(a)(3)) is computed per property.
Average customer use for the STR exception under Reg. §1.469-1T(e)(3)(ii)(A) is computed per property.
§280A(d) personal-use days are computed per property, against a per-property threshold of the greater of 14 days or 10% of days rented at fair rental.
Depreciation basis is per property. Each rental has its own placed-in-service date, building basis, land value, and MACRS class-life schedule for building components, appliances, furniture, and land improvements.
Schedule E itself has three property columns; hosts with more than three attach a continuation Schedule E and never combine per-property numbers on the form.

Whether you use a spreadsheet, an appointment book, or a purpose-built tool, none of these tests move because of tool choice. See our material-participation reference for the underlying doctrine and the 4-log system for the record structure at a single property.

The one exception is the §469 grouping election. Under Treas. Reg. §1.469-4, taxpayers can elect to treat multiple activities as a single activity for material-participation purposes. It is a formal statement filed with the tax return, not a software toggle, and once made it generally applies to all future years (a taxpayer may regroup on a material change in facts and circumstances under §1.469-4(e)(2), or if the original grouping was clearly inappropriate under §1.469-4(e)(1)). The rest of this guide walks what changes about the operational work of maintaining the records at 2, 5, and 10 properties, not what changes about the tests themselves. The tests are the same. Gathering evidence for them is what scales.

At 2 properties: the grouping-election conversation begins

Two properties is where per-property logs still fit comfortably in a spreadsheet, and where the §469 grouping question first gets interesting.

The operational picture is still manageable manually. Two tabs per record type (participation activities, mileage trips, expenses, guest stays, personal-use days), property-level totals rolling up cleanly at year-end, both properties fitting inside the three-column Schedule E form without a continuation sheet, and two depreciation schedules that still fit on a single page. Most hosts at this stage do not need purpose-built tooling to keep the records straight; they need the discipline to keep the tabs current.

What changes is the strategic question. Do you keep the two properties as separate §469 activities, each with its own material-participation test, or do you make a §1.469-4 grouping election so the hours combine? Two illustrative examples:

Property A: 120h, Property B: 60h

Separately: A clears the 100-hour prong of Reg. §1.469-5T(a)(3) (still needs the "not less than any other individual" prong on its own facts); B does not, and without another §1.469-5T(a) test satisfied, B's losses suspend for the year. Under a §1.469-4 grouping election: both properties are treated as one activity; 180 combined hours clear the 100-hour prong on the grouped activity.

Property A: 40h, Property B: 70h

Separately: neither property reaches 100 hours; without another §1.469-5T(a) test satisfied on either, both losses suspend. Under a §1.469-4 grouping election: 110 combined hours clear the 100-hour prong on the aggregated activity, assuming the taxpayer's hours also exceed those of any other participant on the grouped activity.

The grouping election is a CPA conversation, not a software choice. Field Ledger does not implement or model the election; it captures per-property hours so a CPA making the election has clean raw data. Two constraints hosts routinely miss at this stage:

Each property still has to satisfy the STR exception on its own. Under a Reg. §1.469-4 grouping, the material-participation test aggregates; the STR-exception qualification test does not. Every property inside the grouping must average 7 days or less of customer use (or fit another Reg. §1.469-1T(e)(3)(ii) exception). A property averaging 14-day stays cannot ride into the STR exception on a grouping with 3-day-average properties.
Long-term rentals cannot be grouped with STRs. A duplex where one unit averages 30-day stays and the other 3-day stays is two different §469 activities regardless of any grouping filed; the STR exception either applies to a rental activity or it does not, and long-term rentals fail its qualification test.

Personal-use days remain a per-property calculation regardless of grouping. If you personally use Property A for 12 nights during a season and it rented 80 nights that year, that property's §280A(d) status is approaching the reclassification threshold on its own. Property B is unaffected. The greater-of-14-days-or-10%-of-rental-days rule applies to each property independently. See our multiple-STRs section for the doctrinal detail that mirrors this treatment.

At 5 properties: spreadsheets stop scaling

Five properties is where three problems start compounding at the same time.

Spreadsheet drift

Ten to fifteen tabs across five properties. Naming conventions slip. A cleaning payment tagged to the wrong property in March gets caught in November if you are careful, in April of the next year if you are not. The failure is not dramatic; it is the slow accumulation of small errors that a CPA cannot reconcile without asking questions you can no longer answer from memory.

Per-property depreciation basis

Each of the five properties has its own building basis, land value, placed-in-service date, and post-acquisition capital additions. Each carries its own MACRS 27.5-year residential schedule for the building itself and its integrated systems, plus separate 5-year schedules for appliances, furniture, carpeting, and computers, 7-year schedules for office furniture, and 15-year schedules for qualifying land improvements (a cost-segregation study is what separates individual building-system components out of the 27.5-year basis into shorter class lives). That is five separate asset registers to maintain, five separate §1.263(a)-1(f) de-minimis-vs-capitalize decisions to track ($2,500 or less per invoice with consistent accounting procedures and an annual election statement attached to a timely-filed return), and five separate lists of what to hand your CPA at year-end. Field Ledger captures per-property assets with a suggested MACRS class-life; the annual depreciation deduction is computed by your CPA on the year-end schedule. See our depreciation guide for the mechanic.

Revenue reconciliation from one 1099-K

Airbnb, VRBO, and Booking.com each send one 1099-K per host tax ID, not one per property. Splitting that gross number back into per-property Schedule E line 3 income requires booking-level detail from the platform's transaction-history export, matched against per-property payouts. Doable manually at two properties; a real chore at five. See our 1099-K reconciliation guide for the multi-property mechanic.

The per-property hour math gets harder

The arithmetic changes shape at five properties. Reg. §1.469-5T(a) tests each property independently by default, so "two hours a week per property times 52 weeks equals 104 hours" is the number that matters at each property (not 520 aggregate hours across five). That 104-hour figure clears the 100-hour prong of Reg. §1.469-5T(a)(3), but the second prong ("not less than any other individual on the activity") has to survive scrutiny separately at each property. Aggregating hours to a single 520-hour figure to satisfy §1.469-5T(a)(1)'s 500-hour test requires a §1.469-4 grouping election (covered in the "2 properties" section above). Without the election, no single property reaches 500 hours in this example, and each property is tested against §1.469-5T(a) on its own hours. Reconstructed hours are routinely disallowed in Tax Court; the regulation on its face permits reasonable approximations from appointment books and calendars, but examiners and judges strongly prefer contemporaneous records.

Five properties is the count where purpose-built per-property tooling starts to save real hours instead of just being a nicer version of the same spreadsheet. Field Ledger's Operator plan is scoped to five properties on the same per-property mechanics that ship at every plan tier: per-property material-participation cards, per-property Schedule E CSV export, per-property depreciable-asset register, and the property picker in the top bar for switching context. Nothing exotic; the same per-property record you had at 2 properties, without the spreadsheet drift.

At 10 properties: records meet entity structure

Ten properties is where the record-keeping conversation ends and the entity-structure conversation begins. The two overlap.

Entity structure enters

LLC-per-property, series LLC (available in some states), a single consolidated LLC, or personal ownership: each has different liability, financing, and tax-reporting implications. This is attorney and CPA territory, not software territory. Field Ledger does not model entity structure; it tracks records per property regardless of how those properties are owned. If you have one LLC that owns two properties and separate LLCs for the other eight, you have three tax returns (each LLC's) plus your personal return, and per-property record hygiene has to survive that fan-out.

Manager and co-host records become the pinch point

With ten properties you are almost certainly not doing every cleaning and every guest handover yourself; you have a manager, a cleaning team, a handyman on retainer. The §1.469-5T(a)(3) "not less than any other individual" prong now becomes an evidence question: did you do more hours than your manager did on the property in question? If your manager keeps no contemporaneous timesheet on the properties they cover, the evidence for the "more than anyone else" claim is thin. Doctrinally the test still runs; practically it is hard to defend without corroborating records (cleaning invoices, guest-check-in schedules) that show what other participants actually did.

Recordkeeping volume at scale

A single-property record file is one folder of receipts. A ten-property record file is ten folders plus the cross-references between them: which cleaner worked which property in which week, which manager handled which check-in, which supplies delivered to which address. Field Ledger's per-property tagging keeps the structure intact at scale. Activities you enter as free-form prose parse into structured records under the active property; mileage trips (using a Trip: line) and expenses (using an Expense: line) file under that same property as structured entries. Pulling every record for property X, tax year Y later takes one filter change rather than grepping every note file for the property name.

Portfolio-level management metrics (not §469 tests)

Portfolio-level views become useful at this scale even though they are not §469 tests. Field Ledger's dashboard surfaces total counted hours across all properties, a count of properties that individually reached the 100-hour threshold, and average hours per property. These are management metrics for spotting the property that quietly slipped behind on hours in Q3 while you were focused on Q4 acquisitions. They are not §469 aggregations. Each property's material-participation determination still runs against that one property's own hours unless a Reg. §1.469-4 grouping election is filed. The Portfolio plan is scoped for unlimited properties on the same per-property mechanics.

How Field Ledger handles multi-property

Field Ledger is built around per-property records. Every activity (participation hours), trip (mileage), expense, guest stay, personal-use day, and depreciable asset is stored with a property foreign key at the database level. The property picker in the top bar switches context without losing your place; capture on the Review page files each confirmed record under the active property. Per-property mechanics that ship today:

Material participation, per-property progress against §469 hour thresholds: the 100-hour and 500-hour thresholds from Reg. §1.469-5T(a) rendered as per-property "Reached" or "Below" badges. Field Ledger surfaces the underlying hours (yours and any non-owner participant hours you log); your CPA evaluates the "not less than any other individual" prong of Reg. §1.469-5T(a)(3) and any other Reg. §1.469-5T(a) test that requires facts-and-circumstances judgment. Badges are never worded as "PASS" or "FAIL."
Average customer use per property under Reg. §1.469-1T(e)(3)(ii)(A). Computed from that property's guest-stay records, displayed as a narrative status pill (under the 7-day threshold, over 7 but under 30, or STR exception per-se rule not met).
§280A(d) personal-use status per property. Narrative pill with four states (no data, comfortably within, approaching the §280A(d) threshold, §280A(d) threshold exceeded with residence reclassification risk). Uses the greater-of-14-days-or-10%-of-rental-days rule per property.
Schedule E line-by-line CSV export per property. One CSV per property with subtotals mapped to Schedule E category numbers. Your preparer uses each CSV to populate that property's column on the form.
Per-property depreciable-asset register with MACRS GDS class-life suggestion. Each asset stored under the property that owns it, with a suggested class code based on the item description (5-year for appliances, furniture, and computers; 7-year for office furniture; 15-year for qualifying land improvements; 27.5-year for the building itself and integrated building-system components). The annual depreciation deduction is computed by your CPA on the year-end schedule.
Property picker top-bar with per-property state. Capture, review, MP summary, stays, personal-use, and export pages all scope to the active property. Dashboard shows every property's card side by side in a responsive grid.

Deliberate omissions worth naming:

§469 grouping election: not modeled. The election is a CPA-mediated decision filed with the tax return, not a software toggle. Field Ledger stores per-property hours cleanly so a CPA making the election has raw data to work from.
Portfolio-level material-participation determinations: the dashboard shows counted-hours totals across the portfolio and a count of properties that individually reached the 100-hour threshold. Both are informational management metrics. Neither is a §469 test at the portfolio level.
MACRS annual depreciation deduction: assets are captured with MACRS class-life suggestions. The deduction math is on your CPA.
Entity-structure modeling: LLC configuration, series LLC, consolidated ownership. Field Ledger is org-scoped; entity mapping happens outside the ledger on your tax returns and legal-structure filings.
IRS 3-column Schedule E form output: the export produces per-property CSVs with the line-by-line subtotals your preparer needs, not a form-alike three-column layout. Your CPA (or your tax software) populates the form itself.
Most §469 material-participation tests: not computed as pass/fail verdicts. Field Ledger surfaces per-property hours against the 100-hour and 500-hour thresholds of Reg. §1.469-5T(a); the more-than-anyone-else prong of (a)(3), the substantially-all test (a)(2), the significant-participation aggregation (a)(4), the prior-year tests (a)(5) and (a)(6), and the facts-and-circumstances test (a)(7) require your CPA's judgment on your specific facts.

Try Field Ledger's per-property §469 record

Every log, every trip, every expense, every stay, every personal-use day tagged to a specific property. The three record axes that matter for the STR strategy (§469 material-participation hours, §469 average-stay days, §280A personal-use days) computed per property. The Schedule E export split per property. Your CPA gets one file per property in April, not five spreadsheets full of guesses.

Per-property "Reached / Below" badges against the 100-hour and 500-hour §469 thresholds
Per-property §1.469-1T average-customer-use status pill
Per-property §280A(d) personal-use status with narrative reclassification-risk pill
Per-property Schedule E line-by-line CSV export
Per-property depreciable-asset register with MACRS class-life suggestions
Operator plan scoped to 5 properties, Portfolio plan for unlimited

Start free trial

714-day free trial, no credit card required. Renews monthly or annually at the plan price you select until canceled. Cancel anytime in Manage Billing. Plus applicable US sales tax.

Frequently asked questions

Do I need a separate Schedule E for each property?

No. Schedule E has three columns on a single form. Properties four through six go on a continuation Schedule E, seven through nine on another, and so on. Each property occupies its own column; income and expenses are never combined across properties on the form. Field Ledger exports one CSV per property with the line-by-line subtotals your preparer uses to populate each column.

What is a §469 grouping election and should I make one?

Under Treasury Reg. §1.469-4, taxpayers can elect to treat multiple activities as a single activity for §469 material-participation testing. For STR hosts, this means combining hours across properties so the aggregate satisfies a material-participation test even when no single property does on its own. The election is a formal statement filed with your tax return; once made, it generally applies to all future years, though a taxpayer may regroup on a material change in facts and circumstances (§1.469-4(e)(2)) or if the original grouping was clearly inappropriate (§1.469-4(e)(1)). Whether it fits your facts depends on which properties you actually work in, whether losses at low-hours properties are worth combining with gains at high-hours ones, and how your year-over-year picture is likely to shift. This is a CPA conversation, not a software choice.

Can I combine long-term and short-term rentals into one §469 grouping?

No. The STR exception under Reg. §1.469-1T(e)(3)(ii) requires an average period of customer use of 7 days or less (or one of the other narrow exceptions in that regulation). Long-term rentals do not satisfy that condition. A grouping that combined both types would fail the STR exception on the long-term side; the STR exception either applies to a rental activity or it does not. Practically, if you own both types, they are separate §469 activities regardless of any grouping election.

Under a §469 grouping election, does each property still need to satisfy the 7-day rule?

Yes. Grouping combines the material-participation test; it does not exempt any property from the STR exception's own qualification test. Every property inside the grouping must average 7 days or less of customer use (or fit another Reg. §1.469-1T(e)(3)(ii) exception) for the grouping to qualify for the STR exception. A property that averages 14-day stays cannot ride into the STR exception on a grouping with 3-day-average properties.

Does one 1099-K cover all my properties?

Yes. Airbnb, VRBO, and Booking.com each issue one 1099-K per host tax ID, aggregating gross booking payouts across every listing that host operates on the platform. Splitting that back into per-property Schedule E line 3 income requires the booking-level detail from the platform's transaction-history export, matched against per-property payouts. Field Ledger's multi-property model supports the per-property allocation; the 1099-K itself remains a single form covering the entire portfolio.

Should each property be in its own LLC?

This is attorney and CPA territory, not software territory. Common structures include LLC-per-property, series LLC (available in some states), a single consolidated LLC, or personal ownership. Each has different liability, financing, and tax-reporting implications. Field Ledger tracks records per property regardless of entity structure; entity mapping happens outside the ledger on your tax returns and in your legal-structure filings. Consult an attorney experienced in real estate holding structures for your state.

How does Field Ledger's dashboard handle 10+ properties?

The dashboard shows one material-participation card per property in a responsive grid, plus org-wide informational summaries: total counted hours across the portfolio, count of properties that individually reached the 100-hour threshold, and average hours per property. Those org-wide numbers are management metrics, not §469 tests at the portfolio level. The property picker in the top bar lets you drill into any single property's full record. The Portfolio plan ($79/mo) is scoped for unlimited properties on the same per-property mechanics that ship at every plan tier.

Related guides

Sources

General information about U.S. federal tax rules for short-term rentals; not tax advice.

The key takeaway

Portfolio size changes the shape of the record-keeping problem, not the tests themselves. The IRS still tests §469 material participation, average customer use, and §280A personal use per property regardless of how many properties you have or which software you use. A §469 grouping election under Treas. Reg. §1.469-4 is one way to combine material-participation hours across properties, but it does not exempt any property from independently satisfying the STR exception. At every portfolio size, contemporaneous per-property records are the artifact your CPA and a potential examiner rely on. Not tax advice; consult a qualified tax professional.