Dubai rent arrives as post-dated cheques. Each one is a row on the contract with a due date, a bank and a status — pending, deposited, cleared or bounced — so the question of what has actually been banked has an answer you can open rather than remember.

Onboarding ends by splitting the annual rent across the frequency you chose — annual, semi-annual, tri-annual, quarterly, bi-monthly or monthly. Each instalment becomes a cheque row carrying its number, bank, amount, due date and the period it covers. Cash, bank transfer and crypto are recorded the same way, so a contract paid by transfer still has a schedule rather than a note.

Pending becomes deposited, deposited becomes cleared, and each step stamps its own timestamp. The buttons enforce the order: a cheque cannot be cleared before it has been deposited. When a cheque is settled some other way, the clearing method records which — cleared normally, or returned and paid in cash, by transfer or in crypto.

Every cheque due date is an event on the calendar beside move-ins, expirations and payment-plan instalments, and the calendar filters by event type and by building. A quarter's collections can be read as a month block rather than assembled from four records.

A cheque due inside thirty days raises a notification, and it stays on the list until the cheque moves. A cheque still unbanked after its due date is raised again as overdue for thirty days. A cheque marked bounced raises a high-priority alert of its own, and a cheque_bounced email trigger is available for the templates.

No. A tenant sees the schedule and the four statuses in their portal, and that view is read-only — the database policy behind it grants select and nothing else.
The demo opens instantly, in the role this workflow belongs to, on sample data. There is no account to create and no form in front of it.