Opera
Cloud

Opera Cloud should be treated as the system of record for guest reservations, folios, payment status, cashiering activity, routing, room assignments, and end-of-day procedures. Agents should use this guide as a practical reference during live operations, especially when reviewing arrivals, preparing for check-in, checking due-outs, verifying billing, or supporting Night Audit. This guide is not a replacement for manager direction, Hyatt standards, or property-specific SOPs; when something appears unusual, the correct response is to pause, document what was found, and escalate before making a billing or reservation change that could affect the guest experience.

Before checking in a guest, the agent should review the reservation carefully enough to understand what the guest is expecting and what the hotel is financially responsible for collecting. At minimum, confirm the guest name, dates, room type, rate code, payment method, guarantee method, routing instructions, alerts, traces, comments, and any special requests. If the reservation is prepaid, third-party, direct bill, group-related, award-related, or has any unusual notes, the agent should slow down and verify the setup before proceeding.

Reservation review is not just a clerical step. It is the point where the Front Office prevents avoidable guest issues. A guest should not discover at check-in that routing was missed, a virtual card was not prepared, a billing note was ignored, or a special request was visible in the system but never acknowledged. If something does not look right, document what you see and ask a supervisor or manager before making assumptions.

Opera Cloud billing review should focus on who is responsible for each charge and whether the folio is set up to support that responsibility. Agents should verify whether room and tax, incidentals, parking, package charges, resort or destination fees, and other charges should remain on the guest folio or route elsewhere. The presence of a note does not automatically mean billing is correct; the folio setup must match the instruction.

For third-party reservations, confirm whether the reservation is guest-pay, prepaid, or virtual-card supported. If a virtual card is involved, verify that the correct folio window and routing instructions are in place before check-in. For award stays, confirm the expected routing and benefit handling according to current property procedure. For direct bill, group, or Sertifi-supported reservations, verify that the required authorization or billing documentation exists before relying on the instruction.

High-balance and authorization concerns should be handled proactively. When a guest exceeds the approved credit limit or a payment method declines, the issue should be documented and communicated clearly in the shift handoff. The goal is not only to collect payment, but to prevent the next shift from inheriting an unexplained balance or a guest interaction with no context.

Due-outs should be reviewed throughout the day and should not be left unresolved without notes. If a room is still due out, the agent should determine whether the guest has extended, requested late checkout, failed to depart, has an unresolved balance, or needs manager follow-up. If a due-out cannot be checked out, the reason must be documented so the next shift understands exactly what remains pending.

Open folios require the same discipline. An open folio with no explanation creates unnecessary confusion for the next agent, Night Audit, and leadership. Every unresolved folio should have a clear note explaining the reason it remains open, what action has already been taken, and what the next step should be.

Cashiering should be closed carefully at the end of the shift. Agents should ensure their bank is counted, discrepancies are reported, required receipts or supporting documents are organized, and the cashier report is closed according to property procedure. A cashier report should not be treated as a formality; it is part of the financial record for the shift.

Any unusual payment issue, adjustment, refund, correction, disputed charge, or unresolved balance should be included in the shift handoff. If a manager would need context to understand the transaction later, that context should be documented before the agent leaves.

Night Audit should verify that the property is ready for End of Day before audit is started. This includes reviewing arrivals, no-shows, due-outs, open folios, payment concerns, routing concerns, outstanding deposits, cashier status, and unresolved guest issues. Audit should be run with enough time to identify and resolve errors before the morning operation begins.

If Opera Cloud stops during audit, produces an error, or identifies a posting issue, the auditor should not continue blindly. The issue should be reviewed, corrected when appropriate, and escalated when needed. If system support is required, follow property procedure and document the issue in the shift report so the AM team understands what occurred.

Agents should escalate when a billing setup is unclear, a virtual card does not appear to be working, a guest disputes charges, a direct bill or group instruction is incomplete, a due-out cannot be resolved, a folio remains open without explanation, a payment method declines on a high balance, or a Night Audit issue may affect the business date. Asking for help before taking action is always better than creating a larger correction later.

Good escalation includes specific information. Instead of saying, “Opera is not working,” explain what screen you are on, what reservation or folio is affected, what action you attempted, what error or concern appeared, and what needs to happen next. Clear communication helps leadership solve the issue faster and protects the next shift from confusion.

Before leaving an Opera Cloud task, ask yourself whether the next person would understand what you did, what still needs attention, and why the reservation or folio looks the way it does. If the answer is no, add a note, include it in the shift report, or escalate it. Operational consistency depends on leaving a clear trail for the next person.