Booking change to final bill record chain: which identifier joins each hand-off, from channel sale to invoice

Short answer

A company connects booking-change-to-final-bill records by following the identifiers each hand-off stores. Software writes most of them: the channel manager issues one ID that survives every later amendment, and the property system files it beside its own number. People write the rest, by typing a room, a date or a reason. Mapping which keys are machine-written and which are typed shows where the chain will hold and where someone would have to rebuild it by hand.

Visual briefFull-size diagram
Five record links snap together from channel booking to folio adjustment; the third link, a night rekeyed by hand with no channel ID, shows as a weak dashed link and then turns green once the channel ID is noted on the rekeyed reservation.
Illustrative chain. Recorded keys hold; the joins people make by hand are the weak links.

This identifier map is one part of the booking-change-to-final-bill evidence chain and metadata packet. The hub traces one amended stay end to end; here the only job is to name the key on every link, so an introducer can ask which joins are recorded and which are inferred.

Each row below is one link, using the main guide's Illustrative extended stay. The right-hand column is the test: was the join written by software, or typed by a person?

StepRecordKey that carries the linkSystemWritten by
1. Original saleChannel bookingChannel IDChannel managerSoftware
2. Sale arrivesStay recordChannel ID filed on the stay recordProperty systemSoftware
3. Amendment madeChange messageSame channel ID, plus a message IDChannel managerSoftware
4. Amendment arrivesStay record updateChannel ID, if the message was deliveredProperty systemSoftware
5. Manual re-entrySecond stay recordNew local number; channel ID only if staff add itProperty systemPerson
6. Extra fee agreedChat conversationRoom and date typed in the conversationChat toolPerson
7. DepartureInvoice and chargesLocal stay numberProperty systemSoftware
8. Charge correctedInvoice adjustmentLocal stay number plus reason text, if typedProperty systemPerson, for the reason

Steps 1 to 4 share one identifier set by software. Steps 5, 6 and 8 depend on what somebody keyed. That split is what the introducer is trying to learn, and the company can usually describe it from memory.

Which identifier carries each hand-off

Channel manager to property system. SiteMinder's developer documentation shows one widely used integration. Its Reservations PUSH method sends every amendment as a separate message. The first UniqueID in each message identifies the booking through all later amendments or cancellations, and a second identifies the individual message. If the property system files that first ID, every later amendment joins back to the original sale without anyone matching names.

Inside the property system. Mews documents an action log recording which details changed and who changed them: the employee, the local number, date and time, the nature of the change and a reason where one was given, filterable by types such as Start changed or Space changed. That log is the timestamp layer. Whether amendments arriving through an integration appear in it the same way as staff edits is a question for the company; the Mews page reviewed does not say.

Property system to chat. Most chat tools are not keyed to the local stay number in a way that survives export. The usual join is room plus date, which is inferred, unless staff paste the number into the conversation.

Property system to invoice. Charges and adjustments sit under the local stay number, so this link is recorded. What can be missing is the reason: an adjustment without reason text looks like an ordinary price fix.

Where the chain commonly breaks

Four breaks are worth asking about, in the order the stay moves through the systems.

  1. An amendment that never arrives. SiteMinder retries a failed or timed-out delivery; after repeated failures the booking times out and the property receives an email advising it to contact its system provider. If an agent then keys the amendment by hand, the second stay record has no channel ID. Step 5 is the weakest link here.
  2. A fee agreed in chat. A late departure, upgrade or pet fee accepted in a conversation reaches the invoice only if someone posts it. The conversation and the charge share no key.
  3. An adjustment without a reason. If staff skip the reason field, the dispute and its fix cannot be told apart from a rate correction.
  4. A property system replacement. If the group switched systems, check whether old channel IDs and local numbers came across, or whether earlier history sits in a read-only archive with different keys.

None of these makes the history worthless. A labeled break with a known cause is more useful to a reviewer than a chain that only looks clean.

A partner does not repair anything. The useful step is to record, from the company's own account, whether a repair habit exists and since when.

Weak linkRepair habit to ask aboutRecorded or inferred after repair
Manual re-entryChannel ID or original local number noted on the second recordRecorded, from the date the habit started
Fee agreed in chatLocal number pasted into the conversation, or the charge posted with a noteRecorded when done; inferred otherwise
Invoice adjustmentReason code requiredRecorded
Old system historyMapping table from old to new numbersRecorded if the mapping was kept

Illustrative. A company may have all, some or none of these habits; each answer is worth one line. For the scorecard version of these questions see the completeness checklist, and for what an export reads like when the links are missing see what a PMS-only export leaves out.

This page names SiteMinder and Mews because their documentation is public. It does not imply that SourceX has a connector for either, or for any guest messaging tool. How records would move is settled after review, and export fields nobody has checked should be marked unknown.

Who can confirm the keys and authorize a discussion

Two people answer different questions. The revenue manager or systems lead can say which identifiers are stored and how rekeys are marked. Only the CEO can authorize a licensing discussion for the group and sign for it; the COO, commercial director or owner's representative often sponsors the introduction. In franchised or managed hotels, note who signs the PMS and channel manager contracts, because that often shows who controls the records.

Before an introduction, check the basics: 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.

Unknown until SourceX reviews it: SourceX's current data needs for this record type, what franchise agreements allow, how guest personal data would be de-identified, and any offer. Partners never ask for or handle reservations, folios or threads. Related reading: hospitality operating procedures, the hospitality industry page, change order records in construction for a similar amendment chain in another industry, 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 can name the key on each link and say how it marks rekeyed nights, register as a partner, check 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 the hotel have to export anything to map this chain?

No. The front office or revenue manager can say which identifier each system stores and how manual rekeys are marked. The partner writes down those answers; reservations, folios and threads stay where they are.

What if the group uses a different channel manager or PMS?

The chain is the same shape. Ask which identifier the channel manager sends with each booking and change, whether the PMS stores it, and whether the PMS keeps a dated log of who changed what.

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