Guide · 9 min read
What Is a Hotel Folio? A Complete Guide for Hotels and Guests
A hotel folio is the itemized account of every charge tied to a single stay — the source document behind every invoice, receipt, and expense report. This guide covers exactly what's on it, the difference between guest and master folios, how split folios work, and how modern property management systems export them so finance teams (and Concur) can actually use the data.
What is a hotel folio?
A hotel folio (sometimes called a guest folio or guest account) is the itemized ledger of every transaction posted against a reservation during a stay. Room rate, occupancy tax, restaurant charges, parking, spa, in-room movies, minibar — anything billed to the room — plus every payment and adjustment, with a running balance.
The folio is generated and updated continuously by the hotel's property management system (PMS) — Mews, Opera, Cloudbeds, Apaleo, and so on. At check-out, the closed folio becomes the source document for the guest's invoice or receipt. The word itself comes from the Latin folium (leaf) — each stay historically got its own page in the front-desk ledger.
What's on a hotel folio
Every folio carries the same skeleton, regardless of PMS:
- Guest & reservation info. Name, address, reservation number, room number, arrival and departure dates.
- Folio number. A unique identifier — critical for accounting reconciliation and chargeback disputes.
- Charge lines. Each posting with date, description, charge code, and amount (room, tax, F&B, incidentals).
- Tax breakdown. Occupancy tax, VAT, city tax, and tourism levies shown as separate lines for compliance.
- Payment lines. Cash, card authorizations, settlements, and any deposits or pre-payments.
- Running balance. The folio's open balance after every posting — what the guest owes right now.
- Routing codes. Internal markers showing which folio a charge was sent to (relevant for split billing).
Guest folio vs master folio
A guest folio belongs to one guest or one room. A master folio is a parent account that aggregates many guest folios into a single bill — used for conferences, wedding blocks, sports teams, and corporate travel programs.
With a master folio, the organizer or company settles one statement at the end of the event; individual guest folios still exist for audit trail but the cash settlement happens at the master level. This is the foundation of every corporate hotel billing workflow — and where modern aggregation tools earn their keep, because exporting 80 guest folios and rolling them into a clean monthly invoice is the slow part.
Split folios explained
A split folio divides a single stay across two or more accounts. The classic case: the guest's employer pays for room and tax, the guest pays for everything else.
On a modern PMS, the front desk routes individual charge codes — room, tax, parking, F&B, minibar — to whichever folio should carry them. At check-out the system produces two (or more) PDFs, each a complete folio in its own right, addressed to the correct payer. Done badly, this becomes a 15-minute manual reconciliation; done well, it's a drag-and-drop in seconds.
From the SwiftInvoice playbook
Our split-billing flow lets reception drag charges between two recipient folios and generates both PDFs in a single step — typically under 20 seconds per stay. See the split-billing demo →
Exporting a folio from your PMS
Every PMS can print or PDF a folio. The harder problem is getting clean, structured folio data out of the system so an invoicing or accounting tool can do something with it — aggregate it into a corporate statement, push it to your GL, or re-bill it to a travel agency.
- • Mews: Connector API exposes folios, postings, and payments as JSON. Webhooks fire on folio closure.
- • Opera (OHIP): REST endpoints for folios and postings; OAuth-based auth.
- • Cloudbeds: REST API with folio + transaction endpoints.
- • Apaleo: Modern REST API, webhook-first, well-suited to event-driven invoicing.
Mews users
SwiftInvoice listens to Mews folio-closed webhooks and produces a finance-ready invoice in under 10 seconds — no CSV exports, no copy/paste. Book a Mews integration pilot →
Itemizing a hotel folio for Concur & expense tools
Concur (and Expensify, Brex, Ramp) expect each charge category as a separate line so taxes, room, and incidentals get coded to the right GL accounts. A summary receipt won't pass — you need the itemized folio.
- Request the itemized folio at check-out, not the summary receipt.
- Upload the PDF to Concur and use the Itemize tool on the expense entry.
- Split the total into Room, Tax, F&B, Parking, and Other — matching the folio's lines.
- Attach the folio PDF as the supporting receipt. Finance can now reconcile cleanly.
Frequently asked questions
What does folio mean in a hotel context?
Folio means the itemized account of charges and payments for a single stay. The word comes from the Latin folium (leaf) — each stay used to get its own page in the front-desk ledger.
What is a folio number?
A unique identifier the PMS assigns to each folio. You'll need it when requesting a copy of an old folio, disputing a charge, or reconciling against a corporate statement.
Is a folio the same as an invoice?
No. The folio is the live ledger of charges during the stay. The invoice (or receipt) is the closed, formatted document produced from the folio at check-out for the payer.
How is a folio balance calculated?
Sum of all charge lines minus sum of all payment lines, in real time. A positive balance means the guest owes the hotel; zero means the folio is settled and ready to close.
Can one stay have multiple folios?
Yes — that's a split folio. The PMS routes individual charge codes to different folios so each payer gets a clean PDF addressed only to them.
Turn folios into finance-ready invoices in seconds
SwiftInvoice Pro plugs into Mews, Opera, and Cloudbeds to aggregate folios, split charges across payers, and roll corporate stays into monthly statements — automatically.