How can a hotel post restaurant and bar charges to the correct room through EPOS?
A reliable room charge connects the restaurant ticket to the right guest account. Use this hotel EPOS room charge integration checklist to test identification, posting, corrections and reconciliation before going live.
Connect your EPOS to the hotel PMS, then match the guest’s name and current room to an eligible reservation and folio. Map food, drinks and payment methods before posting. Send a traceable ticket reference, check that the charge arrived once, and reconcile both systems. Test wrong-room corrections, split payments and failed transmissions before staff use room charging with guests.
Match the guest, folio and department
The folio is the guest’s account of charges and payments. A room number alone is insufficient: occupants change, guests move rooms and one reservation may have several billing accounts. Confirm the guest’s name, current stay and intended folio before posting.
- Eligibility: check that the stay is active and room charging is authorised. Test any no-post restriction or spending limit; a room-charge permission does not guarantee payment.
- Mapping: agree food and beverage department codes, tax treatment and the EPOS “room charge” tender. Keep tips, service charges and discounts separately mapped where used.
- Traceability: retain the outlet, ticket reference, transaction time, reservation reference and posting status. Ask how staff distinguish accepted, rejected and unresolved transactions.
Supplier mappings differ. For example, Access’s department and payment mapping guidance distinguishes revenue departments from payment types and describes defaults for unmapped items. Use it as a configuration example, then verify your own connector.
Work through a £96 restaurant ticket
Illustrative example: Alex Morgan is checked into room 204, reservation TEST-204. Restaurant ticket REST-1042 contains £72 of food and £24 of drinks. All names, references and codes below are fictional. The restaurant is VAT-registered; this November meal is eaten on the premises, with no tips, service charge or discount.
| Charge | Example department | Net | VAT | Gross |
|---|---|---|---|---|
| Food | REST-FOOD | £60 | £12 | £72 |
| Drinks | BAR-DRINK | £20 | £4 | £24 |
| Total | Two revenue categories | £80 | £16 | £96 |
Net = gross ÷ 1.20. This example follows HMRC’s on-premises catering guidance and the standard VAT rate. Check different supplies separately.
Select Alex’s active stay and approved folio, confirm the £96 total and submit using the room-charge tender. Check the PMS for REST-1042 and its department breakdown. The guest account should increase by £96 once. Closing the EPOS ticket as a room charge transfers the amount to the hotel account; it does not establish that the guest has paid £96 in cash or by card.
Prove the exception handling before launch
Run each test separately from the original £96 scenario. Record the expected result, actual result and person responsible for resolving a failure.
| Test | Required outcome |
|---|---|
| Wrong room: 214 instead of 204 | Use the supported transfer or reversal-and-repost process. Room 214 ends with £0 from this ticket; room 204 has £96. Keep the original reference and correction history. |
| Repeated transmission | Resend REST-1042 in a controlled test. The folio must still contain only £96 for that sale. Ask whether the connector recognises duplicate references or needs a supervised recovery process. |
| Split payment | Take £36 by card and post £60 to the room. The EPOS ticket still totals £96; only £60 reaches the folio. Confirm this split is supported. |
| £24 drinks correction | Before payment, an approved £24 credit reduces the ticket’s folio contribution to £72, including reversal of £20 net and £4 VAT. Retain a link to the original transaction. |
| Room change or restricted account | After moving Alex to room 208, identify the same stay correctly. Test a checked-out stay, no-post flag and an insufficient limit; require a visible block or an agreed staff control. |
| Timeout or missing mapping | Identify the ticket as unresolved or rejected. Check the folio before retrying; a lost acknowledgement does not prove that posting failed. Review any default-category posting. |
Agree who owns each correction. Staff need a documented route, permission level and audit record. If a guest has already paid, correcting a folio and returning money are separate checks; confirm the refund procedure for the payment method used.
Reconcile the sale without counting it twice
Agree with your accountant which system supplies each revenue stream to the accounting package. The restaurant sale, the room-account transfer and the eventual guest payment describe different parts of one transaction.
For REST-1042, the sale is £80 net plus £16 VAT. The folio carries £96 to collect. Exporting the same sale as revenue from both EPOS and PMS would duplicate it unless the accounting design explicitly handles that overlap.
- Match ticket references and gross totals between EPOS room-charge tenders and PMS postings, allowing for documented reversals and timing differences.
- Separate room-charged sales from purchases paid directly at the bar; check what each report includes before adding totals together.
- Agree the business-day cut-off, including sales after midnight, and review unresolved tickets before checkout.
- Reconcile the first trading day and repeat after department, tax or connector changes.
Assess your RoomRaccoon connection with a real scenario
When comparing hotel software integrations, request a demonstration with your exact EPOS product, version and outlets. Confirm UK availability, package or upgrade requirements, connector fees and support responsibilities. Then check how the chosen hotel property management system presents the charge to reception and the guest.
RoomRaccoon’s Lightspeed consolidated add-ons documentation describes optional ticket-level display and transfers of whole tickets rather than individual items. It does not establish support for every split-payment, refund or retry scenario. Confirm the current behaviour for your UK configuration.
Bring a sample restaurant receipt, your department codes and the £96 test above. Ask to see the correct folio, a wrong-room correction and a repeated transmission, with the resulting reports.
Discuss your EPOS and room-charge workflowQuestions about EPOS room charges
Can two guests in one room use different accounts?
Possibly, depending on the connector’s guest and folio selection. Demonstrate two named guests in the same room and verify the chosen account receives the charge. Do not assume room selection also selects the correct payer.
Does the guest see every item on the hotel invoice?
Check the configured display. A connector may show itemised charges or a ticket summary. With RoomRaccoon’s documented consolidated Lightspeed setup, the hotel invoice shows the ticket reference; the restaurant receipt supplies the item breakdown.
What should staff do during a connection outage?
Follow the agreed exception procedure and retain the ticket reference. Check whether any posting reached the folio before entering it manually. Confirm how queued transactions are reconciled after recovery; do not assume offline room charging is available.
Sources and scope
Sources checked on 10 November 2026. The tests are suggested acceptance criteria, not a claim that every connector supports each workflow.












