How can an Irish hotel post restaurant and bar charges to the correct guest folio?
A busy restaurant can serve residents, visitors and guests who have just changed rooms. This guide turns those situations into practical checks for sending itemised charges to the right hotel account.
Connect the restaurant or bar point-of-sale (POS) system to the hotel property management system (PMS), then match each authorised charge to the current reservation and intended guest folio: the account recording that guest’s charges and payments. Confirm the guest’s identity, retain item and tax details, and reconcile accepted postings. Room numbers alone are insufficient. Split bills, room moves, reversals and retries must be tested for your specific connector.
Define the posting rules before service
Ask both suppliers to document what travels from POS to PMS and what returns as confirmation. Treat the following as acceptance requirements, not assumed RoomRaccoon features.
- Identify the stay and payer. Confirm the name, current room and charging permission. For shared rooms, identify the intended guest account. Company-paid accommodation does not automatically authorise personal extras.
- Keep traceable detail. Agree fields for reservation and folio references, outlet, receipt and transaction IDs, time, item description, quantity, gross amount and Value-Added Tax (VAT) code. Preserve restaurant and bar lines separately.
- Prove the result. Staff need to distinguish accepted, rejected and pending charges. Establish who investigates failures and how corrections retain a link to the original receipt.
Use a reservation reference that survives a room move wherever supported. If lookup relies on room numbers, require a fresh guest check before posting. Stop when the identity is ambiguous.
A POS test matrix with expected balances
Hypothetical training example: Ada occupies room 204, reservation A and folio F204; Ben occupies room 205, reservation B and folio F205. These are invented references and prices. Run each row independently in an agreed test environment. Balances below cover only the stated extras, in euro including VAT; exclude accommodation, deposits, tips and discounts.
| Scenario | Action and test data | Required result and evidence |
|---|---|---|
| 1. Room charge | Send T101: restaurant meal €44 and bar wine €18 to Ada’s F204. | F204 increases by €62; F205 by €0. Match both item descriptions, outlet codes, VAT codes and transaction reference across systems. |
| 2. Split receipt | Split T102 (€96): meals €60 to Ada’s F204; drinks €36 to Ben’s F205. Confirm both allocations before sending. | F204 receives €60 and F205 €36: €96 altogether. Preserve the original receipt reference and allocated lines; neither folio receives the full €96. |
| 3. Room move | After a €62 posting, move Ada from 204 to 310. Refresh the POS lookup and add T103, a €14 bar charge. | Reservation A retains €76 in extras. The €14 reaches Ada’s account; a new occupant of room 204 receives €0. Record the reservation reference before and after. |
| 4. Cancelled line | Post T104: meal €30 plus wine €12. Reverse the wine through the agreed correction process after posting. | Keep the €42 original and linked −€12 correction, leaving €30. Reverse the corresponding tax amount too. Separately test a void before transmission: only €30 should post. |
| 5. Resent transaction | Post T101 for €62, then simulate a lost acknowledgement and resend the same transaction identifier with supplier assistance. | The folio remains €62, not €124. Retain evidence of duplicate rejection or controlled handling; an uncertain acknowledgement must trigger investigation. |
| 6. Non-resident diner | A visitor pays T106, €42, by card at the restaurant. Also attempt a room charge without a valid resident account. | Record €42 as a POS payment and €0 on guest folios. The invalid room charge must be blocked or held for review, never assigned to an arbitrary room. |
For each row, retain the POS receipt, PMS posting, transaction status, actual balance, tester and pass/fail result. Reception and restaurant supervisors should sign off together.
Included meals need a separate test. If breakfast is already included in a package, consuming it must not create another payable charge. Agree how package consumption is recorded and test an extra item bought alongside it.
Catch missing charges and incorrect tax mapping
At shift end, compare accepted POS room-charge totals with the matching PMS additions, less linked reversals, using the same cut-off time. Track pending and rejected transactions separately. A room transfer is not a card payment: reconcile payment takings separately and prevent the same sale being counted twice in accounting.
After an outage, inspect the queue and destination folio before manually entering a charge. Otherwise an automatic retry may add it again. Test attempts against checked-out guests and agree an authorised exception process.
Keep food and drink VAT codes distinct
In the Republic of Ireland, accommodation remains at 13.5%. From 1 July 2026, qualifying restaurant and catering services attract 9%; alcohol and specified drinks, including soft drinks and bottled water, remain at 23%. A combined accommodation-and-meal package requires fair and reasonable apportionment. See Revenue’s accommodation and meal guidance and current VAT rates.
Assuming T101 is an ordinary November 2026 dine-in sale, its €44 meal includes €3.63 VAT at 9%; its €18 wine includes €3.37 at 23%: €7.00 total after rounding each line. Have your accountant approve item classifications, package allocation and rounding before mapping goes live.
What Gleesons demonstrates with RoomRaccoon
The Gleesons Roscommon case study describes a 26-room Irish hotel where the Pixelpoint integration replaced broad beverage groupings with individually categorised items on receipts and within the system. This supports the value of item detail; it does not establish how every connector handles reversals or retries.
Review RoomRaccoon’s hotel software integrations directory and property management system, then confirm your POS version, data direction, required subscription or additional fees, and supported workflows. Ask which matrix steps are automatic and which require staff action.
Bring a sample restaurant receipt and this test matrix to discuss room-charge handling for your property.
Book a demo for your propertyQuestions about hotel POS room charges
Can two guests sharing a room pay separately?
Only use automatic routing if the connector can identify the intended account. Otherwise agree and test a supervised allocation process before accepting the charge.
Does deleting a POS item remove the PMS charge?
Do not assume so. A void before transmission and a reversal after posting are different tests. Verify both the folio balance and correction trail.
Can non-residents use the same restaurant till?
Include them in testing. Their cash or card sale should follow the POS settlement process without creating a resident room charge.
What if the connection only sends receipt totals?
Check whether item and tax detail remains retrievable and whether separate revenue categories survive. A matching gross total alone does not prove correct tax mapping.
Sources and checks
Checked 13 November 2026. The matrix is a proposed acceptance test, not a record of tests performed at Gleesons.
- RoomRaccoon: Gleesons Roscommon — Pixelpoint item detail.
- RoomRaccoon: Integrations & App Directory — integration categories.
- RoomRaccoon: Property Management Software — PMS context.
- Revenue: VAT treatment of Guest and Holiday Accommodation — April 2026 guidance.
- Revenue: Current VAT rates — rate values.
