Guide
Security deposit on a booking
Kasura records the security deposit on the booking and closes it as returned in full, partly kept, or fully kept.
On the booking
Staff set the security deposit amount when they create the booking, beside the rental price. The status starts unpaid. A booking deposit, if the shop takes one to hold the dates, is a different amount. So is any rental prepayment.
At release or check-in
When the customer picks up, or when the guest checks in, staff record how the security deposit is held: cash, a held passport, a held ID, or none. Cash can be marked received. A held document is not a cash payment.
At drop-off or check-out
When the customer brings the vehicle back, or when the guest checks out, staff close the security deposit. Vehicle drop-off can also record fuel, the odometer, and fees. Stay check-out does not use those vehicle fields.
Three outcomes
Staff choose one: returned in full, partly kept, or fully kept. Partly kept and fully kept need a reason. Kasura calculates the figure from the deposit and the fees staff entered. Staff decide whether a fee is fair.
Not the rental price
The rental payment and any rental prepayment are the price of the rental. A booking deposit holds the booking before it starts. The security deposit is what may be returned or kept for damage, fuel, or fees.
The record does not move money
Paid, unpaid, returned, or kept is a status on the booking. Kasura does not refund a card, place a card hold, or connect GCash, Maya, or QR Ph. Any cash the shop hands back happens at the counter, outside the record.
One booking, one outcome
The amount, the type, and the outcome stay on the same booking. There is no second deposit ledger inside Kasura.
What this guide does not mean
- It does not place a card hold or issue an automatic refund.
- It does not connect GCash, Maya, or QR Ph.
- It is not the rental prepayment and not a booking deposit.
- Recording the outcome does not move money.