The follow are required entries for interfaced bookings:
Client Interface ID
Tres matches GDS records to Trips using the client’s Interface ID. The interface ID is a unique code assigned to each client profile. Interface IDs must not include spaces or special characters, and we recommend interface IDs are ten or fewer characters.
This ID can be entered in Travelport + using one of the following formats:
DI.FT- AN{interface ID}
DI.FT-CA{interface ID}
Examples:
DI.FT-AN310641876
DI.FT-CA010030
The Interface ID in the Tres client profile must match this exact value.
If Auto Create Client Profiles is enabled in Agency Settings:
An address must be included in the GDS PNR (Passenger Name Record).
- The first line of the billing address is used as the default client profile name.
- If a billing address is not included in the PNR, Tres will not automatically create a new client profile.
- Customer name and address details will interface to Tres for new client creation.
Example:
W.GEORGE BENSON*111 MOODY LN*CHICAGO*IL*P/60603
Additional Entries:
Skip To:
Generating Invoices
Travelport+ creates interface files (MIRs) for the following commands:
- TKP Generates tickets, invoice, and MIR for all segments
- TKPDIDAD Generates an invoice and mir for PNRs without air bookings
- TKPDJD Generates itinerary update for existing Tres bookings
ARC/BSP Tickets
A MIR is created automatically when issuing tickets using the TKP format. Any other automated segments are included in the MIR record. For standard tickets, no additional entries are required.
ARC/BSP Travel Agency Service Fees (TASF)
Travelport+ offers a smart button to assist with issuing ARC/BSP service fees. The button will issue the service fee document and add the required free-text remarks to the PNR. To enter a service fee booking without the Smart Button, create a service fee using the regular SFP format, for example, SFPUSD25.00. Redisplay the PNR, and create a free-text remark using the following format.
See Travelport+ Service Fees in Tres for details.
Non-ARC/BSP Tickets
For non-ARC/BSP tickets, enter the following free text remarks:
DI.FT-MS{segment number}S*VC{airline code}*CF{ticket/confirmation number}*SG {optional segment numbers}*TF{total fare}*TX{taxes}*CM{commission}
Example, all segments:
DI.FT-MS1S*VCWN*CF2401091534*SG*TF500.00*TX75.00*CM0
Example, specific segments:
DI.FT-MS1*VCWN*CF2401091534*SG 01 03*TF500.00*TX75.00*CM0
Itinerary Update (HU)
Information Updated Using Itinerary Updates
Changes to existing hotel and car reservations and flight schedules can be interfaced to Tres using Itinerary Update. To update a Tres trip:
- Enter the PNR remark: DI.FT-HU
- Generate an itinerary using TKPDJD
During interface, Tres looks for invoices matching the itinerary PNR record locator. When it finds a match, it updates the following:
- Hotel and car reservations:
- Any existing hotel and car reservations are voided.
- Hotel and car reservations in the itinerary are added to the most recent trip with the PNR record locator.
- Existing car and hotel reservations with a start date prior to itinerary date are ignored. This retains any past date reservations active in Tres, even if they’ve fallen out of the itinerary. Past date reservations remain in the original trip.
- Flight schedules
- Tres updates flight schedules on all bookings related to the PNR record locator.
- Only matching flight segments based on departure city are updated. New segments are not added, and existing cities are not changed.
- Updated information includes departure and arrival dates and times, and flight numbers.