← back to reference index

Reservation & folio

TuluyanOS Front desk staff too provisional · D87, D88

Front desk › registration, room, charges, payments, check-in and check-out (D87)

STATUS: interactive demo — behavior shown here is the intended contract (nothing is saved). Demo Location: La Union Beach Villas (stays on), business date Mon, Sep 28 2026.

Maria Santos

HT-24811 · Direct · Deluxe Twin, room 201 · Fri Sep 25 → Mon Sep 28 (3 nights) · 2 adults · With breakfast

Balance

In house · departs today, check-out by 12:00 NN

Folio · room 201

Room nights post at night audit (2:00 AM)
DateItemAmountActions
Restaurant/café bills come in from the POS with “Charge to room” (BentaOS on).

Totals

Payments

Check-out needs a zero balance. Only an Owner or Manager can move a balance to company billing (receivable, logged).

Implementation notes for Cursor

Entities: Reservation, StayGuest (ID fields encrypted, masked, reveal logged), Folio + FolioLine (room_night, add_on, pos_charge, fee, discount, adjustment; voids keep the line with voided_at), Payment.folio_id, BIR invoice at settlement (§13, §19).

Key states: Check-in needs ID type + number and the signed card; a dirty room warns (override allowed). Voids and adjustments: Owner/Manager with a reason, Staff via Manager PIN or remote approval (D83, kind folio_adjustment). Senior/PWD share = line ÷ guests in the room, VAT removed, then 20% off. LGU fee is outside VAT. The café order was already receipted at the POS, so it appears as “charged to room” and is not taxed again. Check-out with a balance is refused unless moved to company billing.

Forbidden inventions: No deleting folio lines, no editing posted room nights (post an adjustment), no free-text prices on charges (catalogue add-ons only), no senior discount on the whole room when others share it.

Governs: D87; modules/STAYS.md §6, §7, §9; PLAN-265, PLAN-266, PLAN-267.