Assisted Ticketing

Building Manual Fares from an E-Ticket

 

Assisted Ticketing provides a user interface to store manual fares, which can assist with exchanges. The Manual Fare Builder tab gives you an option to build a manual based on an e-ticket.

Important!

The Manual Fare Builder feature in Assisted Ticketing does not provide any guarantee against ADMs (Agency Debit Memos):

  • Agents are obligated to obtain all of the necessary approvals before proceeding with Manual Fare Build.
  • Agents should always check all Filed Fare elements before storing or updating the manual fare.

 

To build a manual fare from a e-ticket:

  1. Retrieve a PNR/Booking File that needs a manual fare store.

  2. Click the Ticket icon to launch the Smartpoint Assisted Ticketing window.

    Tip! You can also enter the #MANMASK Quick Command.

  3. Select the Manual Fare Builder tab.

  4. Expand Select Fare Source to view a list of all the available stored Filed Fares and e-tickets in the PNR/Booking File.

  5. Click the Filed Fare list arrow to select the desired fare.

  6. Click LOAD MASK FROM E-TICKET to expand the Select Segments and Passengers section. By default, the data in this section is based on the selected ticket.

  7. Select the applicable segments and passengers. At least one segment and passenger must be selected.

  8. Click CONTINUE to expand the Stored Fares section.

  9. Optional. Select Enable per-pax Fares to store a fare for each passenger by PTC separately.

  10. Scroll through the section to review or update fare details for each the passenger and segment selection.

    Tips!

    • For itineraries that include segments in the United States, PFC and ZP taxes may be required.

      Itineraries that include segments with airports in the United States typically require charges including:

      • PFC: Passenger facility charge (Tax Code: XF).

      • ZP: US Federal segment fee (Tax Code: ZP)

    • Pre-filled tax data may be inaccurate in Smartpoint 11.4 and earlier, and should be corrected.

      • In Smartpoint 11.4 and earlier, tax data may be inaccurate. Pre-filled tax fields should be reviewed and corrected, if necessary.

      • In Smartpoint 11.4.1 and later, an alternate source of tax data returns accurate data, if available. If data is not available, the tax fields are blank and tax data can be manually entered.

    • For more information about Manual Fares entries and business processes, see Manual Fare Build and other manual fares topics in the Travelport Knowledge Base.

  11. Optional. Add endorsements and ticketing modifiers.

    Modifier

    Details

    Endorsement (EB)

    Endorsements specify restrictions applicable to a ticket. These remarks are created based on the fare for the ticket.

    Examples:

    • VALID UA ONLY

    • VALID FLTS DATES SHOWN

    • NONREF

    Manual Fare builder supports a total of 87 characters, which can be added in 1 to 4 lines.

    Click the Add icon to add up three additional endorsement lines.

    Note: Not all characters display on the issued e-ticket or in the order entered. Each airline has its own restrictions for the maximum number of characters displayed on an issued e-ticket.
    Plating Carrier

    The 2-character airline code for the carrier that is responsible for ticketing the fare.

    Fare Type

    Select either IT (Inclusive Tour) or BT (Bulk Tour) modifiers.

    See the ETKT Fact Sheet in KB0016545 in the Travelport Knowledge Base to determine if a carrier supports BT and/or IT ticketing.

    Inclusive Tour fares include charges in addition to the airfare, such as accommodations or ground transportation as part of a "package".

    Inclusive Tour (IT) suppresses the fare and does not print the fare construction on the passenger receipt.

    Bulk Tour fares are usually given to agencies who book a high volume of seats such as a consolidator or wholesaler. However, typically accommodations or other package items are not required for this fare.

    Bulk Tour (BT) suppresses the fare and does not print the fare construction on the passenger receipt.

    In Tour Code, enter a corresponding tour code (TC) for the IT or BT fare. Tour codes (TC) are issued by an airline to identify a tour deal.

    The tour code must be entered into the fare as a ticket modifier so that both the airline and the local BSP know the source of the fare and the agency's authorization to use the fare.

    The Tour Code can be a maximum of 14 characters. The code can also be used in combination with an Inclusive Tour or Bulk Tour indicator.
    Commission

    Smartpoint 11.0 and later

    Confirm or change the commission and select Percentage or Amount.

    When you issue a ticket, Travelport+ (1G) automatically defaults to the commission rates that are held in the commission table provided by Travelport+ (1G) or stored in your AAT table.

    However, you may need to change the commission level if either:

    • An agency arrangement exists with an airline.
    • The airline has changed their standard commission but not yet advised Travelport+ (1G) .

    Ticket Designator

    Smartpoint 11.2 and later

    United States and Canada only.

    A designator filed by carriers to indicate a type of fare such as a specific private fare, promotion, or discounted fare.

    Note: This modifier displays only for US (ARC) and Canadian (BSP) PCCs.

    The Ticket Designator field is different from the Tkt Dsgr field:

    • This Ticket Designator field adds the ticket designator to the T-Line (ticket line) of the stored fare.

      Example

    • The Tkt Dsgr fields associated to each stored fare line adds the ticket designator to the fare basis code (FBC) line.

      Example

      In this example, the Tkt Dsgr value is MFXL.

    Known Host Limitation
    The maximum length of the ticket designator modifier is 10 alphanumeric characters. However, this ticket designator combined with the FBC (fare basis code), cannot exceed a total of 15 alphanumeric characters.
    If this 15-character limit is exceeded, an error displayed as either a pop-up message or as header text: ERROR 340 - TICKET DESIGNATOR IS TOO LARGE.

  12. Click STORE NEW FARE(S) to store the manual fare to the PNR/Booking File.

    Note: The Update Filed Fare feature is enabled when the Mask is loaded from an e-ticket. If you select UPDATE FILED FARE, the existing Filed Fare is updated instead of storing the manual fare as a separate Filed Fare.

    A popup message to confirm the successful Manual Fare build is displayed.

  13. Select from the save and close options:

    • SAVE CHANGES AND CONTINUE ends and retrieves (ER) the PNR/Booking File and refreshes Assisted Ticketing.

    • SAVE CHANGES AND CLOSE ends and retrieves (ER) the PNR/Booking File and closes Assisted Ticketing.

    • CLOSE exits Assisted Ticketing with ending and retrieving (ER) the Booking File.