Quoting One Rate in Three Currencies: Display, Settlement and What You Actually Receive

Three different numbers wear the same name. Only one of them ever reaches your bank account.

Last updated: September 23, 2026

A rate you publish isn't a rate that arrives. Between the number on your calendar and the figure in your statement there are usually three separate conversions. Each is set by a different party, and each is taken at a different moment. That's why the same stay can be described by three honest numbers at once. This guide maps those three conversions and who controls each one. It explains why the difference between a displayed rate and a settled rate is legitimate rather than a fault, and what widens it. Then it sets out the policy and the monthly check that keep the gap from quietly becoming your margin.

Key Takeaways

• Three conversions, three parties. The channel sets the display one, the charging side sets the settlement one, the receiving side sets the last.
• The gap is time, not error. Each conversion is taken at a different moment, so the numbers drift apart without anybody making a mistake.
• Fewer conversions, smaller gap. Every extra hop adds a rate you didn't choose and a moment you didn't pick.
• Rounding is a pricing decision. A rate that survives rounding in one currency can look careless in another that carries no decimals.
• Reconcile the first payout monthly. One booking walked end to end catches what a monthly total never will.

The three currency conversions between a listing price and a payout, and who sets each one

Start with the number you control. Your listing carries a rate in one currency, and every other figure in the chain is derived from it. What follows isn't one conversion but three, and the useful thing about naming them separately is that each has a different owner.

The first conversion is yours to trigger but not to set: the channel shows your rate in the currency the guest is browsing in. The rate it uses, the moment it takes it and the way it rounds are all that channel's choices, and they're part of the reason two guests looking at the same night can be shown two different figures. Where a property follows a currency that carries no decimals — yen and won are the common cases — the rounding rule does visible work, because a rate that looks precise in dollars becomes a coarse, round number in yen.

The second conversion happens at the point of charge. The amount the guest sees is turned into the currency the booking settles in, by whoever processes that payment, using that party's own reference and its own timing. This is the hop most hosts never see, because it happens inside a transaction rather than on a screen.

The third conversion is the one you actually feel: settlement currency into the currency your account holds, applied by the receiving side, at whatever moment that side applies it. Everything that has accumulated — each conversion reference, each rounding, each fee — is visible here for the first time. And it's visible only as a net figure.

Sometimes two of the three collapse into one, usually when the guest browses in the same currency the booking settles in. A stay quoted to a domestic guest and the same stay quoted to an overseas one then don't travel the same path, so comparing their payouts tells you less than it appears to.

Why the displayed rate and the settled rate legitimately differ, and by how much it can

The first thing to accept is that the difference isn't an error. Three conversions taken at three moments won't produce the same number, and no amount of care on your side makes them. What you can control is how wide the gap gets.

Four things widen it. Time: the longer between the quote and the payout, the further each reference can move, which is why a booking made months ahead sits at the wide end. Hops: each conversion is another rate you didn't choose, so a path with three is wider than a path with two. Roundings: small individually, and they only ever accumulate in one direction on a net figure you can't unpack. Additions between display and settlement: taxes, local levies and fees that were never in the displayed rate at all, and that a guest reasonably believes were.

How much? There's no fixed figure to quote. Any percentage named as typical belongs to somebody else's market on somebody else's dates. The answer is structural: the gap scales with time and with the number of conversions. To find yours, take a stay you quoted at 100, look at what the guest was charged and what arrived, and express the difference as a share of the quote. Five stays across three months gives you a range that means something.

Setting a policy that keeps the difference from eating the margin

A currency policy is four decisions, and all four should be written down before a guest asks about any of them.

Quote in one currency and own it. Pick the currency your costs are actually in — the one your cleaner, your utilities and your tax are denominated in — and publish in that. Quoting in a currency you don't pay bills in simply adds a conversion you chose to take on.

Decide who absorbs the difference, in writing. Either your rate is fixed in your currency and the guest's total moves with the conversion, or the guest's total is fixed and your net moves. Both are defensible; what isn't defensible is leaving it undecided, because the decision then gets made per booking by whoever answers the message.

Remove hops where you can. Every conversion you delete from the chain is one you no longer pay for. Where a channel lets you choose the currency a rate is published in, choose the one that sits closest to settlement rather than the one that reads best on screen.

Round deliberately. Set rates that survive the rounding rules of the currencies your guests actually browse in, rather than rates that look precise in your own. A rate of 97.50 is a decision in a currency with two decimals and a rounding artefact in one with none.

Two details make the policy easier to hold. Currency and timezone follow the property, so a portfolio spread across countries isn't running one rate but several, each with its own rounding. That's a reason to check each property's setting rather than assume a global default. And the figures you use to judge any of this — occupancy, average daily rate and revenue per available night — only compare cleanly when they're read in the same currency as the costs they're set against.

The reconciliation check to run on the first payout of each month

Pick one booking from the month just closed and walk it end to end. Not a total, not a summary: one booking, with its dates in front of you. Write down five numbers in order — the rate you published, the amount shown to the guest in the currency they browsed in, the amount charged in the settlement currency, every deduction listed, and the amount that arrived. Then answer three questions.

Does the difference sit inside the range you measured for your own bookings, or is it outside it? Anything outside means one of the three conversions behaved differently this time, and the only place to find out which is the statement that itemises it. Do the deductions look like the things you expect — commission, taxes, a cleaning line — or is there one you can't name? An unnamed deduction is a change you haven't read about yet. And did the arrival date match the terms you thought you were running, or has the interval between departure and payout moved?

Keep the result as one line per month: date, booking reference, the five numbers, and what you concluded. Twelve of those lines tell you more than any dashboard total, and they're the only way to notice a slow drift, which looks exactly like normal on a figure you only glance at.

Reading those three performance figures alongside the calendar you quoted from at localsbnb.com keeps the whole check in one sitting. Occupancy, average daily rate and revenue per available night sit next to the rate that produced them.

FAQ

Should I publish in the currency most of my guests use?

Publish in the currency your costs are in. Guests browse in their own currency either way, because that conversion belongs to the channel, so publishing in theirs adds a hop without removing one.

Why did two guests pay different amounts for the same night?

Because each saw the rate converted into a different browsing currency at a different moment, and possibly along a path with a different number of hops. Same night, different route, different total.

How often should I review my rates if currency moves?

On a fixed schedule rather than reactively — monthly is enough for most properties. A rate you change every time a headline moves is a rate nobody can recognise, including you.

Same name, three numbers: the rate you publish, the rate the guest is shown, and the amount that arrives. Name them separately and the gap stops being mysterious and becomes a policy question with four answers and a monthly check. Quote in the currency you pay bills in, delete the hops you can, and set rates that survive rounding. And if you want the calendar, the currency setting per property and the three figures that judge the result in one place, that's what localsbnb.com is for.

---

Conversion behaviour, settlement currencies and payout timing differ by channel, by region and over time; check the current terms shown for each channel you sell on before relying on anything here.