The Ghost Card That Kept Charging
Vertex Media issues 400 virtual cards for hotel and air. A quarterly audit finds 38 disputed hotel transactions totaling $47,000, many for no-show fees on bookings canceled more than 48 hours before arrival. Merchant descriptors are truncated, so the reconciliation team cannot match charges to bookings. Nine percent of hotel bookings are canceled within 48 hours of arrival, but cancellation is not automatically pushed to the card. VAT reclaim is missing on 22% of eligible EU hotel invoices because invoices are requested only at checkout and often never collected. The TMC's reconciliation file arrives 11 days after month-end. Finance wants to reduce write-offs and improve reclaim, and has asked whether the virtual card program should be narrowed or fixed.
1. Diagnose the control gaps. Which gaps are causing the write-offs, and which are causing the lost VAT reclaim?
Read the worked answer
Write-off drivers
- No cancellation-to-card link: a canceled booking does not close or adjust the virtual card, so a no-show charge can still authorize.
- Poor descriptor data: truncated merchant names prevent matching a charge to a booking, so disputes are raised late or not at all.
- Late reconciliation: the TMC file arrives 11 days after month-end, eating into dispute windows and making root-cause analysis retrospective.
- Card design: if cards are not single-use or date-bounded, they remain open to charges after the trip.
VAT reclaim drivers
- Invoice capture at checkout: invoices requested only at departure are often missed, and without a valid VAT invoice reclaim is impossible.
- Booking data not carried to invoice: even when an invoice exists, VAT fields may not be matched to the transaction.
- Ownership: no one owns reclaim at the transaction level, so the 22% gap persists.
Reasoning: the write-offs are an authorization-control problem, while the VAT loss is a document-capture problem. They need separate fixes, though both depend on linking the card to the booking record.
2. What immediate recovery actions should Vertex take in the next 30 days?
Read the worked answer
Actions
- Pull all 38 disputed transactions and match them manually to booking records using traveler name, dates, and property; dispute within the card network's deadline where evidence supports it.
- Contact the highest-value merchants directly for refunds or credits; prioritize repeat offenders.
- Suspend or reissue cards associated with repeated post-cancellation charges.
- Request missing EU invoices for the 22% gap while properties still retain records; set a 30-day deadline.
- Freeze new card issuance for any booking type not covered by a cancellation feed until the process is fixed.
Reasoning: recovery is time-bound. Dispute windows and hotel record retention both expire, so speed matters more than perfect root-cause analysis. Manual matching is expensive but justified against $47,000 in write-offs and the VAT exposure. Suspending repeat-offender cards protects the balance sheet while the redesign proceeds. Do not narrow the program yet; narrowing would sacrifice the control benefits of virtual cards without fixing the underlying link.
3. Redesign the virtual card process. What changes would prevent recurrence, and how would you measure success?
Read the worked answer
Redesign
- Issue single-use cards tied to a specific booking, with amount and date range; auto-close at checkout or cancellation.
- Integrate the TMC booking feed so cancellation triggers a card closure or authorization limit change within minutes.
- Require enriched merchant descriptors from the card issuer, or use a mapping table.
- Request the VAT invoice at booking and at checkout automatically, and store it against the transaction.
- Move reconciliation to a 3-day cycle with exception reporting.
Measures
- Post-cancellation charges as a percentage of cancellations (target near zero).
- Disputed transactions per 1,000 bookings.
- VAT reclaim rate on eligible EU hotel nights (target ≥ 95%).
- Reconciliation completed within 3 business days.
Reasoning: the program should be fixed, not narrowed. Virtual cards give control that ghost cards cannot, but only when the card lifecycle is linked to the booking lifecycle. Each design change addresses a diagnosed gap, and the metrics test whether the link actually holds.