> ## Documentation Index
> Fetch the complete documentation index at: https://help.kwentra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# NTMP Financial Reporting

> kwentra sends your posted journal entries to the Saudi Ministry of Tourism every night. Set it up once per licence.

kwentra sends your posted journal entries to the Saudi Ministry of Tourism every night, through NTMP.

### **Business Value**

* Meets the Ministry's new financial reporting rule for licensed Saudi hotels.
* Sends entries every night. No file, no portal, no manual upload.
* Keeps your accountants' daily work the same.
* Holds back entries it cannot send correctly.
* Records every submission with its date, totals and the Ministry's reply.
* Reports each hotel on its own for a head office group.

### **Use Cases**

* A portal administrator approves kwentra's access request, and reporting can start.
* A chief accountant maps the accounts once, and entries go out every night.
* An accountant fixes a posted mistake with a reversing entry, as auditors expect.

### **How It Works**

| **Where:** Front Office → Settings Gear Sign → Integrations → NTMP - الرصد السياحي → Financial Reporting Setup |
| - |

Your guest and occupancy reporting to NTMP does not change. This adds your financial accounting entries.

For setting up the guest and occupancy feed, see [NTMP Integration Setup](/compliance-integrations/ntmp-integration-setup).

#### **What the Hotel Does, Once**

1. **Your NTMP portal administrator approves the access request.**
   * kwentra sends a request against your tourism licence number.
   * It appears in your NTMP facility portal.
   * Nothing can be reported until someone at the hotel approves it. The Ministry needs your consent, not ours.
