Blog›Pricing

Payment Links and Manual Bank Transfers in a Hotel PMS Workflow

Payment links and manual bank transfers both show up in a hotel PMS workflow, and keeping them tracked and reconciled needs a slightly different routine for each.

The Prime Host Partners team19 Nov 2026 · 7 min read

A guest paying through a payment link you sent, and a guest paying by direct bank transfer, both end up as money your property needs to match against a specific reservation — but they reach your records differently, and treating them with the same workflow is where small properties lose track of a payment, or chase one that already arrived.

Full guide on this topic
Why these two payment paths behave differently

A payment link, generated through your gateway or PMS and sent to the guest directly, typically comes back with a confirmation the moment the guest pays — the system that generated the link usually knows the payment happened almost immediately. A bank transfer has no such built-in confirmation: the guest initiates it from their own bank, and your property finds out it arrived only when someone checks the bank statement or account, which can be hours or days after the guest believes they've paid.

Treating both as equally “pending until confirmed” causes different problems — a payment link left unconfirmed when it's actually already landed just needs someone to check the system, while a bank transfer marked as received before it's actually verified against the statement can lead to releasing a room or confirming a booking for money that hasn't arrived yet.

Where each one tends to go wrong

Payment links can go stale if the guest doesn't act on them right away — the link itself may expire, or the guest may lose the message, and the reservation sits unconfirmed with no payment while the dates get closer. Bank transfers are harder to match automatically, since the amount, the sender's name and the reservation reference don't always line up cleanly with what your PMS expects, especially if a guest transfers from an account under a different name than the booking. Both paths also create a timing gap between “the guest believes they've paid” and “your property has actually confirmed the money arrived,” and that gap is exactly where a booking can be wrongly treated as guaranteed or wrongly treated as unpaid.

Where payment links and transfers commonly break down
1An expired or ignored payment linkThe guest never completes it, and the reservation sits unconfirmed without anyone following up.
2A bank transfer that doesn't match cleanlyThe sender's name or the reference doesn't line up with the reservation, making it hard to confirm which booking it belongs to.
3The confirmation timing gapThe guest believes payment is done before your property has actually verified it, especially with transfers.
How to track both properly

For payment links, set a short follow-up window — if the guest hasn't paid within a defined time, flag the reservation rather than letting it sit silently unconfirmed. For bank transfers, check your account statement directly rather than taking the guest's word that the transfer was sent, and match it against the reservation using the amount, expected date and any reference the guest was asked to include. Record the confirmation in the PMS the moment either payment type is actually verified, not when the guest says they paid, so the reservation's status reflects reality rather than an expectation.

A guest saying “I paid” and your bank statement actually showing it are two different facts, and only one of them should change a reservation's status.
Keeping both payment paths under control
Set a follow-up window for unconfirmed payment links instead of letting them sit indefinitely.
Always ask bank transfer guests to include a clear reference, and check for it when matching the statement.
Verify the bank statement directly before marking a transfer-based reservation as paid.
Record payment confirmation in the PMS at the moment it's actually verified, not when the guest claims it.
Review unconfirmed reservations regularly as the stay date approaches, regardless of which payment method was used.
How Prime Host stops this from happening again

Bank-level reconciliation matches payout batches and expected payment timing against your reservations, which helps close the gap between a payment being sent and your property confirming it actually arrived. Activity history keeps a record of when a reservation's payment status actually changed and who confirmed it, so if a guest and your records disagree later about when payment was verified, there's a clear trail rather than a memory to rely on. The public demo at try.primehostpartners.com is open to try without signing up.

Frequently asked
How long should I wait before following up on an unpaid payment link?
Set a specific window appropriate to how close the stay date is, and flag the reservation if the guest hasn't completed payment by then, rather than letting it sit unconfirmed indefinitely.
How do I match a bank transfer to the right reservation?
Ask guests to include a clear reference when transferring, and verify the amount, expected date and reference against your actual bank statement before confirming the booking as paid.
Should I confirm a reservation as paid based on the guest telling me they transferred?
No — confirm it once the transfer actually shows in your bank statement, since there's no automatic notification the way there often is with a payment link.
Want to see all of this working for real?
Walk through the actual system in read-only mode. Nothing to fill in.

Read next

© 2026 Prime Host Partners
Privacy PolicyTerms of Service