Why the payment question gets lost between people
A deposit often travels through more than one conversation. The guest speaks to reception, the owner sends bank details, and a different colleague checks the bank account. If the result stays with the person who handled it, the next shift sees only part of the story.
The problem is not always missing money. It can be missing information about money that was received. It can also be an unclear agreement: one colleague expected a deposit while another told the guest to pay at the property.
Both situations create work at the worst time. A guest arrives expecting a simple check-in and is asked to explain an earlier payment. Reception starts searching old messages. The manager is interrupted to confirm an arrangement made days ago.
A clearer process moves that work before arrival. The person checking the list does not need to solve every financial question personally. They need to separate what is already clear from what needs an authorized colleague's attention.
This is why a good follow-up list is usually smaller than the arrival list. Many guests have already met their current payment terms. Others have a future deadline. The important group is the bookings with a missing amount, unclear evidence or an agreement the team has not yet understood.
Start with the amount due now, not the whole stay balance
A booking can have an unpaid balance without having an overdue deposit. Those two amounts should not be treated as the same thing.
Suppose a stay costs Rp2,000,000. The guest agreed to pay Rp500,000 before arrival and the remaining Rp1,500,000 at the property. Once the deposit is confirmed, the guest has met the current requirement. Sending a message that says the booking is overdue because Rp1,500,000 remains would contradict the agreement.
Read the original confirmation and any later agreed changes. Look for the deposit amount, payment deadline and the party responsible for collecting it. If the terms are unclear, resolve that before writing a reminder.
For an OTA booking, the channel may collect from the guest under the applicable arrangement. The hotel's bank statement may show a later payout. A payout that has not arrived does not automatically mean the guest owes reception another payment.
Our local payment guide explains the different ways a guest might pay. The question here is narrower: what has this guest agreed to pay before arrival, and has that requirement been met?
Make “paid” mean something the next shift can understand
The word paid can hide several meanings. The guest clicked a payment button. A screenshot was sent. A payment service confirmed success. A colleague recorded a bank transfer. The hotel received a payout. These events are connected, but they are not interchangeable.
Agree which record the team checks for the payment route in use. For a bank transfer, an authorized colleague may need to match the incoming amount and reference. For an online payment, the relevant payment record should show the successful result required by that flow.
A screenshot is useful when locating a transaction. It should not be the only reason to mark the booking paid. Equally, a screenshot that has not yet been checked is not proof that the guest failed to pay.
Use plain descriptions in the handover: “payment confirmed,” “waiting for the bank check,” “partly paid” or “not due until Tuesday.” These tell the next person what to do. A single unclear color or a note saying “check money” does not.
Kiyo's hotel payment tools keep payment status and reference beside the booking. The information reflects what is recorded in or confirmed to Kiyo. Money received outside the system still needs the appropriate record and check before colleagues can rely on it there.
Walk through six bookings before sending any reminders
The following example is fictional. The team is reviewing arrivals on 20 September. The amounts are in IDR and describe deposits, not the full value of every stay. “Confirmed” here means the correct payment evidence has been checked; it does not automatically mean a bank payout is complete.
Booking A: the deposit is complete
The guest arrives on 21 September. A deposit of Rp500,000 was due on 19 September, and the full Rp500,000 is confirmed. Reception leaves this booking off the deposit reminder list. Any balance due at the property remains governed by the agreed terms.
Booking B: only part of the deposit arrived
This guest also arrives on 21 September. The deposit was Rp600,000, due on 19 September, but only Rp300,000 is confirmed. Reception follows up on the remaining Rp300,000. Asking for Rp600,000 again would ignore the payment already received.
Booking C: the guest sent evidence that still needs checking
The guest arrives on 22 September. The agreed deposit is Rp400,000, due on 20 September. A screenshot has arrived, but no amount has yet been verified. The finance contact checks the bank or payment record before reception sends a demand. The open question is whether the payment can be confirmed, not whether the guest should be accused of missing it.
Booking D: the deadline has not arrived
The guest arrives on 23 September. Their Rp700,000 deposit is due on 22 September, and no payment is recorded yet. Reception keeps the agreed deadline and checks again on that date. This booking is not overdue on 20 September.
Booking E: payment at the property was agreed
The guest arrives on 21 September and was not asked for a deposit. Nothing has been received, which is consistent with the agreement. Reception prepares for payment at the property rather than inventing a new pre-arrival requirement.
Booking F: an overdue deposit needs a decision
The guest arrives on 24 September. A deposit of Rp500,000 was due on 18 September, and no payment evidence has been received. The manager reviews the terms and agrees the next contact. The missing deposit does not by itself authorize cancellation or release of the room.
All six bookings might look unfinished on a quick balance check. Only some need a payment reminder. Others need verification, a later review or no deposit action at all. That is the distinction the team needs before contacting guests.
Keep the follow-up sheet small enough to use
For your own list, record the booking reference and arrival date first. Then add the agreed deposit, due date, confirmed amount, remaining question, responsible person and next action. Those fields let another shift continue the work without rebuilding it.
A useful entry might read: “Booking B, arriving 21 September. Deposit Rp600,000 due 19 September; Rp300,000 confirmed. Reception to follow up on Rp300,000 remaining.” The next person can understand the amount and action immediately.
For Booking C, the note should sound different: “Screenshot received; finance contact checking payment evidence before a reminder is sent.” Do not turn an unfinished verification into an unpaid label merely to simplify the sheet.
Keep detailed bank information and unnecessary guest data out of the overview. Link to the appropriate restricted record when an authorized person needs more detail. This is a simple working list for your team, separate from Kiyo’s booking screens.
Use the booking calendar to connect the list to upcoming stays. Keeping arrival and payment work close together makes the list easier to prioritize than a separate collection of screenshots with no clear booking attached.
Follow up in a way that does not make the guest start again
A useful reminder recognizes what the hotel already knows. If part of the deposit was received, acknowledge it. If evidence is being checked, tell the guest that rather than asking them to repeat the whole payment.
For the partial-payment example, reception could explain that Rp300,000 has been confirmed against the Rp600,000 deposit and ask about the remaining Rp300,000 under the agreed terms. Include the correct booking reference and the appropriate payment route if another payment is needed.
Keep the wording respectful. A guest may have made an honest mistake, misunderstood the deadline or completed a payment that has not yet been matched. The purpose of the message is to resolve the next step, not to assign blame.
If the guest disputes the amount or the agreement, involve the person who can review the original terms. Do not let several colleagues send different instructions. Give the guest one current answer after the hotel has established what is correct.
For a QRIS-specific question, use our QRIS guide for hotels. The payment method affects where the evidence is checked, but the principle stays the same: find the correct booking, confirm the result and ask only for what remains due.
Where Kiyo makes the daily work easier
The practical problem is often the distance between the reservation and the payment conversation. One is in the calendar, one is in a private chat and the answer about the bank transfer is in the owner's memory.
Kiyo's booking record brings the guest, dates and recorded payment information together. Reception can open the stay and see the payment status associated with it, instead of starting a search across unrelated notes.
That changes the handover. The evening colleague can leave one clear open question attached to an identifiable stay. The morning colleague can find the same booking and continue from that point. A payment confirmed or entered through the appropriate process can be reflected in the record the team uses.
The system does not remove the need for an authorized person to check money received elsewhere. It also does not turn a paid booking into proof that settlement reached the bank. Those are real boundaries, but they do not reduce the value of keeping the booking question and payment information together.
This is the reason to consider Kiyo: less searching to understand one guest's position, and a clearer starting point for the person who must resolve the remaining question. The team can spend its time finishing the check instead of reconstructing it.
Finish the handover with actions, not another pile of messages
Before the review ends, remove resolved bookings from the action list. Leave only the items another person needs to handle, with a clear owner and next review point. That prevents the next shift from sending a second reminder after the first issue was already settled.
Keep urgent arrivals in view, but do not ignore a later booking whose deadline has passed. The order should reflect both the arrival date and the unresolved payment question. Ask a manager to decide any action that changes the guest's booking or agreed terms.
The wider pre-arrival booking check includes rooms, dates and reservation changes. The front-desk handover guide explains how to pass unfinished work between shifts. Your deposit list should connect to those routines rather than become another private spreadsheet only one person understands.
Return to tomorrow's arrivals. Reception should now be able to explain which guests have met their deposit terms, which bookings need a bank or payment check, and who will contact the guests with an actual amount still due.
That is a calmer beginning to check-in. The guest is not asked to prove the same payment twice, and the hotel does not mistake an unclear record for a clear answer.
