Egencia T&E Feed Format
T&E Feed format
Feed Format fields
All strings will be in US English.
Field | Format | Required | Description & Values |
CompanyID | Integer | Y | Egencia ID of the company |
CompanyName | varchar(60) | Y | Name of the company |
AccountLastName | varchar(60) | Y | Last name of the Egencia account holder |
AccountFirstName | varchar(60) | Y | First name of the Egencia account holder |
AccountMiddleName | varchar(60) | N | Middle name of the Egencia account holder |
AccountEmailAddress | varchar(132) | Y | Email address of the Traveler |
TravelerLastName | varchar(60) | Y | Last name of the traveler |
TravelerFirstName | varchar(60) | Y | First name of the traveler |
TravelerMiddleName | varchar(60) | N | Middle name of the traveler |
DepartmentName | varchar(60) | N | Name/Code of the department that the transaction was associated with |
TravelerGroupPolicyName | varchar(60) | N | Name of traveler group that account holder belongs to currently |
LineofBusinessID | Integer | Y | The line of business the transaction belongs to.
6 – is coupons and will not be sent and will not be included as part of the XSD.
|
BookingTypeID | Integer | Y | The type of the booking
6 is Unused and will not be included in the XSD. 9 is UTT Exchange and will not be included in the XSD since it’s not available. 10 is Cancel Refund – only EU specific- will not be included as part of the XSD UTTMCO – Redemptions are not identifiable. They will be sent as purchases. Generated MCOs we receive in the feed show up as exchanges.
|
MeetingName | varchar(255) | N | Name of the meeting if this is a booking associated with a meeting or conference |
VendorName | varchar(255) | N | Name of airline, hotel, car, rail or other vendor |
VendorCode | char(3) | N | IATA Airline codes, Car vendor codes etc if present. |
ItineraryNumber | varchar(13) | Y | Egencia Itinerary number |
TicketCode | varchar(20) | N | 10 digit Ticket number - For LCCs & non-Air LOB – these may not be present. |
TicketCodePrior | varchar(20) | N | The 10 digit prior ticket number since the ticket number changes on an exchange. Refunds/Partial Refunds the value of TicketCodePrior is the same as TicketCode. |
PNRCode | varchar(35) | N | PNR number in the GDS – Only for Air & GDS hotels. |
ConfirmationCode | varchar(255) | N | Confirmation code |
GeographyTypeName | varchar(50) | N | The geographical location of the booking For Egencia US, the values are “Domestic” or “International” For Egencia CA, the values are “Domestic”, “International” & “Transborder” where “Transborder” means flights between US & CA. |
IssueDateTime | smalldatetime | Y | Date and time of transaction in default timezone of the point of sale (for US it will be in PST) |
TravelStartDateTime | smalldatetime | N | Date/Time of departure at origin/Checkin DateTime/Pickup DateTime/Travel start dateTime in local time |
TravelEndDateTime | smalldatetime | N | DateTime of arrival at destination/Checkout DateTime/Dropoff DateTime/Travel End dateTime in local time |
LocationFrom | varchar(100) | N | Freeform location text of the Origin |
AirportCodeFrom | char(3) | N | IATA Airport code of the Origin |
CityNameFrom | varchar(60) | N | Airport code of Origin airport OR Pickup City For Limo & Other, this might be a free form location text. NOTE: Empty for Hotel bookings |
RegionNameFrom | varchar(60) | N | Name or code of State or Province of Origin or Pickup State |
CountryNameFrom | varchar(80) | N | ISO Country code of Origin |
LocationTo | varchar(100) | N | Freeform location text of the Destination |
AirportCodeTo | char(3) | N | Airport code of the destination. Also, the Airport code of the location of the hotel. |
CityNameTo | varchar(60) | N | IATA Airport code of Destination airport OR Dropoff City also location of Hotel. For Limo, this might be a free form location text.
|
RegionNameTo | varchar(60) | N | Name or code of State or Province of destination or Dropoff State or State in which hotel is located |
CountryNameTo | varchar(80) | N | ISO country code of destination or country code in which hotel is located. |
BookingAmtGross | money | N | Price of the transaction – includes Base, Taxes and add/collects. |
BookingAmtBase | money | N | Base fare of the transaction |
BookingAmtTax | money | N | Taxes. This includes Tax1Amount, Tax2Amount, Tax3Amount if available and Other taxes |
CurrencyCode | char(3) | N | Currency code in which the TransactionPrice, Base fare, Taxes and Other taxes are represented. |
Tax1Code | varchar(10) | N | Code of tax breakdown – This could be for GST/HST/QST in CA or GST in AU or Service Tax in IN. For purchases, this will be tax for the ticket. For exchanges, this will be the differential tax of the exchange.
|
Tax1Amount | money | N | Amount of tax |
Tax2Code | varchar(10) | N | Same as for Tax1Code |
Tax2Amount | money | N | Amount of tax |
Tax3Code | varchar(10) | N | Same as for Tax1Code |
Tax3Amount | money | N | Amount of tax |
CreditCardTypeID | tinyint | N | Type of Credit card used for the transaction
|
RateType | varchar(20) | N | Is the rate Published/Negotiated /Merchant This will be unknown for Cars & offline bookings. |
LowestLogicalFare | Money | N | This is the cheapest in policy flights that is also within the reasonable policy set by the company. |
AirCabinClassID | tinyint | N | For Air:
|
CarDisplayGroupID | smallint | N | For Car:
|
HiredCarVehicleTypeID | Tinyint | N | For Limo/TownCar
|
PolicyStatusID | tinyint | N | Was the BookingAmtGross in policy or not.
|
PolicyReasonCode | char(4) | N | Reason code indicated by user for overriding policy |
PolicyReasonCodeDesc | varchar(255) | N | Description of the Reason code |
CentralBillBool | int | N | Boolean to determine whether or not this was a central bill credit card transaction CentralBillBool="0" for non-central bill card CentralBillBool="1" for central bill card |
CustomerDataElementTxt
| varchar(2000) | N | Custom defined fields by the company – Upto 15 name, ID, value fields Format: “<ID&&Name&&Value><< ID&&Name&&Value>…” Example: “ID1&&DeptCode&&1011<ID2&&Authcode&&Foobar” etc. |
File name specification
The file name format will be the following
<VendorName>_Egencia<2LetterPOSAcronym>_<DateFrom>-<DateUntil>.zip
Where <DateFrom> and <DateUntil> will be in YYYYMMDD format and will specify the date range the data is for. <DateFrom> and <DateUntil> will be the same for a single day’s data.
<VendorName> is the name of the T&E vendor
Example, “TnEVendor_EgenciaUS_20080913-20080913.zip” will be the filename of the file dropped for a company called “TnEVendor” on 09/15 containing data of all transactions on 09/13 for “TnEVendor” clients signed up for the integration.
The following attribute information is added to each feed file
Name of the file – Tag to use “FileName”
Date range of data in the file
Tag to use “DateFrom”. Value will be in ISO Date format.
Tag to use “DateUntil”. Value will be in ISO Date format.
Date/Timestamp of creation of the file – “CreatedDateTime”
VersioningInfo of the feed format – “VersionInfo” – Value “1” for now.
SFTP site details
You will access files over SFTP from a site setup on our side.
NOTE: We will share the SFTP site details as soon as they are set up on our side.
Custom unique identifier
Upon special request to the implementations manager, the implementation manager can designate a specific CDF (Custom Data Field) to be mapped to a new field called “EmployeeCode”. While the same information is included in CustomerDataElementTxt, by singling this data into it’s own field, it helps T&E vendor to find this data point more easily. This datapoint is often used as unique identifier for the user’s Egencia and T&E vendor accounts.
This is an optional custom field
Data format is varchar(60)
2024 DATABASICS, Inc