System Overview
How every module in Veridien PMS connects and where to find things in the sidebar.
A property management system is only as useful as your understanding of how its parts relate to one another. Veridien PMS is built around the idea that hotel departments do not work in isolation —a reservation made online touches the channel manager, the front desk, housekeeping, billing, and analytics before the guest even arrives. This page explains those connections so you can anticipate where information flows and why a change in one module ripples through others.
The Big Picture
Think of Veridien as a hub-and-spoke system. The property sits at the centre. Every module reads from and writes to shared data —rooms, guests, folios, and calendars —so that everyone on your team sees a single source of truth.
When a guest books a room on an OTA, the Channel Manager pushes that reservation into Reservations. The Front Desk sees it on the arrivals board. Housekeeping knows a room needs to be prepared. On check-in, a Folio is created in Billing & Finance. If the guest orders room service, the Restaurant module posts charges to that same folio. At checkout, the folio closes, housekeeping marks the room dirty, and Analytics records the revenue.
That single guest journey touches six modules. Understanding this flow is why the system overview matters.
Module-by-Module Breakdown
Front Desk & Reservations
These two modules are the operational heart of the system.
Reservations is where bookings live before, during, and after a stay. You create reservations here, assign rate plans, attach guest profiles, and manage group blocks. Every reservation has a lifecycle: it starts as Confirmed, moves to Checked In when the guest arrives, and ends as Checked Out, Cancelled, or No Show.
Front Desk is the real-time operational view. It shows today's arrivals, in-house guests, and departures. The front desk is where staff perform check-ins, check-outs, room moves, and walk-in bookings. It reads from Reservations but adds the urgency of "what is happening right now."
The reason they are separate is intent: Reservations deals with planning (future bookings, availability forecasting), while Front Desk deals with execution (the guest is standing in front of you).
Key Concept: Property
A Property in Veridien represents a single hotel, resort, or accommodation site. All modules, rooms, staff, and settings exist within the context of a property. If you manage multiple properties, you switch between them using the property selector in the sidebar.
Billing & Finance
Every financial transaction in Veridien passes through Billing & Finance. The central object here is the Folio —a running account attached to a reservation or a guest. Room charges, taxes, restaurant charges, minibar postings, and payments all appear as line items on a folio.
Billing also handles night audit, the end-of-day process that posts room charges, reconciles payments, and rolls the business date forward. Tax configuration, payment methods, and invoice generation live here too.
The reason billing is its own module rather than part of Front Desk is separation of concerns. Front desk agents post charges; finance managers reconcile them. The module boundary matches the responsibility boundary.
Restaurant & Outlets
Hotels often have revenue-generating outlets beyond rooms: restaurants, bars, spas, and shops. In Veridien, each outlet can manage its own orders, tables, and kitchen display system (KDS).
The Restaurant module handles table management, order creation, item customization, and kitchen communication. When a guest with an active reservation orders from an outlet, the charge can be posted directly to their room folio —bridging Restaurant and Billing seamlessly.
Key Concept: Module
A Module is a functional area of Veridien that groups related features together. Modules appear as top-level sections in the sidebar. Your administrator decides which modules are enabled for your property and which staff roles can access them.
Housekeeping
Housekeeping tracks the cleanliness and maintenance status of every room. When a guest checks out, the room status flips to Dirty. A housekeeper cleans it and marks it Clean. A supervisor inspects it and marks it Inspected. Only then does the front desk see the room as ready to sell.
This status pipeline prevents the front desk from assigning a dirty room to an arriving guest. It also lets housekeeping managers see workload at a glance and assign rooms to specific attendants.
Rooms can also be placed Out of Order (OOO) for maintenance, which removes them from available inventory automatically.
Channel Manager
The Channel Manager connects your property to online travel agencies (OTAs) like Booking.com, Expedia, and others. It synchronizes two things: availability (how many rooms you have to sell) and rates (at what price).
When a reservation comes in from a channel, the Channel Manager creates it in Reservations and reduces availability across all connected channels to prevent overbooking. When you close a room type for a date range, the closure propagates outward.
Rate parity —keeping the same price across channels —is managed here. So is the mapping between your internal room types and the room types each OTA expects.
Analytics
Analytics aggregates data from every other module into reports and dashboards. Common metrics include:
- Occupancy rate —percentage of available rooms that are occupied
- ADR (Average Daily Rate) —average revenue earned per occupied room
- RevPAR (Revenue Per Available Room) —total room revenue divided by total available rooms
- Revenue by outlet —how much each restaurant, bar, or spa is generating
Analytics does not change data; it reads it. But the insights it provides drive decisions in every other module —adjusting rates, staffing housekeeping shifts, or renegotiating OTA commissions.
Key Concept: Permission
A Permission controls what a user can see and do within a module. Permissions are grouped into Roles (e.g., Front Desk Agent, Housekeeping Supervisor, General Manager). Your administrator assigns roles to each user account, and the system enforces access accordingly.
Sidebar Navigation
The Veridien sidebar is your primary way of moving between modules. It is organized into the following sections, each mapping to a module described above:
- Dashboard —a summary view showing key metrics and alerts for the current business date.
- Front Desk —arrivals, in-house, departures, room rack.
- Reservations —booking calendar, new reservation, group management.
- Restaurant —outlets, orders, KDS, table plans.
- Billing & Finance —folios, payments, night audit, tax setup.
- Housekeeping —room status board, task lists, inspections.
- Channel Manager —channel connections, rate mapping, sync logs.
- Administration —property settings, users, roles, room type configuration.
- Analytics —reports, dashboards, export tools.
Within each section, sub-pages let you drill into specific workflows. For example, under Front Desk you will find separate pages for the arrivals list, the departures list, and the room rack view.
Not seeing a sidebar item?
The sidebar is role-based. If your account does not have permission to access a module, that section will not appear in your sidebar. This is by design —it keeps the interface focused on what you need. If you believe you are missing access to a module you need, contact your property administrator.
How Data Flows
To reinforce the connections, here is a simplified flow of a typical guest stay:
- A guest books on an OTA. The Channel Manager receives the booking and creates a Reservation.
- Availability decreases across all channels automatically.
- On the arrival date, the Front Desk sees the reservation on the arrivals board.
- Housekeeping prepares the assigned room and marks it Inspected.
- The front desk agent performs check-in, creating a Folio in Billing.
- During the stay, the guest dines at the hotel restaurant. The Restaurant module posts charges to the folio.
- On departure, the front desk performs check-out. The folio is settled, the room flips to Dirty, and housekeeping begins its cycle again.
- Analytics records the revenue, occupancy, and source data for reporting.
Every step involves at least two modules communicating through shared data. That interconnection is the reason Veridien is a single integrated system rather than a collection of standalone tools.
Next Steps
Now that you understand how the modules connect, proceed to First Login to set up your account and orient yourself in the interface.