Ability to Correct Closed Items with Future Consumption Dates
Summary
Provide hotels with a controlled way to correct closed bill items that were accidentally posted with a future consumption date, even though the item was actually consumed in the past and already charged on a guest bill.
Problem
In the “Add Product [+]” workflow, users occasionally select an incorrect future consumption date by mistake. When this happens:
- The item is still closed on the bill at the correct amount and date of posting.
- However, the consumption date remains in the future.
- As a result, the item continues to appear on the Guest Ledger until that incorrect date becomes past.
- Existing workflows such as Rebate or Reissue do not help because they cannot modify the consumption period of a closed bill item.
This leads to confusion during reconciliation, inaccurate ledger reporting, and unnecessary follow‑up for staff.
Impact on Hotels
- Ledger accuracy is compromised.
- Accounting teams may misinterpret future‑dated consumption as unbilled revenue.
- Front office and back office teams spend time investigating items that appear open but are actually already settled.
- Correcting a simple date mistake requires workarounds or support intervention.
Requested Enhancement
Introduce a secure, time‑bound option for hotels to correct the consumption date of closed items when the date was entered incorrectly.
Ideal behavior:
- Hotels can update the consumption date to:
- The date the item was actually consumed, or
- The date the transaction was performed.
- A short correction interval (e.g., same day, 24 hours, or configurable admin-defined window) should be applied to prevent misuse or retroactive adjustment of historical revenue.
- Audit logs should clearly reflect:
- The original incorrect date
- The corrected date
- The user who performed the correction
Benefits
- Ensures Guest Ledger accuracy without waiting for the incorrect future date to pass.
- Reduces unnecessary accounting discrepancies.
- Removes the need for manual workarounds or support tickets for simple user error.
- Creates transparency and accountability through audit logging.
Example Scenario
A minibar item is consumed on March 5, but the user accidentally selects April 5 in the consumption date field. The item posts correctly on the guest’s bill, but because consumption is in the future, the item remains on the Guest Ledger until April 5 — even though it has already been settled. With this enhancement, staff could correct the date immediately and maintain an accurate ledger.