How to check a Booking.com commission invoice

A practical monthly workflow for comparing Booking.com commission invoice lines with the latest reservation status, value and supporting records.

Reviewed 22 August 20267-minute readBy LodgeRoot Operations Team

A monthly Booking.com commission invoice can contain many ordinary lines and a small number that need more context. The goal of a review is not to assume that every difference is an overcharge. It is to connect each invoice line to the latest valid reservation record and create a short queue of questions that someone can resolve.

Start with a defined review period

Keep the first pass narrow. Use one property, one invoice period and the reservation records that correspond to that period. Record the invoice number, invoice date, currency and the person responsible for completing the review. This prevents an open-ended investigation and makes it possible to repeat the same process next month.

Booking.com's payment documentation distinguishes gross and net payout models and notes that an official commission invoice is still generated. The exact payment and commission arrangement depends on the property's agreement and local setup, so the property's own Extranet and contract remain the source of truth.

Build one comparison row per invoice line

A useful working sheet does not need to reproduce every field from the PMS. Keep only what is needed to explain the comparison:

  • redacted reservation reference;
  • guest stay dates or another non-identifying date reference;
  • latest reservation status;
  • final accommodation value shown in the source record;
  • commissionable value or basis shown on the invoice;
  • commission rate and amount;
  • reason the line needs review;
  • owner, evidence needed and next action.

Do not copy guest names, phone numbers, card details or platform login credentials into the working sheet. A redacted reference suffix can be enough for the property to find the full record in its own system.

Check five types of line first

1. Modified stays

Compare the invoice basis with the final stay dates and final value, not only the original booking confirmation. Keep the modification timestamp and the source that shows the current version. A difference is a review question until the property confirms how the change was recorded in Booking.com.

2. Cancellations and no-shows

Confirm the final reservation status, any applicable cancellation or no-show fee and whether that status was recorded in the relevant system within the required timeframe. Do not assume that a cancelled booking automatically produces zero commission: the applicable policy and fee treatment still need to be checked.

3. Unusual rates or calculation bases

Compare the rate and commissionable basis with similar lines and with the property's own agreement. Taxes, fees and extra charges can be treated differently, so document the exact component that creates the difference instead of comparing only the grand total.

4. Possible repeated lines

Look for the same redacted reference, stay dates, amount and commission appearing more than once. Similar values alone are not evidence of a duplicate; confirm whether the rows represent separate rooms, adjustments or distinct reservations before escalating them.

5. Lines with missing context

A line can deserve attention simply because the reviewer cannot trace it to a current reservation record. Put these in a separate "context required" queue. That is more accurate than labelling them as errors.

Separate a flag from a confirmed finding

Use simple statuses such as needs context, explained, question prepared and closed. Record the evidence that changed the status. This leaves an audit trail for the next reviewer and prevents the same line from being reopened without new information.

A safe review rule

A highlighted line is not proof that Booking.com made an error. It is a prompt to compare the invoice with the property's latest source record and applicable agreement.

Close the month with three outputs

  1. A list of explained differences that need no further action.
  2. A short evidence-backed queue of lines that need clarification.
  3. A recurring checklist for the next invoice period.

Keep copies according to the property's own retention policy and remove temporary working files when they are no longer required. If a LodgeRoot review is suitable, it starts with one redacted monthly invoice and does not require Booking.com or PMS login access.

See the output format

Review a fictional commission invoice result.

No real hotel, guest or booking data is used in the example.

Open the sample report

Official references

This guide is operational information, not accounting, tax or legal advice. Confirm the current rules in the property's Booking.com Extranet, agreement and local professional guidance.

About this guide

Prepared and reviewed by the LodgeRoot Operations Team as practical workflow guidance for independent accommodation teams. It separates review flags from confirmed errors and links to primary sources where a platform-specific point is discussed. Verify contractual, accounting, tax and platform decisions with the relevant source or adviser.