Virtual Card Reconciliation: Why Your Expedia Payments Don't Match Your Bank (And How to Catch It)

If you run Expedia Collect (prepaid bookings where Expedia pays you via a virtual card), you've almost certainly lost money to this and not known. The pattern is boring: a booking arrives, your PMS shows the charge was processed, your accounts receivable report shows it cleared — but the cash never shows up in your operating account.

The root cause is almost always a timing mismatch between the virtual card's activation window and when your front desk ran the charge.

01What an Expedia virtual card actually is

When a guest books an Expedia Collect reservation, Expedia generates a single-use virtual card — a 16-digit card number that exists only for that one reservation. The card has an activation date (the scheduled check-in) and an expiration date (the scheduled check-out, or occasionally check-out plus one day).

Outside that window, the card doesn't work. Not 'charges less'. Not 'requires approval'. The transaction simply declines with a generic payment-gateway error that your PMS often classifies as a temporary processor issue.

02The four scenarios where you lose money

1. Late check-in across midnight

Guest books April 15–17. Arrives at 01:12 on April 16 because their flight was delayed. Front desk runs the pre-auth at 01:15. The card's activation date is April 15 — which technically ended 1 hour and 15 minutes ago. The authorization fails. Typical loss per incident on a $160 ADR: one night's room revenue plus tax, ~$180.

2. Early departure with re-charging

Guest booked 3 nights, leaves after 1. Your night auditor voids the remaining 2 nights and re-charges for the single stayed night. The re-charge attempt runs after the guest has checked out — after the card's expiration date. The re-charge fails. The PMS shows 1 night of revenue; the bank received nothing.

3. Incidentals charged next-day

Guest checks out on April 20 leaving a minibar tab of $38. Your night auditor batches incidentals on April 21 morning. The virtual card expired at midnight. The $38 charge fails.

4. Rate change with new authorization

Guest upgrades at check-in; your PMS generates a new authorization for the difference. The virtual card covers the original amount at the original rate — not the upgraded rate, and not a new authorization request. The original auth stays; the incremental auth fails.

03The per-scenario dollar loss, at a 93-room indie

04The reconciliation pattern that catches it

There are two places a virtual-card gap shows up: your PMS and your merchant-processor statement. Both report 'transaction successful' from their side because each only sees half of the picture. The missing money only surfaces when you reconcile them against each other.

1. 1Pull the last 30 days of Expedia Collect transactions from your PMS. Filter to 'captured' status only.
2. 2Pull the same date range from your payment processor's transaction log. Filter to successful captures.
3. 3Inner-join on last 4 digits of card number + amount + date. Any PMS row without a matching processor row is a silent failure.
4. 4For each silent failure, re-authorize against the guest's card-on-file if available. If not, open an Expedia Partner Central dispute with subject 'Virtual card capture failed — request replacement authorization' and reference the itinerary ID.

05When to dispute vs when to eat the loss

Expedia's policy is that the hotel is responsible for charging within the virtual card's window. They are not contractually obligated to issue a replacement authorization. In practice, their Partner Care team does issue one about 40% of the time, if you can show documented reason (flight delay, cooperative guest, late-night check-in beyond your control).

The rule of thumb: any single incident over $100 is worth filing. Under $50, file it in a monthly batch or skip — the operational cost of chasing $40 failures exceeds the $40.