Importing Corpay Payments · Cordovan Docs

A supplier paid in a foreign currency is paid through Corpay. The advisor records the payment on the trip in the supplier's currency, and the bank shows only its dollar cost, so the two never match on Record Bank Transactions. Import Corpay reads Corpay's payment history, gives each recorded payment the dollar cost of its deal, and matches its bank line. This covers exporting the history, reading the result, what to do about a deal that wasn't matched, and what every message means. The video uses sample data. For users with the accounting role.

When OTA pays a supplier in a foreign currency, the money goes out through Corpay. The advisor records the payment on the trip in the supplier's currency, for example EUR 290.00. Corpay takes the dollar cost from the Chase checking account, for example $328.44, as one ACH debit per deal. On Record Bank Transactions the two amounts can't be matched, because the payment is in euros and the bank line is in dollars.

Import Corpay fixes that. You upload Corpay's payment history, and each payment recorded on a trip is given the dollar cost of its Corpay deal. Its bank line then matches it the same way a dollar wire or ACH does.

This is for users with the accounting role. Record Bank Transactions is in the sidebar under Finance, Bank Transactions.

Before you start

The supplier payment has to be recorded on the trip with Apply Payment, as OTA paid, by ACH or Wire. The Amount and Currency are what the supplier received, in their currency. The Payment Date is within a week of the Corpay deal date. Recording a Vendor Payment covers Apply Payment.
The Chase activity that holds the Corpay debits should already be imported with Upload CSV. If it isn't yet, import it afterwards: the match is made either way.

Importing the history

In Corpay, open Payments, then History, choose the dates, and export it as a CSV file. Overlapping dates are fine.
In the portal, open Finance, Bank Transactions.
Click Import Corpay at the top right, next to Upload CSV, and choose the file.

A green message gives the result, for example Corpay: 2 of 4 payments given their dollar cost, 2 bank lines matched to trips. It reads like this:

2 of 4 payments given their dollar cost: the file had 4 Corpay deals, and 2 were paired with a payment recorded on a trip.
1 already had it: deals paired by an earlier import. Nothing changes for these.
2 bank lines matched to trips: bank lines that were matched to those payments as a result.

A deal can be paired and still have no bank line matched, when the Chase activity for that day isn't imported yet. It matches as soon as you upload it.

What changes on the page

Each matched Corpay debit now shows its trip in the Trip column, marked Auto-matched. Under the trip name are the vendor, the method, the amount the supplier received and what it cost through Corpay, for example Villa Positano · Wire · €290.00 · $328.44 via Corpay.

A matched line is coded to Supplier Balances and shows To post. Check the match, then submit it with the rest of the page using Submit to Tres. TRES books it as a supplier payment on the reservation for the dollar amount on the bank line. The payment's remarks in TRES name the foreign amount and the deal, for example "EUR 290.00 via Corpay deal 1048211".

If a match is wrong, use Change or Unmatch under it, as for any other trip match.

Deals that weren't matched

Deals the import couldn't pair are listed in an amber box under the green message, with the date, the beneficiary, the amount and currency, the dollar cost and the Corpay internal note. Under each is the deal number and the reason.

Reason	What to do
No OTA-paid … supplier payment recorded on a trip within 7 days	Nobody has recorded this payment on a trip, or it was recorded with a different amount, currency or date, or as client paid or by card. Ask the advisor to record it with Apply Payment, as OTA paid, by ACH or wire, in the currency sent and for exactly the amount sent. Then import the same file again.
2 recorded payments fit; match the bank line by hand	More than one payment has the same currency and amount within the week, and the vendor names don't settle it. Use Match to trip… on the bank line and pick the right one.

Importing again is always safe. Deals already paired are left alone, and only the new ones are matched.

Rows Corpay funded in another currency, not dollars, are skipped without being listed. These are Corpay converting money back to OTA, not supplier payments.

Matching one by hand

You don't have to import the history to post a Corpay debit. On the bank line, click Match to trip… and pick the payment from All unmatched OTA ACH / wire payments. The picker warns Amount differs from the bank line — the bank amount is what gets booked, and that is expected for a foreign-currency payment. The import saves you this step and records the deal number on the payment.

Messages you might see

Message	What it means
Only .csv files are accepted — export the payment history from Corpay as CSV.	The file isn't a CSV. Export it from Corpay again as CSV.
This doesn't look like a Corpay payment history CSV — missing column(s): …	The file is missing a column the import needs (Date, Deal #, Currency, Amount, Cost Currency or Cost). It may be a different Corpay report, or the Chase file chosen by mistake.
No payments found in the file.	The file has a header but no rows. Check the dates you exported.
Row …: unreadable date … / no deal number / unreadable amount or cost / no currency	That row was skipped. The rest of the file was imported.

Good to know

Advisors don't do anything different. They record the payment in the currency sent, as they already do. The Apply Payment window reminds them to enter exactly what the supplier received.
The bank amount is what's booked. TRES and the ledger get the dollar amount on the bank line, so the exchange rate Corpay charged is already in it.
One deal, one payment. Each Corpay deal is paired with one payment recorded on a trip. A supplier paid in two parts needs two Apply Payment entries, one per deal.