> ## 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.

# Guest Profile — Identity Number Required by Document Type

> Selecting a Document Type on a guest profile now requires the matching identity number — Passport number for Passport, Driving license number for Driver License, ID number for the rest.

Selecting a document type on a guest profile now requires the identity number that matches it.

### **Business Value**

* Prevents identity numbers being typed into the wrong field.
* Improves data quality for police and tourism reporting.
* Blocks incomplete identity data at the point of entry.
* Applies everywhere a profile is created or edited.
* Requires no setup — the rule is always on.

### **Use Cases**

* Receptionist selects Passport and must enter the passport number itself.
* Front office agent cannot save a profile with a blank identity number.
* Compliance officer exports guest identity data with the correct number per document.

### **How It Works**

| **Where:** Front Office → Guest Profile • Back Office → Profile form |
| - |

A guest profile records a **Document Type** and, separately, the number that goes with it. Each document type has its own field for that number:

| Document Type | Required number field |
| - | - |
| Passport | **Passport** |
| Driver License | **Driving license number** |
| Identity Card, Residency / Iqama, Visitor, Family, GCC, Other | **ID number** |

Until now all of these fields were optional and unchecked, so staff could select **Passport** and type the number into **ID number**, or leave it blank altogether — producing bad data for police and tourism reporting.

Now, when a document type is selected, the number field that matches it becomes required — and only that one.

#### **Only the Matching Field Counts**

Filling a different identity field does not satisfy the rule. Selecting **Passport** and entering the number into **ID number** is still rejected; it must go in the **Passport** field.

#### **When the Rule Applies**

* The rule runs on both **create** and **edit** of a profile.
* If **no** document type is selected — the default — nothing is required and all identity fields stay optional, exactly as before.
* Saving is blocked with a message on the required field:
  * Passport — *Passport is required for the selected document type.*
  * Driver License — *Driving license number is required for the selected document type.*
  * All others — *ID number is required for the selected document type.*

#### **Other Ways Identity Data Arrives**

The same mapping is followed by the flows that fill these fields for you:

* The **ID scanners** that auto-fill identity data
* The **guest portal** and **capture ID** flows

#### **What Is Not Affected**

* **Existing profiles are not re-validated** and there is no data migration. An older profile with a mismatched number is only required to comply the next time it is edited.
* Profiles created by **integrations** — Online Booking and channel/OTA — are not blocked.
* Profile **import** is not blocked.

| **Note:** This rule is always on and is independent of the Mandatory Fields feature. If your property also makes **Document Type** mandatory there, this rule then guarantees the right number is filled in as well. |
| - |


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