Compare six fields that affect the stay
| Field | Compare | Why the difference matters |
|---|
| Reference and source | The external or direct reference and the hotel's corresponding record | Prevents reviewing or changing the wrong booking |
| Guest | The named guest and contact context needed for the stay | Helps reception recognise who is arriving |
| Room | Booked room type and any confirmed assignment or change | Protects the offer the guest purchased |
| Dates | Arrival, departure, and resulting nights | Changes capacity and what the hotel expects to provide |
| Booking state | Active, changed, cancelled, or another supported current state | Determines whether the stay still needs to be operated |
| Payment state | What is due, recorded, or confirmed, using the appropriate payment reference | Prevents confusing a booking confirmation with collected money |
The table is a comparison aid. It does not mean all six fields must appear in one screen. Open the booking details and the relevant source record when the calendar alone does not answer the question.
Kiyo's booking record keeps guest, stay, and payment status together. Payment state reflects payments recorded in or confirmed to Kiyo. A transfer received elsewhere must be recorded to appear, and a pending confirmation should remain pending until the appropriate evidence resolves it.
Reception can open the booking and check its payment information without hunting for a separate note. A room block shows the stay, but the payment record answers whether the guest still owes money.
What to check each morning
Each morning, check that the hotel's booking agrees with the source and any confirmed changes. The job is to prepare the right stay for the guest. Checking the bank account, accounts, or commission statement is separate work.
The questions are simple: who is arriving, which room did they book, what are the dates, is the booking still active, and what payment is confirmed? A wrong answer can change what reception promises.
The original source matters, but it may not tell the whole current story. A direct booking may have an agreed change. An OTA may have issued a revised reservation. A payment may have arrived through a separate route. Resolve the actual sequence instead of assuming whichever screen was opened last must be right.
Kiyo brings recorded direct and manual bookings together with reservations from connected and mapped OTA channels. A reservation left outside the system remains outside the calendar until it is entered. That condition is the reason a daily review still matters even when distribution is connected.
The PMS versus channel manager guide explains how those systems' jobs relate. The daily check confirms that the stay received from the source matches what reception is preparing.
Start with bookings that changed
A small front desk rarely has time to re-read every reservation from the beginning. Prioritise the bookings where an error is more likely to affect someone soon.
Start with upcoming arrivals, new reservations since the last review, changed dates or room types, cancellations, and records with unclear payment information. Include unresolved channel updates and manual bookings received during a busy shift.
This is an exception-first routine, not an instruction to ignore the rest of the calendar forever. Periodically review how bookings enter the system and whether any source is being missed. A repeated missing source is a workflow problem, not a reason to keep checking the same bookings by hand indefinitely.
Kiyo's booking and distribution overview describes recorded reservations alongside channel and payment exceptions. The useful benefit for reception is being able to begin from an identifiable booking rather than searching disconnected notes for a guest name.
Keep the review window manageable. The team should finish with specific resolved discrepancies and named open actions, not a large spreadsheet nobody will maintain tomorrow.
Match the booking before changing it
A guest name is a useful clue, but it is not always a unique identifier. A guest may have two rooms, two separate stays, or a booking made by another person.
Start with the reservation reference and source. Then compare the guest, room type, and dates. For a connected OTA booking, retain the external reference as well as the hotel's own identifier so the same stay can be found on both sides.
Do not merge or delete similar-looking bookings simply because the names match. First establish whether they represent duplicates, separate rooms, or a changed reservation. A mistaken cleanup can remove a valid stay.
Kiyo's public booking workflow keeps the source and external reference with the reservation context. That makes it easier to follow the same stay across the channel and the hotel's record. Correct connections and successful processing remain necessary for external reservations to appear.
If a telephone or WhatsApp booking was entered manually, check the agreed details against the hotel's actual confirmation. Do not treat an informal enquiry as a confirmed room sale merely because it appears in a message thread.
Finish the check with one stay the team can trust
Return to the illustrative three-night booking in the opening. The latest confirmed change on the original channel shows two nights. Reception matches the external reference, checks the room and dates, and follows the property's correction process. The hotel booking and affected availability now agree with the confirmed two-night stay.
The deposit remains a separate question. The manager checks the payment record before changing its status. The incoming shift receives a corrected stay and one clear payment question, rather than three conflicting stories.
Kiyo makes this a shorter investigation by keeping the guest, dates, room, booking source, and recorded payment status with the reservation. Reception can open the stay it has already found, compare the source reference, and see which detail needs checking. Money taken outside the system still needs to be recorded or confirmed before it appears.
The guest feels the difference at check-in. Staff can confirm the correct dates instead of asking them to explain a change they already made. The receptionist can continue the job without calling the colleague who went home.
For connected channels, Kiyo can receive new bookings, changes, and cancellations and update affected availability after processing. If an update is delayed or fails, investigate the connection rather than adding a second booking just to make the calendar look right.
The availability guide for several OTAs covers the ongoing room and channel work. If the same difference returns, fix the cause instead of making reception repeat the correction every morning.
Check the payment separately
A guest may hold a confirmed reservation with an unpaid balance. Another may have paid through a channel whose payout has not reached the hotel. Those are different situations, and neither should be reduced to a vague label such as paid booking.
Check the amount, currency, payment reference, and confirmed state in the appropriate record. A screenshot sent by a guest can help identify a transaction to investigate; it should not automatically overwrite the hotel's confirmed payment position.
Do not request a second payment simply because an update is slow. Equally, do not mark a balance settled just to remove it from an arrival checklist. Give the uncertain payment to the person authorised to verify it.
Kiyo's booking/payment context is useful because the question remains attached to the stay. It does not turn a successful reservation into proof of bank settlement. The hotel revenue, cash flow, and profit guide explains why recorded booking value and received cash can differ.
OTA commission is another separate check. The OTA costs guide helps with distribution economics; this routine is about making tomorrow's booking accurate enough to operate.
Give every open discrepancy a next action
A useful unresolved item says which booking is affected, what disagrees, who owns the check, and when the team needs an answer. “Check booking later” leaves all four unclear.
For example, an internal note might say that the source shows two nights while the hotel record shows three, with the manager responsible for checking the latest revision before the arrival review. This describes the work without inventing a resolution.
Keep the guest promise aligned with what is known. If the hotel is still checking an arrival change, do not send a message presenting it as completed. Once the discrepancy is resolved, make sure the team uses the corrected information in its next guest contact.
The front desk handover guide provides the wider pattern for passing unfinished work between shifts. Add unfinished booking checks to that handover, so the next shift does not depend on a private list on one person's laptop.
For an independent hotel in Indonesia, this can be a short review between reception and the manager. Its value is the quality of the decisions, not the size of the meeting.
Act immediately if two guests need the same room
Some discrepancies are administrative. Others show that the hotel cannot fulfil two active stays with the available room inventory.
When the review reveals a real conflict, move into guest protection and containment. Do not leave it on tomorrow's list just because some references still need checking. Preserve the evidence, stop the problem expanding through the property's established process, and involve the person who can agree a guest solution.
The double-booking response guide owns that incident workflow. This article's job is to find the mismatch earlier and keep the record accurate; it does not replace recovery once the conflict exists.
Stop the same mistake coming back
After resolving an item, ask why it happened. If manual bookings repeatedly arrive late, the team needs a clearer entry process. If the wrong room type repeatedly appears from one channel, examine the mapping. If payment questions dominate, review how external payments are recorded and verified.
Do not count the number of checks as proof that the system improved. Look for fewer repeat causes, faster resolution of known exceptions, and clearer arrival records. These are observations to review, not promised Kiyo outcomes.
Kiyo is a practical fit when the hotel's bookings, channel context, and payment questions are scattered across separate tools. A connected record gives reception a clearer place to start and a way to keep the discrepancy attached to the stay. The daily habit completes that value: compare, resolve, and hand over anything still open.
