Hotel booking, cash register and PMS: which records must connect?
Follow one stay from direct booking to accounting, decide which system owns each record, and test the handovers before your team relies on them.
- Bahram Davoodi

A guest books on your website, pays a deposit and adds breakfast at reception. At departure, the team needs one clear answer: what has already been paid, and what is still due? That answer becomes harder when the reservation, payment and invoice carry different references.
For an Austrian hotel, pension or apartment business, choosing software starts with deciding which system owns each part of the stay. This guide focuses on the handovers between booking, room management, reception sales and accounting. The broader hotel software guide for Austria covers general selection requirements.
Give each part of the stay a clear responsibility
A property management system, usually shortened to PMS, typically coordinates reservations, rooms and the operational stay. A hotel cash register handles sales and payments at a configured checkout. A website provides a route for direct enquiries or bookings. Accounting then needs the underlying documents and payment records.
These jobs may share a platform or use several connected applications. Write down where each record is maintained before discussing an interface. A useful starting map is:
Record | Responsibility to agree |
|---|---|
Room availability and stay dates | The system that controls whether a room can be sold |
Guest and invoice recipient | The record reception uses to identify the stay and bill the correct party |
Deposits and additional services | The account that shows charges, payments and the open amount |
Final invoice and accounting entry | The agreed document issuer and the process that transfers its records |
The hotel setup offered by Lonio describes room resources, reservations, guest folios, website booking and hotel administration. Confirm which responsibilities your proposed configuration covers, especially if you already use a PMS or external booking channels.
Five questions to settle before connecting systems
1. Which calendar decides whether the room is available?
Choose the authoritative availability record. Then test a direct booking, a telephone extension and a room blocked for maintenance. Reception should know where to make each change and how it reaches other booking routes.
Ask what happens during a delayed update or failed transfer. A calendar connection alone does not demonstrate that rates, deposits, invoices and guest details also move between systems. List the information exchanged, its direction and the expected delay. Include cancellations in that list.
2. How does every record identify the same stay?
A room number can change during a stay and will be reused for the next guest. Use a stable booking reference when checking handovers. Keep the guest, stay dates and invoice recipient distinguishable; a company may pay while an employee occupies the room.
In a demonstration, move the guest to another room and correct the invoice address. Check which records update and which require review. Do not accept a match based only on a surname or room number as proof that the entire journey is connected.
3. Where is the deposit recorded as money received?
Separate a requested deposit from a successful payment. The booking confirmation, payment status and actual settlement may describe different stages. Reception needs to see the received amount and its reference before deducting it at checkout.
Lonio documents charges, deposits, payments and balances within its reservation and folio workflow. Test how the selected payment route reaches that record, including a failed payment and a refund. Agree the accounting treatment with your accountant; an operational balance check is not a tax rule.
4. Are extras charged to the room or already settled?
Breakfast, parking or a shop purchase should have a clear destination. An item paid immediately at reception must not also remain payable on the guest account. Conversely, an item charged to the stay needs to appear before the final bill is issued.
Ask a team member to post one extra, correct it and then find the history from reception. The existing guide to minibar, breakfast and hotel extras covers this handover in more detail.
5. Who issues the final invoice?
Agree which application issues the final document and how the other records refer to it. The goal is a traceable record of the same sale, without accidentally creating a second independent charge in another application.
Check private and company invoices, partial payments and a correction after departure. The digital invoice functions in Lonio connect sales information with documents and outstanding amounts. Your exact numbering, document flow and responsibilities still need to be configured.
Rehearse one stay before going live
Use a simplified test case: a stay priced at €480, additional services of €60 and a deposit of €150. The expected remaining amount is €390. These are invented test amounts, not hotel tariffs or a tax calculation.
Run the journey with reception and the person responsible for bookkeeping:
- Create the booking and record its reference, dates and invoice recipient.
- Receive the test deposit through the intended payment process.
- Change the room or stay dates and verify the affected records.
- Add the extra services, showing which are payable at checkout.
- Settle the remaining €390 and inspect the final documents.
- Find the corresponding payment and accounting records, then demonstrate how a later correction is traced.
Repeat the handover after a connection interruption. Ask how the team sees an unsuccessful transfer and how a retry avoids recording the same item twice. A successful demonstration should show the exception as well as the normal path.
Finish with the accounting handover
Ask your accountant to review the example documents and required account mappings. The accounting tools in Lonio connect operating records, payments and configured exports; the scope depends on the package and setup.
Before choosing, take your current software list and this test stay to a Lonio demonstration. Confirm room resources, booking channels, any existing PMS connection, payment methods, export requirements and the agreed costs. A general integration claim is less useful than seeing your own reception-to-accounting handover work with the proposed configuration.
