The short answer
A hotel property-management system and a point-of-sale system can both be internally correct and still report different revenue. The PMS usually reflects folio postings and the hotel business date; the POS may reflect outlet checks, settlement time, item-level discounts, service charges, and its own close-of-day process. If the two systems apply different dates, categories, or gross-to-net rules, their totals are not directly comparable.
The practical fix is a bridge, not a forced match. Begin with the POS sales total, then list timing differences, transfers, voids, discounts, taxes, service charges, foreign-exchange effects, complimentary items, and manual journals until the bridge lands on the PMS or finance total. Each item needs a definition, owner, source record, and resolution rule.
Seven common causes of the mismatch
An outlet may close after midnight while the PMS rolls its business date earlier or later. Calendar-day extracts then assign the same check to different dates.
One report can include tax, tourism fees, service charges, or gratuities while another excludes them or posts them to separate ledger accounts.
Breakfast, packages, minibar, banqueting, and room-service items may map to broad PMS buckets that do not mirror POS outlet or item groups.
A correction entered after close can appear on the current POS day but reverse a prior PMS posting, especially when approvals happen the next morning.
POS checks posted to rooms can fail, duplicate, queue, or be transferred between folios. Cash and card checks may take a different path.
Finance may reclassify revenue or the PMS may split a package across rooms, food, and other services using allocation rules absent from the POS.
Property, outlet, and finance systems can apply different exchange rates, decimal precision, or rounding levels.
A repeatable reconciliation procedure
1. Define the question. Write the metric in plain language: for example, “net food revenue earned on the hotel business date, excluding VAT, service charge, tips, and complimentary items.” The wording is part of the control.
2. Freeze evidence. Export the PMS revenue report, POS transaction detail, interface log, and finance journal for the same business date. Record report names, filters, timestamps, property timezone, and whether late postings are included.
3. Reconcile one category. Choose one outlet or revenue code with enough activity to expose the process but a manageable number of transactions. Avoid starting with the entire month.
4. Build a mapping table. For every POS item group, document its expected PMS transaction code and general-ledger account. Mark taxes, charges, discounts, and package components separately.
5. Produce the bridge. Show the starting total, each reconciling category, and the ending total. Attach transaction identifiers so a reviewer can reproduce the movement.
6. Set tolerances and owners. A small rounding tolerance may be acceptable; an unexplained interface failure is not. Name who investigates, who approves adjustments, and when an item escalates.
7. Test recurrence. Repeat the method across several busy and quiet dates. A one-day match does not prove that the process is controlled.
What good looks like
The same inclusions, exclusions, date boundary, and currency apply to every report.
A variance links back to a check, folio, interface message, or journal—not a spreadsheet plug.
Thresholds determine who acts, by when, and what evidence closes an exception.
Recurring causes become mapping or process fixes, rather than permanent manual work.
Methodology and limitations
This guide applies control-design and data-lineage principles to a typical hotel PMS–POS–finance flow. It is intentionally system-neutral because fields, interfaces, business-day rules, and accounting policies vary by property. It does not replace review by the hotel’s finance team, auditor, tax adviser, or system vendor. A difference is not automatically lost revenue or fraud; it is a prompt to establish whether both numbers answer the same question.
For a broader sequence, use the hotel data audit, read The AI-ready hotel starts with trusted data, or see how leadership can reconcile its core KPIs.