Level 3 · Process · P09 · Reservations & Revenue

Cancellation handling and fee determination

ReviewedHotel National ZermattPayment ProviderGuest
KPIs
KPITargetCadence
Cancellation fee leakage<= 2% of cancellationsmonthly
No-show charge success rate>= 90% first attemptmonthly
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

P09 Cancellation Handling and Fee Determination - Modeling Notes

Date: 2026-05-18

Process intent

Model full cancellation handling: policy eligibility, fee proposal/guest consent, payment capture attempts, refund treatment, and operational cancellation execution.

Participants

  • Hotel National Zermatt
    • Reservations
    • Finance
    • Operations / Front Office
  • Payment Provider
  • Guest

Distinct process behavior

  • DMN decision gate for cancellation eligibility and fee/refund levels.
  • Separate path when fee is due vs fee-free cancellation.
  • Guest negotiation loop:
    • fee proposal sent
    • guest accepts/rejects
  • Finance capture logic with fallback:
    • on-file payment attempt
    • alternate payment request
    • retry gate
    • pending-payment outcome if unresolved
  • Settlement branch with refund/no-refund merge before cancellation execution.
  • Operational close-out (release inventory + notify service partners) before final confirmation.

DMN artifact

  • /home/kieran/Documents/Hotel-Zermatt/assets/decisions/decision_hotel_national_p09_cancellation_fee_determination.dmn
  • Inputs:
    • ratePlan
    • hoursToArrival
    • isNoShow
    • channelType
  • Outputs:
    • cancellationAllowed
    • feePercent
    • refundPercent
    • reason

Non-blocking lint warnings

Right-to-left flows are intentional for retry/rework paths and finance-to-operations merge routing.

Related processes in Booking changes & cancellations (4)