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 Cloudbeds — not all reports reflect the same data that FLYR receives via the integration. This article covers which reports to use for validation, as well as known data gaps specific to the Cloudbeds integration, their causes, and suggested workarounds.
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 Cloudbeds reports
Pull the Occupancy History and Forecast in Cloudbeds, using net values throughout, to validate your data against FLYR. 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. If you're raising a discrepancy with our support team, also include the Transaction Details report pulled for the specific day in question.
1. Postings on accounts and PM rooms are not traceable
Description
Revenue posted directly to accounts or PM rooms in Cloudbeds is not accessible via the API 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. Occupancy counts differ for properties using split (virtual) inventory
Description
Cloudbeds has a functionality called Split Inventory, where physical room types can be sold in multiple configurations (e.g., a double room sold as a twin or a single). Cloudbeds calculates occupancy by adding up both physical and virtual inventory when calculating total capacity, which can differ from how FLYR reports occupancy.
FLYR reports on physical inventory only — the actual room types, not their virtual derivatives. This means that occupancy percentages or room counts in FLYR may differ from what Cloudbeds shows, as the two systems are measuring different things.
Suggested workaround
This difference is expected and is not a data error. FLYR's approach gives a more accurate picture of physical capacity utilisation. If you have questions about how your specific split inventory setup is mapped in FLYR, contact our support team.
Summary
FLYR's integration with Cloudbeds captures the majority of operational and financial data accurately. Following the suggested workarounds and using the correct validation reports 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.