Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Virtual credit card bookings from Booking.com, Agoda, and Expedia create a three-date settlement chain — booking date when the VCC is issued, charge date when the hotel swipes it at check-in, and bank credit date when the acquiring bank settles — with no OTA wire transfer to anchor the reconciliation, leaving hotels unable to confirm which bookings have actually settled.
Run a three-way match between OTA extranet booking export (booking ID, VCC reference, face value, commission), acquiring bank settlement file (charge date, amount, batch reference, card mask), and PMS folio (reservation, nights, taxes). Match on OTA booking ID to PMS reservation, then on PMS reservation to acquiring bank charge through card mask and amount. Flag VCCs not yet charged, charges without a matched VCC, and amount variances.
OTA extranet adapters for Booking.com, Agoda, Expedia VCC exports; acquiring bank settlement file ingest (HDFC, Axis, ICICI merchant statements); PMS connector for reservation and folio data; rules for activation-window timing and charge-eligibility dates; variance handlers for partial charges, late charges, and reissued VCCs.
A daily VCC reconciliation showing each booking matched to its PMS reservation and acquiring bank charge, an exception list for unactivated or uncharged VCCs, a commission-leakage view comparing VCC face value to PMS folio after commission, and a ledger entry stream booking VCC revenue net of MDR and commission.
A 220-key hotel in Goa runs 38% of its room nights through Booking.com and Agoda. Each booking arrives with a VCC that activates a few days before check-in. The PMS shows the reservation, the acquiring bank shows the charge, and finance has to prove every settled rupee maps to a real booked night. This article is for hotel finance and revenue teams running OTA inventory through VCC payment models in India.
What Hotel OTA Virtual Card Reconciliation Involves
OTA virtual card reconciliation is the process of matching each OTA booking to its VCC charge at the acquiring bank, confirming the face value charged corresponds to the contracted net rate after commission, and recognising the room revenue on the correct stay nights. Unlike a net-settlement OTA where the operator wires money on a schedule, the VCC model puts the hotel in charge of triggering the cash flow at check-in.
The reconciliation problem is timing. The booking date sits in one period, the charge date in another, and the bank credit date in a third. A February booking for an April stay sees the VCC issued in February, charged on the 14 April check-in, and credited on 16 April through the acquiring bank’s standard cycle. The PMS books revenue on the night of stay; the bank credit lands two days later; the OTA’s extranet shows the booking on day zero.
How VCC Settlement Differs from Net Wire Settlement
VCC Issuance at Booking
When a guest books on Booking.com or Agoda, the OTA issues a single-use Mastercard or Visa number to the hotel through the extranet. The face value is the net payable to the hotel — that is, the gross room rate less the OTA commission already deducted. The activation window is typically tied to a few days before the check-in date and runs until shortly after checkout.
Charge at Check-In
The hotel charges the VCC at check-in, usually as a pre-authorisation followed by a capture, or sometimes as a direct sale for the full stay value. The charge processes through the hotel’s normal card terminal or PG and lands in the acquiring bank’s settlement queue. The card mask and approval code are written back to the PMS folio.
Bank Credit and MDR
The acquiring bank settles the charge in the standard cycle — T+1 to T+2 for most Indian acquirers — net of MDR. The MDR on a commercial card is generally higher than on a domestic consumer card, and finance must book it as an expense with 18% ITC against the acquiring bank’s tax invoice.
VCC Reconciliation Three-Way Match
| Source | Key Fields | Role in Match |
|---|---|---|
| OTA extranet (Booking.com, Agoda, Expedia) | Booking ID, VCC reference, face value, commission | Anchors the booked liability and net payable |
| PMS (Opera, IDS, eZee) | Reservation number, room nights, folio total | Anchors the consumed nights and revenue recognition |
| Acquiring bank settlement file | Charge date, amount, card mask, batch reference | Anchors the cash credit |
Settlement Timing Complications
The booking-date to charge-date gap creates a deferred-revenue exposure: a booking made in March 2026 for a stay in May 2026 is a confirmed liability with no cash and no consumption. If the VCC activation window opens late or the OTA modifies the booking, the charge can fail at check-in and the hotel discovers it only when the bank settlement arrives short.
The charge-date to credit-date gap is shorter — usually a day or two — but cuts across month-end. A 31 March check-in charge that credits on 2 April must be accrued at month-end against the acquiring bank receivable to keep revenue and cash in sync.
The cardholder dispute window is usually 60 to 120 days from the charge date depending on the card scheme. Disputes on consumed bookings are rare because the VCC was issued by the OTA, not by the guest, and the OTA bears the chargeback risk in most contracts. But cancellations and partial stays still flow through VCC reversals, and those reversals can hit the acquiring bank file weeks after the original charge.
Reconciliation Against the PMS Folio
The match key chain runs OTA booking ID to PMS reservation to acquiring bank charge. Each PMS reservation must carry the OTA booking ID written by the channel manager. Each acquiring bank charge must carry a card mask that ties to the VCC stored on the PMS folio. The reconciliation engine walks bookings, finds the matching reservation and folio, then locates the bank charge by amount and approximate date, and clears the booking. Unmatched bookings sit in the exception queue: VCC not yet charged, charge declined and not reissued, amount variance from a folio adjustment, or duplicate charge from a re-swipe.
Hotels using payment gateway reconciliation tooling for their direct-booking PG flows extend the same engine to OTA VCC charges, since the acquiring bank settlement file is identical in shape. Reconciliation software India ingests Opera, IDS, and eZee exports alongside acquiring bank statements and OTA extranet pulls, and produces a daily VCC reconciliation with exceptions surfaced by age and value. The FHRAI publishes operator guidance on OTA contracting models that hotel finance teams can reference for commission and payment terms.
For the broader hotel industry reconciliation surface, see the Hotels & Hospitality industry guide.
The following questions address the VCC, charge timing, and PMS-folio matching issues hotel finance teams encounter most frequently.