User Guide - Version 3. Amadeus Airline Service Fees

Transcription

1 User Guide - Version 3 Amadeus Airline Service Fees

2 Table of Contents Introduction... 3 How Amadeus Airline Service Fees work... 4 Type of Fees... 4 The shopping and pricing workflow... 4 New command entries... 5 Best Practice... 5 Example scenarios No FP element exists in PNR and pricing input option used FP element entered before pricing the PNR No FP element exists and no pricing input option used OB Fees Standalone calculation transaction Overview Pre-requisites Options Entries Example of the OB fees Standalone transaction Error messages Manual addition, modification and deletion of OB fees Add an OB fee Modify an OB fee Delete an OB fee Sales Reports Graphical functionality No FP element exists in PNR and pricing input option used FP element entered before pricing the PNR No FP element exists and no pricing input option used System Warning and Error Messages Document control Document Release Information Release number Date updated Updated by Details of update /01/11 Sarah Bowden Document creation /02/11 Sarah Bowden Graphical functionality included and cryptic screenshots updated. Add, modify, delete commands included /04/11 Sarah Bowden Added new screen shot of pricing summary panel /06/11 Sarah Bowden Addition of OB fees Standalone calculation transaction /08/11 Sarah Bowden Update to Standalone section as not yet available /12/11 Sarah Bowden Updated for release of Standalone option Page 2 of 23

3 Introduction The Amadeus Airline Service Fees solution is designed to support Airline Ticketing Fees (also known as OB fees). OB fees are defined and collected by the validating carrier and charged to the passenger when a ticket is issued. These fees can be imposed to cover charges for a specific form of payment or for other ticketing services. Form of payment fees priced automatically at the shopping and pricing request based on either the form of payment stored in the PNR or with the use of a new pricing option. Ticketing fees priced automatically at the shopping and pricing request based on the PNR and itinerary data. These are not currently applied in the UK market. The deployment of the solution has been phased in order to focus on the processing of Form of Payment (FOP) fees and the implementation of a generic credit card fee. The generic credit card fee is filed by the airlines with the FCA sub code. Notes OB fees will be collected on first ticket issue only. OB fees will be shown in the Grand Total line of a TST. Two new transactions will provide details of the stored OB fees. No OB fees will appear on the ticket. OB fees are non refundable. Please contact the individual carrier for details on charges and any other specific conditions. Page 3 of 23

4 How Amadeus Airline Service Fees work Type of Fees The Airline Service Fees product aims at supporting all types of ticketing fees, including form of payment fees through travel agencies. Initially, Amadeus is focusing exclusively on the deployment of a generic credit card fee. This Fee is defined by a 5 digit code: 2 digit code OB and 3 digit sub-code FCA. The shopping and pricing workflow These fees are automatically calculated by the system based on either: the Form of Payment (FOP) stored in the PNR or an optional input in the fare search or pricing request. Amadeus focus on a generic credit card fee and the support of this optional input provides agents with the flexibility to quote a credit card fee early in their workflow without having the credit card number and before a PNR is created. Agents have 3 options to trigger the Credit Card Fee application in the flow: Input the Form of Payment (FOP) in the PNR before the PNR pricing (FP element) Input the FCA sub-code in the shopping or pricing request Re-price after inputting the Form of Payment (FOP) in the PNR in order to quote accurate CC Fee and issue a Ticket with an automated FCMI When calculated, fees are included in the grand total of the pricing record (TST), providing agents with an immediate visibility of the total price. The grand total consists of the fare, taxes and the OB fees. Two new transactions will provide details of the stored OB fees. If there is no FP element or the optional input is not used, a message in the pricing output warns agents that a form of payment fee may apply for the validating carrier. As OB fees are only applicable on first issue, the FCA sub code should not be used with any Amadeus Ticket Changer pricing command. OB fees are only applicable on the first issuance. Page 4 of 23

5 New command entries /R,FA-OBFCA add generic credit card fee to the pricing entry (can be used with FXP, FXX, FXB, FXR, FQP, FXA,) TQO TQO/T2 display a list of OB fees for the TST (if only one TST exists) display a list of OB fees for a specific TST TQC TQC/T2 display the pricing context; information on the validating carrier, forms of payment and point of sale (Amadeus Office ID) for which OB fees have been applied (if only one TST exists) as above for a specific TST HEFEES, GPOBF Help pages for airline ticketing fees TTX Initiate the OB fees Standalone transaction Best Practice To ensure the correct fees are collected we suggest the best practice is to always ask the customer how they wish to pay for the booking. If they advise by credit card but do not have the number then you must follow scenario one. Follow up entries can be found on page 12 to ensure the correct fees are charged at ticket issuance. If they are not aware of how they will pay for the booking, advise that extra fees may be incurred if paying by credit card. Page 5 of 23

