Built for the Arab world — from Casablanca to Muscat
Property management that already understands post-dated cheques
Most property software was written for monthly card payments and month-to-month leases. Yours are annual contracts settled in four cheques handed over at signing. This one starts there.
No card required. No password to remember — we email you a link.
Cheques to bank
Next 30 days
| Cheque | Bank | Amount | Dated |
|---|---|---|---|
| 004417 | Emirates NBD | 32,500AED | 12 JanCleared |
| 004418 | Emirates NBD | 32,500AED | 12 AprCleared |
| 009120 | ADCB | 48,000AED | 02 JulOverdue |
| 004419 | Emirates NBD | 32,500AED | 12 JulDue |
Illustrative figures.
2 → 5,000
Units per account, same software
AR + EN
Full RTL layout, not a translation layer
4 layers
Enforcing tenant isolation
14 days
Free trial, every feature
The spreadsheet works until it does not
Every operator we speak to runs the same stack: a spreadsheet for the rent roll, a WhatsApp group per building, and a drawer of cheques someone has to remember to bank. It holds together at forty units. At four hundred it costs you a full-time hire, and at some point it costs you a cheque.
- A cheque presented late, or presented twice, because the register lived in someone’s head
- A renewal missed because the reminder was a calendar entry on one person’s laptop
- A resident calling the office to ask a question the system already knows the answer to
- A statement to an owner assembled by hand, and disputed because of it
Features
What you get today
Everything listed here is running software you can use during the trial. What is still being built is further down the page, said plainly.
Portfolio and rent roll
Properties, buildings and units with occupancy, availability and market rent. Headline figures are aggregated in SQL, so a 5,000-unit operator gets the same accurate number as a 5-unit landlord rather than a total quietly capped at the first page.
Post-dated cheque register
Every cheque you hold, what it is against, where it physically is, and when it is due to be banked. Overdue cheques sort above upcoming ones, because an unpresented cheque that is late is more urgent than one due next week — not less.
Leases and tenancies
Annual contracts quoted the way the region quotes them, with instalment counts, security deposits and multi-currency support from the first day. AED, SAR, QAR and EGP are first-class, not a settings page.
Resident portal
Your residents sign in on your own domain and see their tenancy, their balance, their invoices, their cheque schedule and their maintenance requests. Every question they can answer themselves is a call your office does not take.
Maintenance requests
Residents raise requests with a priority — including an emergency route, because a burst pipe at 2am is not a ticket. The unit and lease are derived from their own tenancy, so nobody can file against a flat that is not theirs.
A website for each client
Every account gets a public marketing site with vacancy listings on its own subdomain from the moment it exists, and can point a custom domain at it. Bilingual, indexed, and served from cache.
Arabic and English, properly
Right-to-left layout throughout, Arabic typefaces that shape ligatures correctly, and separate indexed URLs per language. Enforced by a lint rule that fails the build on a physical CSS property, so it cannot rot.
Billing, ledger and VAT
Rent invoices itself from each lease’s schedule into a double-entry ledger that refuses, at the database level, to store an unbalanced entry. Trial balance, P&L, balance sheet and a VAT return summed from the books — with a cross-check against the invoices, stated before you file.
Late fees and follow-up
Opt in to a late-fee policy and overdue invoices are assessed automatically — once each, enforced by the database, straight into the books, with no VAT on the fee because the law calls it compensation. Every arrear carries its chase history: reminders sent, when, by whom.
Printable bilingual tax invoices
Every invoice prints as a bilingual document carrying the registration number in force when it was issued — and on Saudi invoices, ZATCA’s Phase-1 QR, TLV-encoded over real byte lengths so Arabic names scan correctly.
Audit trail that cannot be edited
Who changed what, when, from which address, written in the same database transaction as the change itself. The table is append-only at the database level, so a correction is a new row and never a quiet rewrite.
Built for the region
Why regional software matters here
These are not settings we added. They are assumptions the system was built on, and retrofitting them into software designed for monthly card payments is why the international products feel wrong.
Cheques are the payment rail
Rent arrives as one to twelve post-dated cheques handed over at signing. That means custody, presentation dates, bounce handling and a legal escalation path — a first-class part of the data model, not a note in a comments field.
Leases are annual, not rolling
Rent is quoted and negotiated per year, with the instalment count as a separate commercial term. Software that models a monthly rent and multiplies by twelve gets renewals, proration and the cheque schedule all subtly wrong.
VAT that differs by country
5% in the UAE, 15% in Saudi Arabia, and different rules for residential and commercial. A single global tax rate is not a simplification here, it is an error.
Arabic is not a translation layer
Contracts, invoices and resident communication are bilingual, and the Arabic has to be right — correct shaping, correct direction, and a layout that mirrors rather than one with the text swapped in.
Resident portal
The office phone stops ringing
Residents sign in on your domain, with your name on it — no app to install and no password to reset.
- Their tenancy: contract reference, term, annual rent and instalment count
- What they owe right now, and what is overdue
- Every invoice, with the amount paid against each
- Their cheque schedule — which have cleared, which are still to be presented
- Maintenance requests raised and tracked, with an emergency route
- In Arabic or English, chosen per person
Security
Your data cannot reach another customer’s account
Enforced in four places, and tested on every single commit.
Most multi-tenant software separates customers with a WHERE clause and a code review. That works until one query is written without it. We assumed that query would eventually be written, and made it fail anyway.
The database refuses cross-account rows
PostgreSQL row-level security is enabled and FORCED on every table holding customer data. The application connects as a role with no permission to bypass it, so a query that forgets to scope itself returns nothing rather than someone else’s ledger.
Keys that cannot point at another account
Child records reference their parent through a composite key that includes the account id. A lease belonging to another customer is not forbidden by a policy — it is a key that does not exist.
Residents are narrowed inside their own building
A second layer of database policy limits each resident to their own tenancy. On a 360-unit building, staff see 340 leases and a resident sees one. That is a measured result from the test suite, not a design intention.
Tested, not asserted
Sixty automated tests run against a real PostgreSQL instance on every change, including a matrix that seeds two accounts and attempts to read across the boundary from every table. The build fails if any of them succeeds.
In development
Being built next
Listed here rather than above because it is honest, and because you will find out during the trial anyway. Dates are intentions, not commitments.
SoonBank reconciliation and owner statements
The double-entry ledger, per-property books, trial balance and VAT return are live. Reconciling them against the bank statement, and producing owner statements from the ledger rather than by hand, is the next accounting layer.
SoonContract registration packages
Ejari/Tawtheeq/Ejar references are recorded on the lease and the bilingual tax invoice already prints. What remains is the ready-to-file registration package — the documents each authority wants, assembled in the order it wants them.
SoonOwner portal
The same self-service the resident portal gives tenants, for the landlords whose properties you manage.
Try it against your own portfolio
Fourteen days, every feature, no card. Add a building and see whether it matches how you actually work.