Introducing Terrace Accounts Receivable: Stop profit leakage in your hotel — Read more →
terrace
Credit Card Reconciliation

Hotel Credit Card Reconciliation

Hotel credit card reconciliation software that matches every card settlement, virtual credit card, refund, and chargeback against your PMS folios, merchant batches, and bank deposits.

less manual card matching
90%less manual card matching
of VCCs traced to folio
100%of VCCs traced to folio
faster chargeback response
3xfaster chargeback response
The unified card workflow

One platform for every hotel card reconciliation.

Terrace ingests merchant settlements, OTA virtual credit cards, refunds, and chargebacks, then matches every card payment against folios, deposits, and the GL. Your team only reviews real exceptions instead of running line-by-line spreadsheets.

  • Direct settlement file ingestion from major processors
  • Booking.com, Expedia, and other VCC matching against folios
  • Chargeback evidence assembly and audit trail
Terrace hotel credit card reconciliation dashboard

What is hotel credit card reconciliation?

Hotel credit card reconciliation is the process of matching card payments recorded in the PMS against the merchant processor's settlements, the OTA's virtual credit card amounts, and the actual bank deposits — then resolving any difference caused by refunds, voids, chargebacks, partial authorizations, or timing. Done well, it confirms that every card the front desk swiped (or every VCC an OTA issued) settled, deposited, and posted to the GL correctly.

Hotel virtual credit card reconciliation is a subset of this process. VCCs from Booking.com, Expedia, and other OTAs are issued for a specific amount at booking time but the final folio frequently differs after upgrades, ancillaries, or cancellations. Hospitality credit card reconciliation software like Terrace AI automates both standard card and VCC matching across every property in a portfolio.

What teams check
  • Every folio card payment tied to settlement
  • VCC amounts match folio totals
  • Refunds applied to original tender
  • Chargebacks linked to source folio
  • Net deposit reconciles to batch fees
  • POS card payments tied back to PMS

Why hotel credit card reconciliation is painful for accounting teams

VCC amounts rarely match folio totals

Virtual credit cards from OTAs are issued for a fixed amount that may not equal the final folio after upgrades, ancillaries, or cancellations.

Refunds split between original and new tender

Refunds processed against a different card or tender than the original sale break simple one-to-one matching and require manual research.

Chargebacks reopen prior periods

Chargebacks can arrive 30–120 days after the original charge, reversing posted revenue and requiring evidence to be assembled from the PMS and folio.

Tokenized card data hides the original tender

Settlement files often only show truncated PAN or token IDs, making it hard to tie a deposit back to the actual card used at check-in.

Multiple POS systems use different processors

F&B, spa, and golf may run on separate POS and processors from the front desk, creating multiple card reconciliations per property.

Net deposits hide per-card detail

Processors deposit net of interchange and reserves, so without the batch detail you cannot tell which specific cards funded a deposit.

What data is matched in hotel credit card reconciliation?

Folio card payments
PMS payment posting
  • Folio ID
  • Card token
  • Amount
  • Auth code
Merchant settlement files
FreedomPay, Shift4, Elavon
  • Batch ID
  • Truncated PAN
  • Gross
  • Net
Virtual credit card records
Booking.com VCC, Expedia VCC
  • VCC number
  • Auth amount
  • Charge window
Chargeback notifications
Processor portal
  • Case ID
  • Original auth
  • Reason code
Refund records
PMS and processor
  • Refund amount
  • Original sale
  • Tender
Bank deposit lines
Daily bank statement
  • Posting date
  • Description
  • Net deposit

Common hotel credit card reconciliation exceptions

VCC charged less than folio total

The virtual credit card was authorized for less than the final folio amount due to room upgrades or ancillaries.

VCC unused at checkout

A virtual credit card was issued but the property collected payment on a different tender, leaving the VCC unused.

Refund processed against wrong card

A refund was applied to a different card than the original sale, requiring manual cross-referencing.

Chargeback against settled folio

A chargeback notice arrived for a previously settled folio and reverses recognized revenue.

Settlement amount differs from folio

The processor settled an amount different from the folio total due to a partial auth, void, or adjustment.

Card on file used outside the PMS

An ancillary charge was put on the card on file from a POS outside the PMS, creating a settlement with no folio link.

How hotels manually reconcile credit cards

  1. 1

    Pull daily processor settlement files from each merchant account at the property.

  2. 2

    Export PMS payment posting reports broken down by card type and folio.

  3. 3

    Match each settlement line to a folio payment using card token, amount, and auth code.

  4. 4

    Reconcile virtual credit cards against folio totals, flagging mismatches for review.

  5. 5

    Investigate refunds, voids, and partial authorizations that broke simple matching.

  6. 6

    Research chargeback notices against the underlying folio and assemble dispute evidence.

  7. 7

    Post adjustment entries for interchange, chargebacks, and timing differences.

  8. 8

    Close the period and store the audit trail of matched and resolved settlements.

