Contact Info
What should Saudi hospitality groups get right in an ERP project?
Saudi hotel, restaurant and catering groups need ERP processes that respect how invoices are issued under ZATCA rules at the POS, PMS and head office, handle block bookings and deposits around Hajj and Umrah seasons, track Saudization and payroll across outlets, and work in Arabic with Hijri dates where needed. I design that back office remotely, compare platforms independently and support the implementer through testing and go-live.
Last reviewed by Vikas Saroj
Hospitality in Saudi Arabia has been expanding alongside the national push to grow tourism, entertainment and events. New hotels, dining concepts, venues and catering operations are opening across Riyadh, Jeddah, the holy cities and new destinations, and many groups are growing faster than their finance and supply processes.
I help Saudi groups design the layer that sits behind the guest systems: which system issues each invoice, how POS and PMS sales reach the ledger in riyals, how central purchasing and a production kitchen supply the outlets, and how workforce data supports both payroll and nationalization reporting.
Reservations, folios and orders stay in the PMS and POS. The ERP brings the money, stock and people together so owners can see each outlet and property clearly.
For Saudi groups I concentrate on compliance-sensitive invoicing, seasonal revenue, supply and workforce data across properties and outlets.
Deciding which documents the POS, PMS and ERP each issue, from simplified invoices at the counter to standard invoices for corporate and event clients, and what each vendor must confirm about ZATCA compliance.
Designing contracts, advance payments, allotments and receivables for agents and service companies that book rooms and meals around pilgrimage seasons, events and holidays, with clear release and settlement rules.
Production planning, batch costing and transfers for a central kitchen supplying restaurants, hotel outlets and catering contracts, including large event orders that need their own costing and invoicing.
Requirements so employee records carry the nationality, role and location details that nationalization reporting needs, while payroll, GOSI contributions and allowances post to the right outlet.
Defining Arabic and bilingual layouts for invoices, statements, purchase orders and contracts, plus Hijri date handling where it matters, and testing them on every shortlisted platform.
Scripted demos built on your seasonal, invoicing and central kitchen scenarios, scored without any vendor incentive, then a review role over the implementer while testing and early month-ends run.
An ERP for hospitality should make these numbers available without a spreadsheet. I design the data model and reports around them from the start.
Review properties, outlets and invoicing
Requirements and shortlist in Arabic
Rollout timed around the seasons
In hospitality, most tax invoices are not created by finance at all. A restaurant receipt comes from the POS, a hotel folio from the PMS, a banquet or catering invoice may come from a sales tool, and only corporate billing and intercompany invoices start in the ERP. Under ZATCA's e-invoicing rules, each of those systems may carry obligations for how invoices are generated, formatted, stored and, for many taxpayers, shared with the authority.
That makes the first design question who issues what. I build a responsibility matrix listing every invoice and credit note type, the system that creates it, whether it is a simplified invoice to a consumer or a standard invoice to a business, and how compliance is achieved. Each POS, PMS and ERP vendor is then asked to confirm, in writing, how their product meets the requirements that apply to you.
The ERP still needs the results: daily sales and VAT from each source, with credit notes and voids reconciled. I test scenarios such as a room folio transferred to a company account, a refund on a later day and an event deposit invoiced in advance. Applicability and integration waves are confirmed with your tax advisor. The general Saudi tax picture is on my Saudi ERP consultant page.
Hotels and caterers serving pilgrims in Makkah and Madinah work to a calendar shaped by Hajj and the Umrah seasons, and to a different rhythm from city business hotels. Rooms and meals are often contracted in blocks with licensed service companies and agents, with advance payments, allotments, release dates and settlements after the season. Getting this right is both a commercial and a service responsibility to the guests who travel for worship.
In the ERP, these arrangements become contracts with customers, deposit liabilities, invoices against delivered nights or meals, and receivables that may run after the season closes. I design how contract terms are recorded, how deposits are applied, how unused allotments are treated under each agreement, and how aging is reported by agent. The PMS still manages rooming lists and stays.
Elsewhere in the Kingdom, peaks follow events, school holidays, Ramadan evenings and entertainment seasons. Catering and venue businesses may see their largest orders around these periods. I make sure the cost side follows: temporary staff, extra purchasing and central kitchen capacity should all be visible against the revenue they support. Hotel-specific PMS design is covered on ERP for hotels.
Workforce planning in Saudi hospitality runs alongside nationalization requirements under the Nitaqat program, which looks at the share of Saudi nationals employed by an establishment and its activity. Requirements for particular roles in hospitality and food service have been introduced over time. Your HR and legal teams interpret those rules; my role is to make sure the data they need exists and is accurate.
That means employee records with nationality, job title, establishment and location, linked to the entity that employs them. Payroll may run in a dedicated HR system connected to the government platforms for wage protection and social insurance, while the ERP receives payroll journals by outlet and department. I specify that interface so labor cost includes allowances, housing and GOSI contributions, not only base salary.
Seasonal staff complicate the picture. Pilgrimage-season hotels, event caterers and new openings bring in workers for limited periods, sometimes through agencies. Agency invoices should be matched to rosters or approved hours and charged to the outlet that used them. Clear workforce data also helps when opening a new property, because the group can see its nationalization position before it hires rather than afterwards.
Saudi restaurant and catering groups frequently centralize production. One kitchen may prepare dishes for several branches, hotel outlets, airline or corporate catering contracts and large event orders. Each of those customers expects consistent quality, and each has a different cost and pricing model, so production and costing in the ERP have to keep them apart.
I design recipes and sub-recipes with yields, production orders planned from branch orders and catering schedules, batches labeled with use-by dates, and agreed prices for each branch transfer. Catering contracts get their own price lists and invoicing rules, and large event orders are costed before acceptance so the sales team knows the margin. Supplier documentation, such as halal and health certificates, is held against the supplier record with expiry reminders for the food safety team.
Much of the ingredient supply is imported or bought from local distributors, so landed costs and price agreements matter. Outlet-level food cost and recipe control are explained on ERP for restaurants, and anyone also supplying packaged goods to supermarkets should read my Saudi food and beverage ERP page.
Many Saudi hospitality documents are written first in Arabic, from tax invoices to supplier contracts and employee letters. Some agreements and government interactions reference Hijri dates, so templates and reports may need both calendars. I include Arabic and bilingual output in every vendor demo, because right-to-left layout quality differs between platforms and add-ons.
The platform shortlist usually includes Zoho, Odoo, ERPNext and Microsoft Dynamics 365, each tested against your own scenarios: a POS day with credit notes, a pilgrimage-season deposit settlement, a catering order from central kitchen to invoice and an Arabic statement to an agent. I also ask each vendor and implementer how they handle ZATCA requirements and where their connectors come from. Groups moving off spreadsheets or a basic accounting tool can plan the switch with my data migration approach.
I schedule remote workshops on Saudi working days and hours, and kitchen and outlet teams get short recorded walkthroughs they can watch between services. On-site visits can be considered by arrangement. The group-level model is described on ERP for hospitality groups, and my wider Saudi material is on the Saudi Arabia hub.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
Not necessarily. Consumer receipts are often issued by the POS, folios by the PMS and business invoices by the ERP. What matters is that every system that issues invoices meets the requirements that apply to you. I map which system issues each document and ask each vendor to confirm compliance, with your tax advisor deciding applicability.
Each contract is recorded with its allotment, rates, deposit terms and release dates. Advance payments sit as liabilities until nights or meals are delivered, invoices follow actual consumption under the agreement, and receivables are tracked by agent. The PMS manages the rooming list, while the ERP manages the money.
It can hold the employee data needed, such as nationality, role and establishment, and produce internal reports from it. Official calculations and submissions happen on government platforms and are interpreted by your HR team. I make sure the data is complete and consistent so those reports are reliable.
My workshops are in English, and I define Arabic requirements for documents, templates and reports, then test them on each platform with your bilingual team. Arabic output is reviewed by your staff, because layout quality and terminology are best judged by native readers.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.