Certified RDP Spa Interface
Resort Data Processing Spa Integration
Look up an in-house guest, post the spa charge to the room folio, apply a credit, and close night audit in RDPWin. One certified interface, supported by the same team that supports Paired Plus.
WHY OPERATORS CHOOSE PAIRED PLUS
4 certified tools in the Resort Data Processing spa integration
Room Charges
Post a treatment, add-on, or retail sale to the guest folio in RDPWin. The spa ticket and the room charge stay in the same transaction.
Guest Lookup
Find an in-house guest by name, reservation number, or room before the service is closed. The front desk does not have to read the folio back.
Room Credits
Reverse or adjust a spa charge on the same folio when a service is voided or comped. Finance does not need a side spreadsheet..
Night Audit
Spa revenue is already on the RDP folio when the night audit runs. Credits, voids, and departmental codes close with the rest of the property.
Trusted by Leading Hotels & Resorts
Resort Data Processing spa integration at Couples Resorts
Couples Resorts has run Paired Plus with Resort Data Processing for 15 years. Spa staff look up the in-house guest, post the charge to the room folio, and night audit closes in RDPWin without a second payment or a call to the front desk.
- In-house guest lookup by name, reservation, or room
- Spa treatments and retail posted to the RDP folio
- Credits and voids on the same room charge
- Night audit closed without a spa spreadsheet
- Supported by the Paired Plus team, not a handoff to RDP
Paired Plus support, California and Oregon
Resort Data Processing spa integration support
Room-charge and night-audit questions stay with Paired Plus. The support team is in California and Oregon, knows the RDPWin folio posting, and does not send you to Resort Data Processing for a spa ticket that failed to post. Button labels can be renamed in the software for the wording your desk uses.
Resort Data Processing spa integration, in use for 15 years
Whether it be a question or the rare hiccup we run into, my friends at Paired Plus are always quick to get us answers. We've been clients for 15 years now and wouldn't dream of working with anyone else. Their exceptional service and reliability keep us coming back, ensuring our business runs smoothly every time!
Resort Data Processing spa integration FAQ
These are the questions resort IT and spa managers ask before connecting Paired Plus to RDPWin: what posts to the folio, how a guest is found, and who supports a charge that does not post.
Paired Plus connects the spa desk to the hotel system so an in-house guest can be charged without a second card. The Resort Data Processing spa integration sends the closed ticket to the RDPWin folio: a treatment, an add-on, or a retail sale, using the departmental code the property already uses. A void or a comp returns as a credit on that same folio. Staff do not retype the sale into the property management system, and the front desk does not have to read the room number back over the phone. If a charge does not post, the Paired Plus team in California and Oregon works it with the spa instead of sending the ticket to another vendor.
Before a ticket is closed, the desk searches the in-house list and confirms the person is still checked in. The RDP spa integration matches on name, reservation number, or room, then shows the folio the charge will hit. That check matters when two guests share a surname, a group block has several rooms, or the guest has already checked out. A match stops the sale from posting to the wrong room. The front desk does not have to stay on the phone while the therapist is finishing the service. Lookup is the first step of the charge, not a separate report the accounting team runs the next morning.
The hotel system keeps the reservation, the room, and the folio. Paired Plus keeps the book. Resort Data Processing spa software is the spa side of that split: the appointment book, the provider schedule, retail, packages, and the ticket that becomes the room charge. A resort can run one spa or several outlets from the same login, with reporting by location. Button labels can be renamed for the wording that desk uses. The hotel system is not replaced, and the spa is not asked to live inside a room-reservation screen that was built for the front desk.
A missed post usually shows up at the spa desk or during the night audit, not in a ticket queue at the hotel vendor. The RDP PMS integration is supported by Paired Plus. The team is in California and Oregon and already knows how a spa ticket becomes a folio line. You are not handed from the spa company to the property-management company to explain the same charge. Have the room, the ticket number, and the time of the sale ready. Credits and voids are handled on that same path, so finance is not reconciling a side spreadsheet the next day.
The desk stays in Paired Plus. The RDPWin spa interface is the lookup and posting layer behind the ticket, not a second program the therapist has to open. Staff find the guest, confirm the room, close the service, and send the amount to the folio. A retail add-on on the same ticket posts with the service. If the guest wants to pay by card instead of charging the room, the sale stays in the spa system and never goes to the folio. The interface is there for in-house room charges, not for every transaction the spa takes.
Spa revenue needs to be on the folio before the property closes the day. The RDP night audit reads those posted charges, credits, and voids with the rest of the outlets, using the departmental codes set up for the spa. A ticket still open in Paired Plus is not on the folio yet, so the desk should close or void it before audit starts. Once it has posted, accounting can see the spa total inside the hotel system instead of importing a separate file. That is the point of the connection: one set of numbers when the night is closed.