Released 15 January 2021
A major release with UI enhancements primarily focused on Credits (Unused Tickets) and expansion of supported credit card types, including tokenization.
Profiles VIP & Access Level UI Indicators & Search
Credit Card Types - Expanded
Credits (Available Tickets) UI - Enhancements
Credits Import File - Enhanced
Credits Sync - Enhanced
Trips Processing - Enhancements
Profiles VIP & Access Level UI Indicators & Search
This enhancement will allow selected company users and TAMs (Travel Consultants) the ability to be presented with visual indicators of the VIP status as well as the access level a Profile holds within their company (i.e. TA - Travel Arranger, TM - Travel Manager).
The ability to include VIP (toggle) status and access level (option) as search criteria in Profiles will also be available, as seen in the following example for Arranger (i.e. Travel Arranger - TA).
This enhancement is designed to improve the user experience (UX) by avoiding or minimising the need to check individual profiles for the same.
A user will only be able to display Profiles in search results they are authorised to view. e.g. A Travel Arranger (TA) will only have VIPs displayed in search results if any of their delegated travellers hold a VIP status.
Credit Card Types
The current list of supported Credit Card types has been expanded in Kudos for both Company and Travellers to include:
UATP/Airplus - TP
Japan Credit Bureau (JCB) - JC
Discover Card - DS
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.
TokenEx is a data protection platform that provides cloud tokenization, encryption, and data vaulting through a vendor-agnostic platform that secures all sensitive data.
Company Credit Cards can be stored in the company profile via Kudos Administration, as seen in the following example.
Similar to a company, a Profile (e.g. traveller) can be used to store both personal and company-issued credit cards, as seen in the following example.
Credits (Available Tickets) UI
Credits is a centrally managed register of available tickets that still hold value and allow use for travel on a future date before expiration.
These enhancements provide major overall of the Credits e-form used by TAMs (e.g. travel consultants) to record unused airline tickets and credits (e.g. name, ticket number, expiry date).
Mandatory fields in each section are denoted with an * (asterisks).
The smart fill search now supports a query using the airline’s 2 character code.
This field is now limited to a maximum of 10 characters.
When recording a ticket number, the airline’s numeric prefix should be excluded.
The currency (code) stored in the Travel Office, or otherwise the Agency will apply by default.
To record a credit in a different currency
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.
Trans-Border may be shown as
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.
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).
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.
The complete or abbreviated form of the fare calculation line of the entire trip, used and unused components.
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).
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.
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.
Airline Change Fee
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
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.
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.
Credits Search received a minor update with two (2) additional columns to allow Credit Type and Status to be shown, as seen in the following example (Table view).
Credits Import File
In line with the aforementioned Credits UI enhancements, the Import (file) that allows the bulk import (or update) of credits has been updated.
The Kudos Administration Import/Export menu Import Ticket Credits option will recognise an import file (CSV) containing additional columns to support the new fields (e.g. Status, Credit Type).
An import file (CSV) containing only the previous columns will still be recognised (accepted).
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.
Credits can now be synced in bulk (in mass) using the Company Sync screen and selecting the Sync Credit option. This will trigger a sync of all credits for the selected company to the selected integrated system. The following example will sync all credits (Eticket) for Stark Industries (company) to Amadeus Cytric.
An individual credit when created and updated in the UI by a TAM will continue to trigger sync to all integrated systems that support credits (unused tickets).
Sync History Button
The Kudos Travel Platform - Consultant Desktop UI has been updated to provide visibility to a TAM (e.g. travel consultant) of a credit’s sync (history). Selecting this option, as seen in the following example, will display a credit’s sync history (if applicable) to the agency’s integrated system.
This enhancement sees existing Trips Processing services modified to lessen the classification of non-critical validation errors that prevented Trips from being processed successfully. Trips Error Reports will now be split into two (2) sections - Failures and Warnings ⚠ .
Failures - Processing of trip stopped.
A trip with an unmatched traveller (i.e. no profile) as well as segments containing generic or fake/fictitious location codes like “XXX” and “XHZ”, among others will not be processed. An unprocessed trip will not be displayed in Trips and Care.
⚠ Warnings - Processing of trip allowed.