Why is it Necessary to Configure the Opera File Export?
In order to send guest data through the SES Hospedajes portal, Civitfun must first collect the information. Since Opera encrypts certain data and we cannot access them via API, it is necessary to configure the daily creation of file exports to be stored on your SFTP. In this way, Civitfun, by having access to your SFTP, can retrieve the data and send it to SES Hospedajes.
Currently, with Opera support, a File Export in .xml can be built, which is the recommended format. If you prefer to work with a File Export in .txt, Civitfun also supports it. Below we explain how to generate a compatible .txt file for the Traveler Registration tool.
Which Fields and in What Order Should I Include Them in the File Export?
Below are the 27 fields that must be included in the file export (considering space for fields one or two). It is essential that the fields follow the specified order, and that each line in the file corresponds to a guest (an example is shown at the end of the article).
The file export must be generated daily for each hotel and saved in a format that matches the configuration set up in the Traveler Registration section. If you manage multiple hotels using the same SFTP, we recommend creating a separate directory for each one.
As for guest data included in the fields "Document Type", "Gender", "Payment Type" and "Relationship Between Travelers", you must use the specific codes detailed later in this article.
Field Reference Table
In the table below, you will find a mapping between each field required by Royal Decree 933/2021, the name of the data field in our documentation, and the corresponding field in Opera.
| Royal Decree 933/2021 | Field Name | Opera Field |
|---|---|---|
| Identity document number (fill only NATIONAL_ID_NUMBER or FOREIGN_ID_NUMBER) | numeroDocumento | NATIONAL_ID_NUMBER (NIF) |
| Identity document number (fill only NATIONAL_ID_NUMBER or FOREIGN_ID_NUMBER) | numeroDocumento | FOREIGN_ID_NUMBER (NIE, PAS or OTRO) |
| Document type (ID, passport, TIE) | tipoDocumento | ID_TYPE |
| - | - | ID_DATE: Issue date |
| First surname | apellido1 | PATERNAL_SURNAME |
| Second surname | apellido2 | MATERNAL_SURNAME |
| Name | nombre | FIRST_NAME |
| Gender | sexo | GENDER |
| Date of birth | fechaNacimiento | BIRTH_DATE |
| Nationality | nacionalidad | NATIONALITY_DESC |
| Check-in date and time | fechaEntrada | ARRIVAL |
| Reference number | referencia | CONFIRMATION_NO |
| Check-out date and time | fechaSalida | DEPARTURE |
| Number of travelers | numPersonas | NUM_PERSONAS |
| Payment type | pago tipoPago | PAYMENT_METHOD |
| - | - | ROL: TI (holder) and VI (accompanying traveler) |
| Full address | direccion direccion | ADDRESS |
| City | direccion nombreMunicipio | CITY |
| Postal code | direccion codigoPostal | ZIP_CODE |
| Province | - | STATE |
| Country | direccion pais | COUNTRY |
| Landline phone (only one of phone, mobile or email is mandatory) | telefono | PHONE |
| Mobile phone (only one of phone, mobile or email is mandatory) | telefono2 | MOBILE |
| Email (only one of phone, mobile or email is mandatory) | correo | |
| Contract date | fechaContrato | UDF or calculated value (reservation insert/creation date) |
| Relationship between travelers (if any are minors) | parentesco | New UDF (to be indicated by an adult guest) |
| Document support number (required if type is NIF or NIE) | soporteDocumento | New UDF |
| Payment method identification (Optional) | - | New UDF |
| Payment method holder (Optional) | - | New UDF |
| Card expiration date (Optional) | - | New UDF |
| Payment date (Optional) | - | New UDF |
Document Type Codes
| Description | Code |
|---|---|
| Tax Identification Number | NIF |
| Foreigner Identification Number | NIE |
| Passport | PAS |
| Other | OTRO |
Gender Codes
| Description | Code |
|---|---|
| Male | H |
| Female | M |
| Other | O |
Payment Type Codes
| Description | Code |
|---|---|
| Cash | EFECT |
| Credit Card | TARJT |
| Payment Platform | PLATF |
| Transfer | TRANS |
| Mobile Payment | MOVIL |
| Gift Card | TREG |
| Pay at Destination | DESTI |
| Other | OTRO |
Relationship Between Travelers Codes
| Description | Code |
|---|---|
| Grandparent | AB |
| Great-grandparent | BA |
| Great-grandchild | BN |
| Sibling-in-law | CD |
| Spouse | CY |
| Child | HJ |
| Sibling | HR |
| Grandchild | NI |
| Parent | PM |
| Nephew/Niece | SB |
| Parent-in-law | SG |
| Uncle/Aunt | TI |
| Son/Daughter-in-law | YN |
| Guardian | TU |
| Other | OT |
When Should the File Export Be Generated?
Civitfun sends data to SES Hospedajes at 04:00 AM. Therefore, the file must be available on the SFTP by that time. We recommend scheduling the export generation from Opera at 01:00 AM to ensure timely delivery.
Example of File Export
Below is an example of one guest's data in the file export. The file contains 27 fields, follows the indicated order, and each line corresponds to one guest (in the screenshot, due to space, it appears as two lines, but it is a single line in the actual file).
I hope this article is helpful! If you need more information, contact us at support@civitfun.com — we’ll be happy to help. 😊✍️