At FLYR, we work to ensure a reliable and accurate integration between Protel and FLYR. That said, certain limitations in how Protel structures and exposes data can result in instances where reported figures between the two systems don't fully align.
If any of these discrepancies were identified during your onboarding process, our team would have proactively flagged and discussed them with you. Below is a detailed overview of known data gaps, their causes, and suggested workarounds.
1. Postings on accounts and PM rooms are not traceable
Description
Revenue posted directly to accounts or PM rooms in Protel is not accessible via the integration in a way that allows FLYR to trace or attribute it. Because there is no booking-level reference attached to these postings, the revenue cannot be surfaced in FLYR reporting.
Suggested workaround
Post revenue directly to the booking rather than to an account or PM room. This ensures FLYR can retrieve and correctly attribute the revenue.
2. Tentative and optional bookings mapped confirmed in FLYR
Description
Protel's "Tentative" and "Optional" booking statuses are not differentiated from confirmed bookings at the integration level. As a result, reservations carrying these statuses in Protel are treated as Confirmed in FLYR, which may cause a mismatch for future dates depending on which data you are looking at in Protel.
Suggested workaround
Be aware that Tentative and Optional bookings contribute to on-the-books figures in FLYR. Properties that use these statuses frequently should account for this when reviewing forward-looking data in FLYR.
3. Data Validation is DQE report is valid for data validation (on-premise only)
Description
For properties running Protel on-premise, data validation against FLYR should only be performed using the DQE (Data Quality Export) report. Other reports available in Protel — including the Manager Report and any custom-created reports — may include revenue sources (such as account room revenues) that FLYR does not receive via the integration. Comparing FLYR against these reports will produce apparent discrepancies that do not reflect a real data issue.
Suggested workaround
When validating revenue data for a Protel on-premise property, always use the DQE report as the reference. If you are unsure how to generate this report, please contact your Protel support team.
Note: This limitation applies to Protel on-premise only. Protel Air properties are not affected.
Summary
FLYR's integration with Protel captures the majority of operational and financial data accurately. The scenarios above reflect specific structural limitations within Protel — particularly for on-premise deployments — that can cause persistent discrepancies. Following the suggested workarounds and using the correct validation report will significantly reduce confusion around data differences between the two systems.
For information on temporary discrepancies, see PMS–FLYR data discrepancy: data not matching.
If you have any questions or encounter a discrepancy not listed here, reach out to our support team. We're here to keep your reporting as accurate as possible.