Revenue and pricing

Where room revenue leaks: a monthly audit from the reservation to the invoice

Revenue leakage is money a hotel was entitled to but never collected. This guide outlines a monthly audit that samples twenty reservations to compare three records, revealing gaps in rates, extras and comps.

  • 11 min read
  • AI Otel Editorial

AI draft · awaiting editorial review

Contents

Key takeaways

  1. A leak is a gap between three records, the reservation, the folio and the fiscal document, not a low price.
  2. Twenty reservations a month, chosen by a rule rather than by memory, reveal a pattern faster and more cheaply than a full-year review.
  3. Every deviation needs a document: a rate code, a written approval or a reason attached to the correction. No document means a finding.
  4. Comp rooms and uncharged no-shows cost room-nights, so report them as a count and a value, not as a footnote.

Revenue leakage is money a hotel was entitled to under its own written terms but never posted, invoiced or collected. A monthly hotel revenue leakage audit samples twenty reservations and compares three records, the reservation, the guest folio and the fiscal document, so the pattern shows up in weeks rather than at year-end.

The room was sold at one rate and posted at another. The guest was charged for breakfast twice, or not at all. Nothing looks wrong in the monthly total, and that is exactly the problem: leaks are small, spread across many places and invisible in totals. This article gives you a routine that fits in one sitting a month. After reading it you can draw a sample, compare it in three directions and put the result on one page for the owner.

What counts as room revenue leakage, and what does not?

Leakage is revenue the hotel was entitled to under its own written terms but did not post, invoice or collect. It is a gap between what was sold and what was recorded, not a price the hotel chose to accept.

The audit compares three records. The reservation holds what was sold, to whom and on which terms. The folio, the guest bill, holds what was consumed during the stay. The fiscal document holds what the hotel declared and collected. A leak is a gap between any two of them that nothing explains.

Plenty of gaps are not leaks. A discount agreed in writing before arrival, a contracted corporate or agency rate, a comp approved by an owner and a rate the revenue manager deliberately opened to fill a gap are decisions, and decisions have documents. Apply one test to every deviation: is there a document that explains it? A rate code, a signed approval, a written agreement, a reason on the correction. If yes, note it and move on. If no, it is a finding.

Treat overcharging as a finding too. A guest charged more than the confirmed rate produces a refund, a complaint and a review, so record the direction of the gap, not only its size. Measure each finding as a count and a lira amount, so one month can be compared with the next without percentages or estimates. And keep the audit about the process: the question is which control was missing, not which person was careless.

Key pointA leak or not a leak

A leak: sold but not posted, consumed but not invoiced, charged but not matching the confirmed terms. Not a leak: a written discount, a contracted rate, an approved comp. If the document exists, it is a decision. If it does not, it is a finding.

How do you sample twenty reservations without reading everything?

Pick twenty reservations by a fixed rule, spread across channels and situations, and read the same three records for each. The sample is small enough to finish in one sitting and varied enough to show whether a problem is general or isolated.

Stratify the twenty: five from online travel agencies, five direct (hotel website, phone, walk-in), five group or corporate, and five that involved an extra, a comp or a room move. Force two difficult cases into every sample: one no-show and one late cancellation that carried a charge. These are the cases most often handled outside the system.

Choose by rule, not by memory. For example, take the fifth reservation on each of four arrival days, or every tenth name on the arrival list. A sample chosen by curiosity finds only what someone already suspected. Before you look at any money, record the reservation number, the arrival date, the channel and the last person who changed the booking. That history is where the explanation usually sits.

Keep the sample list in a file and carry it forward, so next month's sample does not repeat the same reservations and the audit covers the year evenly. If most of the first sample produces findings, keep the sample at twenty and add a direction rather than growing the list. The aim is a repeatable routine, not a bigger project.

ChecklistThe monthly sample

  • Five OTA reservations
  • Five direct reservations
  • Five group or corporate reservations
  • Five reservations with an extra, a comp or a room move
  • Within the twenty: one no-show with a charge, drawn from the OTA or direct group
  • Within the twenty: one late cancellation with a charge, drawn from the OTA or direct group
  • Reservation numbers written down
  • Last-change history noted for each

