At FLYR, we work to ensure a reliable and accurate integration between Cloudbeds and FLYR. That said, certain structural characteristics of how Cloudbeds organises and exposes data can result in instances where 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 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.