summary
Booking.com gives hosts two damage options: a traditional damage deposit guests pay upfront, or the damage program, where guests pay nothing upfront, and you submit a damage payment request within 14 days of checkout. The catch with the program is the fine print: Booking.com mediates, but payment occurs only if the guest agrees, so it’s a facilitated request, not a guarantee. US hosts get a third layer, automatic Host Property Insurance on Booking.com reservations. None of these replaces real short-term rental insurance; the workable setup is a modest program cap for friction-free bookings, plus independent coverage for the losses that matter.
Every host’s damage question is really two questions: what happens when a guest breaks something, and will I actually see the money? Booking.com’s official pages answer the first in detail and go quiet on the second, while the horror stories ranking beside them answer the second and skip the mechanics. It’s also a corner of the platform where the mechanics differ sharply from Airbnb’s, which trips up hosts expanding from there (the structural differences are explained in how Booking.com works for hosts). This guide covers: the deposit-versus-program choice; what “deposit per accommodation per stay” actually means; the real claim process, including its deadlines and evidence rules; how the whole system compares with Airbnb’s AirCover and genuine insurance; and the layered setup that experienced operators land on.
How do Booking.com’s damage policy options work?
You configure damage protection per property in the extranet (Property tab, then Policies), alongside the cancellation and prepayment terms that determine what guests owe if they cancel or no-show, choosing between two models, per partner.booking.com documentation accessed July 2026:
- Damage deposit. The traditional route: guests pay a refundable deposit capped at the amount you set (country-specific maximums apply), and you refund it after a clean checkout. Money in hand before damage happens, at the cost of booking friction and refund admin.
- The damage program (damage payment requests). Guests pay nothing upfront and instead agree that if damage occurs, you can request payment through Booking.com afterward, up to the cap shown on your listing. No friction at booking; the collection risk moves to after the stay.
The strategic difference is who carries uncertainty. Deposits make the guest carry it (and some guests book elsewhere rather than front the cash); the program makes you carry it, in exchange for a cleaner booking flow. That trade-off is the whole decision, and the right answer depends on your property’s exposure to damage and your market’s price sensitivity.
What does “deposit per accommodation per stay” mean?
It’s Booking.com’s phrasing for how the deposit amount applies: once per booked unit, per reservation, regardless of how many nights or guests the stay includes. A $300 deposit per accommodation per stay on a five-night booking for four people is $300 total, collected once and refunded once. Guests see this phrase at booking and routinely misread it, so if you run deposits, restate the terms plainly in your pre-arrival message; a guest who understands the deposit is refundable and singular disputes it far less often.
How do you file a damage claim on Booking.com?
The damage program’s process, with its real constraints:
- Document immediately after checkout. Clear photos of the damage, plus invoices or receipts for any money exchanged (replacement purchases, third-party cleaning beyond normal turnover).
- Submit within 14 days of checkout, per Booking.com’s damage program terms. The damage payment request is filed from the reservation’s details page in the extranet, with a description, the amount, and your evidence. Miss the window and the request can’t be made, so inspection needs to be part of every turnover, not a when-you-notice event.
- Booking.com contacts the guest. The platform informs them of the request and collects their response: agreement, comments, or refusal.
- Wait for processing and payout. Requests can take up to 14 days to process, and an accepted payment may take up to 30 days to reach your account via bank transfer.
Now the honest part. Booking.com facilitates; it doesn’t underwrite. If the guest refuses to pay or ignores the request, the program pays you nothing, and the platform states as much in its own materials. Covered categories are sensible (broken furniture and fixtures, water damage, holes, lost keys, extra cleaning with an invoice), while routine mess, wear and tear, and undocumented claims are out. Treat the program as a mediated request channel with real but modest recovery odds, and set your expectations, and your protection stack, accordingly.
US hosts get one genuine upgrade: properties in the US, Puerto Rico, and US Virgin Islands are automatically covered by Host Property Insurance on Booking.com reservations, an actual insurance layer (handled with an insurance partner) that pays on approved claims rather than depending on guest goodwill. It applies only to Booking.com stays and carries standard exclusions, but for American hosts it meaningfully changes the math.
How does Booking.com’s damage protection compare with AirCover and real insurance?
The three-way comparison nobody puts in one place:
| Booking.com damage program | Airbnb AirCover for Hosts | STR insurance | |
|---|---|---|---|
| What it is | Mediated payment request to the guest | Platform-funded damage protection with high stated limits | A policy you buy, covering property and liability |
| Pays when guest refuses? | No (except US Host Property Insurance layer) | Yes, subject to Airbnb’s assessment | Yes, subject to policy terms |
| Covers stays from | Booking.com only | Airbnb only | Every channel, plus vacancy |
| Cost to host | Free | Included | Annual premium |
The pattern to notice: platform protections are per-platform and weakest exactly where losses get serious, while insurance is channel-agnostic and strongest there. Airbnb’s equivalent mechanics, including how its deposit-free model works, Airbnb handles the same risk through AirCover and a deposit-free model that works differently from Booking.com’s, and Airbnb’s deposit-free AirCover model works on fundamentally different terms, while short-term rental insurance is the only layer that covers every channel, including vacancy. Multi-channel hosts should assume the floor, not the best case, from any platform program.
Do Booking.com damage deposits cost you bookings?
Damage deposits on Booking.com do cost some bookings, and the platform’s own product direction says as much: the platform built the deposit-free damage program precisely because upfront deposits add checkout friction on a marketplace that competes on frictionless booking. A meaningful share of guests, especially the hotel-accustomed travelers Booking.com attracts, will pick the identical listing that doesn’t hold their money. That doesn’t make deposits wrong; it prices them. High-damage-exposure properties (large groups, event-friendly homes, premium furnishings) can rationally pay the conversion cost. Standard properties usually do better with the program’s cap doing the deterrent work, since the visible “you may be charged up to $X” line filters careless guests nearly as well as a deposit does, without parking anyone’s cash. Whichever you choose, guest screening upstream beats collection downstream, which is where a tool like Screen & Protect earns its place: verifying who’s checking in reduces the incidents you’d otherwise be claiming for.
What should hosts actually do?
Layer it, cheapest deterrent first:
- Set the damage program cap deliberately. A visible, realistic cap (enough to cover your likely worst common incident) deters carelessness at zero conversion cost.
- Screen guests before arrival. Identity verification and risk screening prevent the small fraction of stays that cause most of the damage.
- Make turnover inspection a documented step. The 14-day window only helps if damage is found on day one, photographed, and receipted.
- Carry real STR insurance for the tail risk. Platform programs handle broken lamps; insurance handles floods, fires, and liability- the losses that end businesses.
- US hosts: know your Host Property Insurance terms. It’s automatic on Booking.com stays; read what it excludes so layers 1 to 4 cover the gaps.
Cheap deterrence up front, evidence discipline in the middle, genuine insurance underneath. Hosts who run that stack stop caring whether any single platform program is generous, which is the wrong thing to care about.
Frequently asked questions about Booking.com’s damage policy
Does Booking.com hold a damage deposit for hosts?
It depends on your configuration. Hosts can require a traditional deposit up to a set cap, with handling depending on your payment setup, or use the damage program, where no deposit is taken and damage is claimed after checkout through a payment request. The choice is made per property in the extranet’s policy settings.
What does “damage deposit per accommodation per stay” mean on Booking.com?
The deposit amount applies once for the booked unit and the whole reservation: not per night, not per guest. A $300 per-accommodation-per-stay deposit on a week-long booking for four people is $300 total, collected once and refunded after a damage-free checkout.
How long do I have to claim damage on Booking.com?
14 days from guest checkout to submit the damage payment request from the reservation’s details page, with photos and any invoices. Processing can take up to 14 days, and accepted payments arrive by bank transfer in up to 30 days, so the full cycle can run about six weeks.
Does Booking.com guarantee damage payments?
No. Under the damage program, Booking.com contacts the guest and facilitates payment, but money moves only if the guest agrees. The exception is US properties (including Puerto Rico and the US Virgin Islands), where automatic Host Property Insurance can pay approved claims on Booking.com reservations regardless of guest cooperation.
What does Booking.com’s damage program not cover?
Routine cleaning and general mess, normal wear and tear, and claims without evidence. Covered categories include damaged furniture and fixtures, water damage, holes in walls, lost keys, and third-party cleaning beyond normal turnover, with invoices or receipts required for any costs claimed.
Do I still need insurance if Booking.com has a damage policy?
Yes. The damage program is a mediated request, not coverage; it pays nothing when guests refuse, applies only to Booking.com stays, and excludes the catastrophic losses that matter most. Dedicated short-term rental insurance covers every channel, liability, and the tail risk no platform program touches.
Key takeaways
- Booking.com offers a deposit (guest cash upfront, booking friction) or the damage program (no upfront money, a mediated claim after checkout).
- The program’s claim window is 14 days from checkout, evidence is mandatory, and payment happens only if the guest agrees.
- US hosts get automatic Host Property Insurance on Booking.com stays, a real coverage layer the rest of the world doesn’t.
- Platform protections are per-platform and weakest for serious losses; multi-channel hosts need channel-agnostic insurance underneath.
- The winning stack: a deliberate program cap, guest screening, documented turnover inspection, and genuine STR insurance for the tail.
Stop damage before the claim form
Hostfully’s Screen & Protect verifies guests and adds protection across your channels, so damage requests become the exception. Get started with Hostfully.