Benchmark Fares QuickTravInvoicing module Benchmark fares

Size: px
Start display at page:

Download "Benchmark Fares QuickTravInvoicing module Benchmark fares"

Transcription

1 Benchmark Fares QuickTravInvoicing module Benchmark fares Overview A benchmark fare option has been added to QuickTrav Invoicing, which works on similar principles to the published fare option. For each ticket / refund notice issued, you can specify a comparative benchmark fare and a difference reason code. This can be made compulsory on specified debtor accounts. Then you can generate reports for your clients showing the fare vs. the benchmark fare grouped by the difference reason code. Client debtor accounts can be flagged to force the capture of benchmark fares. Otherwise the capture of benchmark fares is optional. Tables of default benchmark fares can be set up for any client account. These tables let you specify a benchmark fare per airline / routing / class combination as agreed with the client. These facilitate easy and accurate data capture. Tables of benchmark fare difference reason codes must be set up for all clients for which you capture benchmark fare information. When invoicing, each ticket and refund notice captured will be prompt for 1) a benchmark fare and 2) a difference reason code. The benchmark fare (1) will default per the clients lookup table (if it can be found in the lookup table). The benchmark fare information is saved with the invoice and printed in the invoice message. The client travel analysis / quick reporter can be used to generate benchmark fare savings reports (this reporting is very similar to the published fare saving reporting). Setup Generalsetup Go to menu option Setup, Company,, open the selected branches, and select the "Fares"Tab. Go to option Use client benchmark fares / savings: Tick on the to activate. Tick the if you want capture the reason for the differences Tick the to print on the invoice document along with the benchmark saving information. Editing existing accounts : For each debtor that you wish to force capturing of benchmark fares, open the Edit Debtors screen (Setup, Clients, ) and select the "Benchmark Fares"Tab to activate the option. p164

2 Note -the capture benchmark information for debtor accounts that have this option turned off (and leisure accounts) is optional. Table ofdefaultbenchmark fares (per client) Lookup tables of default benchmark fares can be set up for any debtor or leisure client. They should generally be set up for all debtor accounts flagged with the force capture of benchmark fares option. The fares captured should match those agreed with the client. These lookup tables make the invoicing process much easier as the default benchmark fare can be inserted in the invoice automatically. The lookup tables can be created under "Client Benchmark Fares", select and the following table opens: Code Airline Routing Use a unique 3chr code for each item, generally the use of 001 to 999is advisable Enter the airline numeric code Enter the routing city pair. Note Jnb/Dur is the same as Dur/Jnb so you do not have to enter both. QuickTrav will reverse the routing cities to find a p165

3 Class Fare Deactivate match if necessary Enter the applicable class or classes (multiple classes are allowed) Enter the benchmark fare for the airline / routing / class combination Switch to activate or deactivate the particular benchmark fare Enter all combinations of airlines / routings /classes per your agreement with your client For tickets with multiple flights eg Jnb/Dur/Cpt/Jnb QuickTrav will add up the individual fares for the individual flights (Jnb/Dur, Dur/Cpt, Cpt/Jnb) and will insert the total as the default benchmark fare. Note these tables are setup per client. Once all information is completed click on the to save the added benchmark fare. Table ofbenchmark fare difference reason codes (per client) If you specify a benchmark fare, you must always specify a difference reason code to explain the difference. Lookup tables of benchmark fare difference reason codes must be set up for any debtor or leisure client for which you wish to capture benchmark fares. The lookup tables can be created under "Benchmark fare difference reason codes", select and the following table opens: Code Use a unique 3chr code for each item, generally the use of 001 to 999is advisable Description Enter a meaningfull description for each "difference"reason applicable to the client. Note these tables are setup per client. Once all information is completed click on the to save the added benchmark fare. p166

4 Activating Benchmark Fares Select Setup, Company,, click on, and select the option: Capture Benchmark Fares? Benchmark Fare limit Factor Benchmark Fare upper Limit % p167

5 Benchmark Fare lower Limit % Override Benchmark Fare Limits Password Captured Benchmark Fare Difference Reasons Show Benchmark Fare Difference Reasons on Documents? p168

6 Creating / Editing Benchmark Fare Tables Select Setup, Clients, and select the tab. Tick the option. Note:The capture of benchmark information for debtor accounts that have this option turned off and leisure accounts is optional. Table ofdefaultbenchmark fares (per client) Lookup tables of default benchmark fares can be set up for any debtor or leisure client. They should generally be set up for all debtor accounts falgged with the 'Force capture of benchmark fares' option. The fares captured should match those agreed with the client. These lookup tables make the invoicing process much easier as the default benchmark fares can be inserted in the invoice automatically. Creating a New Benchmark Fare: To create the table click on. Key Enter a unique 3character reference for each item, p169

7 Deactivate Airline Routing Class List Fare generally the use of 001 to 999is advisable Switch to activate or deactivate the particular benchmark fare Enter the airline numeric code Enter the routing city pair. Note 'Jnb/Dur' is the same as 'Dur/Jnb' so you do not have to enter both. Quick Trav will reverse the routing cities to find a match if necessary Enter the applicable class ot classes (multiple classes are allowed) Enter the Benchmark Fare for the airline / routing / class combination Creating a Bencjmark Fare Difference Reason: To create a reason click on Code Deactivate Description Enter a unique 3character reference for each item, generally the use of 001 to 999is advisable Switch to activate or deactivate the particular benchmark fare difference reason Enter a meaningful description for each "difference" reason applicable to the client. p170

8 Invoicing Benchmark Fares ManualInvoicing To manually invoice an air ticket, proceed in the normal manner, and at the end of the air tickets invoice line, you will see a new Tab has been added, called Fare Comparison, where you will be prompted to enter the benchmark fare along with the difference reason code. Quick Trav will lookup the 'airline / routing / class' combination(s) in the default benchmark fare table for the client specified in the invoice header. If found Quick Trav will automatically insert the calculated benchmark fare, making the data capture easier and more accurate. If not found and the account is flagged 'Force capture of benchmark fares', a warning message will display and you will have to manually capture the benchmark fare and difference reason before you can continue. Automatic Invoicing To automatically invoice an air ticket, the consultant must now add the entry E*' Entry: To use the default benchmark fare per the clients benchmark fare lookup table, specify with the following entry:e*d,xxx(d being the default setting & xxxbeing the reason code) To manually specify the benchmark fare use the following entry:e*4000,xxx (4000 being the benchmark fare and xxxbeing the reason code) E* Benchmark E* being the Benchmark fare p171

9 Fare E*1000,xxx xxx being the Benchmark fare reason code If you have more than one ticket on the Pnr/Invoice with different fares and different benchmark fares, then you must enter a benchmark fare for each ticket in the following format: E*Amount1,Code/Amount2,Code/Amount3,Code with each benchmark fare separated by a / following by","and the reason code. p172