5.3 Release Notes

FEATURE

Profiles VIP & Access Level UI Indicators & Search

PLATFORM

FEATURE

Credit Card Types - Expanded

PLATFORM

FEATURE

Credits (Available Tickets) UI - Enhancements

PLATFORM

Platform Administration

FEATURE

Credits Import File - Enhanced

PLATFORM

FEATURE

Credits Sync - Enhanced

SYNC

FEATURE

Trips Processing - Enhancements

TRIPS

The support of these additional card types also includes tokenisation via Tokenex. The Travel Platform maintains PCI DSS and Data Privacy obligations with our partnership with Cloud Security platform TokenEx.

Airline
ENHANCED

The smart fill search now supports a query using the airline’s 2 character code.

Ticket No
ENHANCED

This field is now limited to a maximum of 10 characters.

When recording a ticket number, the airline’s numeric prefix should be excluded.

Currency NEW

The currency (code) stored in the Travel Office, or otherwise the Agency will apply by default.
This will prepopulate to and be stored with monetary based e-form fields e.g. Base Fare, Airline Change Fee.

To record a credit in a different currency
(e.g. USD), select an alternative from the list provided.

Status NEW

Allows the status (i.e. state) of a credit to be categorised to assist in its future use.

Open: A credit with one (1) or more segments that remain all unused (available).

Exchanged: A credit that has been used towards another booking/ticket is deemed to have been exchanged.

Refund Requested: A credit that has been submitted for a refund by the agency. This may include tickets/credits where a tax only refund has been requested.

Partial: A credit containing more than one (1) segment with only some remaining available (unused) for future use.

Ticket Type NEW

Allows a credit to be categorised based on the trip type that was booked/ticketed.

This can assist in a credit's future use as some airlines only allow a credit to be used towards a trip type of the same e.g. International credit cannot be used towards a Domestic trip. Though variations may exists, the following are basic definitions of each Ticket Type.

Domestic: Both the departure and arrival airports are located in the same country as the fulfilment agency.

International: The departure and arrival airports are in different countries, or

The trip begins in a different country to that of the fulfilment agency e.g. AU fulfilment agency and flights within the US (domestic) only.

Trans-Border: A trip within the same region as the fulfilment agency, though the departure and arrival airports are in different countries.
e.g. Sydney (AU) - Auckland (NZ); Toronto (CA) - New York (US) Singapore (SG) - Jakarta (ID).

Trans-Border may be shown as
Trans-Tasman in some markets
(e.g. Australia & New Zealand).

Credit Type NEW

Eticket: Majority of credits issued will utilise the travel document type of an E-ticket.

Virtual Card: Some airlines offer a Virtual Card instead of, or in addition to an Eticket as a way to store available credit.

Non GDS: Low Cost Carriers (LCCs) like Jetstar (JQ) and Easyjet (U2) are primarily ticketless airlines. This option allows such airlines to have their credits added to the register.

MCO/EMD: The introduction of ancillary services (e.g. paid seat, extra baggage) requires the use of EMDs. Some airlines may allow EMDs for prepaid services or products to be held in credit. It may also be used in lieu of an Eticket or Virtual Card.

Name Change Eligible NEW

Some airlines allow tickets and credits to be name changed to a different traveller. This toggle allows such information to be recorded to assist in a credits future use.

A Status of Partial does not allow this toggle to be used.

Refundable NEW

This toggle allows a ticket/credit to be easily identified as refundable, if the airline/fare rules permit.

It sometimes can be easier to hold a refundable ticket in credit with the view of using prior to it expiring. Only when it will not be used prior, is the refundable ticket submitted for a refund.

Fare Basis Code NEW

Also referred to fare basis or FBC, is a code used by the airline to identify the fare type used. It allows for future use, including to verify rules applicable to the fare(s).
If more than one (1) FBC is required to be recorded, each should be separated by
a , (comma) e.g. SKX0A,SKW0A

Office ID NEW

The ticketing Office ID (OID) of the fulfilment agency. It allows for future use, including to retrieve Eticket data. If a ticketing OID is not applicable (e.g. ticketless airline), the booking OID should be recorded instead.

Routing NEW

The complete or abbreviated form of the fare calculation line of the entire trip, used and unused components.
It allows for future use including for partially used credits with some airlines not allowing the same city pair that has already been flown to be booked again with the remaining credit.

Booking Class NEW

Also known as the reservation booking designator (RBD), this is the single alpha code used to book/identify each segment. It allows for future use, including to verify rules applicable to the fare(s).
If more than one (1) RBD is required to be recorded, each should be separated by
a , (comma) e.g. J,D

Pricing Code NEW

Also known as the private fare code, this is the code used to obtain the fare(s) when priced in the GDS or booked direct with the airline.
If more than pricing code is required to be recorded, each should be separated by
a , (comma) e.g. STK01, STK10

Waiver Code NEW

Also known as an authority code, this may be given by the airline to modify the standard fare rules or charges that would otherwise apply to ticket/credit.
e.g. An airline may provide waiver code “COVID19” to allow a ticket to be held in credit, as well as forgo reissue/change fees, though the fare booked would not normally allow.

Airline Change Fee
NEW

Also known as a reissue or exchange fee, this is cost the airline will charge when the ticket/credit is used in the future. This value can be derived from the fare rules. If more than one (1) fee applies, the highest (most restrictive) should be recorded.

Airline Refund Fee
NEW

This is cost the airline will charge when the ticket/credit is submitted for a refund. This value can be derived from the fare rules. If more than one (1) fee applies, the highest (most restrictive) should be recorded.

Additional Information NEW

Any relevant and supplementary information about the credit being recorded should be added here. It allows for reference in the future when the credit is being used.

Department NEW

Only if the credit being recorded is associated to a company with Departments, will this field be shown.

Allows a credit to be linked to a Department of the company, if required.

Cost Centre NEW

Only if the credit being recorded is associated to a company with Cost Centres, will this field be shown.

Allows a credit to be linked to a Cost Centre of the company, if required.

Booking-Office/Booking File ID ENHANCED

Formerly the Tramada File No. Stored, the field label has been revised to be more generic of any TMS (Travel Management System) or Mid-Back Office (MBO).

Allows the booking office/file ID (number) related to available (unused) credit being added to the register to be recorded.

New Booking-Office/Booking File ID ENHANCED

Formerly the Tramada File No. Used, the field label has been revised to be more generic of any TMS (Travel Management System) or Mid-Back Office (MBO).

Allows the booking office/file ID (number) related to the credit’s used (in the future) to be recorded.

To accommodate the aforementioned Credits UI enhancements, the Ticket Sync has been updated to only send Credit Type: ETicket.

This is designed to avoid credit sync failures occurring with integrated systems (services) that support credits (unused tickets). OBT - AMADEUS CYTRIC

Credits held with an airline not issued on a travel document type of an E-ticket are recommended to be added to the register using an alternative option e.g. Non GDS for a ticketless airline credit.