MASTERKEY BLOG

New: Restore Previous Status for Leased Units

We’ve introduced a new feature that will help you in case a Tenant changes mind about renewing a lease. Two scenarios apply to in this situation:

  1. Tenant sends a notice of non-renewal of the lease, you change the status of the Unit to ‘Upcoming”, and then Tenant changes mind and decides to renew the lease anyway.
  2. Tenant agrees to renew the lease, you change the status of the Unit to ‘Renew reserve’, and then Tenant changes mind and decides not to renew the lease anyway.
To proceed in these two situations, you previously had to go through several transaction steps before you could arrive at the desired Unit status. We’ve now added a new feature for these situations, so that you can restore the previous status of the leased Unit with just one click.

Where do I find this feature?

It made sense to place this button in the Unit history, because you want to go back to the last status in the Unit history.

 

1)History button  2)Restore previous status button  3)Current status:Reserved  4)Previous status:Leased

How do I get this feature?

The button is controlled by your User policy, so you need your System Admin / Manager to give you access first. Once enabled, this button is will only show for:

  • Units which have been converted from ‘Leased’ to ‘Upcoming”. 
  • Units which have been converted from ‘Leased’ to ‘Renew Reserve’.

What do I need to know before doing this?

  • The unit will be restored in the previous lease status with all the transaction details attached including Tenant details, contract, payments, receipts and invoices.
  • Payments will be restored with the same payment status i.e. Paid or Unpaid.
  • A new entry will be added to the Unit history about restoring previous status. 
  • There will be no changes on the Landlord Lead when you set the Unit status as ‘Upcoming’ or ‘Renew reserve’.
  • After restoring the previous status, the Unit will show the Tenant and Landlord Leads in closed status as it was closed due to the transaction.  

blog comments powered by Disqus