A booking can look complete in the agency inbox while remaining different in the supplier’s operation. The agency may hold the requested date, the supplier may have confirmed another departure, and an exported list may still contain an earlier passenger count. These differences usually become expensive in attention before they become obvious to the guest.
This article proposes an operational reconciliation method for travel agents and activity suppliers. It is an editorial workflow, not a claim about any particular booking platform, accounting system or contractual requirement. The examples are fictional.
Decide what the reconciliation proves
Begin with a narrow question: does the supplier’s current operational record describe the service the agency has confirmed to the guest?
That question is different from checking whether an invoice has been paid or whether a cancellation attracts a fee. Those tasks can use linked references, but they need their own records and responsible people.
Define the scope of each review. A daily departure check might cover tomorrow’s activities. A weekly check might identify bookings awaiting supplier confirmation farther ahead. Combining every purpose into one oversized spreadsheet can make an urgent date mismatch harder to see.
Write the review boundary at the top of the working file: service dates covered, suppliers included, extraction time and the person responsible for closing exceptions. Staff should know which bookings the review actually includes.
Build a reference bridge
Keep the agency booking reference and supplier booking reference together. If an intermediary or marketplace has another reference, store that separately too. Do not replace one with another because the supplier’s code seems more useful today.
A reference bridge might read:
- Agency reference: AG-0417.
- Supplier reference: SUP-8062.
- External channel reference: CH-2719, where applicable.
- Current service record: the version being checked.
- Link established by: staff member and source confirmation.
These are invented codes. Their purpose is to show the relationship, not prescribe a numbering scheme.
Preserve leading zeros, letters and punctuation that form part of a reference. Treat identifiers as identifiers rather than amounts. If a spreadsheet alters imported values, correct the import process before trying to match the changed codes.
A shared surname, hotel or travel date can help investigate an unmatched record. None should become the permanent link in place of a confirmed reference.
Keep the source export intact
Save the original agency and supplier extracts before cleaning the working copy. Record when each was obtained and what date range it covers. A file downloaded yesterday may contain a valid snapshot of yesterday’s information while missing a change accepted this morning.
Use separate areas for raw source data, comparison work and resolved exceptions. This keeps a well-intentioned cleanup from removing the evidence needed to explain a discrepancy.
Google documents splitting text, removing duplicates and trimming whitespace in Sheets. Those tools can help prepare a working copy, but they do not decide whether two bookings are operationally identical.
For example, two rows with the same guest name may represent separate activities, a split party or a replacement after cancellation. Review their references and history before removing anything as a duplicate.
Compare the service date and time precisely
Use the local date at the activity destination as the main service date, and label it explicitly. An agency’s office date or an email timestamp can differ from the date the supplier needs for dispatch.
Keep the departure time and pickup arrangement distinct. A booking for a 9am activity may involve an earlier hotel pickup; treating those as one field creates an apparent disagreement that staff then “fix” incorrectly.
Where time zones matter, write the destination or time zone beside the service time. Avoid interpreting a bare number copied from a message.
Compare the source records without silently choosing the more convenient value. If the agency says 18 November and the supplier says 19 November, put the booking into the exception queue. A staff member must establish which service was requested, accepted and communicated before the record changes.
Check product and option together
A product title is often too broad for a reliable match. The same excursion name might cover morning and afternoon departures, shared and private arrangements, or versions with different inclusions.
Compare a stable product identifier where available, then the option, departure and important confirmed inclusions. Keep the supplier’s wording alongside your agency wording when they differ.
For a fictional island excursion, “Island Day” in one list and “Island Day Premium” in another is a question to resolve. Do not infer equivalence from the shared first words.
Record why the match is accepted. A short note such as “supplier confirmed option B corresponds to agency’s private departure” is useful evidence. An unexplained green cell gives the next reviewer no way to assess the decision.
Use the private-tour change approval workflow when the mismatch involves a route change awaiting acceptance.
Compare passenger categories without losing meaning
Keep adults, children and infants separate where those categories affect the service. Also record the supplier’s applicable category definitions or booking option where needed. An agency’s generic “child” field may not map neatly to the supplier’s product.
Start with the total party, then compare each category. A total of six in both systems can conceal four adults and two children in one record versus five adults and one child in the other.
Do not change a category just to make totals agree. Ask which detail is correct and whether the supplier needs further information to apply its own product rules.
Special arrangements may need separate quantities. The tour meal-count guide explains why a passenger total does not automatically equal the number of meals or portions ordered.
Use a small exception vocabulary
Choose a few clear states and define what moves a booking between them. A practical starting set is:
- Matched: required fields agree and the source references are linked.
- Agency only: no corresponding supplier record has been established.
- Supplier only: no corresponding agency record has been established.
- Conflict: linked records disagree on a required detail.
- Awaiting reply: a specific question has been sent to a named party.
- Resolved: the correction or accepted explanation is recorded.
Keep “resolved” separate from “matched” if a history of corrections matters to your team. A resolved exception may require the next comparison to verify that the change actually appears in the supplier’s list.
Avoid a single “pending” bucket. It obscures whether staff are looking for a record, waiting for an answer or holding a known conflict.
Work through one fictional mismatch
Imagine the agency record AG-0417 shows a shared departure on 18 November for four adults and two children. The linked supplier record SUP-8062 shows the same date and total of six, but lists five adults and one child.
The reviewer marks a passenger-category conflict and links the original confirmation. They do not change the supplier row. The booking owner checks the guest details and the product’s category definitions, then sends a precise question with both references.
The supplier confirms the correct categories and supplies an updated record. The agency checks whether any guest-facing information also needs correction, records the response and marks the exception resolved.
At the next operational extract, the reviewer verifies that the corrected categories are present. That final comparison closes the loop between a helpful reply and the record staff will use on departure day.
Preserve cancellations and replacements
A cancelled booking and its replacement should remain traceable as separate events. Removing the cancelled row can make the replacement look like an unexplained duplicate, especially when both carry the same guest name.
Record the relationship: original reference, cancellation status, replacement reference and the source confirming the change. Do not assume a replacement inherits every inclusion, pickup or special arrangement automatically.
When supplier and agency statuses disagree, prioritise understanding the operational consequence. Is a seat still being held? Is a driver expecting the party? Has the guest been told the service is cancelled?
Keep financial outcomes in the relevant authorised workflow. Operational reconciliation establishes what is currently expected to run; it should not silently invent a refund decision or amend agreed terms.
Assign ownership and a response target
Every exception needs a named owner, a precise next action and a review time. “Supplier issue” is a category, not an owner. “Check later” is an intention, not a review time.
Prioritise by service proximity and effect on the guest. A conflicting departure tomorrow requires different attention from a missing optional note several months ahead.
State who may make each correction. The reviewer may identify a mismatch while the booking owner handles the supplier conversation. A supervisor may need to approve a replacement service. Keep those responsibilities explicit enough that two people do not send conflicting requests.
When a deadline passes, escalate through the team’s normal contact route with the references, unresolved question and upcoming service date. A concise evidence bundle is more useful than forwarding an entire message chain without context.
Share the minimum useful information
A reconciliation file should expose only the guest information needed by the people doing the work. Do not copy passports, payment details or long personal conversations into a broadly shared operational sheet.
Keep source links accessible to the relevant team, and use the organisation’s established access and retention arrangements. A supplier may need the confirmed passenger count without needing the agency’s internal notes about a guest.
If using Sheets, distinguish edit access from the ability to view results. Protecting a working range can reduce accidental changes, but it does not replace appropriate sharing permissions or a record of who authorised an amendment.
The central principle is practical: staff should find the answer they need without searching through unrelated personal information.
Make reconciliation part of the departure rhythm
Choose review points that fit when information changes. A supplier sending an updated list after the agency’s check needs another comparison or an agreed process for highlighting changes.
Include the extraction time in a handover. “All checked” is incomplete if a newer file has arrived. Say which departures were reviewed, which source version was used and which exceptions remain open.
Measure the work through useful outcomes: unresolved conflicts approaching departure, repeated causes and corrections that failed to reach the operating list. A large number of matched rows can hide one serious exception.
Use recurring causes to improve booking capture. If product options are repeatedly unclear, fix the mapping at entry. If imported references lose zeros, fix that handling. Reconciliation should reveal where the next mismatch can be prevented.
Questions teams often ask
Can we match by lead guest name first? Use it as an investigative clue when necessary, then establish and preserve the reference relationship. Names alone are not a reliable operational key.
Should we delete duplicate-looking rows? Keep the raw extract and review references, statuses and replacement history before removing rows from a working comparison.
Does equal passenger total mean the booking matches? No. Categories, product option, date, departure and important confirmed arrangements can still differ.
When is an exception closed? When the required answer or correction is recorded and, where relevant, verified in the operational source that will be used.
Do we need a new system? Start by defining the comparison and ownership. A small, controlled process can expose what a future system would actually need to handle.
Sources and implementation notes
Primary references reviewed on 22 October 2026: Google Sheets data cleanup tools and Google Sheets number and date formatting. These sources support tool behaviour only. The reconciliation method, reference examples, exception states and management suggestions are original editorial guidance and should be adapted to the team’s systems and agreements.
