Shown one price, charged another — date changes, re-priced stays and the screenshot that settles it

You shortened a stay by one night. The change screen did the arithmetic in front of you and named a figure — a refund of a few hundred, there in plain digits. You tapped confirm. The new reservation came back a couple of dollars more expensive than the old one, for one night less, and the refund you were shown behaved nothing like the number in your account. Support read the same screen back to you and said the system had done its job.

Most travellers read that moment as either theft or a bug. It is usually neither, and telling the difference decides what you write next. A change to a reservation is rarely a subtraction, and the figure a screen shows mid-flow is often only one half of two separate money movements. That does not make every gap acceptable — it means the question worth asking is narrower than "why did the number move?". The question is whether the final amount you confirmed matches the money that actually left your account. This guide is general information rather than legal advice, written to help you tell those two situations apart and act on the right one.

Why a change re-prices the whole stay

Here is the mechanic almost nobody is shown. When you shorten, extend or move a reservation, the system rarely removes a night from an existing booking. It closes the old reservation and writes a new one covering the nights that remain, at whatever those nights sell for on the day you make the change.

That single design choice explains most of the confusion, because it splits your money into two movements that need not arrive together:

• A refund of the original reservation. This is the figure the change screen tends to display most prominently, and it is usually the gross amount going back — the whole of what you paid, or the refundable share of it.
• A charge for the newly written reservation. This is priced today, not on the day you booked. It can land on a different statement line, on a different date, and sometimes in a different currency.

Read the first number alone and you expect several hundred back. What arrives is several hundred back and a fresh charge that may be larger than the piece you removed. So one night fewer costing more is arithmetically possible without anyone acting badly. Rates move for reasons that have nothing to do with you: the rate you booked six months ago is no longer on sale, the remaining nights turn out to sit on an event weekend, a length-of-stay discount tied to the longer trip falls away, taxes recalculate against a smaller total.

What the terms add is where the rules for a change live. Amendments, cancellations and refunds send you straight back to the policy you accepted (B6, A9) — meaning the conditions on your specific rate, shown on the property page, during booking and in your confirmation email. There is no general fairness test sitting above that. So the strong version of your request is never "this feels wrong"; it is "the screen stated this total, my card says that one".

The ways two numbers come apart

Before writing to anyone, work out which gap you actually have. They look identical on a statement and they are not remotely the same request — one is a plain arithmetic mismatch, another is a currency question for your bank, and one of them is a situation where the rules run against you.

Two rows of that table deserve a closer word, because they are the ones people most often read the wrong way, at their own cost. The currency row sends more travellers into pointless complaints than any other: a total displayed in euros and charged in another currency will not match to the cent, and a few percent of drift is the exchange rate doing its ordinary work rather than anyone overcharging you. The obvious-error row is the honest limit of this whole subject. Where a rate was plainly a mistake — a suite listed for the price of a coffee — the published position is that it does not bind, and the reservation can be cancelled with everything you paid returned. You can hold someone to a screen; you cannot hold them to a typo.

How can one night less possibly cost more?

Because a change usually is not a subtraction. The old reservation is closed and a new one is written for the nights that remain, at whatever those nights sell for today. A rate you locked six months ago disappears, a weekend turns out to be an event weekend, and a discount tied to the longer stay falls away. The arithmetic is real — which does not mean the screen explained it to you properly, and that is the part worth raising.

What people assume — and what the rules say

The assumptions below cost travellers real money in both directions. Some send people into arguments they cannot win; others make people drop a gap that would have been paid back with one message.

The workable position sits between the two extremes. A moving number is not proof of wrongdoing, and an explanation of the system is not proof that your account is right. Only the comparison settles it.

Where the request stands firmest

Some versions of this situation line up clearly behind you. They share one feature: a specific amount was stated to you at the moment of agreement, and a different amount moved.

• The confirmation and the statement disagree. This is the strongest case there is and needs no interpretation. Your confirmation email is generated automatically and carries the total you accepted; a charge above it was not part of that agreement. Cancel inside a permitted window and the terms are equally specific about the sum owed back — the exact amount initially charged, fees included (A8).
• A change screen stated a final figure and the money contradicts it. If the screen you confirmed named a refund or a new total, that is the number you agreed to, and the gap is a plain question of arithmetic rather than an opinion about pricing.
• The property charged something other than the confirmed rate. The reservation is meant to be handled as the page described it when you booked (2.5.3), and the property's own contract forbids adding administration or card-payment charges beyond what your confirmation lists (2.5.4).
• A mandatory cost never appeared in the displayed total. Price descriptions are supposed to state which taxes and charges are included (§1G), so a compulsory line that surfaced only at the desk was never part of the amount you accepted.

