NTMP has moved into the general ledger
When most hoteliers in the Kingdom first heard about the National Tourism Monitoring Platform, they thought of it as a front office matter: bookings, check-ins, occupancy. That picture is now incomplete. The Ministry of Tourism also asks hotels for financial information, and that reaches into the general ledger.
Over the past months, I have sat with finance teams across Saudi Arabia, from single independent hotels to multi-property groups. The questions are remarkably consistent. Which of our accounts go where? What happens if a batch is rejected? How do we prove what we sent?
This piece shares what I have learned from those conversations. I will be honest: most of the difficulty is not technical. It is about structure, discipline and records. Get those three right and NTMP financial reporting becomes routine.
Lesson 1: Start with the chart of accounts, not the submission
NTMP publishes its own chart of accounts for each facility. Your hotel has its own chart too, often shaped by an operator’s standard, the USALI framework or years of local habit. The two rarely line up neatly.
The instinct is to sort this out at month-end, when the report is due. That is the most expensive moment to do it. Under pressure, someone decides whether a line belongs under one NTMP category or another, and that decision changes from month to month.
The teams that report smoothly do the mapping once, up front. Every internal GL account is linked to its NTMP number before the first submission. After that, every journal entry is categorised correctly by design. There is no guesswork and no mismatch between what you book and what the Ministry receives.
My advice: treat the mapping as a finance project in its own right. Involve the person who knows your chart best, document the decisions, and review the mapping whenever you add new accounts.
Lesson 2: A batch that does not balance should never leave the building
Every accountant knows debits must equal credits. Yet unbalanced batches are one of the most common reasons financial submissions go wrong. A missing line, a rounding difference or an entry posted to the wrong period is enough.
The principle I share with every team is simple: the check belongs before submission, not after rejection. If a batch does not balance, the system should refuse to send it. Fixing an error inside your own books takes minutes. Explaining it after it has reached the regulator takes far longer.
Hotel groups face a second challenge. A single journal entry often touches several properties, such as a shared service charge, a central purchase or a group-level allocation. Each facility reports to NTMP separately, so that entry has to be split correctly across facilities.
When the split is done by hand, consolidation errors creep in. When it is automated, with each facility’s share calculated and balanced, the data flows to NTMP cleanly, however many properties you run.
Lesson 3: Compliance is something you can prove
Sending data is only half the job. The other half is being able to show, months later, exactly what was sent, when, and what the Ministry replied. In my experience, this is the part hotels most often overlook until someone asks.
Four habits make the difference:
- Keep a log for every facility. Every request and every response should be recorded, so any submission can be traced in seconds.
- Make recovery easy. Connections fail, and batches get rejected. A failed batch should be resent with one click, not rebuilt from scratch.
- Test without risk. New mappings and setups should be tried in a test mode that cannot send live data by accident.
- Lock what has been filed. Once an entry has been submitted, it should not be possible to quietly reset it to draft. Corrections should be made openly, with a clear trail.
That last point matters more than people expect. Regulators trust records that cannot be rewritten after the fact, and your own auditors will appreciate it too.
How we built these lessons into Web Prol’IFIC Back Office
At Prologic First, we designed our NTMP financial data integration around exactly these three lessons.
The integration pulls the NTMP-published chart of accounts for each facility and lets your team map internal accounts to NTMP numbers, so every GL entry is categorised before it is sent. It refuses to send an unbalanced batch, and it splits journal entries across facilities automatically for hotel groups.
Every request and response is kept in a per-facility log, with one-click resend for failed batches. A test mode lets you validate your setup without ever sending live data, and filed entries cannot be reset to draft, in line with the Ministry’s compliance expectations.
The result is that finance teams spend their time on the numbers, not on moving them.
Five questions to ask your team this month
Whatever system you use, these questions will tell you how ready you are:
- Is every GL account mapped to an NTMP account, and is that mapping documented?
- What stops an unbalanced batch from being submitted?
- If you run more than one property, how are shared entries split between facilities?
- Could you show an auditor every submission from last quarter, with the Ministry’s response?
- Can a filed entry be changed without leaving a trace?
If any answer starts with “it depends on who is on shift”, that is your starting point.
A closing thought
NTMP is part of a bigger story. Saudi Arabia is building one of the most data-driven tourism sectors in the world, and the hotels that thrive will be those whose own data is clean, structured and trustworthy. Reporting to the Ministry is simply the most visible test of that.
If your team is working through NTMP financial reporting, I am always happy to compare notes. You can reach me at Imran@prologicfirst.ae
By Imran Shaikhnag,
Regional Manager, KSA, Prologic First