Level 3 · Process · P10 · Reservations & Revenue
No-show detection and charging
ReviewedHotel National ZermattPayment ProviderGuest
KPIs
| KPI | Target | Cadence |
|---|---|---|
| Cancellation fee leakage | <= 2% of cancellations | monthly |
| No-show charge success rate | >= 90% first attempt | monthly |
Systems
- Payment provider (pre-auth & capture) — Card handling, charge retries, refunds
- PMS — Core property management (rooms, guests, folios)
- RMS — Pricing and forecasting
People & roles
- Reservations Manager — Booking lifecycle
- Revenue Manager — Pricing
Process model
Drag to pan, use the controls to zoom, or open full screen on smaller devices.
Linked decision table
Swipe horizontally to inspect wide decision tables, or open full screen for more space.
Modeling notes
P10 No-Show Detection and Charging - Modeling Notes
Date: 2026-05-18
Process intent
Model overnight no-show handling from cutoff detection through policy-driven charging, retry/fallback outcomes, and operational inventory release.
Participants
- Hotel National Zermatt
- Front Office
- Finance
- Operations / Housekeeping
- Payment Provider
- Guest
Distinct process behavior
- Cutoff-triggered no-show candidate decision (not guest-request triggered).
- DMN policy decision to decide whether no-show charge is allowed.
- Charge capture branch with retry loop before pending-recovery outcome.
- Separate no-charge release outcome when policy denies charging.
- Successful charge branch includes revenue posting and inventory/forecast release.
DMN artifact
/home/kieran/Documents/Hotel-Zermatt/assets/decisions/decision_hotel_national_p10_no_show_charge_policy.dmn- Inputs:
ratePlanguaranteeTypebookedNightslateNoticeHours
- Outputs:
chargeAllowedchargeNightsreason
Non-blocking lint warning
Flow_P10_Retry_Yes is a deliberate right-to-left retry loop from failed charge to reattempt capture.
Related processes in Booking changes & cancellations (4)