These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Hospitality ERP
- Features
- Reporting
Reporting
Give property teams a common way to follow arrivals, readiness, kitchen work and open financial obligations. Reports retain their source, service date and company scope, so an operational status does not stand in for an occupancy fact or a monetary event.
OverviewRoom Readiness Board×
Hospitality ERP · Reporting
New
Room Readiness Board
Rooms
| Room code | Property | Room type | PMS occupancy | Local readiness | Current assignment | |
|---|---|---|---|---|---|---|
| 204 | Mariner Row Hotel | Courtyard king | Vacant | Dirty | Calder assigned Room 204 | |
| 305 | The Lantern Courtyard | Garden view queen | Occupied | In progress | Calder assigned Room 204 | |
| 118 | Mariner Row Hotel | Family connecting rooms | Unknown | Clean | Vale assigned Room 109 | |
| 412 | Mariner Row Hotel | Standard two queens | Vacant | Inspected | Haddad assigned Room 502 | |
| 216 | Mariner Row Hotel | Accessible king | Occupied | Restricted | Vale assigned Room 109 |
6 of 6 records
204Rooms · RMS-92357
VacantPropertyMariner Row Hotel
Room typeCourtyard king
Local readinessDirty
Current assignmentCalder assigned Room 204
Readiness inspectionRoom 412 suite inspection
What you can do
Follow arrivals and the current stay position
Arrivals and Stay Position uses the current authoritative PMS reservation, assignment and stay information. It distinguishes room-type demand from physical rooms, actual occupancy from planned dates, and confirmed state from pending requests or unresolved source gaps.
Stay nights use the property’s calendar and timezone. Actual events retain their timestamps, while the business or service date is separate from ERP posting periods. The report does not infer room revenue from a guessed nightly rate or create an alternate room-availability engine.
Explain room readiness and unfinished work
Room Readiness brings local cleaning, independent inspection, PMS occupancy and room restrictions together without collapsing them into one status. New faults, changed turnover revisions and overlapping blocks remain visible even when an earlier inspection passed.
Housekeeping Work follows actual assignments, observations, completed visits and missed or rescheduled work. Do-not-disturb and service-declined instructions retain their practical consequences. A task marked for tomorrow is not proof that a room was cleaned today.
| Operational question | Report |
|---|---|
| Which guests and room changes need attention? | Arrivals and Stay Position |
| Which room checks or restrictions remain open? | Room Readiness |
| What cleaning work was performed or deferred? | Housekeeping Work |
| What was prepared, used and costed in the kitchen? | Kitchen Production and Cost |
| Where is stock, and what has actually been consumed? | Property Stock and Supply |
Connect kitchen output with actual supply use
Kitchen Production and Cost follows released recipe work, actual accepted inputs and time, terminal output, standard value and signed variance. Packaging counts and ingredient quantities retain their own units; intermediate throughput is not added as another finished quantity.
Property Stock and Supply separates current storeroom or department custody, active reservations, actual consumption, unused returns and issued WIP. Held valued food remains financially owned while its eligibility is restricted. Aggregate lot history is not another current stock balance.
These views help the kitchen and warehouse explain a difference without assuming that a PMS charge or housekeeping completion proves physical use. Food-service cost and guest revenue may reference the same service while retaining different economic owners.
Follow purchases and local goods orders
Purchasing and Receipt Position compares approved commitments with actual arrivals, accepted tranches, returns and matched bills. A partial receipt remains partial even after one supplier invoice is matched.
Goods Order and Billing Position follows the local goods route from accepted order through actual handover and eligible billing. Performed, returned, cancelled and remaining quantities stay distinguishable; their commercial value is allocated once across those transitions.
The local goods report does not add PMS folio charges as extra invoices. A source routing choice determines which system owns that sale before its effect, and a correction preserves the original history.
Reconcile the PMS bridge to the books
PMS Ledger Reconciliation compares authoritative additive source components with approved, posted and held bridge scope. Guest receivable, deposits, corporate balances and tender clearing remain distinct. Missing, duplicated or conflicting source events are part of the report rather than silently treated as zero.
A wrapper or folio summary is not added to its underlying detail. PMS tender events and actual bank settlements reconcile through the same clearing source, avoiding a second cash entry. Source and ERP monetary carrying use an explicit common cutoff.
Receivables and Payables Aging follows the selected local open financial sources and actual settlements. Local Financial Statements reconcile the company’s posted books with their subledger and PMS controls. Different transaction currencies are not summed as though they were one monetary unit.
Keep access and history useful
Reports follow current role, company, property and purpose scope. Attendants receive needed room/task information without unrestricted guest documents, folios or payment details. A report’s visibility does not grant authority to approve its underlying action.
Approved mappings and retained source versions explain why a number appeared. Corrections preserve earlier facts, and incomplete history remains explicit at cutover. One reconciled opening ledger and nonposting detail prevent historical imports from recreating past charges, stock or payments.
The report catalogue groups the complete set; roles and permissions explains who prepares and reviews the work.
What your team sees
- Room Readiness Board. Review occupancy and local readiness as separate operating states.
- Kitchen Production Schedule. Follow released kitchen batches and current production progress.
- Period Close Work. Follow the financial tasks behind reconciled property results.
What it keeps track of
Data model- Users
- Authenticated actors and explicit entity/role scope; no party record automatically creates an account.
- Hospitality policies
- Versioned operational and financial rules with explicit finite limits.
- Master changes
- Protected master activation without direct Manage permission bypass.
- Document revisions
- Immutable typed document snapshots and source basis.
- Approval decisions
- Authoritative human decisions independent of document lifecycle.
- Authority delegations
- Time- and scope-bounded coverage, never a new role.
- Integration events
- Authenticated inbound/manual evidence with idempotent economic effects.
- Integration deliveries
- Outbound intent, attempt and reconciliation; a timeout is not nonexecution.
- Migration batches
- Reviewed cutover: one full opening GL plus nonposting detailed balances.
- Migration items
- Replay-safe original identities, detailed remaining balances and prior effects.
Who uses it
Permissions- Front Desk Coordinator
- And Property Manager review arrivals and commercial work.
- Housekeeping Supervisor
- Follows readiness and actual tasks.
- Kitchen Manager
- And Warehouse Manager review kitchen, supply and consumption evidence.
- Purchasing Manager
- Follows supplier commitments.
- Accountant
- Reconciles local and PMS financial sources, with Finance Manager reviewing mappings, monetary decisions and close.
- Admin
- Manages approved report access.
Set up Hospitality ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.