6 Example scenarios 1. No FP element exists in PNR and pricing input option used Step 1 Book the flights Step 2 Price the booking adding the new input option (/R,FA-OBFCA) The OB fees are shown on a separate line in the fare. The Total value includes the OB fees. Note the messages at the bottom of the fare. Manual manipulation of fees appears whenever the FCA sub code is added to the pricing command. When a pricing summary panel is displayed, the applicable taxes and fees are combined and are shown in the Tax/Fee column. Page 6 of 23

7 Step 3 Enter passenger info and reprice to store the fare TQO will show the list of OB fees TQC will show information on validating carrier, FOP and Office ID Step 4 Enter the Form of Payment Step 5 Issue the ticket (Completed PNR) E-ticket display Page 7 of 23

8 Notes The TST will show the Total and Grand Total figure. To see a breakdown of the OB fees, the follow up entry of TQO is required. Where the FA element shows the total ticket price, this will not include any OB fees. The e-ticket record will not show any OB fees. The ITR will show a breakdown of the OB fees (example of partial ITR below) Page 8 of 23

9 2. FP element entered before pricing the PNR Step 1 Book flights and enter passenger information including FP element. (Example shows PNR created from a traveller profile) Step 2 Price the PNR (no input option required) The message Airline Fees Included appears under the total fare where the fees breakdown is shown. The follow up entries of TQO/TQC can be made. Step 3 Issue the ticket (Completed PNR) Page 9 of 23

10 3. No FP element exists and no pricing input option used Step 1 Book the flights Step 2 Price the booking (without adding any input option) Note the message at the bottom of the fare. Step 3 Enter the passenger information and reprice to store the fare Step 4 Enter the Form of Payment and issue the ticket Note the warning message. Because the form of payment is credit card, the system requires the booking to be repriced to check for form of payment fees. Page 10 of 23

11 Step 5 Reprice the PNR Note fees are now included Step 6 Issue the ticket Page 11 of 23

12 OB Fees Standalone calculation transaction Overview When an agent makes the TTP entry on a PNR, the system performs 3 checks to ensure that the accurate OB fees are charged and collected. If the processing fails because of at least one of these checks, an error message is generated depending on the check that has been done. Currently the PNR would have to be re-priced in order to calculate the correct OB fee amount. The OB fees Standalone functionality allows the automated calculation of the OB fees of a TST without repricing the PNR and impacting the fare guarantee. Once the OB fees Standalone transaction is processed, OB fees are calculated or recalculated and the TST is updated. This means that the agent can calculate or recalculate the fees without impacting the fare previously quoted and so keep the fare guarantee. Pre-requisites The PNR must contain a TST (first issue identifier: F, I, U) for which OB fees are to be calculated or recalculated, the Validating Carrier and the FOP to be used for the ticket issue. The OB fees Standalone transaction can be processed when there is only one TST per passenger covering the same itinerary for all the selected TSTs. Options The TST number is optional. When not present the OB fees Standalone calculation is requested for all TSTs present in the PNR. The multiple TSTs selection is only supported where each passenger has one and only one TST and all selected TSTs share the same itinerary association Specific sub-codes can be added. Entries TTX TTX/T1 TTX/T1-2 Page 12 of 23 All TSTs updated with new OB fees amount TST 1 updated with new OB fees amount Selected TSTs updated with new OB fees amount.

13 Example of the OB fees Standalone transaction The booking is created and the TST is stored. The form of payment is entered as credit card and the TTP entry is made. Enter TTX The OB fees are calculated and the Grand Total is updated. Page 13 of 23

14 The TST is updated to include the OB fee. Note the FCMI has not changed. The TTP entry can be made again Note When issuing a ticket, if the stored fare contains OB fees and the form of payment is not a credit card, the following message is generated: OPTION NOT AUTHORISED WITH FOP IN PNR The TTX entry would need to be made to remove the OB fees from the TST to allow ticket issue. Page 14 of 23

15 Error messages If the user is not authorised to use OB Fees, the following message is generated: ENTRY NOT AUTHORISED If the Issue Identifier is not in First Issue mode, the following message is generated: INVALID ISSUE IDENTIFIER If no valid Form of Payment is associated to the TST, the following message is generated: NEED FORM OF PAYMENT If no valid base fare or equivalent fare is present in the TST, the following message is generated: NEED BASE FARE If no TST already exists, the following message is generated: NEED TST If several TSTs are requested and one pax has more than one TST, the following message is generated: MULTI TST NOT SUPPORTED If several TSTs are requested and all the selected passengers do not share the same itinerary, the following message is generated: MULTI TST NOT SUPPORTED If an invalid TST reference is provided, the following message is generated: INVALID TST NUMBER Page 15 of 23

