Data elements required from PMS

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

#Data elementsDescriptionMandatory / OptionalComments
1Property ID/NameIdentification of the propertyMThe 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).
2DateDate of stay (history)M
3CodeName of the market or rate codeMUsed for mapping to segments. If no code is delivered, there must be another way to extract the segment from the data.
4Room NightsNumber of room nightsM
5Guest Nights AdultsNumber of adult guest nightsM
6Guest Nights ChildrenNumber of children guest nightsO
7Revenue RoomsRoom revenue without F&B, VAT and other authority charge ratesMIf the revenue includes VAT, this can be corrected in the mapping. Only one percentage can be used in the mapping to subtract additional charges.
8ArrivalsNumber of room nights arrivalsMRequired if using departures.
9DeparturesNumber of room nights departuresMRequired if using arrivals.
#Data elementsDescriptionMandatory / OptionalComments
1Property ID/NameIdentification of the propertyOIf a data set (file) includes data for multiple properties, the property identifier needs to be part of the data set (file).
2Department ID/NameDepartment nameM
3Transaction dateTransaction dateMUsed to ensure correct day is updated.
4Account ID/NameAccount ID/NameOUsed to ensure correct classification of revenue.
5RevenueRevenue, e.g. accommodation, F&B, others. The amount excludes VAT and other authority charge ratesMIf the revenue includes VAT, this can be corrected in the mapping. Only one percentage can be used in the mapping to subtract additional charges.
#Data elementsDescriptionMandatory / OptionalComments
1Property ID/NameIdentification of the propertyMThe 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).
2Snapshot dateThe date on which these were the actual reservationsMThis is important for having a correct overview for pickups.
3DateDate of stay (future)M
4CodeName of the market or rate codeOUsed for mapping to segments. If no code is delivered, there must be another way to extract the segment from the data.
5Room NightsNumber of room nightsM
6Guest Nights AdultsNumber of adult guest nightsM
7Guest Nights ChildrenNumber of children guest nightsO
8Revenue RoomsRoom revenue without F&B, VAT and other authority charge ratesMIf the revenue includes VAT, this can be corrected in the mapping. Only one percentage can be used in the mapping to subtract additional charges.
9ArrivalsNumber of room nights arrivalsMRequired if using departures.
10DeparturesNumber of room nights departuresMRequired if using arrivals.
11Room nights tentativeNumber of room nights tentativeM
12Room revenue tentativeRoom revenue tentativeM

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.

Was this article helpful?

Related Articles