Skip to main content

Amadeus GDS Integration for Tres - Entries Affecting Interfaced Bookings

www.trestechnologies.com
© Tres Technologies. All Rights Reserved.

Amadeus GDS Integration for Tres - Entries Affecting Interfaced Bookings

  • Updated

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 Amadeus using one of the following formats:

Amadeus Account Number (AIAN)

Format: AIAN{account number}

Examples:

AIAN3105551234

AIANALPHACORP

The AIAN number will also print on GDS documents such as invoices, itineraries, and e-ticket receipts.

Interface Remark (RM*AN)

Format: RM*AN{interface ID}

Examples:

RM*AN5551234567

RM*AN010030

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:

ABGeorge Benson,111 Moody LN/Chicago IL 60603

 

Additional Entries:

Skip To:

Billing Address - AB/ABS

If 'Auto Create Client Profiles' in enabled, the billing address is mandatory.  The first line of the billing address is used as the default client profile name, so if it's not included in the PNR, Tres will not automatically add the new client. Customer name and address information interfaces to Tres for any new clients. In Amadeus, enter HELP ADDRESS for additional information.

Billing Address entry – AB

ABNAME,ADDRESS1/ADDRESS2,CITY ST POSTAL

Billing Address entry – AB

ABCUSTOMER NAME
ABADDRESS 1
ABADDRESS 2 (optional)
ABCITY, ST POSTAL CODE

Branch Override - RM*BR

For branch override, the descriptor is *BR, but it's followed by the branch name set up in Tres in Settings > Branches, not a branch number.  

Override to specific branch and associated ARC/BSP number

*BRBRANCH NAME

Override to specific branch and different ARC/BSP number

*BRBRANCH NAME*01234567

Generating Invoices

ARC/BSP Tickets and Service Fees

Tickets and ARC/BSP service fees issued electronically in Amadeus will have all the necessary information for importing into Tres. Agents only need to ensure that an invoice is generated.

Non-ARC/BSP Air Bookings

Non-ARC/BSP bookings are dependent on the use of special account remarks (RM) line and a valid invoicing command.

The following format should be used. The example shows the mandatory fields required by Tres:

  • RM*MS{segment number}*VC{vendor interface ID}*TC{travel category}*TF{total fare}*CM{commission}
  • RM*MS(segment number)*FP(form of payment)

Example:


RM*MS50*VCSVCFEE*TCSERVICEFEE*TF35.00*CM100*PNSMITH/JOHN
RM*MS50*FPCCVI4444333322221111/1235

Each non-ARC/BSP booking should be assigned a segment number that is higher than the segment numbers used by live Amadeus reservations. We recommend starting your MS numbers with the number 50 and incrementing for each additional Non-ARC/BSP booking.

For example, to invoice a cruise booking and a tour booking on the same invoice:

  • RM*MS50*VCRCCL*TCCRUISE*TF2500.00*CM14*PNSMITH/JOHN
  • RM*MS51*VCFUNJET*TCTOUR*TF2275.00*CM$325.00*PNSMITH/JANE

Additional descriptor codes

The above examples include the minimum information required, but additional booking details can be included in the accounting remarks lines.

If your accounting lines exceeds the maximum number of characters, you can continue the details by adding an additional remark line using the same segment number for each line.

Code Purpose Format Example
TC Travel Category *TC{category} *TCCRUISE
VC Vendor Interface ID *VC{vendor interface id} *VCRCCL
CF Confirmation Number *CF{confirmation number} *CF123456ABC
SD Start Date *SD{date} *SD22SEP
ED End Date *ED{date} *ED27SEP
SG Capture Segment Details (All Air Segments) *SG *SG
SG Capture Segment Details (Specific Segments) *SG {seg number} {seg number} … *SG1 3 5

 The following travel categories are valid when using the TC descriptor code:

  • Air
  • Car
  • Cruise
  • Excursion
  • Hotel
  • Insurance
  • Miscellaneous
  • Rail
  • Service Fee
  • Tour
  • Transfer

Hotel- and Car-Only PNRs

For hotel and car bookings included on invoices, Tres will automatically import automated hotel and car reservations.

Tags

Tags can be added to all bookings or linked to a specific booking. To assign a tag to all bookings on a PNR:

RM*UD{tag name}{space}{data}

Example:

RM*UDPONUMBER 123456

To assign to a single segment, use an MS line as described earlier:

RM*MS1*UDPONUMBER 123456

RM*MS50*UDPONUMBER 123456

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:

  1. Enter the PNR remark: RM*HU

  2. Generate an itinerary using BT

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.

Tres Travel Sub-Categories

If using Travel Sub-Categories in Tres, use the following format:

RM*MS(200+the ticket reference)*TT(custom travel category), for example, RM*MS201*DOM AIR; RM*MS202*TTDOM AIR

Follow the *TT descriptor with the sub-category name, for example RM*MS99*TTDOM AIR

Related articles