2. **Your financial controller or chief accountant maps your accounts.** See [Map Your Accounts](#map-your-accounts) below.

You do not create or send any credentials. kwentra sets up the connection after you approve.

#### **Set Up Financial Reporting**

Add one entry for each licence. Fill in these fields:

| Field | What to enter |
| - | - |
| **Licence number** | The property's tourism licence number. |
| **Facility ID** | The facility ID for this licence. |
| **Facility secret** | The secret for this licence. After you save, leave it blank unless you are replacing it. |
| **Report to NTMP** | Turn it on. Nothing is reported for the property until it is on. |
| **Submission mode** | **Live** for a real property. Use **Test** only for trials. |
| **Submit at (hour, UTC)** | The hour each day the entries are sent. |

* **Submit at** is in UTC, not Saudi time. Saudi time is UTC+3. So 00:00 UTC is 3:00 AM in Saudi Arabia.
* Pick an hour after night audit ends. The day is then closed before it is reported. If you are not sure, keep the default.
* Turning off **Report to NTMP** does not stop the guest and occupancy feed.

Click **Save**, then **Test connection**. It checks that the details work and that the property is approved. If something is wrong, it tells you which one.

| **Note:** Copy the facility ID and secret with no space at the end. One extra space causes an authorisation error that does not say what is wrong. |
| - |

#### **Map Your Accounts**

| **Where:** Front Office → Settings Gear Sign → Integrations → NTMP - الرصد السياحي → Accounts Mapping |
| - |

The Ministry has its own standard list of accounts. Every entry kwentra sends must use one of them. So you match your accounts to the Ministry's accounts.

* Work through it with your financial controller or chief accountant.
* You do it once. The property reports nothing until it is done.
* The Ministry's accounts appear as soon as the screen opens. You do not need to load them.
* Several of your accounts can go under one Ministry account. This is normal when your chart has more detail.
* Leave a Ministry account empty if nothing is reported under it.

What you map depends on your chart:

| Your chart | What you map |
| - | - |
| American system (no analysis codes) | Your kwentra accounts. |
| British system, or a head office | Your main accounts. A main account covers every account under it. |

**On the screen**

* Under each Ministry account, type an account code or name in **Add main account by code or name**.
* Some main accounts have entries with different analysis codes. For these, the screen asks which code and which values to map.
* You can add another code to narrow it more. Or you can leave it to cover everything else.
* Values already mapped to another Ministry account show as taken.
* Each main account shows the codes it covers, or that it covers everything else.
* A warning box lists your accounts that are not mapped yet. Entries on those accounts are held back until you map them.
* A main account counts as mapped once any of its codes is mapped.
* Use **Search ministry accounts** to find an account. Tick **Show mapped only** to see your progress.

**On a spreadsheet**

A spreadsheet is often easier when you work with an accountant.

1. Click **Export CSV**. The file lists every Ministry account, even on a new property. It is your worksheet.
2. The accountant fills in your account codes. One code per column.
3. Add as many columns as a row needs. The import reads all of them.
4. Click **Import CSV** to load the file.

The first two columns come filled in: `ntmp_account` (the Ministry account code) and `ntmp_account_name`. The other columns depend on your chart.

**American system: no analysis codes**

The file has `kwentra_account_1`, `kwentra_account_2`, and so on. It has no `analysis_code` column. List every account that belongs under the Ministry account.

| ntmp\_account | ntmp\_account\_name | kwentra\_account\_1 | kwentra\_account\_2 | kwentra\_account\_3 |
| - | - | - | - | - |
| 111101 | Cash on Hand | 101310 | 101320 | 101330 |

Here, three cash accounts all go to the Ministry's **Cash on Hand**.

**British system and head office: analysis codes**

The file has an `analysis_code` column, then `main_account_1`, `main_account_2`, and so on.

Your hotel gives each department or team an analysis code (T code). For example, `T0=10` can be the Rooms department. `T0`, `T1`, `T2` and so on are analysis codes.

* Put the code in `analysis_code`. Every main account in the row uses it.
* The row takes only the entries with that code.
* To need two codes at once, put a comma between them: `T0=10,T1=120`.
* To map the row to several codes, put a space between them: `T0=10 T0=15`.
* Leave `analysis_code` empty for a main account with no analysis codes.

| ntmp\_account | ntmp\_account\_name | analysis\_code | main\_account\_1 |
| - | - | - | - |
| 510101 | Rooms Payroll - Salaries and Wages | T0=10 | 500001 |
| 521101 | F\&B Payroll - Salaries and Wages | T0=15 | 500001 |
| 610101 | A\&G Payroll - Salaries and Wages | | 500001 |

* Payroll account 500001 is on three rows.
* Its `T0=10` entries go to Rooms Payroll. Its `T0=15` entries go to F\&B Payroll.
* All its other entries go to A\&G Payroll. That row has no code, so it takes what is left.

**Give one account a different code**

Sometimes one account in a row uses another analysis code. Add a colon and that code after the account.

| ntmp\_account | ntmp\_account\_name | analysis\_code | main\_account\_1 | main\_account\_2 | main\_account\_3 |
| - | - | - | - | - | - |
| 510202 | Housekeeping Supplies Expense | T0=10 | 600103 | 600104 | 600105:T1=115 |

* 600103 and 600104 use the row's code, `T0=10`.
* 600105 uses `T1=115` instead of `T0=10`.

To use no code at all for one account, end it with a colon only, like `600104:`.

**Rules for the file**

* You can map one main account to several Ministry accounts only if each row has a different analysis code.
* If an entry fits more than one row, the row with the most codes wins.
* The import stops if you use a T code your chart does not have. It also stops for a value the main account never uses.
* If the same account and codes are on two rows, the import stops. It loads nothing and names the account.
* Export the file and import it again, and you get the same mapping back.

#### **Head Office Groups**

A head office runs several hotels in one kwentra. It reports each hotel to the Ministry on its own.

**Set it up**

1. On **Financial Reporting Setup**, add one row for each hotel licence.
2. On each row, choose the analysis code that marks this hotel. A hotel code can belong to one licence only.
3. Map your main accounts once. The mapping covers every hotel's copy of the account.

The hotel code is only used to split the entries by hotel. You cannot use it in the mapping, so the screen leaves it out.

**What is sent**

* Lines with a hotel's code go to that hotel's report.
* If a hotel's lines do not balance, kwentra adds one balancing line. It goes to **Due to Related Parties** (253201) by default.
* Lines with no hotel code belong to the head office. They are not sent, and no warning shows.
* An entry with no hotel code at all sends nothing. **Reporting Logs** shows it as head office only.

**City ledger**

Set up one head office AR department for each hotel, in the AR multiproperty mapping. Its account must be that hotel's own clearance account.

| Step | Sent to NTMP, under the hotel |
| - | - |
| The invoice is closed at the hotel | Debit City Ledger, credit Revenue |
| Head office imports it as an AR invoice | Debit Due to Related Parties, credit City Ledger |
| The client pays the head office | Nothing |

* kwentra stops a department mapping whose account belongs to another hotel.
* It warns you when several hotels share one department.
* These departments do not show in AR payment transfer.

| **Note:** Talk to your account manager before you set up a head office. |
| - |

#### **Check What Was Sent**

| **Where:** Front Office → Settings Gear Sign → Integrations → NTMP - الرصد السياحي → Reporting Logs |
| - |

**Reporting Logs** lists every batch sent to the Ministry, with its date, totals and the Ministry's reply.

* **Failed** means the Ministry refused the batch, or kwentra could not convert an entry.
* For a head office, it shows which hotels each entry went to. Or it shows that the entry stayed with the head office.

**Cancel a batch sent with the wrong mapping**

The Ministry accepted a batch, but the mapping was wrong. You can take it back:

1. Click **Cancel** on the accepted batch, and confirm.
2. kwentra sends a reversing batch. It has the same lines, with debit and credit swapped.
3. The original batch shows as cancelled, linked to its reversal.
4. Fix the mapping and save it. The batch's entries go out again with the new mapping.

* The result shows how many lines were reversed and how many entries will be sent again.
* It also shows how many entries you must post again in kwentra. These are entries sent before this update.
* You can cancel only a batch the Ministry accepted.

#### **The Ministry's Rules**

These rules come from the Ministry, not from kwentra.

| Rule | What it means |
| - | - |
| **Entries must balance** | Debits must equal credits. If a day does not balance, the Ministry rejects the whole day. |
| **Only the Ministry's accounts** | Every entry must use a Ministry account. This is why mapping comes first. |
| **No future dates** | An entry dated after today waits. It is sent on its own date. |
| **Periods close** | After the Ministry closes a period, entries in it cannot be sent. |
| **One currency** | Each property reports in one currency. Entries in another currency must be converted first. |
| **Posted entries only** | Drafts are not sent. |

#### **Tips for Your Accounting Team**

* **Post entries every day.** Drafts are not sent. After a period closes, old drafts may never be reported.
* **Tell kwentra when your chart of accounts changes.** A new account has no Ministry match yet. Its entries are held back until you map it.
* **Correct accounting mistakes with a reversing entry.** The Ministry does not let you edit a sent entry.
* **Sent with the wrong mapping?** Cancel the batch in **Reporting Logs**, then fix the mapping.

#### **Common Questions**

* **Does this replace our NTMP guest reporting?** No. Guest and occupancy reporting continues. This adds financial data.
* **Does our team do anything every day?** No. Keep posting entries as usual. Reporting runs overnight.
* **How long does setup take?** The portal approval takes minutes. Mapping usually takes one or two sessions with your chief accountant.
* **What if an entry cannot be sent?** It is held back, not sent wrong. The usual cause is an account that is not mapped yet.
* **Can we see what was sent?** Yes. Open **Reporting Logs**. It shows each batch with its date, totals and the Ministry's reply.
* **Who sees our financial data?** Only the Ministry of Tourism. It is sent under the credentials your property approved.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.