Changing rent mid-lease (and why Nexxus asks for a written agreement)

Rent changes are where books quietly go wrong, so Nexxus separates three things that other systems blur together.

The model: lease vs booking vs trail

• The lease is the legal record — it keeps its original rate forever, exactly as signed.
• The booking carries the current effective rent — this is what drives the ledger, the tenant's headline rent, and payout math.
• The trail records every change: previous rate, new rate, effective date, who changed it, and a note.

The tenant's Lease tab shows "Monthly rent (as signed)" plus an "Updated rent" row per change — the full story at a glance.

Making a change

Edit the booking's monthly rent. Nexxus asks you to confirm the change is agreed in writing (a renewal, an amendment, a signed notice — whatever your jurisdiction requires), with the effective date and an optional note. The server refuses a rent change without that confirmation — it's the difference between an auditable adjustment and a mystery edit.

What happens to the ledger

The new rate flows to unpaid rent through the ledger's reconcile: charges already paid are never touched, and manual entries are never deleted. If an account already has manual payments, the difference posts as a labeled adjustment rather than rewriting history.

Practical notes

• Set the effective date to what the written agreement says, even if you're entering it late — the trail is your audit record.
• A mid-month change applies to unpaid rent going forward; if you need a partial-month split, post a one-off charge or credit on the ledger for the difference.
• Raising rent at renewal with a new lease? Generate the new lease instead — new lease, new as-signed rate, clean slate.