UPI and LankaQR for Hotels in Sri Lanka: ERP Payment Reconciliation

UPI-linked and LankaQR acceptance creates value for a Sri Lankan hotel only when the payment reaches the correct guest folio, settlement batch, and ERP account. A successful phone screen helps the guest; a matched transaction reference helps the hotel close its books.

This is a hotel reconciliation guide, not a republication of the general retailer LankaQR playbook. For collections tooling, review Capricon Pay; for booking operations, see Capricon Voyage; for the accounting backbone, use the ERP software Sri Lanka hub.

The hotel-specific reconciliation chain

1. Guest or agent receives a payment request tied to a booking or folio reference.
2. The supported UPI/QR flow returns a merchant transaction reference.
3. Front desk records the correct tender against the correct folio—without treating a screenshot as final settlement.
4. The acquirer or payment report groups transactions into settlement batches.
5. Finance matches gross receipts, fees, reversals, and net bank credits.
6. ERP posts the clearing and bank entries, leaving only genuine exceptions unmatched.

Data fields hotels should capture

• Booking reference, guest folio number, property, and cashier or channel.
• Tender type such as supported tourist QR, LankaQR, card, cash, or transfer.
• Merchant transaction reference and date-time.
• Transaction currency, billed amount, and any reported conversion context.
• Settlement batch, gross amount, fee, reversal state, and net bank amount.

Do not confuse acceptance with settlement

Scheme participation, limits, supported apps, currencies, and settlement timing can change by provider. Confirm the current setup with the acquiring bank or payment provider. Operationally, keep the guest acknowledgement, provider transaction, settlement report, and bank credit as separate states.

Daily exception checklist

• Paid QR transaction with no booking or folio reference.
• Folio marked paid but provider transaction is missing or failed.
• Duplicate amount and reference at the same property.
• Reversal or refund not reflected in the guest ledger.
• Settlement total differs from its transaction detail.
• Net bank credit differs from gross less documented fees.
• Payment recorded at the wrong hotel, entity, or currency.

Connect reservations, Pay, and ERP

Capricon Voyage can own the booking reference, Capricon Pay can centralise collection visibility, and the ERP hub explains the finance system of record. The implementation goal is a controlled reference chain—not three products holding unrelated payment notes.

Pilot before multi-property rollout

Pilot one property and one QR acceptance route for two complete settlement cycles. Measure unmatched transactions, average matching time, duplicate tender corrections, and refund handling. Then standardise tender codes and exception ownership before adding properties. Contact Capricon to scope the reconciliation flow.