Mid-term rentals do not fit either mold
A 30-to-90-night furnished stay does not behave like a short-term rental (constant turnover, nightly pricing) or a long-term lease (a fixed term, unfurnished, minimal ongoing management). Tools built for one end of that spectrum tend to force awkward workarounds for the other The Property Tool's calendar and booking model do not assume a stay length, so a 3-night booking and a 3-month one live in the same system without either one feeling bolted on.
One calendar, whatever the stay length
Managing a mix of nightly, weekly, and monthly stays across the same portfolio usually means checking multiple calendars or manually reconciling different booking systems. A single real-time calendar per property handles bookings of any length the same way, so a portfolio mixing corporate housing with shorter stays does not need two separate systems to track it.
Owner reporting that does not care how long the guest stayed
An owner statement should not need a different format depending on whether the month contained one 90-night corporate stay or twelve short bookings. Statements generate from the same booking and expense data regardless of stay length, so the reporting stays consistent even as the mix of stay types shifts month to month.
The space between a stay and a tenancy
A thirty-day-plus furnished let is neither a hotel booking nor a lease, and most software forces it to be one or the other. Treated as a booking it loses the tenancy admin — deposits, documents, notice periods. Treated as a lease it loses the calendar, the furnishing inventory and the turnover.
The Property Tool models occupancy as a dated stay regardless of length, so a ninety-day corporate let sits in the same calendar as a three-night booking and a twelve-month tenancy, with the tenancy detail attached where it applies.
Who the guest actually is
Mid-term demand tends to come from relocations, contractors, insurance placements and healthcare staffing, which means the person paying is often not the person staying. Corporate bookers want an invoice and a contact; the occupant wants the wifi code and a working boiler.
Keeping both against the same stay — the paying party on the ledger, the occupant on the messaging thread — avoids the usual confusion about who to chase for what.
Utilities, furnishing and what is included
Mid-term lets are usually all-inclusive, which puts costs that a long lease passes to the tenant back onto the property's P&L. Getting those recorded against the property as they occur is what makes the owner statement accurate and the margin visible.
Furnishing and inventory sit in the same place: a cost when bought, a maintenance item when broken, both attached to the property rather than to a memory.
Pricing a stay measured in months
Nightly rates make little sense here and monthly rent ignores the gaps. Base rates with seasonal overrides let you set a rate that reflects the length of stay, and the reporting shows occupancy and revenue per property so you can see whether a longer, cheaper booking actually beat two shorter ones.
Common questions
How is a 90-day stay different from a lease here?
Structurally it is not — both are dated stays. The difference is which detail you attach: deposits and notice on one, turnover and furnishing on the other.
Can I invoice a company rather than the occupant?
Yes — the paying party and the occupant can be tracked separately against the same stay.
Do utilities and furnishing costs reach the owner statement?
Yes, once recorded against the property they flow through to the statement automatically.
Can I run mid-term alongside short-term units?
Yes, in one calendar and one ledger — see short-term rentals.
Is there a minimum stay setting?
Booking rules are configurable per unit.