Full-service hotels
Multiple outlets posting to rooms, company accounts, meeting space and a controller who reconciles daily.
Module 01 — Property Management
A property management system for hotels where a stay is complicated: shared rooms, split bills, company accounts, packages that include things, and a controller who reconciles every morning. Two hundred and eighty-six screens, because a full-service property needs them.
Book a demoTask sheets generate and go out to attendants' devices.
Departures settle; folios close and route to company accounts.
Discrepancies between front office and housekeeping surface.
Arrivals check in; queue rooms release as they are inspected.
Turndown sheets; credit limits re-checked against live balances.
Night audit runs its 42 steps and rolls the business date.
One business day, and the parts of it a PMS is actually judged on.
Every shape a booking takes at a full-service property, including the ones that break simpler systems.
Several guests in one room, or one party across many rooms, each with their own folio and their own rate.
Group allotments with pickup tracking, cut-off dates that release unpicked rooms, and conversion from lead to definite.
One booking holding several rooms and room types without becoming several unrelated records.
Deposit rules by rate or market, plus recurring charges that post on their own schedule during the stay.
Waitlisted bookings with an audit trail, and an oversell guard that knows the difference between a decision and an accident.
Departmental traces that appear where the work happens, and alerts that fire at check-in, check-out or on the folio.
Arrivals, in-house and departures, with the room assignment workflow your property already has opinions about.
Search, pre-register and pre-assign before the day starts; queue reservations when the room is not ready.
Move a guest mid-stay with reason codes, and have routing and charges follow them rather than stay behind.
A live house view by floor, status, VIP, or whatever your team sorts by at three in the afternoon.
Non-guest accounts for internal charges, events and anything that needs a folio without a bed.
Sell a suite as one room while its components stay individually addressable for housekeeping and maintenance.
Rule-driven room upsells offered at the desk, priced and posted through the same engine as everything else.
The module that decides whether a migration survives contact with your controller.
Split a bill across windows by payee, so the guest, the company and the travel agent each settle their own part.
Send charges to another window or another guest's bill at posting time, by transaction code, group or date range.
Grant allowances nightly, consume them against real postings, and strike profit and loss on what went unused.
Layered taxes, generated charges, collecting-agent taxes, and tax that follows a routed charge to its new window.
Corrections write offsetting rows that point back at the source. A posted charge is never quietly edited.
XML and print pipelines for fiscal and archival requirements, driven by configuration rather than a code change.
Status, task sheets and the discrepancies that mean somebody is in a room the system thinks is empty.
Dirty, pickup, clean, inspected — with the optional stages your property actually uses, and the ones it does not.
Generate and assign attendant sheets by section and credit, including turndown as its own evening pass.
Surface mismatches between front office and housekeeping status before they reach a guest.
Two different things, tracked differently: one leaves inventory, one does not. With history and warnings.
Workload credit per room type and task so sheets balance across a shift instead of by room count.
Project cleaning workload from the reservation book so staffing is decided before the morning it is needed.
What happens after check-out, when a company takes thirty days to pay.
Move a settled folio into a receivable account at check-out or in batch, with the authorisation trail intact.
Configurable ageing levels and reminder cycles that escalate on their own schedule.
Generate statements per account with the posting history behind each line still reachable.
Post, pay and transfer across many accounts in one pass rather than one at a time.
Collection traces on accounts, so the next person to pick up the file knows what was promised.
Find a charge across accounts and years when a guest disputes a line from last March.
Forty-two steps grouped into four ordered buckets. Each property chooses which run, in what order and in which phase. Every step records what it did, and a non-mandatory failure is logged without failing the night.
Room and tax posting, package allowances, profit and loss, fixed charges, trial balance, block cut-off, auto no-show, cashier close, and the business date roll that ends it.
Arrivals holding deposits, profiles missing country codes, open cashier sessions.
Room and tax, packages and allowances, fixed charges, no-show fees.
Front office status, auto check-out, auto no-show, block cut-off, waitlist expiry.
Trial balance and folio tax summary, materialised per transaction code.
One step, mandatory, last. Everything before it has already reconciled.
If your property is fifteen rooms and one rate, this is more system than you need, and we will tell you so.
Multiple outlets posting to rooms, company accounts, meeting space and a controller who reconciles daily.
Packages with allowances, component suites, long stays and activity-driven charges across the property.
Comp accounting on its own window range, authorizer limits, player statistics and gaming history beside the folio.
Many properties under one configuration, with cross-property posting between partnered hotels in a cluster.
Bring your most awkward routing case, your strangest package, or the report your current system cannot produce. That is a better first demo than a room grid.