Long-term car rental: months built from exact rental days

The system has no billing day and no calendar anchor. Hand the car over on the 17th at 14:30 — the charge arrives every day at 14:30, however many months the agreement lasts. The monthly price is expressed as a daily rate, so partial first and last months stop being a subject of negotiation: what is counted is the time the car is in the client's hands, not dates on a calendar.

Pricing

24-hour rental days; the monthly price is set by the daily rate

First charge

24 hours after handover — postpaid

Deposit

once at handover, tracked separately; under postpay the fleet is covered by a deposit several times the daily rate

Mileage

limit and overage as a tariff rule — planned; charges are counted by time in the client's hands

Late fee

not charged: an overdue day gets flagged and calls in a person

The car went in for repairs, you are waiting for a part, you met the client halfway — the manager puts the charges on pause without filing a fake return. A reason for the pause is mandatory: a pause without a reason is indistinguishable from a mistake. A return record stops the clock the same way — both events write to the same log, and there are never two versions of what happened.

A replacement car is a new period of the same agreement, not a new agreement: the client keeps driving, the accumulated time continues from where it stopped, and the history remembers exactly who was in which car on each of the days.

The system stores the terms, not paper: the daily rate, the charge interval, the deposit and the debiting order — as a snapshot that exists before confirmation and does not change retroactively. The driver confirms the terms in their workspace, and the time, network address and device are saved together with the confirmation. Until the terms are confirmed, the car cannot be handed over — that is a server check, not manager discipline.

In a dispute, the balance due rests on this trail: you can see not only "what was signed" but exactly what was shown to the person and when they agreed.

Every rental day the system reads the balance and debits whatever is there: with a charge of 12 000 ₸ and a balance of 3 000 ₸, 3 000 is debited and 9 000 becomes balance due. After 24 hours an unpaid rental day is marked overdue: the driver gets a reminder, and the fleet sees it on the "Outstanding balances" screen.

You can pay in any portions: bring 100 000 ₸ against 84 000 ₸ due — the balance due is cleared, 16 000 sits on the balance and goes toward the next rental days. No separate notion of "overpayment" is needed. A "cash handed over" request protects against a false overdue mark until the cashier confirms the payment — but only the cash desk actually settles the balance due.

In the workspace the driver sees the terms, the car, the day-by-day balance due and traffic fines — and does not see who owns the car or what the fleet's economics look like. The partner who owns the car sees its utilization and earnings — and does not see the driver's personal data: the driver is shown anonymized, and the client base stays with the fleet.

The fleet sees everything of its own: the day's queue, where each car is, outstanding balances, deposits, document expiry dates. Three workspaces read the same data, so there is no one to argue with about the numbers — and nothing to argue about.

Rental money goes to the fleet directly: in cash or by transfer. The cashier records the payment, specifying the legal entity and the channel — a fleet may have several, and sole proprietor revenue is not mixed with LLP revenue. Rent does not pass through fleeTau accounts, and neither does card data.

The subscription is counted by active cars — those with a rental running during the month. Idle and archived cars cost nothing, the first three cars are free, and annual payment takes 20 percent off.