Ask a small hotel how their systems work and you'll usually hear about two: a PMS (property management system) running the operation — reservations, check-ins, room status — and an accounting package running the books. Between them sits the real system: a nightly or monthly ritual of exports, retyped summaries, and a bookkeeper reconciling one system's revenue against the other's.
The stitching is where hotels bleed. Charges posted in the PMS that never reach the ledger. City ledger balances that don't match receivables. A night audit that closes the operational day while the accounting month closes something slightly different. None of it is anyone's fault — it's the architecture.
What a PMS actually does
For a property of any size, the PMS is the operational heartbeat:
- Reservations and availability — who's arriving, which rooms are sold at what rate, what's left to sell tonight.
- Rates — a calendar of prices by room type, season, and day, because Tuesday in low season and a holiday weekend are different products.
- Front desk — check-in, check-out, walk-ins, extensions, room moves.
- Housekeeping — room status (dirty, clean, inspected, out of order) flowing between the desk and the floors, so a "clean" room means the same thing to both.
- The folio — the guest's running bill: nights, restaurant charges, laundry, the airport pickup — accumulating until settlement at checkout.
- Night audit — the end-of-day ritual that posts room charges, rolls the business date, and locks the day's figures.
- Channel connections — keeping availability and rates in sync with booking sites so the same room isn't sold twice.
Notice that nearly every one of these is also a financial event. A posted room night is revenue. A folio is a receivable in motion. A no-show fee, a deposit, a corporate account settled monthly — all of it belongs in the ledger. The PMS knows about these events first; the question is how they reach the books.
The cost of the gap
When PMS and accounting are separate products, the answer is: batch, export, retype, reconcile. That has three compounding costs.
Delay. The books trail the operation by however long the ritual takes. Management sees last week's position, decides on today's.
Translation loss. Summaries lose detail. "Room revenue: 48,200" in the ledger can't answer which rates, which channels, which corporate accounts — the detail stayed behind in the PMS. When the VAT return needs invoice-level backing, someone goes spelunking.
Reconciliation as a job. Two systems recording the same money will disagree — a refund entered in one, a correction in the other. Someone's month-end becomes finding and explaining the differences, forever.
What "one system" changes
When the PMS and the ledger are the same product, the financial event is the operational event:
- Night audit posts room revenue into the actual general ledger, with the tax treatment applied — not into an export file.
- A folio charge is a ledger entry from birth; checkout settlement hits cash or the guest's company account directly, and the city ledger is just receivables, aged and chased like any other.
- Occupancy, ADR, and revenue reports draw on the same numbers as the P&L — there is no "which system is right?" because there's one system.
- The restaurant's stock, the housekeeping supplies, purchasing from suppliers — the inventory and procurement side of a property — run in the same place, against the same books.
And the operational surfaces stay operational: housekeeping boards for the floors, a rate calendar for revenue decisions, reservation views for the desk. Integration doesn't mean making receptionists do accounting — it means the accounting happens because they did their job, not after.
Who this actually fits
Honesty matters here: global chains run enterprise PMS platforms with armies of integration middleware, and that's the right call at that scale. The one-system argument is strongest for independent properties and small groups — the 20-to-150-room hotel, the serviced apartment building, the guesthouse group — where there is no IT department to babysit integrations and the "finance team" is two people. For them, every stitched seam is a recurring monthly cost paid in evenings.
How BIZA helps
BIZA's hospitality module is a PMS inside the ERP: properties and room types, a rate calendar, reservations, front-desk operations, housekeeping boards, folios with charge posting, night audit, channel mappings, and occupancy/forecast/pickup reporting — all posting into the same double-entry ledger, tax engine, and receivables as the rest of your business, in English and Arabic.
See BIZA for hospitality, or talk to the team.