Techbanq

Hospitality · analytics

One occupancy number the commercial team can act on

A revenue manager pulls occupancy from the PMS, channel production from the OTA extranets, spend from the POS and pace from the booking engine, and the four rarely reconcile. Hotel analytics is the work of making those sources agree on one revenue figure, one occupancy figure and one guest, so a decision rests on numbers the team trusts rather than on the report they distrust least.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
Commercial Director, COO
Decision
Unify property data into revenue and operations dashboards
Languages
EN · AR

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The sources

The four systems a revenue number has to be reconciled from

Each system is authoritative for something and misleading for the rest, and the analytics work is knowing which to trust for what. Trusting one alone is how a revenue meeting argues about which report is right.

The PMS

Occupancy, in-house revenue and the reservation of record — the room side of the truth.

What it distorts if trusted alone: It undercounts channel cost, because commission is deducted where the PMS cannot see it.

The booking engine

Direct-channel pace and conversion — how the property's own bookings are building.

What it distorts if trusted alone: It sees only the direct channel, so on its own it hides where the demand actually came from.

The OTA extranets

Channel production and the commission that comes with it — the intermediated share of demand.

What it distorts if trusted alone: Each extranet reports in its own definitions, so summed naively they double-count and mismatch the PMS.

The POS

Food, beverage and ancillary spend — the revenue that is not the room.

What it distorts if trusted alone: Detached from the guest, it cannot tell you which segment or channel spends on property.

Why the report is distrusted

The dashboard nobody in the revenue meeting believes

The familiar scene in a revenue meeting is three people with three numbers for the same night, each pulled from a different system, and twenty minutes spent arguing about which is right before anyone can discuss what to do. The dashboard on the screen does not resolve it, because it was built on top of the same unreconciled sources and inherits their disagreements. A report that cannot be trusted is worse than no report: it makes decisions slower, not faster, and it trains the commercial team to fall back on instinct.

So the analytics work is reconciliation before visualisation. Before a chart is drawn, the systems are made to agree on definitions — what counts as revenue, when a booking is recognised, how a channel is attributed — and the guest is resolved to one identity across them. Only then is a dashboard worth building, because a number the team trusts is one they will act on. The visual layer is the easy, visible part; the reconciliation underneath it is the part that decides whether anyone believes what it shows.

The model

Four feeds converging into one revenue and operations view

The inputs each carry a partial truth; the reconciliation column resolves them onto one guest, one rate and one set of definitions; the outputs are the views the property actually runs on.

Four data feeds — PMS, booking engine, OTA extranets and POS — converging into a reconciliation column that resolves one guest, one rate and one definition, producing three outputs: a revenue and pace dashboard, an operations and staffing view, and a channel cost and profitability view.

  • PMS feed

    Occupancy, in-house revenue and the reservation record.

  • Booking engine feed

    Direct pace, conversion and the funnel behind it.

  • OTA extranet feed

    Channel production and the commission attached to it.

  • POS feed

    Food, beverage and ancillary spend on property.

What we do

Reconciliation: one guest, one rate, one definition

The feeds are matched to a single guest and a single set of definitions, so revenue, occupancy and channel are counted the same way across all four before anything is charted.

  • Revenue and pace dashboard

    One revenue and occupancy figure the commercial team acts on.

  • Operations and staffing view

    Arrivals and occupancy tied to workload, so staffing follows demand.

  • Channel cost and profitability

    What each channel actually nets after commission, not gross production.

The dashboard is the visible tenth of the work; the reconciliation is the nine-tenths that make it believed.

Our role

What we reconcile and what the revenue team decides from it

  1. 01

    The reconciliation, first

    We make the PMS, booking engine, OTA extranets and POS agree on definitions and on one guest, before any chart is drawn, because a dashboard on unreconciled data inherits the argument.

  2. 02

    The views the property runs on

    Revenue and pace for the commercial team, occupancy and arrivals for operations, and channel profitability after commission rather than gross production.

  3. 03

    A model your team can extend

    The reconciliation and its definitions are documented, so your revenue team can add a question without rebuilding the foundation each time.

The pricing calls, the channel strategy and the operational decisions stay with your commercial and operations teams; we give them one reconciled set of numbers to make those calls on, rather than four systems that disagree about the same night.

Common questions

What buyers ask

Why can't we just use the reports our PMS already produces?+

Because the PMS only sees the room side of the business. It is authoritative for occupancy and in-house revenue, but it cannot see the commission deducted inside an OTA extranet, the direct-channel pace in the booking engine, or the food and beverage spend in the POS. A PMS report is a true account of one part of the picture presented as if it were the whole, which is exactly why the numbers argue with the other systems. Useful analytics starts by reconciling all four so the PMS's strengths are kept and its blind spots are filled, rather than treating one system's partial view as the answer.

Do we need a data warehouse, or can this run off the systems we have?+

It depends on how many properties you run and how often the numbers are needed, and we would rather right-size it than sell a warehouse by default. A single property that needs a reconciled daily view can often be served by a lighter model that reads from the existing systems on a schedule. A group with several PMS instances, multiple extranets and a need for near-real-time pace usually does warrant a central store, because reconciling on the fly across that many sources becomes the bottleneck. The decision is driven by the scale and the cadence of the questions, not by a preference for the heavier architecture.

The OTA figures never match the PMS. Which number is correct?+

Usually neither, on its own, because the two are counting different things and calling them the same name. An extranet reports production on its own terms — often gross, sometimes on a booking date rather than a stay date, and with cancellations handled differently from the PMS — while the PMS reports the stay as it actually happened. The mismatch is not one system being wrong; it is the definitions not lining up. Reconciliation resolves it by agreeing a single set of definitions and matching the bookings across systems, so the OTA production and the PMS revenue become two consistent views of one reality rather than two numbers nobody can bridge.

Review it with us

A reconciliation of where your four systems disagree on revenue and occupancy, and a plan for one trusted view before another dashboard is commissioned.

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.