Overview
If you use Opera Cloud (OHIP) as your PMS and have group bookings, you may occasionally notice a temporary discrepancy between the revenue figures in FLYR and your Opera History & Forecast (H&F) report. In many cases, this is caused by how PM (Post Master) accounts are handled during the data transfer between Opera and FLYR.
This article explains what PM accounts are, why they can cause temporary discrepancies, and what to do when you spot one.
What is a PM Account?
A Post Master (PM) account in Opera Cloud is a special folio used for group billing. When a group of reservations is created, individual room charges are often routed to a central PM folio rather than being settled on each individual reservation. This allows the group organiser or company to settle a single consolidated bill.
How FLYR Handles PM Revenue
For group bookings with a PM account, FLYR is designed to track PM revenues separately and avoid double-counting. However, there is a known temporary behaviour that can occur:
When a group PM account is active, FLYR may temporarily show revenue from both the individual reservations and the PM folio before the payment is posted and reconciled. Once the payment is posted (typically after the night audit), the data corrects itself automatically.
This discrepancy is typically temporary and self-resolves once the PM payment is posted and the data is re-synced. In some cases, a manual sync of the PM booking may be needed — please reach out to support if this occurs.
How to identify which PM is causing the discrepancy
If you are trying to locate the specific booking reference causing an adjustment in FLYR:
Open the relevant tile or metric in FLYR
Click the Explore button (the small compass icon in the upper right corner of the tile)
This opens a detailed drill-down view — add the reference ID or reservation ID as a filter to trace the source of the discrepancy
What to Do if You Spot a PM Discrepancy
Check the date and timing — If the discrepancy is on a future date or the current open month, it may resolve after the next hourly sync or the night audit.
Compare timestamps — Ensure both your Opera H&F report and FLYR data were extracted at the same time to rule out a timing difference.
Identify the PM reference ID — Use the Explore tool in FLYR (see above) to find the specific booking or PM reference causing the discrepancy.
Contact FLYR Support — If the discrepancy persists, share the PM reference ID with our support team via Fin. We'll check if a manual resync of the PM booking will resolve it.