Hotel POS Systems: Connecting Front Desk, Dining and the PMS
See how a hotel POS system posts room charges to the right folio, keeps tips in balance and stays inside Visa's lodging authorization rules.

Photo: Pixabay
On this page 7 sections
- Why a Hotel POS System Has to Talk to the PMS
- How a Room Charge Travels From the Outlet to the Folio
- Room Charges Count Against the Check-In Authorization
- A Two-Night Folio Run Against the 15% Rule
- Setting up Payments in Each Hotel Outlet
- Booking Engine and Phone Payments Need Their Own Controls
- What to Ask Your POS and PMS Vendors Before You Buy
Key takeaways
- Every outlet room charge uses up the card authorization taken at check-in, but the outlet never sees that authorization. Your PMS has to track it.
- Under Visa's lodging rules, a folio that ends more than 15% above the total authorized needs an incremental authorization. If you leave a hold padded and unused, you have to reverse it.
- Visa says the check-in estimate can't include a cushion for damage, theft, insurance or tips.
- Tips added after a check posts to a room are a frequent cause of mismatches between POS and PMS reports. Test how your interface handles them before go-live.
A hotel POS system earns its keep when it shares data with your property management system (PMS). With that link, a server posts a dinner check straight to the guest's room, and the night auditor ties each outlet's sales to the PMS without retyping a ticket. Without it, someone walks charge slips to the front desk and keys them in by hand. That handoff is where charges land on the wrong room and tips go missing.
The folio is the guest's running bill inside the PMS. It holds room nights and lodging taxes along with anything posted from the restaurant, bar, spa or shop. The job is to get every charge onto the right folio, make sure the card authorized at check-in still covers it, and get paid.
Why a Hotel POS System Has to Talk to the PMS
A full-service property runs several businesses under one roof. The restaurant tracks covers and tips through two meal rushes a day. The bar keeps tabs open for hours, some for in-house guests and some for locals. A spa books appointments and sells retail product on the side, and the gift shop scans barcodes like any small store. Each outlet often runs its own point-of-sale software, but the guest expects one bill at checkout.
The PMS interface joins them. A working integration handles four jobs:
- Guest lookup. Before accepting a room charge, the POS sees who is in house by room number and name.
- Posting. Each charge moves to the correct folio, split into revenue categories (food, beverage, tax, gratuity) rather than one lump sum.
- Restrictions. The PMS can block posting for guests who shouldn't run up charges, such as a cash-paying guest with no card on file.
- Reporting. Outlet totals in the POS match outlet totals in the PMS, so the night audit balances.
Payments use the same connections. The desk takes cards in person at check-in and keyed over the phone for reservations, and the booking engine collects them online. Tokenizing a card replaces the number with a reference value that's useless to a thief. When the card from booking or check-in is tokenized and stored with the reservation, the desk can settle the folio at checkout without anyone writing down a card number. Keeping raw card numbers out of PMS notes fields also helps limit your PCI DSS scope.
How a Room Charge Travels From the Outlet to the Folio
A charge-to-room transaction usually runs like this:
- The server closes the check and chooses "room charge" as the tender.
- The POS asks the PMS for in-house guests in that room and shows the registered name.
- Staff confirm the name with the guest and collect a signature, on paper or on screen, per your policy.
- The PMS checks whether the folio allows posting. If the guest is flagged no-post, staff should see a warning before the guest walks away.
- Once cleared, the charge posts with its revenue breakdown, and the POS records the PMS confirmation.
Outlet managers often get this part wrong: a room charge is not a card transaction at the outlet. No card is run in the restaurant. Payment comes later, when the folio settles at checkout against the card authorized at check-in. So the restaurant's card batch will never include room-charged checks, and it shouldn't. Reconciliation has two halves. Outlet card sales tie to the processor's deposits, and outlet room-charge totals tie to the PMS posting report.
Guests flagged no-post need a clear fallback at the outlet: take a card or cash on the spot. The desk should decide who can charge to the room at check-in, so the bartender isn't making that call at 11 p.m.
Tips Entered After Posting Are a Frequent Cause of Mismatches
Gratuities are a frequent source of POS-to-PMS gaps. Say the POS posts a bar check to the folio when it closes, and the bartender adds the tip after the guest has left. The bar's report includes the tip, but the folio doesn't. Unless the interface sends a follow-up adjustment, the hotel never bills the guest for that tip but still owes it to the bartender.
Interfaces handle this in different ways. Some hold the posting until the tip is final. Others post the base amount and send an adjustment afterward, and a few require the tip before the check can post at all. Ask which method yours uses, then test it with a real tab before go-live.
Room Charges Count Against the Check-In Authorization
This rule connects the outlets to the card the front desk authorized. Visa lets lodging merchants send an estimated authorization at check-in because the final bill isn't known yet. Visa's best-practices guide for lodging, car rental and cruise line authorizations says the estimate should be the amount the guest is expected to spend during the stay, plus taxes. Every dinner and spa treatment signed to the room uses up that same estimate, even though the outlet never sees it.
Three Visa network rules follow, and each changes how your desk and PMS should behave:
- The 15% tolerance. Under Visa's lodging guide, you need an incremental authorization at checkout if the final amount is more than 15% higher than the total already authorized. If the folio is within that 15%, it can settle against the existing authorization.
- Incrementals add to the original. An incremental authorization doesn't replace the original; the two are linked and added together. Visa's guidance expanding estimated and incremental authorizations to more merchant types adds a catch. Once a merchant uses an incremental authorization, the 15% tolerance no longer applies, and the merchant must cover the final amount with another incremental or a separate authorization. Confirm with your processor how this applies to your lodging account.
- Unused amounts get released. The lodging guide calls for reversing the difference within 24 hours of checkout when the final amount is more than 15% below the total authorized. Visa's later guidance is stricter: it says merchants must process a partial reversal whenever the estimate exceeds the final amount. Releasing the unused hold at every checkout is the safer habit.
Many desks get one rule wrong: they pad the check-in hold to cover possible damage. Visa's dispute management guidelines for merchants set three conditions. The estimate must be realistic, and the guest must be told it is an estimate that may change. It also can't include extra amounts for potential damage, theft, insurance or tips. Damage is handled separately, as covered in charging guests for damage and smoking after checkout. Visa also charges a Misuse of Authorization System Fee, and its lodging guide lists the common hotel mistakes that trigger it.
Mastercard has its own preauthorization rules for lodging, and the details differ from Visa's. Confirm current terms for each network with your processor. For sizing the incidental portion of the hold, see our guide to how much to authorize and when to release hotel holds.
A Two-Night Folio Run Against the 15% Rule
The numbers below are illustrative. They are not prices or rates from any network or processor.
Assumptions:
- Two-night stay paid with a Visa card.
- Room plus lodging tax totals $360. Your actual tax depends on your state and city.
- Based on the property's history, the desk expects about $100 in incidental spending. It sends an estimated authorization of $460 and tells the guest.
- No incremental authorizations are sent during the stay.
- Outlet amounts include sales tax and tip.
| Folio line | Amount |
|---|---|
| Room and lodging tax | $360 |
| Dinner with gratuity, posted from the restaurant POS | $86 |
| Bar tab with tip, posted from the bar POS | $37 |
| Folio total at checkout | $483 |
The 15% ceiling on a $460 authorization is $529 ($460 × 1.15). A $483 folio is under that ceiling, so checkout settles against the existing authorization.
Now add a $70 spa treatment signed to the room. The folio becomes $553, which is $24 over the ceiling. Under Visa's lodging rule, the desk needs an incremental authorization for the $93 above the original $460. If the guest's card declines it, you want to know while the guest is still at the desk. Better PMS platforms handle this as outlet charges arrive: they compare the folio balance to the authorized total and either prompt staff or request the incremental automatically.
Now take the opposite case. The guest eats elsewhere and the folio closes at $360. That is below $391, the point 15% under $460, so the $100 difference should be reversed within 24 hours of checkout. On a debit card, that $100 is the guest's actual cash. That's why your debit card hold policies at check-in should be written down.
Last is the tip drift case. Suppose the bar posted the tab at $31 before the $6 tip was entered, and no adjustment followed. The bar's POS shows $37 in room charges, while the PMS shows $31. A night auditor comparing the two reports catches the gap while the guest is still in house. If it's found after departure, the hotel has to decide whether to bill a guest who has gone home. For the monthly version of this check, see matching card deposits to sales every month.
Setting up Payments in Each Hotel Outlet
Each outlet takes money differently, and its setup should match.
Restaurants need tip adjustment, split checks and closeouts fast enough for the breakfast and dinner rush. Handhelds let servers run the card at the table instead of carrying it away. Our piece on pay-at-the-table handhelds explains why that helps, and MannyPay's handheld terminals page lists current options.
Bars run open tabs for walk-in customers who aren't staying with you. The bar authorizes a card when the tab opens and captures the final amount, tip included, when it closes. Our explainer on authorize vs. capture timing walks through it. In-house guests can sign to the room.
Spas usually book through their own appointment software. Ask whether the spa system posts to the PMS directly or only through the main POS. If the spa can't post to the room, guests have to pay twice: once at the spa and again at the front desk.
Gift shops work like small retail stores, with barcode scanning, inventory counts, quick card sales and the occasional small room charge.
Giving each outlet its own merchant ID makes deposits map cleanly to outlet sales. Your processor assigns each account a merchant category code during underwriting based on what that business actually sells. Set each outlet up as what it is. A restaurant should never run sales under the lodging account, and lodging sales shouldn't run under the restaurant's. MannyPay's POS systems and Clover POS integration pages show hardware and software for outlet use.
Booking Engine and Phone Payments Need Their Own Controls
Cards collected through a booking engine or over the phone are card-not-present transactions. They carry more fraud and chargeback exposure than a card tapped at the desk, so put the controls where the card is first collected:
- Authenticate at booking. Use 3-D Secure authentication where your booking engine supports it, especially on prepaid rates. Prepaid stays follow their own network rules, covered in Visa and Mastercard rules for prepaid stays.
- Pass a token, not a card number. The booking engine should hand the PMS a token, never a card number in an email or reservation note. Read how to store a card on file safely before you set this up.
- Check the card at arrival. If the name on the booking doesn't match the guest who arrives, treat it as a fraud signal. Our article on spotting bad bookings before arrival lists other warning signs.
- Charge OTA virtual cards on their terms. Online travel agencies often pay with single-use virtual cards that limit when you can charge them and for how much. See how to charge OTA virtual cards from Expedia and Booking.com.
Phone reservations keyed at the desk belong in a virtual terminal or the PMS's integrated payment screen, never on a paper pad.
What to Ask Your POS and PMS Vendors Before You Buy
Put these questions to the POS vendor and your PMS provider together, in writing:
- Does a working interface exist between this POS and our PMS version today, or is it only planned?
- Will posting split charges into revenue categories, or send one lump sum?
- How are tips added after posting handled?
- Can the PMS block no-post guests, and does the POS show that flag to staff?
- Does the PMS compare folio balances to the authorized amount? Does it send incremental authorizations and partial reversals with the correct network indicators?
- What happens when the interface goes down, and how are offline charges posted afterward?
- How are voids and refunds handled once a check has posted to a folio?
- Who supports the interface when it breaks, and are there setup or monthly interface fees?
- Are payment tokens tied to one processor, and do stored cards move with us if we switch?
The last question is easy to skip and expensive to discover late. Choosing a payment processor that integrates with your hotel PMS covers it in detail.
Start with last week's night audit. Put each outlet's room-charge report next to the PMS posting report. Then pull five checkouts and compare each final folio to its authorized total. Look for any outlet that doesn't match, and any folio that settled more than 15% above its authorization with no incremental. Either one tells you where to start fixing. When you're ready to review hardware or processing for your property, see MannyPay's hotel payment solutions or request a free quote. A MannyPay specialist responds within one business day.
Sources
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