And the honest other side, so you do not spend a week on a case that cannot move. If the rate simply re-priced and the new confirmation showed the new total before you pressed confirm, you agreed to that number, however unwelcome it looks now. If the difference matches the day's exchange rate, your bank is the right address, not the property. If the rate was an obvious mistake, cancellation with a full return of what you paid is the published answer rather than a cheap stay. Recognising these early is not giving up — it keeps your energy on the version of the story that a stranger can verify in thirty seconds.

Capture the screen before you confirm

This is the one habit that changes the outcome, and it takes three seconds. Mid-flow screens are not emailed to you, they are not stored in your account, and support cannot always reproduce what you saw. Before pressing confirm on any change, screenshot the page showing the figures. Everything else in the list survives on its own; that screen does not.

• The change screen as it appeared, with the refund figure, the new total, or both visible in one image.
• Both confirmation emails — the original reservation and the amended one. Together they show what you agreed to before and after.
• The statement lines, with dates and amounts, for every movement: the refund, the new charge, any partial.
• The rate conditions on the original booking, since amendments run on the rate's own policy (B6) rather than on a general rule.
• The reference number of any call or chat, so a phone conversation that went nowhere still exists on paper.

One more thing worth knowing before you pick an address: the screen that produced the number belongs to the platform, but your stay contract is with the property, and the money may sit with either of them depending on how payment was arranged (§1H). Sorting out who is answerable for what saves you from arguing with the party that cannot fix it.

The order of events

Keep it short and dated. Most of these situations end at the second rung, and every later step gets easier because the earlier one exists in writing.

Underneath all of this sits a layer the fine print cannot quietly switch off: the consumer rules where you live, which on pricing tend to say one plain thing — before you pay, you should be told the real total you are committing to. The platform's own terms concede that these protections take priority where they apply (A19, A20). We are not a law firm and will not quote statutes at you; for a plain-language read in your own country, the network of European Consumer Centres publishes summaries. And when it is time to write that first message, that is the part we can take off your hands — 2refund turns your answers into a clear request that's yours to send.

The change screen named a refund amount and it never arrived in full. What now?

Put the two figures next to each other in writing: the amount the screen stated when you confirmed, and the amount that reached your account. Ask for the difference and nothing else. If a new charge went out at the same time, list that charge too, because the answer is often that the refund did arrive — and a fresh charge for the re-priced nights swallowed it. Send it through the platform's own complaint channel so it is logged with a reference you can quote later (A16).

The charge is a few percent off the amount I saw. Is that an overcharge?

Usually it is currency conversion, not an error. A total shown in one currency and taken in another moves by a few percent, and "pay in your own currency" at the card terminal adds a markup on top. Compare your statement against the day's rate before you write to anyone: a small gap that matches the exchange rate is a conversion question for your bank, while a gap far larger than the rate belongs with the platform or the property.

What to expect, and how long

A mismatch is settled by arithmetic rather than by judgement, which makes it one of the faster things to resolve — but the pace still depends on who is holding your money. Where the platform organised the payment, a refund it agrees to typically shows up within about five working days of being processed. Where the property took the payment directly, the timing follows the property and can run longer, which is why it pays to establish early which of the two you are dealing with.

Expect the first reply to restate the calculation rather than address the gap. That is not a brush-off so much as a script, and the way past it is to keep replying with the same two numbers instead of a new argument. Keep the request to the exact difference, too. A mismatch puts you back where the paperwork says you should have been — it is a correction, not a windfall, and the narrowness is precisely what makes it hard to refuse.

Support says the system calculated everything correctly. Is that the end of it?

Not by itself. "The system worked" answers a different question from "the money matches what I confirmed". Reply with the two numbers rather than the argument: this total was on the screen I accepted, this amount left my account, please explain the difference or return it. A specific, factual question is harder to close than a general complaint, and it keeps the exchange short.

I did not screenshot the change screen before confirming. Is my case finished?

No, though it is thinner. Your confirmation email is generated automatically and carries the total you ended up agreeing to, and your card statement carries the amount that moved — a gap between those two stands on its own without any screenshot. What you lose is the ability to prove what a mid-flow screen promised, so lead with the paperwork that still exists rather than with your memory of the screen.

Strip this situation down and it comes to one comparison, repeated calmly until someone answers it: the total on the screen you accepted, against the money that moved. Screenshot the screen before you confirm, work out which of the gaps above you actually have, and ask for that difference and nothing more.

The cases in this article are illustrative composites, not real client records. We build them from the patterns we see again and again across the disputes we help with, because we can’t share real customers’ booking details. The stories are invented; the way they play out is true to our experience.

This article is general information, not legal advice. We’re a self-help tool, not a law firm. Rules, fees and deadlines change and vary by country, so always check the policy attached to your own booking and your local consumer protections.