Automated hotel credit card reconciliation with Terrace AI

Terrace connects to your PMS, processors, OTAs, and bank and matches every card automatically, including virtual credit cards and chargebacks.

Settlement ingest

Processor settlement ingestion

Terrace ingests settlement and batch files from every common hospitality merchant processor automatically.

Mar 14 · Card processors
Processor settlement ingestion
5 sources
CC
FreedomPay
BATCH-44218 · 184 auths
$22,418.00Ingested
CC
Shift4
BATCH-77104 · 91 auths
$11,212.40Ingested
CC
Elavon
BATCH-21088 · 62 auths
$8,440.18Ingested
CC
Adyen
BATCH-99411 · 28 auths
$4,118.00Ingested
CC
Square (Spa)
BATCH-66120 · 14 auths
$842.00Late file
379 auths ingested. Square spa terminal file expected by 05:00 ET.
Total $47,030.58Match queue →

VCC matching

Virtual credit card reconciliation

Each VCC from Booking.com, Expedia, and other OTAs is matched against the underlying folio and flagged when amounts diverge.

Booking.com VCC · BKG-441820
Virtual credit card ↔ folio
Mar 14
VCC charged
$498.00
Folio total
$522.50
VCC ending
•••• 3318
Folio
#18841 · 2 nights
VCC short by $24.50
  • • Resort fee posted post-arrival: +$18.00
  • • Tax on resort fee: +$6.50
Recommended: Charge guest card on file · auth Mar 14

Folio match

Card-to-folio matching

Settlements are matched to folio payments using card token, amount, and auth code, even when truncated PANs are all that's available.

Tokenized match · Mar 14
Card settlement ↔ folio
5 of 184 shown
FolioPANAuthAmountStatus
#18841•••• 4242A88412$612.00Matched
#18852•••• 0019A88418$1,212.40Matched
#18867•••• 8861A88419$842.00Partial auth
#18879•••• 3318A88421$498.00Matched
#18884•••• 7100A88425$2,142.00No PMS folio
3 matched · 2 need reviewView all 184 →

Chargebacks

Chargeback queue with evidence

Chargebacks surface in a dispute queue with the original folio, signature, and auth records attached, ready for response.

Dispute queue · 3 open
Chargebacks with evidence ready
Visa / Mastercard
CB-11842Visa · 4853
$612.00 · Folio #18642 · Reason: Service not provided
Folio attachedAuth logSignature
CB-11851MC · 4837
$148.00 · Folio #18711 · Reason: Duplicate charge · Due Mar 20
CB-11860Amex · A02
$42.00 · Folio #18752 · Reason: Cardholder cancelled
Win rate: 78%Submit response →

Refunds

Refund and void tracking

Terrace traces every refund and void back to its original sale so revenue and tax adjustments are posted to the right period.

Refunds & voids · last 7d
Refund and void tracking
4 found
RF
RF-44128
Auth A87618 · Mar 8 · Visa •••• 4242
-$148.00Traced
RF
RF-44131
Auth A87622 · Mar 9 · MC •••• 0019
-$612.00Traced
RF
RF-44142
Unknown · cash sale? · Visa •••• 8861
-$42.00Tender mismatch
VD
VD-44144
Auth A88119 · Mar 13 · Voided · 8m
-$22.00Voided
RF-44142 refunded $42 to Visa 8861, but the original sale was on Visa 4242 — tender mismatch flagged.
3 traced · 1 needs reviewResolve →

Audit trail

Audit-ready settlement trail

Every matched card, VCC, and chargeback is stored with the folio, batch, and bank line used to resolve it.

Audit trail · A88412
Card lifecycle: auth → settle → deposit
Folio #18841
1
Auth captured · $612.00
Mar 12 14:18 ET · Front desk · Opera
2
Settled · BATCH-44218
Mar 13 00:14 ET · FreedomPay
3
Deposited · $611.18 net
Mar 14 · Chase 6471 · interchange $0.82
4
GL posted · 1010-Cash
Mar 14 · Sage Intacct · JE-22418
4 of 4 steps completeExport →
Get started

Put hotel revenue on autopilot

From OTA statement to GL posting — faster cash, accurate books, and less manual reconciliation.

Frequently asked questions

Hotel credit card reconciliation is the process of matching credit card and virtual credit card payments recorded in the PMS against the merchant processor's settlement files and the bank's deposits, then resolving refunds, chargebacks, and timing differences so revenue and cash tie.