A hotel IPTV system learns about guests through its PMS interface, and almost everything guest-specific on the TV depends on five events: check-in, check-out, room move, guest language and charge posting. If those events arrive reliably and in the right order, the welcome screen, language, locked content and billing all behave. If one is dropped, a guest sees the previous occupant's name or a menu in the wrong language.
This reference is written by Singapore-based AV and IPTV integrator Prestige Solutions for hotel IT managers who must connect an IPTV system to a property management system. It lists the data that normally flows each way, the timing we plan for, the failure modes worth testing and a go-live checklist. Interface formats differ by PMS vendor and version, so treat the tables as planning assumptions as of 2026 and confirm field names and message types with both vendors in writing.
The PMS sends room-level guest events, and the IPTV middleware translates each into a change on the guestroom TV. Most hotel interfaces carry the same small set of events, whether the transport is a vendor TCP interface, a serial-over-IP link or a web-services interface. Anything beyond this list should be justified by a specific guest feature, because every extra field is one more thing to keep in sync.

| PMS event | Typical fields | What the IPTV system does |
|---|---|---|
| Check-in | Room number, guest name, language, VIP flag, stay dates | Shows personalised welcome, sets menu language, applies rate-plan channel packages |
| Check-out | Room number, folio status | Clears guest name and preferences, resets language, removes casting sessions and saved app logins |
| Room move | Old room, new room, guest record | Clears old room, applies guest data to new room, keeps pending charges attached to the folio |
| Guest data change | Name or language edit | Updates welcome text and menu language without a TV restart |
| Message waiting | Room, message flag | Shows a message indicator on the portal, where the hotel wants this on TV |
| Database resync | Full in-house list | Rebuilds every room's state after an outage on either side |

The return flow is mostly charge posting. When a guest buys a pay-per-view film, a room service item or a premium Wi-Fi tier through the TV, the IPTV system posts a charge to the room's folio through the PMS interface. The accuracy of that posting matters more than any welcome screen, because errors become billing disputes.
| Return message | Content | Risk if it fails |
|---|---|---|
| Charge posting | Room, amount, revenue code, description, timestamp | Lost revenue, or double posting if the IPTV system retries without an acknowledgement |
| Charge acknowledgement handling | PMS accept or reject, reason code | Guest sees "purchase complete" for a charge the PMS rejected |
| Room status query | Occupied or vacant, guest in house | Purchases allowed from vacant rooms |
| Interface heartbeat | Link alive signal | Silent failure that nobody notices until a guest complains |
Charge posting should be idempotent: each purchase carries a unique transaction ID, and the IPTV system waits for the PMS acknowledgement before it shows success. Where the PMS cannot return an acknowledgement, the hotel should decide in advance whether to disable paid content from the TV, because a retry loop without an ID is how double charges happen.
For planning, we treat a few seconds as the target for guest events and a few minutes as the ceiling for resync after a link outage. These are design targets rather than vendor guarantees, and the PMS vendor's polling or push behaviour can lengthen them.
| Event | Planning target | Why it matters |
|---|---|---|
| Check-in to welcome screen | Under about 10 seconds | The guest often switches the TV on within minutes of entering the room |
| Check-out to cleared screen | Under about 30 seconds | Housekeeping and the next guest should never see a previous name |
| Charge posting | Under about 5 seconds to acknowledgement | Guests press the button twice when nothing seems to happen |
| Full resync after link outage | Within a few minutes for the whole in-house list | Rooms must recover without staff re-entering guests |
The interface fails in predictable ways, and each one can be simulated in a test window with the PMS vendor. A hotel that has tested these in advance spends the first week after opening on guest experience instead of firefighting.
| Failure mode | Guest-visible symptom | What to verify |
|---|---|---|
| Interface link down for 15 minutes, then restored | New check-ins show no name or a generic screen | IPTV requests or receives a resync, and rooms update without manual action |
| PMS restarted during a busy check-in period | Duplicate or missing events | Events are queued, not dropped, and not applied twice |
| Room move done in the PMS | Old room still shows the guest, new room blank | Both rooms update, and pending charges remain on the folio |
| Name with non-Latin characters or long surname | Garbled or truncated welcome text | Character encoding and field length on the TV portal |
| Language code not mapped | Menu falls back to English for a guest who selected another language | Mapping table between PMS language codes and portal languages |
| Charge posted to a vacant or checked-out room | Revenue on the wrong folio | IPTV checks room status before accepting a purchase |
| Clock drift between PMS and IPTV server | Charges stamped with the wrong time, night audit mismatches | Both servers use the same NTP source |

The PMS interface is an internal system-to-system link, so it belongs on a management network rather than the guest VLAN. Place the IPTV middleware and the PMS interface server in the same trusted segment, open only the specific ports the interface vendor documents, and log every message with a timestamp. Guest names and stay dates are personal data. Under Singapore's PDPA the hotel remains responsible for it, so keep retention short, clear data at check-out and restrict who can read interface logs. Confirm the exact obligations with the hotel's data protection officer, because this article is not legal advice.
Keep interface credentials in a vault or the hotel's password manager rather than a shared spreadsheet. If the vendor uses an unencrypted legacy protocol, wrap it in a VPN or restrict it to a dedicated VLAN with firewall rules on both ends.
Not every IPTV feature needs the interface, and separating the two keeps a PMS outage from becoming a TV outage. Live channels, the general portal and information pages should keep working with the PMS link down. Personalised welcome, language selection, pay-per-view, room service ordering with folio charge and checkout review all need the link. Design the portal so that, when the link is down, it hides the features that depend on it instead of showing errors. A guest who sees a clean "available shortly" message calls reception less often than one who sees a failed purchase.
More hotel projects and capabilities are listed on the Prestige Solutions home page. For commissioning detail on the TV and network side, see our reference on hotel IPTV fault isolation across the TV, network and headend, and the multicast and bandwidth reference by room count.
Yes. Live channels, a general portal and information pages work without one. The hotel then gives up personalised welcome, automatic language, check-out clearing and folio charging, and staff must handle those tasks by hand or through the front desk.
Hotel IT should own the monitoring and the first response, while the IPTV supplier and PMS vendor keep ownership of their own side of the link. Name one person on the hotel side who can call both vendors, otherwise each will point to the other when a fault occurs.
Retest after every PMS upgrade, every IPTV middleware upgrade and any change to the hotel's network layout. A short test with one check-in, one room move and one charge takes under an hour and catches most regressions.
Contact Prestige Solutions to review your site drawings and current operating pattern. Call +65 8010 2337 or +65 9825 8218, message us on WhatsApp (+65 8010 2337), or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.
Explore our full product range or speak with our technical team for a tailored consultation.