The final price a guest pays on Booking.com doesn't match the rate you set, and auditing fees and taxes line by line is how you find out where the difference actually comes from.
You set a rate in the extranet, and the price the guest sees and pays at checkout on Booking.com is different — sometimes higher because of taxes and fees added on top, sometimes lower because of a promotion. Before assuming something is wrong, it's worth auditing exactly which components make up the final price, since several of them are legitimate and expected.
The rate you enter in the extranet is typically your base room rate, not the complete amount a guest pays at the end. On top of it, Booking.com and local regulation can add taxes, service charges or booking fees depending on the property's location and setup, and any active promotion adjusts the price the guest is actually shown before those additions. The result is that your rate and the guest's final price are related but different figures by design, not by error.
The audit worth doing isn't why don't these match — they're not supposed to match exactly — it's whether all the components add up correctly to the price actually shown.
Taxes applicable to your property and jurisdiction are usually added on top of the base rate rather than included in it, and the rules for which taxes apply can differ by property type and location. Service fees or booking fees, where applicable, are a separate addition layered on by the platform. A promotion you've opted into changes the base price before any of those additions are calculated, so the starting point for the guest's final price is already different from your standard rate card.
Pull up the exact listing or a test search for your property on Booking.com's guest-facing side for the dates in question, and note the full price breakdown shown to the guest — most listings display taxes and fees as a separate line rather than hiding them. Compare that breakdown against your base rate in the extranet and any promotion that should be active for those dates. If the final price doesn't reconcile even after accounting for a known promotion and your property's standard taxes and fees, that's worth checking against the extranet's current settings rather than assuming the guest-facing display is wrong.
Prime Shield exists for exactly this kind of discrepancy — it compares the rate you sent, the rate you intended to charge, and what the guest actually paid, and flags any gap worth more than 5% in plain money rather than leaving you to reconstruct the stack by hand every time a number looks off. If pricing audits like this are a recurring source of friction, that structural check is the fix — you can see it on the public demo at try.primehostpartners.com without signing up.