A Tenancy Is a Schedule of Things That Have Not Happened Yet
· 11 min read · Faceela
An accounting system is a record of things that have already happened. An invoice was raised. A payment landed. A cost was incurred. Every figure in it is backward-looking, and that is not a criticism — it is the definition. A ledger that recorded intentions would be worthless.
A tenancy is the opposite kind of object. On the day it is signed, almost nothing about it has happened. What exists is a schedule: rent falling due on stated dates, cheques to be presented on stated dates, a deposit held against a condition nobody has inspected yet, a renewal window that opens in ten months, and an obligation to hand somebody else most of the money.
Between those two statements sits the whole problem. The business runs on the schedule. The system holds the history. Nothing in the ledger knows that a cheque should reach the bank on Tuesday, and nothing in the ledger will complain on Wednesday when it did not.
Why the ledger cannot hold a lease
Ask an accounting system for a list of everything owed to you and it will answer confidently. It will list the invoices it has raised.
That is not the same list. A tenancy running for a year, invoiced quarterly, has nine months of contractual rent that no invoice exists for yet. It is owed to you in every sense that matters commercially, and it is absent from every receivable report you own, because the receivable report is a list of documents rather than a list of obligations.
The gap runs the other way too. An invoice raised for a tenancy that was terminated in month three is a receivable the system will keep chasing and the tribunal will not support. The ledger has no way of knowing the contract behind it stopped, because the contract was never a record it held.
The ledger can tell you what you billed. It cannot tell you what you agreed, and the difference between those is the business.
This is the same structural point as outgrowing your accounting software, sharpened by a particular industry. Most businesses outgrow their books because volume rises. A leasing business outgrows them the day the first contract is signed, because the contract is a shape the software has no field for.
The chain, and where each link actually breaks
The work runs in one direction, from an enquiry about a unit to money in an owner's account. Written out, it is not complicated. It is just longer than any one department sees.
An enquiry arrives and somebody views the unit. An offer is made with terms on it. A contract is signed, and a rent schedule is built that has to add up to the contract value. Cheques are collected and held. Invoices are raised on the schedule, not by hand. Receipts are recorded as cheques clear. Arrears are chased up a ladder that ends in a formal notice. Work orders are raised and closed against the unit. A statement is produced for the owner: collected, less fees, less spend. He is paid. The tenancy renews at a lawful figure, or it ends and the deposit is settled against an inspection.
Twelve links. Most property businesses run them across three systems and a shared drive, and the breaks are always in the same places.
| Link | What breaks, and how you find out |
|---|---|
| Contract to rent schedule | The instalments do not add up to the contract value. The tenant finds it in year two, with a calculator |
| Schedule to invoice | Somebody types the rent invoice by hand, so the invoice and the contract are now two opinions |
| Cheque to bank | The presentation date lives in the head of whoever holds the cheques |
| Bounce to arrears | A returned cheque was never converted back into money owed, so the ageing is wrong and looks fine |
| Reminder to notice | Chasing happened over WhatsApp, so there is no dated evidence anything was demanded |
| Receipt to owner | He is paid from a cheque that has not cleared, which means he is paid from your money |
| Spend to mandate | A repair was authorised above the threshold the owner agreed, and nobody asked him |
| Deposit to exit | It was refunded before the inspection, so the only leverage that existed is gone |
None of those is exotic and none is a failure of care. Each one is a place where a fact left one system and had to be carried into another by a person, and people carry things reliably right up until the week they are busy.
The four figures nobody can produce on demand
Here is a faster diagnostic than any requirements document. Ask for these four numbers, now, without warning, and time the answer.
Occupancy, by unit, this minute. Not last month's report. Vacancy is the only cost in this business that accrues continuously and silently, and in most portfolios it is a figure somebody compiles when it is requested — which means nobody looks at it between requests.
Arrears by unit, aged from the date the instalment fell due. Aged from the invoice date is a different and easier number, and it is the one most systems produce. If the invoice was raised late, the ageing understates the problem by exactly the length of the delay.
One owner's balance, right now. Not at month end. An owner asking what he is owed on the fourteenth is asking a reasonable question, and in most operations the honest answer is that it will take until the end of the month to work out.
Which cheques have to reach the bank in the next seven days. This is the shortest question on the list and the one that costs the most when it is answered from memory.
If any of the four requires a person to assemble it, the figure does not exist in your business. It exists in that person, and it is available at the speed of that person, which is not the speed the money moves at.
What is specific to doing this in the Emirates
A great deal of property software is written for markets where rent arrives monthly by direct debit and a lease is a document nobody registers. Four things here are different enough to change the design rather than the configuration.
Rent arrives as paper, in advance. A year's rent is commonly handed over as a small stack of post-dated cheques written months before they are due. That turns collection into a custody and calendar problem before it is ever an accounting one, and it is enough of a subject on its own: the cheque in the drawer is not an asset until somebody walks it to the bank.
The lease has to be registered to be enforceable. Dubai Land Department's tenancy guidance is explicit that judicial authorities and government departments may not consider a dispute or claim relating to a lease contract unless the contract is registered with RERA — the Ejari registration most people think of as paperwork. A registration skipped in week one is a case you cannot bring in month five.
Rent increases are indexed rather than negotiated freely. DLD publishes a rental index that produces the applicable figure for a unit from its area, type and the contract details. A renewal argued from a figure somebody assumed is a renewal that can be undone.
The tax treatment is decided by the unit, not the customer. The Federal Tax Authority treats supplies of commercial property as standard-rated, while supplies of residential property are generally exempt — see the FTA's own real estate guidance. One landlord with a mixed building therefore has two treatments running through one set of books, resolved per invoice line by what the unit is used for. Set that as a default on the customer and a year of returns goes out misfiled, quietly, with nothing to flag it.
That last one is worth dwelling on, because it is the failure that survives longest. It produces valid invoices, a balanced ledger and a clean trial balance. It is only wrong in a way that becomes visible when somebody asks — which is the same shape as a dashboard that is technically correct and still misleading.
The parts that are somebody else's money
A property manager who manages property he does not own is holding cash that is not his. That single fact reorganises everything downstream of collection, and it is the part generic software handles worst.
The rent collected on a unit is the owner's, less the management fee, less whatever was spent with his authority. Until it is paid over, it is a liability on your balance sheet rather than revenue. Deposits are not yours either, and they are not rent, and mixing the two is the most common reason a deposit cannot be returned cleanly at the end.
The obligations that follow are all mechanical: pay only from receipts that have actually cleared, spend only within the mandate the owner signed, and produce a statement that reconciles to both. Those are covered properly in the money in your account is not your money, because they are the half of the business most likely to end in an argument with the person paying you.
The same logic runs, differently, where the money belongs to a body of owners rather than to one: service charges and the budget that spends them is the same trust problem with a committee attached.
What to make a vendor show you
On a live system, on a real portfolio, not on slides. In this order.
- Build a tenancy whose instalments do not add up to the contract value, and show me the system refuse it.
- Activate a tenancy the held cheques do not cover, and show me the system refuse that too.
- Raise a rent invoice by hand against a live contract. If it lets you, the contract is decoration.
- Show me the cheques due in the next seven days, across the whole portfolio, on one screen.
- Bounce one of them and show me the arrears move, the tenant flag appear, and the instalment reopen.
- Show me one owner's balance, mid-month, with the receipts behind it and the uncleared ones excluded.
- Show me occupancy by unit without anyone opening a spreadsheet.
- Take a residential unit and a commercial unit in the same building and show me the two tax treatments resolving per line.
Items 1 and 2 are the ones that separate a product from a demo. Any system can record a schedule. A system that refuses an unbalanced one is making a promise about every figure downstream of it, and refusals are difficult to build and impossible to add later.
Item 3 is the quiet one. Most property modules pass the first two and fail this, because leaving the manual invoice open looks like flexibility and is actually a permanent hole in the reconciliation.
The short version
A tenancy is a forward schedule. A ledger is a backward record. Running a leasing business on a ledger means a person stands between the two, carrying dates and obligations from one to the other, and the business is exactly as reliable as that person's week.
The fix is not more discipline. It is holding the unit, the contract, the instrument and the mandate as records that relate to each other, so that the invoice comes from the contract, the arrears come from the instalment, and the owner's balance is a real liability rather than something compiled on request.
That is what Proptec is — our property and facilities management suite on Odoo, live in six companies, including a UAE portfolio of over five thousand units and a developer in Egypt who has been on it since 2019. What it refuses to do is listed on that page in full, which is the part worth reading first.
What the whole shape looks like as one system rather than three is on the real estate and leasing page, and the businesses we have built this for are in the case studies.