Skip to content
ERPat System
ERPat System
Business

Hotel Operations: Reservations to Folio Billing

A practical look at how a hotel's records hold together from booking to checkout: room inventory, reservations, arrival and departure, and the guest folio that has to add up. Written for owners and managers of small Philippine properties.

CCChelsea Cuevas6 min read

In this guide

TopicBusiness
Time6 min read
Best forOperations leaders comparing disconnected tools with a more unified business system.

What to watch for

Use the article to identify repeat work, handoff gaps and places where one source of truth would help.

  1. 01Where hotel records drift apart
  2. 02Rooms and rates are the base record
  3. 03A reservation should hold something real
In this article

A guest checks out at seven in the morning and the front desk needs to produce one number. Getting to that number means the reservation, the room actually occupied, the nights charged and whatever was signed for at the restaurant all have to agree. In many small properties those four things live in four different places — a booking notebook, a whiteboard behind the desk, a spike of chits and a spreadsheet on the manager's laptop — and the reconciliation happens in the lobby while the guest waits. That gap is where hospitality operations quietly lose money and goodwill.

Where hotel records drift apart

The drift almost never starts with a big mistake. It starts with a phone booking written on a notepad because the person answering was not at the desk, a room swap granted at midnight because a shower was not draining, a late checkout approved verbally by a supervisor who then went off shift. Each one is reasonable on its own. None of them updates the record everyone else is reading.

By morning the whiteboard says one thing and the folder of registration cards says another. The housekeeping list was printed before the swap. The restaurant chit has a room number that was correct at dinner and wrong by breakfast. Nobody was careless; the information simply had no single place to land.

The fix is not more forms. It is having one record per room and one record per stay, updated at the moment the thing happens, by the person it happens to. That is the whole design idea behind the Hotel Management module in ERPat: rooms, reservations, check-in and check-out, and folio billing kept as one connected chain rather than four parallel logs.

Rooms and rates are the base record

Everything downstream depends on the room list being honest. A room that exists in the system but has been out of service since the ceiling leak is a room that will get sold. A rate that was agreed for a corporate account last quarter but never written down anywhere is a rate the front desk will have to guess at, usually in the guest's favour and always in an argument.

So the first setup task is unglamorous and worth doing carefully. List the rooms as they actually are — type, capacity, floor, and the current status of each. Record the rates you actually sell, including the ones you only sell sometimes. If your walk-in rate differs from your corporate rate, that is two entries, not one entry and a habit.

Once the room inventory is real, availability stops being a question someone has to answer from memory. It becomes something the system can answer the same way at three in the afternoon and three in the morning, whoever is on duty.

A reservation should hold something real

A booking is a promise, and the value of recording it in software is that the promise is attached to inventory. When a reservation is taken against a room type for specific dates, that capacity is committed. The next person who checks availability sees what is left, not what was left before the last phone call.

This is the point at which most double-bookings disappear, and they disappear for a boring reason: there is no longer a window between the booking being agreed and the booking being visible. The front desk, the manager reviewing tomorrow's arrivals and whoever is answering messages are all reading the same list.

It also gives you an arrivals view that is worth something operationally. Knowing who is expected, in which room type, for how many nights, lets housekeeping sequence the day and lets the desk prepare registration ahead of the rush instead of during it. The reservation stops being a note to be honoured and becomes the first entry in the guest's record.

Check-in and check-out are ledger events

Treat arrival and departure as transactions, not as a courtesy exchange at the counter. At check-in, the reservation converts into an occupied room, the folio opens, and the room is no longer available to anyone. At check-out, the folio closes, the room returns to inventory for housekeeping, and the stay becomes a settled record rather than an open question.

Recording them at the moment they happen is what keeps the rest of the system truthful. A room that was vacated at six but only marked at noon is a room you could not sell for six hours and a housekeeping assignment that went out late. A guest checked in mentally but not in the system is a guest whose restaurant charge has nowhere to go.

The discipline sounds obvious and is the single most common place small properties let things slip, usually during the busiest hour of the day — which is exactly the hour when the cost of slipping is highest.

