The table below shows the PMI data elements required for PMI Revenue and Productivity (R&P) module.
It shows the elements that we require from the source system PMS (Property Management System).
Within PMS we import both actuals and reservations (on the book).
Statistics Actuals (yesterdays data + preferably 7 days back)
| # | Data elements | Description | Mandatory / Optional | Comments |
|---|---|---|---|---|
| 1 | Property ID/Name | Identification of the property | M | The import flow for a property is mostly set up per property. In this case, the property identifier is specified in the flow. If a data set (file) includes data for multiple properties, the property identifier needs to be part of the data set (file). |
| 2 | Date | Date of stay (history) | M | |
| 3 | Code | Name of the market or rate code | M | Used for mapping to segments. If no code is delivered, there must be another way to extract the segment from the data. |
| 4 | Room Nights | Number of room nights | M | |
| 5 | Guest Nights Adults | Number of adult guest nights | M | |
| 6 | Guest Nights Children | Number of children guest nights | O | |
| 7 | Revenue Rooms | Room revenue without F&B, VAT and other authority charge rates | M | If the revenue includes VAT, this can be corrected in the mapping. Only one percentage can be used in the mapping to subtract additional charges. |
| 8 | Arrivals | Number of room nights arrivals | M | Required if using departures. |
| 9 | Departures | Number of room nights departures | M | Required if using arrivals. |
Revenue Actuals (yesterdays data + preferably 7 days back)
| # | Data elements | Description | Mandatory / Optional | Comments |
|---|---|---|---|---|
| 1 | Property ID/Name | Identification of the property | O | If a data set (file) includes data for multiple properties, the property identifier needs to be part of the data set (file). |
| 2 | Department ID/Name | Department name | M | |
| 3 | Transaction date | Transaction date | M | Used to ensure correct day is updated. |
| 4 | Account ID | Account ID | M | Used to ensure correct classification of revenue. |
| 5 | Account Name/Description | Account Name/Description | M | Used to ensure correct classification of revenue. |
| 6 | Revenue | Revenue, e.g. accommodation, F&B, others. The amount excludes VAT and other authority charge rates | M | If the revenue includes VAT, this can be corrected in the mapping. Only one percentage can be used in the mapping to subtract additional charges. |
Rooms on the books (OTB) data (“today” + 500 days)
| # | Data elements | Description | Mandatory / Optional | Comments |
|---|---|---|---|---|
| 1 | Property ID/Name | Identification of the property | M | The import flow for a property is mostly set up per property. In this case, the property identifier is specified in the flow. If a data set (file) includes data for multiple properties, the property identifier needs to be part of the data set (file). |
| 2 | Snapshot date | The date on which these were the actual reservations | M | This is important for having a correct overview for pickups. |
| 3 | Date | Date of stay (future) | M | |
| 4 | Code | Name of the market or rate code | O | Used for mapping to segments. If no code is delivered, there must be another way to extract the segment from the data. |
| 5 | Room Nights | Number of room nights | M | |
| 6 | Guest Nights Adults | Number of adult guest nights | M | |
| 7 | Guest Nights Children | Number of children guest nights | O | |
| 8 | Revenue Rooms | Room revenue without F&B, VAT and other authority charge rates | M | If the revenue includes VAT, this can be corrected in the mapping. Only one percentage can be used in the mapping to subtract additional charges. |
| 9 | Arrivals | Number of room nights arrivals | M | Required if using departures. |
| 10 | Departures | Number of room nights departures | M | Required if using arrivals. |
| 11 | Room nights tentative | Number of room nights tentative | M | |
| 12 | Room revenue tentative | Room revenue tentative | M |
Please note: The names of data elements are provided in source system (native) codes. These native codes will be translated into PMI names in PMI.
The data we like to receive on a daily basis as early in the morning as possible.
Examples
Links
See this article for file formats – Output Format
See this article for transfer method options – Transfer Method