How can I resolve common revenue reporting discrepancies in FLYR Hospitality?
Revenue reporting discrepancies can arise from various factors, including data mapping issues, report configurations, and the nature of certain revenue sources. This article provides an overview of common issues, their causes, and actionable solutions to help you resolve these discrepancies effectively.
Understanding 'Undefined' or 'Unidentified' Revenue
What is 'Undefined' Revenue?
'Undefined' or 'Unidentified' revenue often appears in reports when revenue cannot be attributed to a specific rate plan or category. Common causes include:
Non-overnight accommodation sources: Revenue from extras or ancillary charges, such as upgrades, no-shows, or late checkouts, may not be tied to a physical overnight booking. To focus on true accommodation nights, use the "Accommodation Revenue Description" filter and select "Overnight." Report extras separately if needed.
Group block revenue: This can occur when no reservations are booked against a group block. To validate, drill down into the 'UNDEFINED' segment and cross-check booking IDs in your PMS. If confirmed, map the group block to the appropriate segment.
Non-integrated rate plans: Revenue from sources not captured by the current integration, such as "Other Revenues" in USALI or STR, may default to the 'Undefined' segment. Review the Accommodation revenue description fields for more insight.
Common Reporting Issues and Their Solutions
Misclassified Rate Codes or Revenue Categories
If discrepancies arise due to misclassified rate codes or revenue categories, make corrections directly in Mews. FLYR automatically pulls updated data from Mews, ensuring that changes are reflected in your reports.
Missing Segments in Reports
Segments may be missing or show no forecast/current accommodation data if the report's base topic is set to Bookings (OTB). Segments without on-the-books data will not appear, even if they have Budget/Forecast values. To resolve this:
Build the report with Budget & Forecast as the base topic.
Reference Bookings as a hidden or extract source if needed.
Pull OTB values from the Bookings topic via lookups joined to the Budget & Forecast base.
$0 ADR in Reports
A $0 ADR may appear when manual transaction routings break the linkage to the original booking, preventing FLYR from attributing revenue to the reservation. To verify:
Identify the booking IDs in your PMS associated with the relevant transaction codes (e.g., 9999).
Search for these bookings in Insights.
Review their corresponding accommodation revenue to confirm whether revenue is being pulled for the relevant dates.
Best Practices for Data Mapping and Report Configuration
Map Rate Plans Accurately: Ensure all rate plans are correctly mapped to avoid misclassification of revenue.
Use Filters Effectively: Leverage filters like "Accommodation Revenue Description" to isolate specific revenue types.
Validate Data Regularly: Cross-check data between your PMS and FLYR to identify and address discrepancies promptly.
Troubleshooting Specific Scenarios
For group block revenue appearing as 'Undefined,' validate and map the group block in your PMS.
If segments are missing in reports, adjust the base topic to Budget & Forecast and use lookups for OTB data.
To address $0 ADR issues, trace manual transaction routings and verify booking-revenue linkages.
By following these guidelines and leveraging the tools available in FLYR Hospitality, you can effectively resolve revenue reporting discrepancies and ensure accurate, actionable insights from your reports.