Generic XML Back Office Export-Specifications
The following table explains information sent in different files:
Table 8-8 Standard Views and Description
File | Description |
---|---|
REVENUE |
Revenue and Payments for the day |
CITY LEDGER |
All City Ledger / Accounts Receivable transactions of the day |
BILLS |
All bills/folios generated on the day (including voided) |
CUSTOMERS |
Profile data for profiles that appear in the BILLS file |
STATISTICS |
Includes Room Nights, Persons, Noshows and Cancellations of the day by Room Class, Room Type and Market Code |
-
<date>: Single date the export is executing.
-
<hotel_code>: Identifier for the property. You can set up a custom code in Administration/Enterprise/Chain and Property Management/Properties/Property Configuration/Property Controls/Hotel Code; otherwise it will use the OPERA Cloud property code.
Formatting Conventions
All date fields use the format YYYY-MM-DD.
All monetary fields have two decimals with dot (“.”) as the separator, no thousand separator is used. Negative numbers have an explicit minus sign (“-“).
Element and attribute tags follow the lowercase and hyphen standard. Secondary information is set as Attribute, main information as Element.
Data Exchange
The information flows from OPERA Cloud to the ERP/Back Office system only. No data is being sent to OPERA Cloud. Exports are usually configured to automatically generate during the end of day routine for the day being closed, but you can manually re-generate for past days.