The folio is the guest's whole story

The folio is the running account for a stay: room nights as they accrue, plus everything else the guest signs for, in one place, in order. Its job is to be complete and to be complete continuously, not assembled at the end from whatever paperwork can be found.

That continuity is what makes checkout fast. If every charge landed on the folio when it was incurred, the departure conversation is a review and a settlement. If charges are collected at the end, checkout becomes an investigation, and investigations in a hotel lobby at seven in the morning are settled by discounting whatever cannot be proven.

!
Software will not enforce a habit you have not set

A folio is only as complete as the charges people actually post to it, at the time they post them. Decide who is allowed to sign a charge to a room and who is responsible for entering it, and make that rule explicit before you blame the system for a short bill.

Charges from the outlets, recorded once

Most hotels are also small food and beverage businesses, and the counter is where a second set of books usually appears. A sale at the restaurant or the sundry counter is simultaneously revenue, stock leaving the store, and — if it was charged to a room — part of a guest's account. Handled as three separate entries, it will be wrong in at least one of them by month-end.

The Point of Sale module exists to collapse that. A counter transaction is recorded once, and it posts straight to inventory and to the ledger, so the stock movement and the accounting entry are not two people's separate jobs. On a single platform, the outlet's takings and the property's books are not two versions of the same day to be reconciled later.

Practically, that means your beverage variance stops being a mystery and your revenue by outlet stops being a spreadsheet exercise. It also means the billing documentation your accountant and the BIR expect comes out of the same records the front desk was using all along.

Where to start

If you are running a property on paper today, do not attempt the whole chain in one weekend. Get the room and rate list right first, because everything else inherits its errors. Then move reservations in, so availability has one answer. Then move check-in and check-out, which is where the habit matters most. Folio billing and the outlets follow naturally once the stay itself is a real record.

The goal is not a more elaborate system. It is a checkout where the number on the folio is the number everyone already expected, and the room is back in inventory before the guest reaches the car.

Technology decision context

Use "Hotel Operations: Reservations to Folio Billing" to make a better systems decision

Technology articles are most useful when they help the team decide what to change next. Focus on the process problem first, then choose the tool or integration that removes the most repeated work.

Part 1Start from the workflow, not the tool

A system change should solve a visible operational problem. Map who creates data, who reviews it and who depends on the result.

  • Identify repeated encoding, manual exports and duplicate records
  • Find handoffs that rely on reminders instead of system status
  • Separate must-have controls from nice-to-have interface features
Part 2Integration details to check

A useful system should reduce context switching and make data easier to trust across teams.

  • Which records need one source of truth?
  • Which reports depend on data from more than one department?
  • What permissions, audit logs and backups are required?
Part 3How to judge success

A better technology setup should improve speed, reliability and confidence in decisions.

  • Fewer manual workarounds after rollout
  • Shorter time from request to approval or report
  • Clear ownership when something is missing or incorrect
CC

Chelsea Cuevas

Content & Marketing Associate

Covers business growth, HR best practices, and the technology behind modern operations.

Relevant solution

Running operations across disconnected tools?

See how ERPat brings HR, payroll, accounting, inventory and sales into one connected platform built for Philippine businesses.

Explore ERPat

Comments

Leave a comment

Questions or thoughts on this article? Send a comment and our team will follow up by email.

Continue exploring

Logistics and Delivery Tracking for Distributors

Deliveries go out, some come back, and the office finds out days later. Here is how distributors can keep dispatch, delivery and returns in one visible record instead of scattered across notebooks and chat threads.

6 min read

Recruitment Analytics: Measuring Your Hiring Funnel

Most hiring problems are stage problems, not volume problems. This guide shows how to measure time-to-fill honestly, find the stage where candidates drop off, and judge sources by hires rather than applicant counts.

6 min read

ERPat System

See how these workflows come together inside ERPat.

Walk through ERPat using your actual process as the reference — one connected system for HR, payroll, accounting, inventory, sales and daily operations.

01Map your current operational workflow
02Identify repeated manual steps and handoff gaps
03Preview a more connected and controlled process