Include VAT Information in Reservation Delivery (FEA91049)

SynXis CRS hosts functionality to capture VAT Billing Detail information on reservations made on SynXis Booking Engine (SBE) and SynXis Voice Agent (SVA). To promote automation and on property operational efficiency, SynXis HTNG reservation delivery to PMS integrations has been enhanced to include this information downstream. The information will be included in reservation messages whenever the details are present on a reservation in SynXis CRS.

VAT Billing details are not available in HTNG Alt Res Delivery to secondary endpoints.

Example: OTA_HotelResNotifRQ xml snippet (See full specification for official use case definitions)

<HotelReservation>
	...
	<TPA_Extensions>
		...
		<BillingInformation>
			<VAT CompanyName="VatCompanyName"
			     VATNumber="123456789">
				<Address>
					<AddressLine>VatAddress1</AddressLine>
					<AddressLine>VatAddress2</AddressLine>
					<AddressLine>VatAddress3</AddressLine>
					<CityName>VatCity</CityName>
					<PostalCode>11111</PostalCode>
					<CountryName>US</CountryName>
				</Address>
				<Telephone PhoneTechType="1"
				           PhoneNumber="1-111-111-1111"
				           FormattedInd="false"
				           DefaultInd="false"/>
				<Email>VatEmail</Email>
			</VAT>
		</BillingInformation>
		...
	</TPA_Extensions>
	...
</HotelReservation>

Tracking an External System User’s API transactions (FEA92169)

The SynXis APIs have been enhanced so customers can now provide additional user metadata that will be tracked in SynXis CRS. This metadata will allow visibility into which users from the customer’s application (external system) initiated the API transactions to SynXis CRS.

A new optional parameter (ApplicationUserMetaData) is now supported in the HTTP headers for inbound requests to SynXis CRS, as well as in the header of the token request for use with REST APIs. The ApplicationUserMetaData parameter has a maximum size of 60 characters.

If ApplicationUserMetaData was provided in any reservation transactions via API, the value will be included in reservation delivery OTA_HotelResNotifRQ message as ResID_Type="3". The following partial XML sample shows how the metadata will be communicated:

<HotelReservations>
	<HotelReservation>
		...
		<ResGlobalInfo>
			<HotelReservationIDs>
				...
				<HotelReservationID ResID_Type="3"
				                    ResID_Value="ABCD456782"
				                    ResID_Source="Corporation representative"
				                    ForGuest="false"/>
			</HotelReservationIDs>
		</ResGlobalInfo>
		...
	</HotelReservation>
</HotelReservations>

Loyalty Accrual Indicator (FEA95383)

For chains that allow guests to earn benefits such as points or free nights based on specific rates booked, the SynXis CRS now supports the ability to configure and apply such policies to rates. The SynXis CRS previously supported the ability to configure if a rate is eligible for accrual. This functionality has been expanded to allow the association of a specific accrual benefit a guest would earn.

A new configuration “Include Accrual Details in Reservation Delivery (HTNG Only)” attribute has been added in SynXis CRS to control if the accrual type will be included in the HTNG reservation message, if associated to the rate.

The following is a sample partial XML:

<HotelReservations>
	<HotelReservation>
		...
		<TPA_Extensions>
			...
			<AccrualDetails AccrualIndicator="True"
			                AccrualTypeCode="Points"
			                AccrualTypeName="Earn Points"/>
		</TPA_Extensions>
	</HotelReservation>
</HotelReservations>

Indicate Tax Rules on Rate Plans (FEA90212)

Reservation Delivery to the PMS has been enhanced to include a comment regarding any Exempt or Pre-Paid taxes.

Reservation Delivery to any secondary endpoints (non-PMS) will not include any Exempt or Pre-Paid tax comments.

The following attributes have been added to the Administration > Integration > Integration Detail > Attributes page to control whether the comments are included:

• Include Exempt Taxes in Comments
• Include Pre-paid Taxes in Comments

Sample partial XML for Exempt taxes:

<OTA_HotelResNotifRQ>
	...
	<HotelReservations>
		<HotelReservation>
			...
			<RoomStays>
				<RoomStay>
					...
					<Comments>
						<Comment GuestViewable="false">
							<Text>~EXEMPTTAXES RBT(0.00), RLT(0.00) EXEMPTTAXES~</Text>
						</Comment>
					</Comments>
				</RoomStay>
			</RoomStays>
			...
		</HotelReservation>
	</HotelReservations>
</OTA_HotelResNotifRQ>

Sample partial XML for Pre-Paid taxes:

<OTA_HotelResNotifRQ>
	...
	<HotelReservations>
		<HotelReservation>
			...
			<RoomStays>
				<RoomStay>
					...
					<Comments>
						<Comment GuestViewable="false">
							<Text>~PREPAIDTAXES RBT(45.00), RLT(30.00) PREPAIDTAXES~</Text>
						</Comment>
					</Comments>
				</RoomStay>
			</RoomStays>
			...
		</HotelReservation>
	</HotelReservations>
</OTA_HotelResNotifRQ>

HTNG - Support Child Ages (FEA60440)

SynXis HTNG reservation messages can support child ages included on reservations in reservation delivery to integrating systems, and in reservation synch to SynXis CRS. Automatically integrating child age breakdowns between SynXis CRS and integrating systems provides an opportunity to improve operational efficiency by removing the task of manually aligning the ages of the children between systems.

Configuration to enable child age breakdown in HTNG reservation delivery and reservation synch is defaulted to not include the information. Integrating systems must support child ages functionality prior to enabling the setting.

SynXis HTNG integrating systems wishing to consume/exchange child ages in reservations with SynXis CRS must be certified.

Example: Reservation Including Children with Ages (Partial)
This partial use case shows a reservation with child ages stored. Two Room Reservation includes 2 Adults and 4 Children. Child 1 is 1 years old, Child 2 is 1 years old, Child 3 is 2 years old, Child 4 is 6 years old.

<GuestCounts IsPerRoom="false">
	<GuestCount AgeQualifyingCode="10" Count="2"/>
	<GuestCount AgeQualifyingCode="8" Count="4"/>
	<GuestCount AgeQualifyingCode="8" Count="2" Age="1"/>
	<GuestCount AgeQualifyingCode="8" Count="1" Age="2"/>
	<GuestCount AgeQualifyingCode="8" Count="1" Age="6"/>
</GuestCounts>