Vertical operating system
A rental business whose books check themselves
Carfleet runs a rental business end to end in English and Arabic — enquiry, contract, handover, invoice, ledger. It does not ask to be trusted with the money: every night it recalculates what should be true across bookings, invoices, payments and the ledger, and reports where its own records disagree.
- Status
- Live
- Category
- Vertical operating system
- For
- Rental and leasing operators in the UAE, from five vehicles to multi-branch fleets across several legal entities
- Languages
- English, Arabic, Russian
A rental operator's day runs across a dozen tools that know nothing about each other — WhatsApp for enquiries, a spreadsheet for the fleet, a PDF template for contracts, a card machine for deposits, one app for Salik and fines, the accountant's login for the books. The money leaks at the seams between them: a deposit nobody collected at the kerb, a late-return day that never got billed, a damage charge no one chased, an invoice raised before the car came back and never caught up. Each one is small, none of them is visible from any single screen, and nothing in the arrangement is capable of noticing.
- 01
One thread per customer across WhatsApp, Telegram, email and web chat, with an agent inside it that answers, quotes against the live fleet, sends the car's own photographs and holds the booking
- 02
A licence, Emirates ID or passport photographed into that chat fills the customer record field by field — no one re-types it, and every machine-read field is marked as machine-read
- 03
Each vehicle carries its whole life: VIN and documents, mileage, every service done and the one falling due, damage history, and what the car has earned against what it has cost
- 04
A handover job cannot close until the deposit is collected or a reason is logged, and a photograph taken after handover is recorded as late rather than backdated
- 05
Return settlement itemises fuel, excess kilometres, damage, Salik and fines into the closing document, with damage priced per vehicle model — a Nissan bumper and a Lamborghini bumper do not bill the same
- 06
Dubai Police fines and tolls arrive matched to the booking that was live at the time; a disputed fine pauses billing rather than vanishing, and a feed that is down says so instead of showing an empty table
- 07
No charge can be billed twice: the database itself refuses a second tax document against a supply already invoiced, rather than leaving it to a check someone can switch off
- 08
A double-entry ledger posted from the rentals themselves rather than re-typed into an accounting package, with the FTA VAT return computed from it — deposits excluded, credit notes netted
- 09
Every night it recalculates what should be true across bookings, invoices, payments and the ledger, and reports the disagreements as one dated digest rather than a stream of alerts
No re-typing
A licence photographed into the chat fills the customer record, field by field
Per car
Mileage, documents, every service and damage, and what it earned against what it cost
VAT-201
Computed from the ledger the rentals posted to, not rebuilt at quarter end
The money rules are written where the software cannot argue with them: a supply already invoiced cannot be invoiced again, a handover job will not close on an uncollected deposit. Where a rule cannot be enforced that way it is re-checked instead, every night, because we would rather be told than assume — and every guard in the build is there because the mistake it now blocks got past us once. That is also what makes it safe to let an agent quote, reserve and follow up: everything it touches is recalculated afterwards by something that cannot be talked round. We open client work the same way — agree the few things that must remain true, put them where they cannot be edited under deadline, and let the models sit above that line.
Invariant
A rental business whose books check themselves