FLYR pulls data at a granular, transactional level and aggregates individual bookings to calculate totals and KPIs. Small variances between FLYR and your PMS are possible.
What does accurate mean?
Data is considered accurate when FLYR achieves 99% accuracy on both units and revenue at a monthly level. This means monthly totals should be within a 1% variance of the PMS.
Insights refreshes hourly. For future dates or recently created bookings, check again after the next refresh before investigating further.
Step 1: Check filters
If a difference above 1% appears, review the dashboard and tile filters in Insights. The Home dashboard can have additional filters applied and, when Fixed Exchange Rates are used, is not suitable for validating revenue against PMS reporting. Use an unfiltered Insights revenue view for validation.
Key filters to compare
Currency — When comparing revenue in Insights with your PMS, select Property Local Currency so each property's revenue is shown in its PMS-defined local currency. Check that the PMS report is not being compared with Group Default Currency or another common conversion currency.
Revenue type — confirm both sources use Net or both use Gross.
Stay date range — confirm both cover exactly the same dates.
Accommodation revenue description — confirm both include the same categories, such as Overnight, Day Use, and No Show. See Correct filtering of revenue description in Insights and Home Page.
Capacity — confirm both use the same capacity definition.
Property — confirm both use the same property scope.
Segment or Macro Segment — confirm neither side has an unexpected segment filter.
If an unfiltered Insights view matches the PMS but another FLYR view does not, the difference is most likely caused by a dashboard or tile filter.
Step 2: Use the correct PMS report
Not all PMS reports are equivalent. Some include revenue categories or booking statuses that FLYR does not receive through the integration. Use the recommended validation report for your PMS in the Discrepancies between PMS and FLYR Reporting Help Center collection.
Step 3: Review known integration limitations
If the correct PMS report is being used and a variance above 1% remains, review the known limitations for your PMS integration in the Discrepancies between PMS and FLYR Reporting collection. Some operational scenarios can create larger variances, and the collection provides recommended practices to improve accuracy.
Step 4: Contact support
If you have checked the correct report, filters, Property Local Currency, revenue type, and known limitations and a discrepancy above 1% remains, contact Fin AI through the in-app chat with:
Property name
Specific dates and metrics that do not align
A screenshot of the mismatch or a link to the Insights dashboard
The PMS report being compared
Once this information is provided, the support team can investigate further.