A Negative Balance and How It Was Reconciled

An account can drop below zero through a chargeback, a damage claim or a fee you did not expect. Four steps get it back.

Last updated: October 31, 2026

The number at the top of the account is a net. When it goes under zero, it's showing you the result of a decision someone else made before you had a chance to answer it — a guest's card issuer, a claims desk, a fee schedule. That's an accounting event, not a verdict on how you run the place. The first hour is about finding which line moved.

Key Takeaways

• A negative balance is a subtraction, not a judgment. Something was deducted. Start there and skip the part where you take it personally.
• Find the line before you build the argument. The line has a date, a reservation and a reason code, and those three decide everything.
• Read the terms in force now. Not a screenshot from last year, not a forum post. The window and the rule that apply are the current ones.
• One case, one folder, one index. A dozen dated items beat forty unsorted ones, every time.
• Don't measure cash with performance numbers. Occupancy, ADR and RevPAR describe the calendar. They say nothing about the balance.

How a balance goes negative

Four routes do most of the work.

A guest disputes the charge with their card issuer, and the amount leaves the account while the dispute is open. A damage claim opens against a reservation, and the platform holds or deducts the amount it's assessing. A fee lands that wasn't in your model — a cancellation handled under a policy you set months ago, a cleaning charge the platform adjusted, a subscription line you forgot. Or you refunded a guest yourself, and the refund cleared before the next payout arrived.

Each route looks different from the outside and identical from the inside. They all hit the same pot, and the pot is what's left after bookings, fees and refunds have been netted against each other. One deduction bigger than the balance takes it under, and the size of that deduction has nothing to do with how well the month went.

That's the part that catches people. A strong month and a negative balance are perfectly compatible. The calendar sold, the guests came, the reviews were fine, and then one line moved by more than the pot held.

So the first question isn't why this happened to you. It's which line did it, and what does that line say.

What to check in the first hour

Open the statement, not the inbox. The statement has the deduction on it, with a date, a reference and usually a short reason. Write those down before you write anything else.

Then find the reservation behind it. A claim on a stay that's still running is a different animal from a claim on one that ended six weeks ago, and the evidence you can still gather is different too. If you're not sure whether the guest is still in the unit, a read-only view of today's arrivals, who's in house and which rooms are due out settles it in seconds, and it settles it with a timestamp.

Then read the current terms for that specific item. Not the terms in general — the item. Every route has its own reply window and its own idea of what counts as evidence, and those are set by the platform and change. The version that matters is the one in force today, which is why the first thing you save to the folder is a copy of the page you read, with the date.

What you don't do in that hour is pay the balance down to quiet the screen. Paying first and asking second is the most expensive way to feel better. It also makes the case harder to argue, because a settled line looks like an accepted one.

localsbnb.com keeps Airbnb, Booking.com, Agoda and Trip.com on one calendar, with the reservation record attached. A deduction can then be traced to a booking, a date and a channel without rebuilding the timeline out of four separate inboxes.

The paper trail that decides it

Whoever reviews the case is reading a file, not listening to a story. Build the file so a stranger can follow it in two minutes.

Start with the line: the deduction, the date, the reference, the reason code as written. Then the reservation: nights booked, nightly rate, guest name, check-in and check-out. Then a timeline in plain order — when the guest arrived, when they left, when the claim appeared, when you replied. Then the evidence that answers the reason code specifically.

That last one matters more than the size of the folder. If the code says damage, photographs of the damage are the answer, and your cleaning schedule isn't. If the code says the unit wasn't as described, the listing copy and the photos that were live at the time are the answer, and a message about your renovation plans isn't. Answer the question that was asked.

Keep the file small and dated. Twelve items with timestamps beat forty screenshots with no context. Name the files by date and subject, and put one line of description in the index for each, so nobody has to open them to know what they are.

Then write once. Short sentences, no adjectives about the guest, no speculation about motive, no rhetorical questions. State what happened, attach what proves it, and say what you're asking for. If the platform's process gives you a form, use the form and keep the long version as an attachment.

One practical note. Keep a copy of the whole file somewhere you control, not only inside the platform's messaging system. Access to a case can change, and the one thing you never want is to be explaining a deduction with the evidence sitting behind a login you can no longer use.

Preventing the next one

You can't prevent a guest from disputing a charge. You can make the next dispute cheap to answer, and you can stop one deduction from taking the account under.

The buffer is the first piece. Size it against the largest single deduction you could plausibly face on your own portfolio, not against an average month. That number is yours to work out from your own statement history, and it's worth revisiting when you add a unit or a channel.

Timing is the second. A refund issued the day before a payout hits a smaller pot than the same refund issued the day after. If you know when money lands, you know which week is a bad week to send money out. That's a calendar problem, and calendars are easier to fix than arguments.

The third is the habit of collecting evidence while the stay is happening. Photos at turnover, dated. The listing as it was when the guest booked. A note of anything the guest reported and what you did about it. None of that is work you do for a claim. It's work you do anyway, and the claim just makes it valuable.

The last is knowing which numbers you're looking at. Occupancy, ADR and RevPAR tell you how the calendar performed. They're useful, they're on the dashboard, and they will never tell you what's in the account. A host who reads a good ADR as a healthy balance is one deduction away from a surprise.

FAQ

Will the platform give the money back?

Sometimes, and nobody can tell you in advance. What decides it is the reason code on the line, the evidence you can produce against that code, and the terms in force when the deduction was made. Read the current terms, answer the specific question that was asked, and don't treat a reversal as the plan — treat it as one of two possible outcomes.

Can I keep taking bookings with a negative balance?

That depends on the platform's current terms and on how the account is set up, so check both rather than assuming either way. What you can control is speed: a line that's answered inside its window is a different situation from one that sits there for a month.

How long does a reconciliation take?

There's no number worth quoting, because it varies by route, by platform and by how complete the file is. The practical version: the clock usually starts when you submit, not when you noticed, which is one more reason the first hour matters as much as it does.

Reconciling a negative balance is unglamorous work — a statement, a date, a folder, a short reply. It's also the whole job. localsbnb.com won't argue a deduction for you, but it keeps the booking, the channel and the dates in one place, which is what the argument is made of.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Chargeback rules, claim processes and payout terms differ by platform and change without much notice, and nothing here states an amount, a cap or a deadline. Confirm the position against the current terms of each platform you use, and take local advice on anything that turns into a legal question.