This before-and-after reading belongs to the booking-change-to-final-bill evidence chain. It takes that hub's Illustrative stay at a fictional 14-property group and reads it twice: first as an outsider holding one export, then with every neighboring record laid beside it.
Before: what one export says on its own
Picture a reviewer holding only the property system's files for one visitor. Each line is accurate. None explains itself.
| Line in the export | What it shows | What an outsider would assume |
|---|---|---|
| Booking 1 | Three days at an agency rate | An ordinary short trip |
| Booking 2 | One day, entered by staff later, at a higher price | A separate phone or walk-in sale |
| Charges on booking 1 | Room, plus a late departure fee | The visitor asked at the desk |
| Charges on booking 2 | One day, later reduced | A pricing slip |
| Change history | Price edited by a manager weeks later, with a short note | Someone fixed a typo |
An outsider would see two unrelated sales under one name, a fee with no visible basis and a discount with a thin note. That reading is not wrong. It is incomplete exactly where somebody made a decision.
After: the same stay with its surroundings
Now add what the other places hold for those days.
- Distribution software shows one sale through the agency, lengthened from three days to four under a single ID. Its delivery history shows the update retried and then timed out.
- The front desk inbox holds the timeout alert telling staff to contact their system provider. SiteMinder documents this path: after repeated failed deliveries, the booking times out and the property gets an email.
- The conversation tool shows the visitor asking to leave late, an agent quoting a price, and a written yes.
- The agency price shown for the fourth day is lower than what staff entered by hand. That gap is why the visitor complained.
Together these describe one four-day stay, a failed hand-off, a manual workaround, a fee accepted in writing and a complaint settled in the visitor's favor: cause, workaround, agreement and outcome.
What is lost without context, and where it lives
| Lost when one export is read alone | Where that context lives | Who usually holds it |
|---|---|---|
| Bookings 1 and 2 are one stay | Distribution software history | Revenue manager |
| Why the fourth day was entered by hand | Delivery history and the timeout alert | Revenue manager; front desk inbox |
| The basis for the late departure fee | The conversation thread | Front office manager |
| The price the visitor expected | Agency-side sale record | Revenue manager |
| Why the discount was the right call | The complaint plus the price comparison | Front office manager |
| Who edited the charges, and when | Property system change log, if kept | System administrator |
Illustrative. Rows describe this example, not a tested export from any vendor.
The last row is the one thing the property system keeps for itself. Mews, for example, documents an action log with the employee, the record number, date and time, what changed and a reason where one was given. A log like that answers who and when. It cannot answer why the visitor expected a lower price.
Every system is blind from its own side
The problem is symmetric. A channel manager export shows bookings and modifications, not what was finally charged. A messaging export shows agreements, not whether they reached the folio. Each export is a partial log; only the joined history turns three partial logs into an explainable decision, which is the kind of record missing from most AI training data.
That joined history is most at risk at three moments: when a group replaces its PMS, when it changes channel manager, and when it closes an old messaging account. If a hotel mentions any of these, note the year and what was kept. The group booking reconciliation guide covers the related case of block bookings ahead of a property system replacement, and operational communications explains why message threads carry so much of the reasoning.
For the identifiers that would join these records, see the record chain for this workflow.
Three questions that show whether the context survived
A partner can learn most of this in one conversation with the revenue or front office manager, without seeing a single record:
- Does the group still have channel manager history for the years the PMS covers, or only recent months?
- When a fee is agreed by message, is it copied to the reservation with a note?
- Has the group changed PMS, channel manager or messaging tool, and did history move with it?
Then check fit. The CEO can authorize a licensing discussion for the group and sign for it; the COO or commercial director often sponsors the introduction. The company needs 50+ full-time employees at peak (contractors 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.
Unknown until SourceX reviews it: what franchise or management agreements allow, how guest details would be de-identified, which export fields exist and any offer. Partners never ask for or handle raw guest records. This page does not imply SourceX connects to any PMS, channel manager or messaging tool. More context: the hospitality industry page and the systems hub.
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 still holds its channel and messaging history alongside the PMS and can say for which years, register as a partner, confirm the group against who qualifies, and read the program terms before introducing its sponsor.