Why the Hotel PMS Decision Is Harder in Egypt Than the Brochures Suggest
Most PMS demos look the same: a clean calendar, a drag-and-drop booking grid, a dashboard full of green numbers. What separates a system that runs your hotel for the next five years from one you will be migrating away from in eighteen months rarely shows up in a 30-minute demo. It shows up in the details that are specific to operating in Egypt: e-invoicing rules from the Egyptian Tax Authority (ETA), a front desk that has to work in Arabic for staff and English for owners or auditors, room rates quoted in more than one currency, and an accounting team that needs the numbers to tie out every single night.
This checklist is written for the person who actually has to live with the decision — an owner, a general manager, or a finance manager — not for a procurement committee reading feature lists. Work through it before you sign anything, and bring it to the vendor call. A vendor who answers these questions clearly, with specifics, is telling you something. A vendor who talks around them is telling you something too.
Does It Actually Handle ETA E-Invoicing and E-Receipts, or Just "Support" Them?
'Supports e-invoicing' is a marketing phrase, not a specification. Egypt's e-invoicing and e-receipt requirements apply to businesses issuing tax invoices and receipts, hotels included, and the practical burden lands on whoever configures and runs the system day to day — not on the vendor's sales team.
- Ask to see an actual invoice generated by the system, submitted through the real ETA integration (not a screenshot or a mock-up).
- Ask what happens when the ETA portal rejects a submission or is unreachable — does the invoice queue and retry, or does it block check-out?
- Ask whether e-receipts for cash and card settlements are handled the same way as e-invoices, or as a separate, half-finished module.
- Ask who is responsible for keeping the tax configuration (rates, codes, exemptions) current as rules change — you, or the vendor.
Is Arabic a First-Class Language, or a Translation Layer Bolted on Top?
A surprising number of systems sold in Egypt were built for another market and translated afterward. That shows up in small but constant friction: date formats that flip when you switch language, reports that stay in English no matter what the user interface says, or an Arabic layout that was never actually mirrored (right-to-left) and just has Arabic labels pasted onto a left-to-right screen.
Front-office and housekeeping staff usually work faster in Arabic; owners, auditors and many finance teams want English for reports and correspondence. The system should let each user work in their own language without the guest folio, the invoice, or the night audit report changing meaning depending on who is logged in. Ask for a live walkthrough in Arabic, not just the English demo with a promise that 'Arabic is also available'.
How Does It Actually Handle Multi-Currency — Not Just Multi-Symbol?
Almost every PMS can print a dollar sign next to a number. Far fewer handle multi-currency the way a hotel with foreign OTA rates, foreign guests paying by card, and a local EGP-denominated ledger actually needs it handled.
| Question | Why it matters |
|---|---|
| Is there one base currency for accounting, with others converted at a stored rate? | Without a fixed base currency, the general ledger cannot balance across a multi-currency day. |
| What happens to a folio balance if the exchange rate changes mid-stay? | A guest checking in on day one and paying on day five should not see their bill move because of a rate the hotel never disclosed. |
| Can a rate be entered per currency pair, or does the system assume one is always worth exactly 1 unit of the other? | Assuming a 1:1 rate anywhere in the system is a common, expensive bug — ask this one directly. |
| Do OTA payouts and card settlements reconcile in their original currency before conversion? | Reconciling after conversion hides the exact spot where a shortfall happened. |
Can You Actually Watch the Night Audit Run, and Does the Ledger Balance Afterward?
Night audit is where a PMS either proves itself or quietly breaks. It is the process that rolls the business date forward, posts room charges for the night, and — in a properly built system — produces a set of numbers that reconciles with the front-desk cash count and the accounting ledger. Ask the vendor to run a real night audit in front of you, on a test property with a handful of open reservations, and show you the output.
- Does the audit produce a clear list of what it posted (accommodation, tax, service charge) per reservation, or just a total?
- What happens to a reservation that was not checked in, or a folio left open, when the business date rolls?
- Is there a double-entry accounting ledger behind the numbers, or does "accounting" mean a set of reports pulled from the same operational tables as the front desk?
- Can you close a business day, discover an error, and correct it without reopening every day since?
If a vendor cannot show you this live, on real data, be skeptical of every other claim in the demo. This is the one part of a PMS that touches every reservation, every payment and every tax figure — it is worth insisting on seeing it work before you commit.
Cloud or On-Premise: What Actually Fits a Hotel in Egypt Today?
The cloud-versus-on-premise debate is mostly settled for new hotel systems, but the reasons matter more than the label. A cloud PMS means the vendor pushes fixes and feature updates without an on-site visit, the front desk can be reached from a manager's phone during an incident, and — critically for e-invoicing — the system stays connected to the ETA infrastructure without a local server needing manual patching.
The trade-off owners worry about most is internet reliability. Ask specifically: what does the front desk do during an internet outage — can it still check guests in and post charges, syncing once the connection returns — or does the property stop functioning? A cloud system with no offline behavior at all is a real operational risk in areas with less stable connectivity; a cloud system that queues and syncs is not.
Channel Manager: Does Availability Actually Sync, or Just Rates?
Every vendor will tell you they "connect to OTAs." The failure mode that costs hotels real money is not the connection — it is a sync that updates rates but lags on availability, producing an overbooking on a sold-out night.
- Ask which channel manager or aggregator the system actually integrates with, by name, and whether that integration is direct or through a third party.
- Ask how fast availability pushes out after a booking or a cancellation — seconds, or a batch job that runs periodically.
- Ask what happens when two channels sell the same last room at nearly the same moment: does the system have a real inventory lock, or a race condition dressed up as a feature.
- Ask to see stop-sell and minimum-stay restrictions actually reach the OTA side, not just the internal calendar.
Data Migration and Total Cost of Ownership: The Two Questions Vendors Hope You Skip
The sale is easy. The migration and the second year of the contract are where most disappointment happens.
| Cost item | Ask about it explicitly |
|---|---|
| Migration of existing reservations and guest history | Who does the mapping, how long does it take, and what happens to bookings that arrive during the cutover. |
| Per-user or per-property licensing | Whether the price changes as you add front-desk terminals, properties or seasonal staff accounts. |
| Support hours and response time | Whether support is local-hours, 24/7, and in Arabic, especially for a night-audit failure at 2 a.m. |
| Training for new staff after go-live | Whether onboarding a new hire six months from now costs anything, or is self-service. |
| Data export on exit | Whether you can take your reservation and financial history with you if you ever leave — in a usable format, not a PDF dump. |
