| Purpose | Understand which past-date and inactive reservation status changes are allowed, warned, or blocked, and what to do next. |
| Best for | Front Desk, Night Audit, Property Managers, and PMS Administrators |
| Use this when | You need to correct a reservation status after check-in, check-out, or No-Show, or a status option is greyed out. |
| Requirements | Permission to edit reservation statuses. Property-level Night Audit preferences may determine whether certain past-date reversions are allowed. |
| Expected result | You can identify whether a reservation status reversion is available and choose the correct next action without creating inconsistent inventory, folio, or reporting data. |
| Limitations | Some status changes are always blocked, regardless of the property's Night Audit preferences. Channel updates may also require separate action. |
Introduction
Cloudbeds PMS applies different rules when you change a reservation back to an earlier status. The result depends on the reservation's current status, the Cloudbeds business date, and, for some past-date changes, the property's Night Audit preferences.
These controls help prevent past stays from being reopened unintentionally, which can affect room occupancy, folio charges, financial records, and end-of-day reporting. Same-business-date corrections remain available where supported, while some past-date reversions display a warning or are blocked.
In day-to-day operations, you may need these options when a guest is checked in or checked out by mistake, when a guest arrives after being marked No-Show, or when staff discover that a reservation status from a previous business date needs to be corrected. This article helps you identify which correction path applies before changing the reservation.
Table of contents
- Who this affects and how
- Understand business date and status reversion
- Check which reservation status changes are available
- Return a Checked Out reservation to In-House
- Return an In-House reservation to Confirmed or Confirmation Pending
- Return a No-Show reservation to Confirmed or Confirmation Pending
- Common questions about reservation status changes
- Configure reservation status reversion preferences
- Why Cloudbeds warns about reactivating inactive reservations
Who this affects and how
Reservation status reversions affect front-office workflows, Night Audit timing, and property-level configuration differently depending on your role.
| Role | What to know |
|---|---|
| Front Desk | Use the reservation status menu to identify which corrections are available. Past-date changes may display a warning or be unavailable depending on the property's settings. Review the status change rules before changing an inactive reservation. |
| Night Audit | Night Audit advances the Cloudbeds business date. That business date determines whether applicable status corrections are treated as same-day or past-date changes. Review business date behavior. |
| Property Manager / General Manager | Understand the financial, reporting, and inventory impact of reopening past stays and decide whether the property should warn staff or block supported past-date reversions. |
| PMS Administrator | Configure the applicable Night Audit preferences as Warn or Not allow. |
Understand business date and status reversion
Cloudbeds uses the business date to determine whether certain reservation status changes are same-day corrections or past-date reversions. The business date advances when Night Audit runs. Until Night Audit advances the business date, the previous calendar day may still be treated as the current business date.
"Today" means the Cloudbeds business date: A reservation with an arrival or departure on the current business date can follow different status-change rules than a reservation whose arrival or departure is before the current business date.
When an applicable status change is on the same business date, Cloudbeds uses the normal confirmation flow. For a past-date change, the result may depend on whether the property's related preference is set to Warn or Not allow.
Warn
Cloudbeds displays a reactivation warning before continuing with an applicable past-date status change. You can:
- Create new reservation to leave the original reservation unchanged and create a new stay.
- Cancel to leave the reservation unchanged.
- Continue anyway to continue with the supported status reversion.
The warning gives you the option to continue with the supported reversion, cancel the change, or create a new reservation instead.
Not allow
Cloudbeds disables the applicable status option. Hover over the disabled option to see why that reservation cannot be changed to the selected status.
Check which reservation status changes are available
Before changing a reservation status, first identify what happened operationally. In most front desk situations, you are either correcting a mistake made during the current business date, correcting an older reservation after Night Audit has already run, or reactivating a guest who was previously marked No-Show.
The available result depends on the reservation's starting status, target status, business date, and the property's Night Audit preferences. Some transitions are always blocked and do not depend on the property's settings.
Common front desk situations
Use these examples to identify which workflow is closest to the situation you are correcting:
| Situation | Status change to consider | What to check first |
|---|---|---|
| A guest was checked out by mistake and should still be staying at the property. | Checked Out → In-House | Check whether the departure is on the current business date and whether another guest is already checked into the assigned room. |
| A guest was checked in by mistake and should still be Confirmed or Confirmation Pending. | In-House → Confirmed or Confirmation Pending | Check whether the arrival is on the current business date. Past-date changes may depend on the property's Warn or Not allow setting. |
| A guest arrives after the reservation was marked No-Show. | No-Show → Confirmed or Confirmation Pending | Check whether the property's No-Show reversion preference allows the change, then review the folio and room assignment after reactivation. |
| You need to reopen a reservation from a previous business date. | Depends on the current and target status | Check the applicable Night Audit preference and review the reactivation warning before continuing. |
Building your property's SOP: Consider documenting which reservation status corrections front desk staff can complete independently, when a manager should review a past-date reversion, and when staff should create a new reservation instead of changing the original stay.
Reservation status change reference
Use the table below after identifying the situation. It shows which status changes are supported, warned, or blocked.
| Current status | Change to | Same business date | Past date: Warn | Past date: Not allow |
|---|---|---|---|---|
| Checked Out | In-House | Normal confirmation | Reactivation warning, then confirmation | Blocked |
| Checked Out | Confirmed or Confirmation Pending | Always blocked | ||
| In-House | Confirmed or Confirmation Pending | Normal confirmation | Reactivation warning, then confirmation | Blocked |
| No-Show | Confirmed or Confirmation Pending | Not applicable. A No-Show reservation's arrival is already in the past. | Reactivation warning, then confirmation | Blocked |
| No-Show | In-House or Checked Out | Always blocked. Return the reservation to Confirmed or Confirmation Pending first, then check in the guest normally. | ||
Changes to Cancelled or No-Show, and changes out of Cancelled, are not controlled by these Night Audit reversion preferences.
Return a Checked Out reservation to In-House
Use this workflow when a guest should still be In-House but the reservation was checked out. A common example is correcting an accidental check-out made by front desk staff.
Cloudbeds first checks whether another guest is already checked into the assigned room.
The room must still be available for the checked-out guest: If another reservation is already checked into the assigned unit, Cloudbeds blocks the change to In-House regardless of the property's Warn or Not allow setting. Move the reservation to a different available unit before trying again.
If the room passes the occupancy check:
- Open the reservation and select In-House from the reservation status menu.
- If the departure is on the current business date, continue through the normal confirmation.
- If the departure is before the current business date:
- With Warn, review the reactivation warning and select Continue anyway to proceed.
- With Not allow, the In-House option is unavailable.
- Complete the final status-change confirmation.
When a status change is unavailable, the option appears disabled in the reservation status menu.
Return an In-House reservation to Confirmed or Confirmation Pending
Use this workflow when a reservation was checked in but should not yet be In-House. For example, a staff member may have checked in the wrong reservation or completed check-in before the guest was ready to be checked in.
An In-House reservation can return to Confirmed or Confirmation Pending when the correction is permitted for its arrival date and the property's Night Audit preference.
- Open the reservation and select Confirmed or Confirmation Pending from the reservation status menu.
- If the arrival is on the current business date, continue through the normal confirmation.
- If the arrival is before the current business date:
- With Warn, review the reactivation warning and select Continue anyway to proceed.
- With Not allow, the selected active status is unavailable.
- Complete the final confirmation.
Before confirming a manual status change, Cloudbeds may remind you that updating a reservation status can trigger automated processes, such as sending an email to the guest.
After you select the new status, review the reservation shown in the confirmation before completing the change.
Return a No-Show reservation to Confirmed or Confirmation Pending
Use this workflow when a guest arrives after the reservation was already marked No-Show. Return the reservation to Confirmed or Confirmation Pending first, then complete the normal check-in workflow if the guest is staying.
You cannot change a No-Show reservation directly to In-House or Checked Out.
The property's Return No-Show reservations to Confirmed or Confirmation Pending preference controls whether this status change is warned or blocked:
- With Warn, Cloudbeds displays the reactivation warning before the status change can continue.
- With Not allow, Confirmed and Confirmation Pending are unavailable.
When the change is allowed:
- Open the No-Show reservation.
- Select Confirmed or Confirmation Pending.
- Review the reactivation warning and select Continue anyway.
- Complete the final confirmation.
- If the guest has arrived, complete the normal check-in workflow after the reservation returns to an active status.
If the original room is still available, Cloudbeds reassigns it to the reservation.
The status menu shows Confirmed and Confirmation Pending as the supported active statuses for a No-Show reservation, while In-House and Checked Out remain unavailable.
After returning a No-Show reservation: Review the folio because pending charges, including the missed night, return to the reservation. If the No-Show was already reported to a connected channel, changing the status in Cloudbeds does not withdraw the No-Show from the channel, so update the reservation in the channel's extranet when needed.
Common questions about reservation status changes
These situations can help front desk teams understand why a status may still be available, why another option is blocked, and which correction path to use.
What should I do if a guest arrives after being marked No-Show?
Return the No-Show reservation to Confirmed or Confirmation Pending first. If the guest is staying, complete the normal check-in workflow after the reservation is active again.
Review the folio because pending charges, including the missed night, return to the reservation. If the No-Show was already reported to a connected channel, update the reservation in the channel's extranet when needed.
Why can I still correct a reservation from yesterday without a past-date warning?
Cloudbeds uses the business date rather than only the calendar date. Until Night Audit advances the business date, the previous calendar day may still be treated as the current business date, so an applicable correction can still follow the same-business-date confirmation flow.
Why can't I change a Checked Out reservation directly to Confirmed?
Checked Out reservations cannot return directly to Confirmed or Confirmation Pending. This transition is always blocked and does not depend on the property's Warn or Not allow setting.
If the guest should still be staying at the property, use the supported Checked Out → In-House correction when available.
Why is In-House unavailable for a Checked Out reservation?
For a past departure, the property's Return checked-out reservations with a past departure to In-House preference may block the change when it is set to Not allow.
Cloudbeds also blocks the change if another guest is already checked into the room assigned to the checked-out reservation.
When should I use Continue anyway versus Create new reservation?
Use Continue anyway when you are intentionally correcting the existing reservation and the status reversion is supported by your property's settings.
Use Create new reservation when the original reservation should remain unchanged or when the guest needs a separate new stay. Creating a new reservation keeps the previous reservation record intact.
Configure reservation status reversion preferences
Property administrators can control supported past-date reversions from the Night Audit preferences in General System Settings.
Go to Account Menu > Settings > System > General System Settings > Night Audit Preferences.
The following preferences control past-date reservation status reversions:
| Preference | Options | Controls |
|---|---|---|
| Return checked-out reservations with a past departure to In-House | Not allow / Warn | Checked Out → In-House when the departure is before the current business date |
| Revert In-House reservations with a past arrival to Confirmed or Confirmation Pending | Not allow / Warn | In-House → Confirmed / Confirmation Pending when the arrival is before the current business date |
| Return No-Show reservations to Confirmed or Confirmation Pending | Not allow / Warn | No-Show → Confirmed / Confirmation Pending |
Review General System Settings for the complete list of system preferences.
The three highlighted Night Audit preferences control the supported past-date reservation status reversions.
Why Cloudbeds warns about reactivating inactive reservations
Reopening a reservation that was already inactive can affect payments, accounting records, inventory, and reporting. The warning gives staff the option to leave the original reservation unchanged and create a new reservation instead.
Expand the sections below for the main operational risks to consider before continuing with a reactivation.
Payment and refund considerations
Payment authorizations and refunds may already have changed when a reservation became inactive. Returning the reservation to an active status does not guarantee that an earlier payment authorization is restored or that a previous refund is reversed.
Before continuing with a reactivated reservation, review its payment status and folio to confirm that the guest's charges and payments are still correct.
Accounting and reporting considerations
Reopening a reservation from a previous business date can change how a past stay is represented in Cloudbeds. This can affect occupancy, revenue, end-of-day reporting, and financial reconciliation.
When the original reservation should remain unchanged, use Create new reservation from the reactivation warning instead of continuing with the existing stay.
API and integration behavior
The Not allow setting also prevents the applicable status change through integrations. The Warn setting does not display an interactive warning to an integration, so an otherwise supported API status change can continue.
Related articles
Now that you understand how reservation status reversions work, review these resources for more information about Night Audit timing, reservation management, and related property settings:
Comments
Before you take the reversion functionality away, you would need to ensure we are able to change the rate on cancelled or no show reservations to zero. Currently, if a reservation is in either status, we are not able to change the room rate to zero. These reservations are then populating our account balances reports. For further example, let's say we have guest who books via an OTA.
However, they cancel well within the free cancellation window. I want that off of our account balance report so I have to go in and revert the reservation to pending, change the room rate to zero, and re cancel the reservation. It was frustrating to get used to this, but before Cloudbeds goes changing things yet again, maybe check in with properties to see why so many revisions are happening?
I agree with the statement above from Yuval. Its better for accounting purposes and balances to have all reservations 0 out after cancellations, no shows, and or when they are checked out.
Hello, Yuval Freincle,
Thank you for clearly sharing your specific requirements for reservation management to be able to change the rate on cancelled or no-show reservations, to zero.
Your feedback, including the OTA example, has already been escalated to our Product Team. They will review all these details (including your experience shared) for product re-evaluation.
We appreciate your valuable feedback, while we continue to improve the platform.
One option for Cloudbeds to consider adjusting would be the system having a setting that you could turn on to automatically change rates to zero when a cancellation is made
I agree with Yuval, we also have the same problem.
That was my first thought when receiving this email!
are positive account balances counted as room revenue on the daily reports?
Hello, James Schuler,
We have already forwarded your inquiry to our Support Team for dedicated assistance. They will contact you as soon as possible with more information.
We are here to help!
Please sign in to leave a comment.