Travel Analytics Terminology
Here is a summary of the terminology we use in Travel Analytics
Dates
We use invoice and departure dates interchangeably throughout the dashboards and download reports depending on the type of date.
Departure Date
Use the departure date to report on all other product types, including, but not limited to accommodation, rental car, land transfers and other land content. This to allow the reporting to match the timing of the service provider (i.e. hotel or rental car company) as closely as possible. This is why data is appearing in Tramada and not Travel Analytics.
Invoice Date
We use the invoice date to report airfare tickets and services fees charged by the Travel Management Company. The invoice date is the date the airfare or service fee is charged and therefore the date that is going to be closest to changes within your financial management and credit card reporting systems. There may be other types of charges where we report by the invoice date, including visa charges, foreign exchange and insurance. Rule of thumb is that any charge where the Travel Management Company is the merchant, we will generally report on it by the invoice date. However, there may be exceptions depending on how the Travel Management Company processes the charge.
Average Lost Savings per Traveller is an average across the date range which indicates what the company is forfeiting per traveller in cost saving for not choosing the lowest available fare within the reporting period.
Cheapest Fare Compliance is the percentage the cheapest fare (or compliant) fare is selected at the time of booking. The cheapest fare is determined by the policy code recorded at the time the booking is made. Policy codes tagged as 'compliant' in Travel Analytics by the Administrator is what the report is displaying.
Compliance is calculated using the policy code data provided by the mid-office system. In Tramada this means at the booking level while in Serko policy data is provided at the segment level.
Cost of Change is the additional collection charged by the airline to reissue a ticket. We total the charges in the data displayed within the cost of change table. Therefore, if there are three changes at $100 for each change, the cost of change will display as $300.
Destinations are locations where a stopover occurs in the itinerary. A stopover is where a traveller spends more than 24 hours at a location. There is often more than one destination in an itinerary especially in a multi-sector round the world itinerary i.e. Melbourne to Singapore to London to New York to Los Angeles to Melbourne.
Locations All of our destinations have geo coordinates. If we have a location that we cannot identify, then by default the coordinates are latitude = 0 and longitude = 0, which geographically, is just under Africa. Therefore, it is critical we have a location in the data otherwise we cannot report or display it correctly.
Non Compliant Bookings are air bookings flagged as non-compliant in travel analytics. Non-compliance is recorded at the policy code level and applies to the original ticket issue. For example, the Lowest Available Fare is generally flagged as compliant and 'Flexibility Required' is flagged as non-compliant.
Online Booking Compliance is the percentage of bookings made online for the organisation or department level selected. Travel Analytics stores the booking method as quoted by the TMC and we tag each method as either online or offline. Examples of online booking methods include Serko, Concur, Online, Web-Res etc.
Restricted Fare Uptake is the percentage of restricted fares booked by the customer. Travel Analytics categorises airfares based on the airline, class of travel and market. For example, Qantas O class fares (Red e Deal) are categorised as restricted fares within Travel Analytics.
Stopover is where a traveller spends more than 24 hours at a location.
Trip is a unique booking reference. Where you have multiple travellers in the one booking, that will be counted as one trip.