Skip to main content

Data Differences Between RMS Cloud and FLYR Reporting

Explanation on data validation reporting and known limitations between RMS Cloud and FLYR

Written by Laya Janssens

FLYR pulls data at a granular, transactional level — every individual booking — and aggregates those records to calculate totals and KPIs. Because data is ingested at this level of detail, small variances between FLYR and your PMS are possible. We consider data accurate within a threshold of 1% at the monthly level.

If you notice a difference, the first step is to make sure you're pulling the correct report from RMS Cloud — not all reports reflect the same data that FLYR receives via the integration. This article covers which reports to use for validation.

If any of these discrepancies were identified during your onboarding process, our team would have proactively flagged and discussed them with you.


Validating data against RMS Cloud reports

Pull the History and Forecast Report in Excel, using net values throughout. When selecting your date range, go slightly beyond the affected dates — for example, if the discrepancy appears around October 12–15, pull the full month of October.


Summary

FLYR's integration with RMS Cloud captures the majority of operational and financial data accurately. No persistent known data limitations have been identified for this integration at this time.

For information on temporary discrepancies, see PMS–FLYR data discrepancy: data not matching. If you have any questions, reach out to our support team. We're here to keep your reporting as accurate as possible.

Did this answer your question?