Skip to main content

Data Differences Between Infor and FLYR Reporting

Explanation on data validation reporting and known limitations between Infor 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 Infor — 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 Infor 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 Infor reports

Pull 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.

Occupancy & Statistics Report — use this report to validate data against FLYR

  • Apply the relevant date filters

Posting Journal Report — include this together with above report when reaching out to support about a specific discrepancy

  • Pull for the specific day | Filter by room category


1. Revenue posted after a guest has checked out is not captured

Description

If a charge is added to a reservation's folio in Infor after the stay has already ended, FLYR will not pick it up. This is because FLYR receives reservation data at the point the booking is processed, and any charges added to the folio once the stay dates have passed fall outside that window.

This can affect situations where, for example, a room charge is settled or adjusted through Accounts Receivable after checkout.

Suggested workaround

Where possible, ensure all charges related to a reservation are posted to the folio during the stay, rather than after checkout. If you notice a revenue gap for a past reservation, contact our support team with the Posting Journal Report for the specific day so we can investigate.


2. Charges posted before a guest arrives are not captured

Description

Similarly, charges added to a reservation's folio before the guest has arrived — such as upselling packages or pre-arrival accommodation postings — are also not captured by FLYR. These pre-arrival postings fall outside the reservation data that FLYR receives at the time of processing.

Suggested workaround

Where possible, post accommodation-related charges to the folio once the guest has arrived, rather than in advance. If you are regularly using pre-arrival postings for upselling or packages, be aware that this revenue will not appear in FLYR until the stay dates are reached and the data is processed.


Summary

FLYR's integration with Infor captures the majority of operational and financial data accurately. The scenarios above reflect specific structural characteristics of the Infor integration 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.

Did this answer your question?