Why your credit card statement rate is the only one that matches your corporate card reconciliation

I spent an hour one Tuesday morning trying to reconcile a corporate Visa statement to an expense report. The numbers were close — within a percent or two of each other — but no line matched exactly. Every receipt had a small phantom difference. The expense report had been built carefully using Mizuho TTM on each transaction date, which is what the company's policy required for the books. The card statement showed completely different yen amounts for the same dollar charges.

After about twenty minutes I worked out where the gap was: the card statement was showing the rate Visa actually applied at settlement, plus the issuer's foreign-transaction markup. The expense report was showing the bank's reference TTM rate on each transaction's calendar date. Same transactions, two completely different reference rates. The difference was the card's markup, plus a small settlement-date timing gap.

This is the thing about credit-card reconciliation that gets glossed over in most expense apps: there is no public source rate that will match your card statement. The only rate that does is the rate the card network and issuer actually used. If you're reconciling a corporate card statement to expense entries that cite ECB or Mizuho rates, you are reconciling two genuinely different numbers and the gap is real.

How card networks set FX rates

Visa and Mastercard publish daily exchange rates that they use to settle foreign-currency transactions. The rate Visa applies on Tuesday October 8 settles transactions presented for clearing that day, regardless of when the actual purchase happened. The "Visa daily rate" is publicly accessible — Visa even has a public lookup tool — and it's typically within fractions of a percent of the interbank mid-market on that date.

Then the issuer adds a markup. This is the part that most cardholders don't see until they look for it. Standard credit cards add 1.6% to 3.5% on top of the network's settlement rate, charged as "foreign transaction fee" or quietly baked into the displayed exchange rate without a separate line. Some cards (the FX-friendly ones — Wise card, Revolut, Sony Bank Wallet, certain travel-focused cards) charge much less or zero markup.

For Mastercard the model is similar with slightly different cadence. For JCB the upstream reference is often a BOJ-related rate plus issuer markup. For American Express the model is different again — Amex uses its own internal rate that bundles network and issuer roles, often resulting in less competitive rates than Visa or Mastercard for the same purchase.

The end result is that the rate on your statement for a US dollar purchase is the network rate at settlement plus the issuer's markup. Both components vary by issuer, by card product, and by transaction date.

The settlement timing problem

This is the second source of confusion. You swipe a card in San Francisco on Monday afternoon. The merchant submits the transaction for clearing on Tuesday morning. The network settles it on Wednesday. The exchange rate that gets applied to the cardholder's statement is the Wednesday rate, not Monday.

For a stable pair this is invisible. For a volatile pair, or one with a big intraday or overnight move, the difference can be visible. A USD/JPY trade on a Fed-day evening can settle two days later at a rate one percent away from the transaction-time spot. If your expense report uses transaction-date Mizuho TTM and your card statement uses Wednesday's settlement rate, the gap is partly the markup and partly the timing offset.

