Rounding hotel prices in two currencies: euro rates, lira bills and who bears the cents
Rounding errors between euro rates and lira bills create mismatched totals. This guide explains the four rounding points, how to write a clear policy, and how to test that every sales path produces the same payable figure.
Contents
Key takeaways
- A euro rate is a contract figure; the lira amount is derived from it, and every system that derives it rounds somewhere.
- Round once, at the last step that must produce a payable amount, and keep the unrounded figure next to it in the record.
- Rounding per night and rounding per stay give different totals, so the rule has to say which one settles the bill.
- The order of discount, conversion and rounding changes the cents, so fix the order in the rule rather than at the desk.
- A difference at checkout is settled by showing the working, not by apologizing for the rate.
Rounding is the step where a euro rate becomes a lira figure. It happens in four places: the rate plan, the channel display, the booking record and the bill. Each rounds at its own moment, so one stay can show two totals. One written rule, shared by all of them, keeps the cents in one place.
A guest books a euro rate, reads one total on the confirmation and another on the folio, and the front desk has two numbers and no rule to choose between them. The gap is usually a few lira, and it is always in the same place: a rounding step nobody wrote down. Hotel price rounding between euro and lira is not an arithmetic problem, it is a policy problem, and policy can be written. After reading this you will know where the four rounding points sit, what a complete rounding rule contains, and how to test that every sales path produces the same payable figure.
Where does rounding happen between a euro rate and a lira bill?
At four points: the rate plan, the channel's display, the booking record and the bill at checkout. Each one converts and rounds on its own schedule, which is why the cents move.
The rate plan is the first point. The hotel sets a euro figure and the lira figure is generated from it, not typed by hand. Decide whether that lira figure is stored once or computed every time it is shown, because the two behave differently when the rate moves. A stored figure stays fixed until someone changes it; a computed figure follows the exchange rate, which is useful for display and dangerous for settlement.
The channel display is the second point. A channel shows what it is sent. Send a lira figure and the channel does not convert; send euro and the channel converts and rounds to its own increment, which you do not control. This is the one rounding step that can sit outside your property entirely.
The booking record is the third. The moment of booking fixes a rate snapshot. Later rate moves must not rewrite the figure the guest already accepted, so the snapshot has to carry the unrounded figure as well as the rounded one.
The bill is the fourth. The folio runs in one currency. A euro charge posted to a lira folio is converted at posting time, which is a different moment from the booking, sometimes weeks earlier.
Display rounding and settlement rounding
Display rounding and settlement rounding are different jobs. Display rounding exists for readability: nobody wants to read a price with four decimals. Settlement rounding has to produce an amount someone can actually pay, with cash or a card. Mixing the two is the usual source of the second total: the display figure, rounded for comfort, gets mistaken for the payable figure, rounded for settlement.
The residue that accumulates
Name the leftover. Call it the rounding residue: the small difference created at each step, which accumulates across nights and across rooms in the same booking. A residue of a few kuruş per night is invisible on a one-night booking and visible on a group block. For more on how two-currency pricing fits the wider picture, see a hotel budget in two currencies with euro revenue and lira costs.
Why can the same booking show two different totals?
Because each total is derived at a different moment from a different starting figure, and each derivation rounds. The confirmation is built at booking time; the folio is built at posting time.
Per night against per stay is the first cause. Three nights at a rounded nightly figure rarely equal the stay total rounded once.
NoteWorked example (for example)
A nightly lira figure of 4.333,33, rounded to 4.333 for display, gives 12.999 over three nights when each night is settled separately. The same unrounded stay total, 13.000 minus rounding, rounded once at settlement, gives 13.000. One lira apart, no error in either path, two numbers on two documents.
Direction matters as the second cause. Rounding up on every line collects a residue in the hotel's favor, and a guest who checks the arithmetic can see the direction even when the amount is small. Rooms multiply it: a family in two rooms for three nights runs the same residue twice, so a rule that looks harmless on one room shows on a group block.
The currency of the folio decides the reference. If the contract is in euro and the folio in lira, the euro figure is the reference and the lira figure is the settlement, never the other way round.
The figure you feed your reports matters later. If average daily rate and revenue per available room are built from rounded nightly figures, comparisons across periods carry the same small distortion, so be consistent about which figure you feed in. The formulas themselves are covered in RevPAR, ADR and occupancy rate: formulas and common mistakes.
Two totals are not automatically a fault. An unexplained difference is.
What should a rounding rule contain?
Five answers in writing: when it rounds, to what increment, in which currency, in which direction, and who absorbs the residue. A rule missing any one of the five will be renegotiated at the desk.
When means naming the single settlement point. Rounding at the display, at the booking, at posting and at the bill are four different policies, and only one of them should decide what the guest pays. To what means the increment: whole lira, five lira, ten lira, or two decimals. The increment should match what the front desk can charge and what the channel accepts, and it should be stated in both currencies.
In which currency means separating the contract currency, which is the reference, from the settlement currency, which is what the guest pays, and saying which one is rounded. Direction means nearest, always up, or always down, plus what happens at the halfway point. Write the tie-break, because it is the case that gets argued.
Who absorbs the residue means the hotel, the guest, or whoever the direction happens to favor. A residue that always lands on the guest's side is a complaint waiting for a quiet week. Where it lives matters too: one line in the rate policy, visible to reservations, front desk and the accountant, and repeated in the channel settings so the same rule travels with the rate.
ChecklistBefore the rule is published, check
- The settlement point is named.
- The increment is stated in both currencies.
- The direction and the halfway tie-break are written.
- The owner of the residue is named.
- Per-night or per-stay settlement is decided.
- The rule appears both in the channel settings and in the front desk's written procedure.
Does the order of discount, conversion and rounding change the cents?
Yes. Rounding at each step compounds, so the same discount and the same starting figure produce different totals depending on the sequence you apply them in.
Three common orders exist: convert then discount, discount then convert, and carry the unrounded figure through to one final rounding. The third gives the smallest residue and the clearest audit trail. Rounding at every step multiplies the residue by the number of steps; rounding once at the end keeps exactly one residue, in one place, that someone can point to.
If the contract states a euro net, the discount belongs in euro, because converting first moves the base the discount is calculated on. A single package price covering room and board has to be split before anything is rounded, and the split method has to be written down. Which base a tax applies to, and which rate and which day apply, is a question for your accountant; the arithmetic order is yours to fix.
Write the order next to the rounding rule in the same paragraph. A rule without an order is half a rule, and the missing half is decided by whoever is on shift. The same order question appears when you set prices for a new season, as covered in setting next season's price rise with lira costs and euro contracts.
Watch outRounding at every step
Rounding at every step is the most common cause of a folio that does not match the confirmation. The fix is to round once at the settlement point and keep the unrounded figure in the record, so the difference can always be shown rather than argued.
How do you check that the website, the channel and the front desk agree?
Run the same three rates through every path and compare the payable figure at the settlement point, not the figure on the screen.
Pick three rates: a low one, a typical one, and one with a discount applied. Three is enough to expose an order problem. Run each through the hotel's own website, one channel, and a manual front desk booking, and write down the payable total and the folio currency for each. Compare the per-night display against the stay total on the same path; a mismatch there is a per-night rounding rule leaking into settlement.
Add a two-room booking to the test, because it doubles the residue and turns a rounding question into a visible amount. Repeat the test after any rate change or channel setting change, and keep the date and the result. A difference that appears only on one path is a settings problem, not a policy problem. Keep the test sheet with the rule, so the next person can rerun it without rebuilding it.
| Path | Currency shown | Where it rounds | Payable total (for example) |
|---|---|---|---|
| Hotel website | Lira | At display, per night | 13.000 |
| One channel | Lira | At the channel, per stay | 12.999 |
| Front desk, manual | Lira | At posting, per stay | 13.000 |
| Travel agency quote | Euro | Not rounded | 300 euro |
How do you explain a rounding difference at checkout?
Show the working: the contract rate, the moment of conversion, the rounding step and the resulting figure, on one line the guest can read.
The front desk needs the unrounded figure and the rounded figure side by side. With only one of them, the conversation becomes an argument about trust. Put the explanation in the pre-arrival message, before the guest looks at the folio. A difference explained in advance is a policy; the same difference explained at the desk is a surprise. A proforma invoice sent before arrival fixes the expectation in writing and gives the desk a document to point at, as described in a proforma invoice for a hotel booking and what it should show.
TipFront desk script, three sentences
Your rate is 300 euro, fixed at the moment you booked. It was converted to lira at the daily central-bank rate on the day of posting. The total was rounded once, to the nearest lira, which makes the difference of one lira you see here. Attach this to the pre-arrival message rather than delivering it at checkout.
Never call the difference a fee. If the gap is larger than the rule allows, it is not rounding: correct it and say so, because a rule stretched once stops being a rule. Record every case. The same difference recurring on one channel is a configuration issue to fix, not a conversation to keep having.
What to do next
Write the one-page rule this week: the settlement point, the increment in both currencies, the direction with its tie-break, the owner of the residue, and the order of discount, conversion and rounding. Then run the three-rate test on the website, one channel and the front desk before the next rate change, so the rule is checked while nothing is at stake. The pieces fit together in one direction: a euro rate is the reference, the lira figure is derived once, and every path derives it the same way.
If you are reading this as a traveler rather than a hotel professional, you can browse hotels across Türkiye (opens in a new tab) and see the payable figure before you book.
Frequently asked questions
Should a hotel quote its rates in euro or in lira?
Separate the contract currency from the settlement currency: the contract currency is the reference figure, the settlement currency is what the guest actually pays, and the confirmation should state both. Which currency a contract or an advertisement may use is set outside this article, so confirm your own case with your adviser. What the hotel controls is that the rule names both figures and the conversion moment.
Why is the lira total on my confirmation different from the price I saw on the website?
The website figure and the booking figure are derived at different moments, and each derivation rounds. The booking record fixes a snapshot, so a later rate move does not rewrite it. The payable figure at the settlement point is the one that counts, and the rule should say so.
Should rounding be per night or per stay?
Per night for display, per stay for settlement, is the simplest split, but the rule has to say which one settles the bill. Per-night settlement accumulates a residue across nights and multiplies it across rooms. Whichever you choose, keep the unrounded figure in the record.
Who keeps the rounding difference?
The rule names the owner: the hotel, the guest, or whoever the direction favors. Small differences in either direction are normal. A residue that always lands on the guest's side is visible to anyone who checks the arithmetic, so state the direction openly rather than leaving it to the system default.
Does rounding change ADR and RevPAR?
It changes them if you feed rounded nightly figures into the formulas, and it changes comparisons across periods if you switch between rounded and unrounded figures. Pick one source figure, use it consistently, and note which one the report uses so two reports are never compared on different bases.


