By the Time You Can Prove It, the Tenant Has Been There Four Months
· 9 min read · Faceela
Every property system will show you an arrears figure. Very few will tell you whether any of it is recoverable, and those are different questions with different answers.
A debt becomes recoverable through a sequence: the tenancy is registered, the money falls due, it is demanded in a way that leaves a record, the demand is escalated formally and served in a way that can be proved, and only then does a case become possible. Each step has a date on it. A step performed without a date, or without a record, does not advance the sequence — it just feels like it did.
The uncomfortable part is the timing of the decisions. Whether you can act in month five was largely settled in week one, when somebody either did or did not register the contract, and in month two, when somebody either sent a dated formal demand or made a phone call.
The difference between owed and recoverable
Dubai Land Department's tenancy guidance is explicit on the first gate: judicial authorities and government departments may not consider a dispute or claim relating to a lease contract unless the contract is registered with RERA. That is the Ejari registration most people treat as a formality to be completed when someone gets round to it.
Treated as a formality, it is a formality right up until the day you need it, at which point it is the thing standing between you and the process entirely. A tenancy that is running, invoiced and in arrears, but never registered, is a commercial relationship with no route into the system that resolves it.
The second gate is evidence of demand. The Rental Disputes Centre publishes what it requires to register a first instance rental case, and the list is instructive as a specification rather than as legal advice: a copy of the latest Ejari lease, identification for the claimant, bank details, supporting documents such as the management contract, correspondence, notices, utility bills and cheques — and, for an eviction claim, a copy of the notarised notice together with the notification officer's report, or registered post with the acknowledgement receipt. Documents are submitted in Arabic or legally translated into it.
Read that as a data requirement and it stops being a legal topic. Every item on it is something a property system either captured at the time or did not. None of it can be reconstructed afterwards, because most of it is dated.
The filing requirements are, in effect, a schema. A system that does not hold those fields is a system that cannot produce a case.
This article is not legal guidance and should not be read as any. It is about which of those facts your software is capturing while the events are happening, which is the only part a systems decision affects.
Arrears is a clock, and most systems start it in the wrong place
Two figures get confused constantly, and the confusion always runs in the flattering direction.
Aged from the invoice date is what most receivable reports produce. It is easy, because the invoice is the document the ledger holds.
Aged from the date the instalment fell due is the real number. If the invoice was raised eleven days after the instalment date, the report understates the age of the debt by eleven days — and it does so silently, on every line, forever.
Where invoices are raised by hand rather than generated from the rent schedule, the gap is not a constant. It is however long the person was busy, which means the ageing report is a record of administrative capacity dressed as a record of tenant behaviour.
The same error has a second entrance. When a cheque bounces and the instalment is not reopened, the debt disappears from the ageing entirely while remaining perfectly real. The handling of that moment is the join between two subjects: a returned cheque is the day the clock starts, and if the instalment quietly stays closed, the clock never starts at all.
The ladder, and what each rung has to record
Recovery escalates. The escalation only works if each rung left something behind.
| Rung | What has to be recorded, not just done |
|---|---|
| Reminder | That it was sent, on what date, to which contact, about which instalment |
| Formal demand | The same, in writing, with the amount and the period stated |
| Notarised notice | The date, the method of service, and the proof of service as an attachment |
| Case | The filing, and everything above it assembled as one bundle |
| Judgment | The award, the costs, and whether the costs were ever billed |
| Enforcement or settlement | What was actually recovered, against what was owed |
Two rungs are where this usually falls apart.
The reminder rung is almost always performed over WhatsApp or by telephone. That is efficient and it is how the business runs, and it also means that months of diligent chasing produce no evidence that anything was ever demanded. The fix is not to stop calling. It is to make the record of the call cheaper to create than to skip, and attached to the instalment rather than to a person's recollection.
The notice rung fails differently. The notice is usually served properly, because by that point somebody senior is involved. What goes missing is its date and its proof of service, stored somewhere retrievable. A notice everyone remembers serving, with no dated proof attached to the tenancy, is a rung that has to be climbed again.
The failures that destroy a claim before anyone files it
None of these is dramatic. All of them are ordinary weeks.
The contract was never registered. Discovered at the point of filing, months in.
The rent invoice was typed by hand. So the invoice, the contract and the ledger are three opinions, and the amount claimed cannot be tied to the agreement without a person explaining it.
The schedule never balanced. The instalments do not add up to the contract value. The tenant's counsel finds this before you do.
Reminders exist only as chat messages. Retrievable in theory, dated in theory, and nobody is going to scroll two years of a group thread in front of a tribunal.
The bounced cheque was handled informally. No dated record that the instalment ever went unpaid.
The notice is in someone's email. Not on the tenancy, not dated in a field, and the person who sent it has left.
Costs were awarded and never billed. The one failure that happens after winning, and it is common, because by then everyone has moved on.
The unit was let under an expired mandate. The agent's own authority to act is now a question, before the tenant's conduct is even reached.
Each of those is a fact that existed at a moment and was not captured. That is the whole diagnosis. The remedy is not diligence, because diligence was present in every case above — it is that the capture has to happen where the event happens, by the person the event happens to, in one action.
What to make a vendor show you
- Show me arrears aged from the instalment due date, and prove it is not the invoice date.
- Bounce a cheque and show me the instalment reopen, the ageing move and a flag appear the same day.
- Log a reminder in ten seconds, from a phone, against a specific instalment.
- Show me the full chase history for one tenancy as a dated sequence.
- Attach a notarised notice with its service date, and show me it stored against the tenancy rather than in a folder.
- Try to escalate to a case without that notice. It should be refused.
- Produce the whole bundle for one tenancy — lease, ledger, cheques, correspondence, notices — as one export.
- Record a judgment with costs and show me the costs become a billable item rather than a note.
- Show me every live tenancy with no registration record on it.
Item 9 is the cheapest and the most alarming. Run it on your current portfolio this week. It takes one query and it tells you how much of your rent roll is currently outside the process that would enforce it.
Item 7 is the one that decides the vendor. Every system stores documents. A system that assembles the bundle in the order somebody else requires it is doing the actual work.
The short version
Arrears figures are easy and recoverability is hard, and the gap between them is made entirely of dates that were or were not captured while the events were happening.
The registration in week one, the ageing anchored to the instalment rather than the invoice, the bounce that reopens the debt, the reminder that leaves a record, the notice with its proof of service attached — none of those is a legal question at the moment it matters. Each is a field that was filled or left empty by somebody who was thinking about something else.
Proptec refuses to escalate to a case without the statutory notice and its date, refuses a hand-typed rent invoice against a live tenancy, and refuses a schedule that does not balance against the contract value. Those three refusals exist because they are the three failures that are invisible until the moment recovery depends on them.
The broader piece on why a lease is a shape a ledger has no field for is a tenancy is a schedule of things that have not happened yet, and the whole operation as one system is on the real estate and leasing page.