Guest Folio

A hotel stay can include more than the room rate, since food, parking, minibar and other services may post over several days, and the folio gathers those transactions in one account view. A folio can show charges, taxes, credits and payments, and some systems split a reservation into billing windows for different payers, with the exact format varying by property.

A fictional guest who stays three nights and buys one dinner sees the room nights and dinner listed separately, so they can check the bill before paying. A company may cover room charges while an employee pays extras, and routing rules can place those items on different folios or windows, so correct payer assignment prevents disputes.

A fictional traveller's employer pays room and breakfast while the guest pays personal drinks, and the front desk checks the agreed instructions before checkout. A deposit may be applied to the folio, while a card pre-authorisation can be only a temporary hold and is not the same as a final charge, so a fictional hotel that holds a card amount for incidentals takes the actual folio balance at checkout and the hold is released under payment-provider timing.

Night audit or end-of-day processing can post room charges and taxes, and staff must review late transactions or corrections, because a folio printed too early may omit final items. A fictional guest who orders breakfast just before departure sees the restaurant charge post after an initial bill preview, so the front desk issues a final updated folio.

Duplicate or misrouted charges also need checking, as a service billed both to the guest and a group master account needs correction, and the hotel should keep an audit trail for adjustments, as when a fictional conference guest sees room hire on their folio that the organiser should pay and the hotel transfers it under documented billing instructions. A guest folio can be a receipt or supporting record, but tax invoice requirements differ by jurisdiction, so check what document a business needs for accounting or VAT and do not assume every folio meets all invoice rules.

A fictional company that requests an invoice with legal entity details receives the required document from the hotel rather than only a screen print. Direct billing may move an approved balance to a city ledger or accounts receivable after checkout, which does not mean the hotel has received cash, so a fictional travel agent approved for monthly settlement has its folio charges become an AR invoice that finance tracks separately.

Open folio functions can allow authorised charges after checkout in some systems, so hotels should set clear cutoffs and notify guests of later legitimate items, since a checked-out status does not always freeze every transaction instantly. A fictional guest who disputes a late laundry charge finds that the hotel checks the service record and its post-stay policy rather than simply assuming the posted item is correct.

For managers, folios reveal ancillary spending, routing errors and disputed items, and summaries can support accounting, but personal data should be protected and access should match staff roles, so a fictional hotel studying minibar revenue gives finance aggregate data while individual folios remain available only to authorised staff. Reconcile folio balances with payments and AR transfers, because a zero balance should have an explanation, such as payment or authorised transfer, and should not arise from an undocumented deletion.

A fictional shift report that shows a folio cleared by a credit prompts the manager to check the adjustment reason and approval, which preserves the audit trail. When speaking with a guest, use plain line-item descriptions, since a confusing code or combined charge creates unnecessary work, and when a fictional guest asks what "F&B 204" means, staff explain the restaurant transaction and show its date, and overall a guest folio is the transaction history of a stay whose value depends on correct postings, payer routing and a clear final reconciliation.