All templates

Automated OTA Reseller Booking Reconciliation

Every Monday, WebRun opens Xola and exports last week's bookings by source channel, cross-checks them against OTA commission reports uploaded to Google Sheets, flags any bookings missing from either side or with commission discrepancies, and posts a reconciliation summary with any mismatches to Slack.

Runs on WebRun · Strict Lockdown policy
Every Monday at 9:00 AM WebRunorchestrates each step
1 Xola pull last week's bookings by source channel
2 Google Sheets cross-check against OTA commission reports
3 Slack post reconciliation summary and flags
In short

How do I automatically reconcile OTA bookings and commissions against my booking system?

Every Monday, WebRun pulls last week's Xola bookings by channel, matches them against OTA commission statements in Google Sheets, and flags any missing bookings or commission discrepancies. A reconciliation summary with flagged items posts to Slack so operators can catch errors and recover revenue weekly.

  • Commission discrepancies and missing bookings are caught every week, not at month-end
  • Finance teams receive a structured reconciliation summary without manual spreadsheet work
  • OTA revenue is verified against the booking system to prevent silent underpayments

Built for tour operators selling on OTAs · activity companies with reseller channels · tour finance and ops managers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens xola.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Xola - pull last week's bookings by source channel
    xola.com
    WebRun in Xola: pull last week's bookings by source channel
    WebRun opens Xola to pull last week's bookings by source channel.
    • Open Xola and filter completed bookings from last week by source channel, separating direct, Viator, GetYourGuide, and other OTA bookings
    • Export booking IDs, tour names, dates, guest names, gross amounts, and channel for each booking
    • Note any bookings flagged as cancelled or refunded during the period

    Done when All last week's bookings are listed by source channel with amounts and booking IDs.

  3. 2
    Google Sheets - cross-check against OTA commission reports
    google.com
    WebRun in Google Sheets: cross-check against OTA commission reports
    WebRun opens Google Sheets to cross-check against OTA commission reports.
    • Open the OTA reconciliation sheet where commission statements have been uploaded
    • Match each Xola booking ID against the OTA report line items
    • Flag any Xola bookings not appearing in the OTA report and any OTA report lines not matched to a Xola booking
    • Calculate expected versus received commission for each OTA channel and note any discrepancies

    Done when All mismatches, missing bookings, and commission discrepancies are flagged in the sheet.

  4. 3
    Slack - post reconciliation summary and flags
    slack.com
    WebRun in Slack: post reconciliation summary and flags
    WebRun opens Slack to post reconciliation summary and flags.
    • Post a weekly reconciliation summary to the finance or ops Slack channel
    • List total bookings per channel, total gross revenue, and total commissions reconciled
    • Highlight any unmatched bookings or commission gaps that need operator attention
    • Include a link to the full reconciliation sheet for detailed review

    Done when The team has a clear reconciliation summary in Slack with flagged items to action.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
xola.com
ScheduleRuns automatically on this cadence
Every Monday at 9:00 AM
DeliveryHow each run's result reaches you
Reconciliation summary · Slack · Google Sheets
OutputWhat each run produces - A weekly OTA reconciliation summary in Slack, plus a detailed mismatch and commission report in Google Sheets.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does WebRun dispute commissions or contact the OTA on my behalf?

No. WebRun flags the discrepancies and presents them clearly in Slack and Google Sheets. Any dispute or follow-up with the OTA is carried out by you or your finance team.

Which OTAs does it support for reconciliation?

It works with any OTA that provides a downloadable commission statement you can upload to Google Sheets, including Viator, GetYourGuide, Expedia, and others.

What if OTA commission statements are not yet available on Monday?

The workflow reconciles whatever is in the sheet at run time. If a statement arrives later in the week, run the workflow again and it will produce an updated reconciliation with the new data.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.