Level 3 · Process · P07 · Reservations & Revenue
Deposit pre authorization handling
ReviewedHotel National ZermattPayment ProviderGuest
KPIs
| KPI | Target | Cadence |
|---|---|---|
| Pre-auth failure follow-up | 100% resolved pre-arrival | daily |
Systems
- Payment provider (pre-auth & capture) — Card handling, charge retries, refunds
- PMS — Core property management (rooms, guests, folios)
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
P07 Deposit / Pre-Authorization Handling - Modeling Notes
Date: 2026-05-18
Process intent
Handle booking guarantee collection and financial risk control with explicit pre-authorization attempts, alternate payment fallback, and booking-at-risk outcomes.
Participants
- Hotel National Zermatt
- Reservations
- Finance
- Front Office
- Payment Provider
- Guest
Distinct process characteristics
- DMN decision before finance actions to determine whether guarantee is required and hold level.
- Guest-facing alternate guarantee loop when pre-authorization fails.
- Retry control gateway (
Gateway_P07_RetryAvailable) before final at-risk outcome. - Parallel post-authorization finalization:
- finance records hold in PMS
- front office sends guarantee confirmation
- Explicit booking-at-risk terminal path.
DMN artifact
/home/kieran/Documents/Hotel-Zermatt/assets/decisions/decision_hotel_national_p07_guarantee_requirement.dmn- Inputs:
rateTypechannelRiskleadDaysstayValueChf
- Outputs:
guaranteeRequiredholdPercentreason
Non-blocking lint warnings
Right-to-left connectors are deliberate rework loops (retry and guest alternate-provision cycle) and retained for operational realism.