The timing gap is also why "use the rate on the date of the receipt" doesn't quite work for card reconciliation. The receipt has the right date for accounting purposes (that's when the economic event happened) but the wrong rate for matching the statement (that's when the money moved on the card network).

Issuer markup, made concrete

Some illustrative numbers based on what I've seen on personal and corporate statements:

• A US dollar purchase on a standard JCB credit card: network rate plus roughly 1.6% to 2.0% markup, depending on the JCB-issuing bank.
• The same purchase on a standard Visa card from a Japanese megabank: network rate plus around 2.0% to 3.0%.
• The same purchase on a Wise debit card: network rate plus essentially zero markup (Wise charges a separate, transparent conversion fee that shows as its own line).
• The same purchase on a Sony Bank WALLET multi-currency card, pre-loaded with USD: zero conversion fee on the actual purchase because no conversion happened — you spent USD that was already in the wallet.
• The same purchase on a Revolut card on the free plan: network rate plus a small weekend-only surcharge if it happened on Saturday or Sunday, zero on weekdays up to monthly limits.

These ranges aren't promises about specific issuers' current pricing (issuers change terms regularly), but they're the order of magnitude you should expect when looking at a corporate card statement. The most useful exercise for anyone new to corporate card reconciliation is to take one foreign-currency transaction, look up the Visa or Mastercard published settlement rate for that date (their public tools), and compare it to the rate that ended up on the statement. The difference is your card's markup, expressed clearly.

Why ECB, Mizuho, Treasury, HMRC will never match

The public reference rates have no markup, by design. They are reference points published by central banks or government bodies for use in accounting, regulation, and research. They don't reflect the rate at which any individual transaction was actually executed.

The card statement is the opposite: it's a specific bank's record of a specific transaction at the rate that bank actually applied. There is no transformation that converts a reference rate into a transaction rate — the markup, the timing, and the issuer's day-to-day pricing are all unknowable from outside.

If your accounting policy says "translate at Mizuho TTM on the transaction date," and you do that, your expense report numbers will be defensible to an auditor — but they will not match the card statement totals. That's not a bug; the two numbers measure different things. The TTM-translated expense report says "this is what the transaction was worth at the reference rate on that date, for book-translation purposes." The card statement says "this is what the company actually paid in home-currency terms after the bank settled."

The right approach for reconciliation

For corporate card reconciliation, use the credit-card-statement-rate policy in Zenrate (or whatever equivalent your accounting software offers). Enter the rate from the statement directly — usually you can derive it by dividing the home-currency settled amount on the statement by the foreign-currency amount on the receipt. Some banks also provide this as an explicit column on CSV exports.

This is the only rate-source policy where the rate doesn't come from a public source, and that's intentional. The rate-source citation in Zenrate's receipt record reads `credit_card`, making clear that the rate is user-entered from the cardholder's statement, not fetched. An auditor reviewing the books later can verify the entered rate against the statement itself — the audit trail points to the bank's statement as the source document.

The receipt record also stores the merchant-currency amount and date (from the original receipt) alongside the home-currency amount and settlement date (from the statement). Both pairs of data are necessary: the receipt establishes what was bought, the statement establishes what was paid. Reconciliation works because both are recorded.

When not to use this policy

For any non-card transaction, the credit-card-statement-rate policy doesn't apply. Wire transfers should use whatever rate the bank quoted on the wire confirmation (often available as a separate field) or the company's standard reference-rate policy if no quote is captured. Cash exchanges at a money changer should use the rate the counter actually applied — this is effectively the same kind of "transaction-rate" record as a card swipe but with the cash receipt as the source document. Direct debits and SEPA transfers use the originating bank's quoted rate at the moment of execution.

The pattern is: if the transaction has its own intrinsic rate (because some bank or counter executed an actual conversion), use that rate and cite the source document. If the transaction is purely a translation of one currency-denominated number into the home currency for accounting purposes (a foreign-currency invoice being booked at the reference rate), use the company's reference-rate policy.

A note on Wise, Revolut, and multi-currency wallets

Wise and Revolut occupy a middle ground. When you spend from a Wise USD balance with a Wise card on a USD purchase, no conversion happens — your USD balance went down by the USD amount and your books should reflect a USD-denominated expense, with the home-currency translation done at the reference-rate policy because the moment of conversion (when USD entered the Wise account from your home-currency balance) was a separate transaction with its own rate.

When you spend from a Wise JPY balance with a Wise card on a USD purchase, Wise does the conversion at the moment of payment and charges its transparent conversion fee. That conversion has its own rate — Wise quotes it on the transaction history — and it's the rate you should record. It functions like the credit-card statement rate: it's the rate that actually moved money, and it's the right number to put in the books for that specific transaction. The audit trail should cite Wise's transaction record as the source.

Revolut behaves similarly. The free-plan weekend surcharge is the main wrinkle — a Saturday FX trade on Revolut free is at a worse rate than the same trade on a weekday, and reconciliation has to use the weekend rate Revolut actually quoted, not the weekday reference.

Why this matters for Zenrate

Most "missing money" in expense reconciliation is just the markup you didn't see. Once you can see it — by recording the card-statement rate alongside the reference rate — you can decide what to do about it: switch to lower-markup cards, accept the cost, or budget for it explicitly as an FX line. Zenrate's credit-card-statement-rate policy exists specifically to make this visible. The receipt record shows both the reference rate (for accounting translation) and the statement rate (for reconciliation), and the difference between them is the markup, exposed in numbers rather than hidden in totals.

— Koryu, Endots LLC