Reservation versus folio: what should match?

Five fields must match: the nightly rate, the number of nights, the room type, the number of guests and what the rate includes. A mismatch in any of them is either a documented change or a finding.

Start with the rate. Compare the rate stored on the reservation with the rate posted night by night on the folio, not with the total, because a total can hide two nights that cancel each other out. Watch the manual override: a rate keyed by hand at check-in with no rate code and no approver is a frequent point where a channel rate and a posted rate drift apart.

Check the package, not just the price. A rate sold with breakfast, a transfer or spa access has to arrive on the folio as those components; otherwise the guest is charged again at the desk or the hotel absorbs the cost silently. Check the nights after any change: early departure, an extension and a room move all rewrite the stay, and the folio sometimes keeps the original nights or the original room type.

Read the reservation history, not only the final record. The question is who changed what and when, and whether the change was authorized. Note the direction of each mismatch, charged less than sold or charged more, and record the amount of the difference rather than the whole rate.

FieldSold value lives inPosted value lives inA mismatch usually means
Nightly rateReservationFolio, night by nightA manual override with no rate code
NightsReservationFolio postingsA change never rewritten on the folio
Room typeReservationFolio room chargesA room move priced at the old type
GuestsReservationFolio occupancy linesExtra guests never added to the rate
Package contentsRate planFolio extrasComponents charged twice or absorbed

Folio versus fiscal document: where do extras go missing?

The folio is the hotel's internal record and the fiscal document is what it declared. Compare them line by line for the sampled stays, because extras are where the two most often part company.

List the extras that commonly fall between the two: minibar, restaurant and bar, spa, late check-out, and transfers arranged at the desk. Each one needs to appear on both records or on neither. Follow any charge that was moved: a line transferred to a company account or a group master bill has to be traceable in both directions, from the guest's bill to the receiving account and back.

Look at corrections. A voided or reversed line needs a reason and a name; a deleted line leaves nothing to audit. Check discounts applied after the guest agreed the price, and ask who authorized the change and whether the authorization is written down anywhere. Check the sending queue, not only the totals: where electronic invoices (e-Fatura or e-Arşiv, the electronic invoice documents) wait for a person's review before sending, a document can sit unsent while the folio is already closed. The same discipline applies to matching terminal totals at night audit, which is a daily check that sits under this monthly one (card reconciliation at night audit).

Stop at the boundary. Which document applies to which taxpayer, and how a board or all-inclusive package is split for tax, are questions for your accountant; the audit only compares what exists.

Watch outDeletions cannot be audited

A deleted line leaves no trace and no reason. A correction should be a reversing entry with a name and a reason. If your system allows silent deletion, that is the first thing to change.

Comp and house-use rooms: what has to be on the record?

Every comp or house-use room needs four things on the record: the reason, the approver, the date and who stayed. A room without them is a room-night the hotel gave away without deciding to.

Separate the categories before counting: complimentary rooms (marketing, complaint recovery, loyalty), house use (staff, contractors, owners) and rooms blocked for maintenance. They carry different approvers and belong on different lines of the summary. Check the inventory side too: was the room taken out of sale deliberately, or was it sold and then comped after the fact? The second case is a different problem from a planned giveaway.

Look for the pattern rather than the single case: the same approver, the same weekday, the same room type, the same reason written in the same four words. Value the comp as room-nights at the rate the room would have sold for, so the owner sees a cost rather than a note. Keep the audit procedural: the control is the written reason and the named approver, and the check exists to protect the people who follow the rule as much as the revenue. Rooms are also one of the places where deliberate loss hides, alongside cash, and the same audit habit catches both (how cash and rooms go missing).

ChecklistPer comp room

  • Reason written
  • Approver named
  • Date recorded
  • Occupant or purpose recorded
  • Room removed from sale before arrival

Four ticks and a value in the summary. Anything less is a finding.

No-shows and late cancellations: was the policy actually applied?

