One amended stay, followed through three systems
The fastest way to judge this chain is to trace one stay. The case below is Illustrative, built for this page: a hotel group with 14 properties and roughly 900 staff sells rooms through two online travel agencies and its own website, connected to its PMS through a channel manager. Guests message the front desk through a messaging tool.
| Day | System | What happens | Identifier carried |
|---|---|---|---|
| Day 1 | Channel manager | Guest books 3 nights on travel site A | Channel reservation ID, sent to the PMS with the booking |
| Day 1 | PMS | Reservation created, rate plan attached | PMS reservation number linked to the channel ID |
| Day 9 | Channel manager | Guest extends to 4 nights on travel site A | Same channel reservation ID |
| Day 9 | PMS | Modification delivery fails, is retried, then times out; the hotel gets an email | None: the modification never lands |
| Day 10 | PMS | Night agent keys the extra night by hand as a new one-night reservation | New PMS reservation number, no channel ID |
| Day 12 | Guest messaging | Guest asks for a late checkout; agent quotes a fee and the guest agrees | Guest name and room, typed in the thread |
| Day 14 | PMS | Checkout: two folios, a late checkout fee, and a rate on night 4 that differs from the travel site | Two reservation numbers |
| Day 20 | PMS | Guest disputes night 4; the hotel adjusts the folio and notes a reason | Original and adjusted charge |
Nothing here is unusual. The day 9 failure follows a documented pattern: SiteMinder's PMS interface documentation, for example, says modifications are delivered to the PMS one message at a time under the reservation's original ID, failed deliveries are retried, and after repeated failures the reservation times out and the hotel is emailed to contact its PMS provider. What makes it valuable as a decision record is that the hotel can, with effort, explain every step: why night 4 sat on a separate reservation, why the rate differed, who agreed the late checkout and what the adjustment fixed. Whether that explanation survives in the archive is the question this page helps a partner ask.
What metadata can a referral partner collect about booking-change-to-final-bill without reading private content?
A one-page packet, filled in from the company's own description. Nothing on it is a guest name, a folio, a message or a card number. Final bills carry payment data, and PCI DSS prohibits keeping sensitive authentication data such as card verification codes after authorization at all, which is one more reason partners stay at metadata level.
System lines (one per system):
- System and role: PMS, channel manager, guest messaging, and any second PMS from before a migration.
- Years held and rough volume: for example, "PMS since 2017, about 60,000 stays a year across the group".
- Object types: reservation, modification message, folio, adjustment, message thread.
- Administrator: who can confirm what is kept and for how long.
- Change history: does the system keep who changed what and when, and since when? Some PMSs log this per reservation; the Mews action log, for example, records the employee, reservation number, time, type of change and any reason given.
Link lines (one per hand-off):
- Which identifier carries across, and whether it is recorded or typed by staff.
- How manual rekeys are marked, if at all.
- Whether messaging agreements are copied to the reservation.
Known exceptions:
- Does the group know that changes sometimes reach only one channel, and roughly how it finds out (night audit, guest dispute, monthly reconciliation)?
Unknown until review: rights under franchise or management agreements, how guest personal data would be handled, export formats, buyer interest and any offer. For a broader template, see the metadata-only inventory guide and the HubSpot inventory template, whose field layout adapts well to a PMS.
Who can sponsor the introduction, and does the group qualify?
The CEO is the person who can authorize a licensing discussion for the whole group and sign for it; the COO, the commercial director or the owner's representative often sponsors the introduction. Name the revenue manager and the systems lead as the people who can answer the packet. In managed or franchised hotels, also note who signs the PMS contract, because that often signals who controls the data.
Check the basics before introducing: 50+ full-time employees at peak (contractors and agency staff excluded), documented operating history, rights to license, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Guest messaging in several languages matters for that last test, so note the rough language mix.
What stays unknown until SourceX reviews the opportunity: demand for this record type, the rights review result, de-identification of guest data, the company's offer and any reward. Related reading: hospitality operating procedures, the hospitality industry page, operational communications as a data type and the systems hub.
Go deeper on booking-change-to-final-bill records
- How reservation, message and folio records link: a record-chain table of each step, its record, its key and its system.
- Booking-change-to-final-bill completeness checklist: a pass, partial or fail scorecard for judging whether the records are complete enough to discuss.
- What a PMS-only export of an amended stay leaves out: one Illustrative stay read before and after its surrounding context is added.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a hotel group can fill in the packet, say how it learns that a change reached only one channel, and controls its own PMS and channel history, register as a partner, confirm the group against who qualifies, and read the program terms before you introduce its sponsor.