What one hotel system export cannot explain about an amended stay: the same case read before and after

Short answer

A single-system export loses the reasons. Read on its own, a property system's records of an amended stay show charges, a discount and who applied it, but not what the visitor bought or agreed anywhere else. The extension bought through an online travel agency, the update that never landed, the fee accepted over text and the price the visitor was shown all sit in other places: the distribution software, the front desk inbox and the conversation tool. Without them, one stay looks like two unrelated bookings and an unexplained refund.

Visual briefFull-size diagram
Four lines from a hotel property system export each sit beside a blank; context pieces from the distribution software, the front desk inbox and the chat tool slide in, showing one extended stay, a timed-out update, a fee accepted in writing and a lower price the visitor was shown.
Illustrative stay. The property system holds the charges; the reasons sit in the other systems.

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 exportWhat it showsWhat an outsider would assume
Booking 1Three days at an agency rateAn ordinary short trip
Booking 2One day, entered by staff later, at a higher priceA separate phone or walk-in sale
Charges on booking 1Room, plus a late departure feeThe visitor asked at the desk
Charges on booking 2One day, later reducedA pricing slip
Change historyPrice edited by a manager weeks later, with a short noteSomeone 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 aloneWhere that context livesWho usually holds it
Bookings 1 and 2 are one stayDistribution software historyRevenue manager
Why the fourth day was entered by handDelivery history and the timeout alertRevenue manager; front desk inbox
The basis for the late departure feeThe conversation threadFront office manager
The price the visitor expectedAgency-side sale recordRevenue manager
Why the discount was the right callThe complaint plus the price comparisonFront office manager
Who edited the charges, and whenProperty system change log, if keptSystem 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:

  1. Does the group still have channel manager history for the years the PMS covers, or only recent months?
  2. When a fee is agreed by message, is it copied to the reservation with a note?
  3. 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.

  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

Is a PMS-only history still worth describing?

Yes, as long as the gap is named. A partner can note that the PMS covers charges and adjustments while channel and messaging history was not kept, and SourceX's review decides what that coverage is worth.

How long do channel manager and messaging records last?

It depends on the vendor contract and the hotel's settings, and it changes when an account is closed. Ask the company how far back each system goes today rather than assuming.

Sources

  1. developer.siteminder.com/siteminder-apis/pms-rms/introduction/pmsxcha…
  2. help.mews.com/en/articles/4245978-action-log
  3. 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