16 Manual addition, modification and deletion of OB fees If the TST has been manually created, you cannot use the TTX entry. To store the correct OB fees in the TST, manual entries are required. From the OB fees list (TQO), you can add, modify or delete fees. The fee is updated in the OB fees list (TQO) and in the pricing context display (TQC). The grand total amount in the TST is also updated. Add an OB fee TTO/SFCA/CPAYMENTFEE/F4.50 TTO/ /SFCA /CPAYMENTFEE /F4.50 TST fee update command Fee sub-code identifier Fee commercial name identifier Fee amount identifier and amount If the Fee sub-code used in your entry already exists in the TQO, this existing fee will be modified as specified in your entry. Modify an OB fee TTO/SFCA/F3.00 TTO/ /SFCA /F3.00 TST fee update command Fee sub-code identifier to be modified New fee amount to be applied You can only modify a fee that already exists in the TQO. You cannot modify the commercial name of a fee. Delete an OB fee TTO/SFCA TTO/ /SFCA TST fee update command Fee sub-code to be deleted You can only delete a fee that already exists in the TQO. If more than one TST exists in the PNR, each of the above commands must include the specific TST number. Page 16 of 23

17 Sales Reports The OB fees will be shown separately in the Sales Reports. TJQ example AGY NO QUERY REPORT 18JAN CURRENCY EUR OFFICE - DUBEB3101 SELECTION: AGENT - ALL 18 JAN SEQ NO A/L DOC NUMBER TOTAL DOC TAX FEE COMM FP PAX NAME AS RLOC TRNC CC LIAPIS/B AA ZTO28A TKTT CC LIAPIS/D AA ZLGR84 TKTT CC GEBHARDT AS ZTP5JK TKTT CC GEBHARDT AS ZUPNE3 TKTB CA WIEDENRO AA ZLOLIP TKTT CA FLEISCHM AA ZLOLIP TKTT CA KLOENNE/ AA 37FD9Z TKTT MX CLEMENTE AA 37FD9Z TKTT MX LUETTGE/ AA 37FD9Z TKTT [ ] TJT example CREDIT 2 AGENCY JAN CASH 3 OFFID/AS- LISNI0110 PT PT ITEM TAX 4 DOC TYPE- OPATB SALE CURR - EUR FEES 5 AL/PROV NI STATUS - PENDING 0.00 COMM 6 DOCUMENT OPATB SALE PNR 38E3FR 7 8 PASSENGER : GARCIA/LUIS MR 9 TOUR : INVOICE : 0 FOP1 : CC VIXXXXXXXXXXXX TAX : 50.00YQ 26.47YP 40.02XT 2 FEE : OBFCA [ ] Page 17 of 23

18 Graphical functionality The examples below show the graphic equivalent of the 3 command scenarios previously illustrated. 1. No FP element exists in PNR and pricing input option used Click on the more options button Tick Apply credit card fee then send to price the booking Example of Pricing Summary The OB fees are in a separate box below the taxes. Note the messages in the other information box Page 18 of 23

19 Example of TST Click on the Airline Fee breakdown icon to view the fee details Airline Fee Breakdown Click on Cancel to close the box and return to the TST. Page 19 of 23

20 2. FP element entered before pricing the PNR The Apply credit card fee option is greyed out as the system will determine the fees (if applicable) from the FP element in the PNR. Note the message in the other information box Page 20 of 23

21 3. No FP element exists and no pricing input option used When pricing the PNR, the Apply credit card fee box is not ticked and no FP element exists in the PNR Note the message in the other information box Page 21 of 23

22 System Warning and Error Messages 1. When the FCA sub code is added to the pricing command (/R,FA-OBFCA), the following message is generated: MANUAL MANIPULATION OF FEES 2. When no FCA sub code is added or form of payment entered, the following message is generated: FORM OF PAYMENT FEES MAY APPLY 3. When OB fees are included in output, the following message is generated: AIRLINE FEES INCLUDED. 4. When there is a form of payment in the PNR (FP element) and the currency specified in the form of payment (if any) is different from the currency of selling, then the pricing request is rejected and the following message is generated: INVALID PAYMENT CURRENCY ENTERED IN THE FP ELEMENT (CM# 08122) 5. If the Validating Carrier is not the same at ticketing time than the one processed at pricing time, then the following message is generated: VALIDATING CARRIERS DO NOT MATCH : PLS REPRICE OR MODIFY FV 6. When issuing the ticket, if the stored fare does not contain OB fees and the form of payment is a credit card, the following message is generated: TST PRICING CONTEXT MODIFIED: PLEASE REPRICE 7. If the form of payment sub code (/R,FA-OBFCA) is used and an FP element already exists in the PNR, the following message is generated: OPTION NOT AUTHORISED WITH FOP IN PNR Page 22 of 23

23 8. When issuing the ticket, if the stored fare contains OB fees and the form of payment is not a credit card, the following message is generated: OPTION NOT AUTHORISED WITH FOP IN PNR Please re-price the booking with no OB fees 9. If you receive the following error message after using the pricing option /R,FA- OBFCA, please call the helpdesk: ENTRY NOT AUTHORISED Page 23 of 23