Booking-change-to-final-bill records across PMS, channel manager and guest messaging: the evidence chain and a metadata packet

Short answer

A partner can note, from one conversation and without opening a single record, which systems hold each step from amended booking to guest agreement to final charge (usually a PMS, a channel manager and a guest messaging tool), how many years and roughly how many stays each covers, who administers each, and which links are carried by a reservation number versus rebuilt by staff. The case to flag is a change that reached only one distribution channel. Licensing value is decided later, by review.

Visual briefFull-size diagram
Three swimlanes for the channel manager, the PMS and guest messaging: a one-night extension made on a travel site reaches the channel manager, fails to reach the PMS, is keyed by hand as a new reservation, and the final folio is disputed because the guest's agreed late checkout sits only in the messaging thread.
Illustrative four-night stay. The link breaks where the modification never arrived in the PMS and was rekeyed under a new reservation number.

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.

DaySystemWhat happensIdentifier carried
Day 1Channel managerGuest books 3 nights on travel site AChannel reservation ID, sent to the PMS with the booking
Day 1PMSReservation created, rate plan attachedPMS reservation number linked to the channel ID
Day 9Channel managerGuest extends to 4 nights on travel site ASame channel reservation ID
Day 9PMSModification delivery fails, is retried, then times out; the hotel gets an emailNone: the modification never lands
Day 10PMSNight agent keys the extra night by hand as a new one-night reservationNew PMS reservation number, no channel ID
Day 12Guest messagingGuest asks for a late checkout; agent quotes a fee and the guest agreesGuest name and room, typed in the thread
Day 14PMSCheckout: two folios, a late checkout fee, and a rate on night 4 that differs from the travel siteTwo reservation numbers
Day 20PMSGuest disputes night 4; the hotel adjusts the folio and notes a reasonOriginal 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

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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does a partner need to see a folio or a guest thread to describe this chain?

No. The partner records which systems hold each step, the years covered, rough volumes, who administers each system and which links are recorded. Folios, messages and card data stay with the hotel; anything beyond metadata is handled after an agreement is in place.

Is a hotel group with mostly franchised properties a fit?

It depends on who holds the records and the rights. Franchise and management agreements often decide whether the brand, the management company or the owner controls PMS and guest data, so note the structure and let SourceX's rights review sort it out.

What if the group has replaced its PMS?

Note the year of the switch and whether reservation history moved with it or stayed in the old system. A chain that spans a migration is still worth describing, as long as the company knows what was carried over.

Sources

  1. developer.siteminder.com/siteminder-apis/pms-rms/introduction/pmsxcha…
  2. help.mews.com/en/articles/4245978-action-log
  3. listings.pcisecuritystandards.org/pdfs/pci_fs_data_storage.pdf
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment