Corporate Card Mapping: VISA
- The table below provides mapping data for VISA only. For a full list of mapping data for all cards together refer to the Integrations Mapping file.
- Category Custom Field population requires configuration within a Coupa instance and data to be populated by corporate card provider on incoming files.
- Coupa can consume tab-delimited files only, comma separated file will not be processed.
- Visa will need an initial starter load file that contains all account holder information, which is used to tie any future transactions back to the correct user. This file must be loaded into an instance (both sandbox and production) before loading transaction files.
- Prior to Release 20, Coupa does not support multiple record blocks (referred to as sets) in one file, both in the starter file and in the transaction files coming after starter file. File providers have the ability to send separate files per master account if requested. If a file is received with multiple record blocks, the file processing will fail and an error message will be raised on the Integration run record.
- As of Release 20, Coupa can support multiple record blocks (sets) in one file, both in the starter file and in the transaction files coming after starter file.
- Setup > Corporate Card Settings > Go to User Mappings > Expense Import User Map > Create may be used to create corporate card integrations for the different valid account types. The Expense Import User Map must include one of these valid account types (VISA, AMEX, MCC, or EMPLOYEE_ID) so that records may be successfully processed.
|
Expense UI Field |
Description |
Visa |
|
Expense Line Fields |
||
|
Description |
Name by which the card acceptor is known/referred |
N/A |
|
Total |
Amount of transaction in invoice currency |
T5_CardTransaction/BillingAmount |
|
Currency |
ISO 4217 three digit numeric Currency Code that this amount is in. Coupa code takes into Consideration the CurrencyExponent and CurrencySign when parsing to Coupa |
T5_CardTransaction/BillingCurrencyCode |
|
Expense Category |
Merchant Category Code (4 digit Code) of the card acceptor which classifies the type of business. AirPlus populates this field with ‘0000’ for unknown if this information is not available. MCC Code drives Category default on an expense line based on instance Corporate Credit Card Category Mapping setup. |
T5_CardTransaction/MerchantCategoryCode |
|
Merchant |
Name by which the card acceptor is known/referred |
T5_CardTransaction/SupplierName |
|
Date |
Coupa maps the PostingDate to Expense Date by default. Customers can choose to have Coupa map the TransactionDate to Expense Date instead of PostingDate. This is a Coupa setup that requires discussion with your Coupa Integration Architect or Implementation Manager. |
T5_CardTransaction/PostingDate OR T5_CardTransaction/TransactionDate
|
|
Rental Car Category Custom Fields* |
||
|
Rental Car |
RentalCarAgreementNumber |
T2_CarRentalSummary/Purchase_ID |
|
Rent Date |
Date the customer picked up the car or, in case of a No Show or Pre-paid transaction, the scheduled pickup date. |
T2_CarRentalSummary/Check-outDate |
|
Duration |
Represents the length of rental, measured in number of days charged in transaction. |
T2_CarRentalSummary/DaysRented |
|
Return Location |
Destination City where car is returned to the Rental company. |
T2_CarRentalSummary/ReturnLocation |
|
Renter Name |
Renter’s name for a Car Rental transaction. |
T2_CarRentalSummary/RenterName |
|
Hotel Category Custom Fields* |
||
|
Lodging? |
HotelReservationNumber |
T9_LodgingSummary/PurchaseID |
|
Arrival Date |
Date customer checked into hotel, or Scheduled Arrival Date in case of a No Show or an Advance Lodging |
T9_LodgingSummary/CheckInDate |
|
Departure Date |
HotelDepartureDate |
T5_CardTransaction/TransactionDate |
|
Duration |
Represents the length of stay, measured in number of nights. |
T9_LodgingSummary/LodgingNights |
|
Rate |
Daily room rate for hotel in Card transaction. |
T9_LodgingSummary/DailyRoomRate |
|
Guest Name |
HotelGuestName |
N/A |
|
Location |
HotelLocation |
T5_CardTransaction/SupplierCity,SupplierState_ProvinceCode,SupplierCountryISO_Code,SupplierPostalCode |
|
Airfare Category Custom Fields* |
||
|
Airfare |
Ticket Number associated with the airfare transaction. |
When charge lines are integrated from your Visa corporate card partner the integration files are parsed and a field called 'Airfare' is pulled from the data. Depending on the partner we have different mappings. The label is generic and it can be renamed using Setup > Expense Categories > Airfare (Edit) and Add Custom Field. |
|
Departure Date |
Departure Date of the airfare transaction. |
T14_PassengerItinerary/Departure Date |
|
Route |
AirSegments |
Currently not supported. |
|
Departure Date |
AirLegDepartDates |
Currently not supported. |
|
Carrier |
Code identifying the travel agency that supplied the ticket. |
Currently not supported. |
|
Class |
PrimaryAirServiceClass |
N/A |
|
Class |
AirLegServiceClass |
Currently not supported. |
|
Passenger Name |
Customer name as indicated on the ticket purchased. |
T14_PassengerItinerary/PassengerName |
|
Domestic |
DomesticInternationalInd |
T14_PassengerItinerary/Domestic/_International_Indicator |
| External Fields | ||
|
External Source Name |
Indicates the Corporate Card File Type. For Visa transactions, hardcoded to corporate_credit_card_vcf4. |
Hardcoded to VISA corporate card file type: corporate_credit_card_vcf4 |
|
External Source Data |
Indicates the Visa Filename the transaction was parsed from |
Hardcoded to VISA Filename transaction was parsed from |
|
External Source Ref |
Indicates a unique source number for each transaction based on 4 segments from the VISA file: |
T5_CardTransaction/account_num posting_date ref_num seq_num |