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 Mews — 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 Mews 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 Mews reports
Pull the reports in Excel where possible, 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.
Manager Report By Day — use this report to validate data against FLYR
Mode: Day | Group by: Service | Status: Confirmed | Values: Net value
Reservation Report — include this when reaching out to support about a specific discrepancy
Group by: Space category | Date range: exact day, 00:00 to 00:00 | Reservation type: Staying
1. Moving reservations between properties is not supported
Description
When a reservation is moved from one property to another within Mews, FLYR does not support the transfer. The reservation will continue to appear under the original property in FLYR and will not be reflected at the destination property, causing a revenue and occupancy discrepancy between the two systems.
Suggested workaround
Avoid moving reservations between properties where possible. If a transfer is necessary, cancel the original booking and create a new booking with the correct property.
2. Revenue posted directly to a guest profile is not traceable
Description
Revenue posted directly to a guest profile in Mews, rather than to a reservation, is not accessible via the integration in a way that allows FLYR to trace or attribute it. Because there is no reservation-level reference attached to these postings, the revenue cannot be surfaced in FLYR reporting.
Suggested workaround
Post revenue directly to the reservation rather than to a guest profile. This ensures FLYR can retrieve and correctly attribute the revenue.
3. Mews operational day reporting
Description
Mews reporting is based on the property's operational (hotel) day, which follows stay overlap and the configured check-in/check-out times. This means the operational day typically spans from around 15:00 to 12:00 the following day, rather than a strict calendar day.
As a result, reservations or transactions recorded in the early hours — before the configured check-out time — are attributed to the previous operational day in Mews reports.
For example, a check-in completed at 11:20 on April 14th will be counted under April 13th in Mews reporting.
FLYR, by contrast, attributes data to the calendar date. This difference in day boundaries can produce discrepancies when comparing data at the daily level, even when monthly totals align.
Suggested workaround
When validating data, compare at the monthly level rather than the daily level where possible. Day-level discrepancies caused by this boundary difference will offset across adjacent dates and should not affect monthly totals. If you are consistently seeing monthly-level discrepancies, contact our support team.
4. Revenue comparison should be filtered to accommodation (stay service) only
Description
Mews includes multiple service types in its revenue reporting — such as stay services, product services, and custom services. FLYR ingests the Stay service in Mews.
If you compare total revenue in Mews against accommodation revenue in FLYR without filtering to the Stay service, the figures will not align. This is not a data discrepancy — it reflects a difference in the scope of revenue being compared.
Suggested workaround
When validating accommodation revenue, always filter your Mews report to Stay service only. The Manager Report By Day, when grouped by Service, allows you to isolate this correctly.
Summary
FLYR's integration with Mews captures the majority of operational and financial data accurately. The scenarios above reflect specific structural characteristics of Mews that can produce persistent discrepancies. 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 Data Validation against PMS Reports. 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.