Compare the charge with the policy the guest saw at booking, then check whether the room went back on sale and whether the charge reached the fiscal document. A no-show that was never charged and never released is two losses, not one.

Check the guarantee first. A reservation held without a card, a deposit or a contract cannot be charged, and the finding belongs to the booking process rather than to the front desk. Compare the amount charged with the policy shown at the time of booking, not with a policy written afterwards: a charge that matches nothing the guest could have read becomes a refund and a complaint.

Follow the charge to the end, posted to the folio or a separate account, then declared on the fiscal document. A charge that stops at the folio is revenue the hotel never recorded. Check the room: was it released back to inventory on the arrival day, or did it stay blocked for the whole stay while also being charged? Check reversals in the other direction too, because a cancelled charge without a reason is easy to overlook.

Group the results by channel. If most uncharged no-shows arrive through one channel, the problem sits in the connection or in the rate plan, not in the person on shift. Where consumer rules limit what may be charged, take advice: the audit compares the charge with the policy, it does not decide what the policy may say. The daily decision of when to charge, release or reinstate is covered separately (no-show handling).

What goes on the one-page summary for the owner?

One page, one row per finding, grouped by cause rather than by date, with an owner and a re-check date on each row. The owner reads causes and amounts; the team reads the fix.

Use six columns: finding, amount, how many similar cases, root cause, who fixes it, re-check date. Group by cause, not by reservation: rate keying, package posting, comp approval, no-show handling, correction practice. Five causes explain twenty findings far better than twenty separate lines.

Assign one owner per cause. Reservations owns rate codes, the front desk owns posting at check-in, accounting owns the fiscal document, the revenue manager owns channel rates. Keep the amounts honest: a comp room is a room-night value, not cash; a rate mismatch is the difference, not the whole rate; an unposted extra is the extra, not the bill. Leave staff names out of the summary and publish causes, owners and dates. Re-check the same cause in next month's sample: a finding that reappears after a fix tells you the fix was a reminder rather than a control.

FindingAmountSimilar casesRoot causeOwnerRe-check date
For example: room sold with breakfast, posted room onlyThe breakfast value, not the room6 of 20Package components not on the rate planReservationsNext month
For example: comp room with no approverOne room-night at the sold rate2 of 20No written comp approval stepFront office managerNext month

What to do next

Run the first sample this month: twenty reservations, chosen by a rule, read in three directions, written onto one page. The single finding matters less than the cause it repeats, and the cause is what the owner can fix before the year-end closes the books.

Frequently asked questions

How often should a hotel audit revenue leakage?

Monthly, on a fixed date, with the same sample rule each time. Monthly keeps the sample small and the memory fresh; a yearly review finds patterns too late to correct the year they happened in. The daily checks, night audit and card reconciliation, stay daily; this audit sits on top of them.

Is a rate mismatch between the channel and the hotel system always a loss?

No. A mismatch is a finding only when nothing explains it. A rate code, a written approval or a documented change turns it into a decision. The audit's job is to separate the two, and to record the direction of the gap, because overcharging also costs the hotel.

Who should carry out the audit?

Someone who does not post the entries being checked: typically the owner, the accountant or the revenue manager, working from read-only reports. The person who keys rates at the desk can supply the explanation but should not be the only one judging it.

Can hotel software find these leaks automatically?

Partly. A system can compare the reservation with the folio and flag differences, and it can report comps and uncharged no-shows. What software cannot supply is the reason: whether a discount was agreed, whether a comp was approved, whether a correction was justified. That judgment stays with a person.

What if the first sample finds nothing?

Check the sample before concluding the hotel is clean. If the twenty were chosen by convenience, choose them again by rule and force in a no-show, a late cancellation and a comp. A clean sample chosen by rule is a good result and a reason to keep the routine.

AI Otel EditorialEditorial team

Drafted with AI assistance from AI Otel’s published fact base. Not yet reviewed by an editor.

Hotel guides for Türkiye on trbnb

For hotels: OtelCiro.

OtelCiro, AI Otel’s hotel growth and consultancy arm, is operating today.

Talk to OtelCiroRequest a briefing