This reference outlines the common causes of data discrepancies between ProfitPace and property sales systems. Review these data points when Pace reports do not reflect current updates, or when data is current in ProfitPace but does not match the Sales System.
The Data
Discrepancy Type | System Impacted | Required Check / Potential Cause |
|---|---|---|
Outdated Pace Reports | General | Verify if the login used to pull data needs updating due to a terminated contact account or a password change. |
Outdated Pace Reports | Delphi | If importing via a data collector on a server that was replaced or refreshed, the software may need to be re-installed. |
Missing Solicitations | General | Verify that solicitations are mapped in ProfitPace. |
Missing Solicitations | SalesPro | Ensure the Trace Call Detail report is exported from the sales system and sent into ProfitSage in the correct format. |
Missing Solicitations | CITY | Confirm that Solicitation Activities have been sent into ProfitSage. |
Current Data Mismatch | General | Verify the event or group is in Definite status. |
Current Data Mismatch | General | Verify forecasted, projected, or blocked revenue has been entered for future groups and events. |
Current Data Mismatch | General | Verify actual revenue has been entered for past groups and events. |
Current Data Mismatch | Delphi | Verify Pickup Complete is checked. For Catering, ensure the BEO has been marked complete. |
Current Data Mismatch | SalesPro | Verify both Rooms and Revenue have been entered into Actual/Pickup for all nights of a group's stay. |
Current Data Mismatch | General | Review the Map Market Segments screen to ensure all appropriate segments are mapped to Group, Banquet, Catering, or Transient. |
Limits
- Administrator Escalation: If you review all of the data points above and are still unable to reconcile the discrepancy, you must contact your ProfitSword Administrator for additional assistance.
Comments
0 comments
Article is closed for comments.