Skip to main content

 

 

Coupa Success Portal

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. 
  • Coupa does not currently support multiple bank account sections in one file, both in the starter file (we store on T3) and in the transaction files coming after starter file. File providers have the ability to send separate files per master account if requested. 

Expense UI Field

Description

Visa

Expense Line Fields

Description

Name by which the card acceptor is known/referred

 

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 TransactionDate. This is a Coupa setup that requires discussion with your Coupa Integration Architect or Implementation Manager.

T5_CardTransaction/TransactionDate

OR

T5_CardTransaction/PostingDate

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

 

Location

HotelLocation

T5_CardTransaction/SupplierCity,SupplierState_ProvinceCode,SupplierCountryISO_Code,SupplierPostalCode

Airfare Category Custom Fields*

Airfare

Ticket Number associated with the airfare transaction.

T14_PassengerItinerary/TicketNumber

Departure Date

Departure Date of the airfare transaction.

T14_PassengerItinerary/Departure Date

Route

AirSegments

T15_LegSpecificInformation/

Departure Date

AirLegDepartDates

T15_LegSpecificInformation/Departure_Date

Carrier

Code identifying the travel agency that supplied the ticket.

T15_LegSpecificInformation/CarrierCode

Class

PrimaryAirServiceClass

 

Class

AirLegServiceClass

T15_LegSpecificInformation/ServiceClass

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:
o Account #
o Posting date
o Transaction reference #
o Sequence #

T5_CardTransaction/account_num posting_date ref_num seq_num

  • Was this article helpful?