Can two leases overlap on one unit? The double-booking guard
No — a unit holds one direct tenancy at a time, enforced everywhere a booking is created or moved. Back-to-back same-day turnover is fine; room-by-room and OTA history are exempt.
No — a unit holds one direct tenancy at a time, and Nexxus enforces it at every gate where a direct booking is born or moved:
- generating a lease from an application (checked before the applicant signs or pays),
- moving an applicant to tenant,
- creating a booking manually,
- editing a booking's dates.
When a conflict exists, the denial names the sitting tenant and their dates, so you immediately know what's in the way.
Back-to-back is fine
A new lease may start the same day the old one ends. Nexxus treats nights as checkout-exclusive — the departing tenant's last night ends the morning the new tenant arrives, so same-day turnover needs no special flag (deliberately unlike Buildium's same-day-move-in setting).
Swapping tenants mid-month
Shorten the sitting booking's end date first, then create the new tenant's booking. The guard will confirm the lane is clear.
Exemptions
- Room-by-room properties — concurrent stays are the model, so the guard doesn't apply between rooms.
- Airbnb/OTA imports — they record stays that already happened, so they're never blocked. However, an existing OTA stay does block a new direct lease over the same dates: the unit genuinely isn't available.
Why the guard is strict
A double-booked unit corrupts everything downstream — two rent schedules on one unit, occupancy over 100%, and a payout run trying to pay an owner twice for the same nights. Nexxus refuses at the front door so you never have to untangle it at the back.