# Booking change to final bill scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/booking-change-to-final-bill-completeness-checklist
Last updated: 2026-11-04

A booking-change-to-final-bill evidence trail breaks mostly at an amendment that exists in one place only: it reached an online agency and the distribution software but never the property system, which then shows a second, unrelated stay. This scorecard tests that weak point and four others (coverage, linkage, timestamps and outcomes) with yes-or-no questions a revenue manager can answer from memory. Each check scores pass, partial or fail, and none needs a record.

The scorecard is part of the [booking-change-to-final-bill evidence chain and metadata packet](/guides/chain-booking-change-to-final-bill). Use it after a first conversation, once you know which systems the group runs and before deciding whether to introduce its sponsor.

## How the scorecard works

Score each check 2 for pass, 1 for partial and 0 for fail, for a maximum of 10. Write the company's words beside each score, not your interpretation. If nobody knows, score it unknown and leave it out of the total rather than guessing.

The total is a conversation aid, not a verdict. It tells you which questions to bring to SourceX and which gaps the company already understands. It does not predict demand, rights review outcomes or any offer.

Three rules keep it at metadata level:

- Ask about what is kept, for how long, in which system and who owns it. Never ask to see a stay record, invoice or conversation.
- Accept rough answers ("since about 2018", "most properties") and note them as rough.
- When the answer differs by property, score the group by its weakest large property and note the spread.

## The five checks, with pass, partial and fail guides

| Check | Metadata question to ask | Pass (2) | Partial (1) | Fail (0) |
|---|---|---|---|---|
| Coverage | For which years does the group hold property system, distribution and chat history? | All three cover the same three or more years | Property system covers years; the others only recent months | Only one system has history |
| Linkage | Does the property system file the channel ID, and do manual re-entries get it or a pointer to it? | ID filed, re-entries noted by habit | ID filed, re-entries not noted | No channel ID kept |
| Timestamps | Does the property system keep who edited a stay and when, for those years? | Dated change log for the full period | Log exists but is short or partly purged | No change log, or never checked |
| Outcomes | Are invoice adjustments made with a reason code or text? | Reason required on every adjustment | Reasons sometimes typed | No reasons kept |
| One-channel gaps | Can a price or length amendment made on an agency site miss the property system, and how is it caught? | Yes, caught at the daily audit and logged | Yes, caught but not logged | Never checked, or "it never happens" |

The checks map onto the record chain. Linkage is about the channel ID: SiteMinder's documentation, for example, says the first UniqueID in a message identifies the booking through later amendments and cancellations, so a property system that files it can join every amendment back to the sale. Timestamps are about the change log: Mews documents an action log with the employee, record number, date and time, the nature of the change and a reason where given. For the full chain, step by step, see the [record chain for this workflow](/guides/booking-change-to-final-bill-record-linkage).

## A scored example (Illustrative)

A fictional 9-property group with about 700 staff, a property system since 2018, distribution software since 2019 and a chat tool since 2022. Its revenue manager answered the five questions in a 20-minute call.

| Check | Company's answer | Score |
|---|---|---|
| Coverage | Property and distribution history since 2019; chat since 2022 | Partial (1) |
| Linkage | Channel ID on every stay record; staff note it on re-entries since 2021 | Pass (2) |
| Timestamps | Change log kept since go-live | Pass (2) |
| Outcomes | Reason text typed on most adjustments, not enforced | Partial (1) |
| One-channel gaps | Daily audit report flags mismatches; each one is logged with a fix | Pass (2) |
| Total | Two partial, three pass | 8 of 10 |

Illustrative. Names, dates and answers are invented.

The 8 is less interesting than its shape. The group's strongest answer is the last one, because it shows exceptions being caught and recorded, which is the hardest part of the trail to rebuild later.

## The test case: a change that reached only one channel

The one-channel check carries the most information, so spend time on it. An amendment is made on an agency site, reaches the distribution software and fails to reach the property system. SiteMinder documents what happens next on its side: delivery is retried, and after repeated failures the booking times out and the property receives an email advising it to contact its system provider. From there the hotel's own habits decide whether the trail survives.

- A group that says "yes, that happens, we catch it at the daily audit and log it" is describing a labeled exception with an outcome. Score it pass.
- A group that catches it but enters the amendment as a new stay with no note scores partial: the exception happened, but the link back is lost.
- A group that believes its integrations never miss scores fail. It may be right, but it has not checked, and an unchecked trail is harder to review than a known gap.

What a single-system export looks like when this check fails is shown in [what one hotel system export cannot explain](/guides/booking-change-to-final-bill-missing-context).

## What the score does not decide

The scorecard tells you whether the records are complete enough to describe. Fit and authority are separate questions.

The CEO is the person who can open a licensing discussion for the group, often with the COO or commercial director as internal sponsor; the revenue manager who answered the scorecard cannot. 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. The [company fit checker](/tools/company-fit-checker) runs the same basic tests.

Still unknown until SourceX reviews it: buyer interest, franchise or management agreement limits, de-identification of guest data, export formats and any offer. Partners never ask for or handle raw records. Related: [hospitality operating procedures](/guides/how-to-assess-hospitality-operating-procedures) and the [hospitality industry page](/industries/hospitality).

## 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 answer all five checks, even with partial scores, and knows how it catches one-channel changes, [register as a partner](/register), check it against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its sponsor.

## Sources

- https://developer.siteminder.com/siteminder-apis/pms-rms/introduction/pmsxchange/api-reference/reservations-push
- https://help.mews.com/en/articles/4245978-action-log
- https://refer.sourcex.si/terms
