> For the complete documentation index, see [llms.txt](https://docs.identomat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.identomat.com/platform-concepts/person-data-mapping.md).

# Person data mapping

### **How it works**

Person data fields — such as name, date of birth, and personal number — are normally populated automatically via the ID document step through OCR, MRZ, NFC, or QR/Barcode extraction. Person data mapping allows clients to populate these same fields through a User questionnaire step instead, covering flows **where document scanning is not required** or **where the client already holds some of the applicant's data.**

When mapping is enabled on a User questionnaire step, individual questions can be linked to specific Person data fields. Answers submitted by the applicant populate those fields in the session's Person data section and become available for downstream identity verification checks.

This is a general-purpose feature and is not tied to any specific verification provider.

***

#### **Field sources and precedence**

Person data fields can originate from multiple sources within the same session. Each field displays a source tag so operators can identify where the value came from:

<table><thead><tr><th width="199.984375">Tag</th><th>Source</th></tr></thead><tbody><tr><td><strong>OCR /</strong> <strong>MRZ</strong> / <strong>NFC / QR</strong> </td><td>Extracted automatically from the document via OCR, MRZ, NFC, or QR</td></tr><tr><td><strong>User review</strong></td><td>Edited by the applicant during document data review after scanning</td></tr><tr><td><strong>User input</strong></td><td>Entered by the applicant in the User questionnaire</td></tr><tr><td><strong>Client provided</strong></td><td>Preset by the client via API or Configuration before the session started</td></tr><tr><td><strong>Operator</strong></td><td>Entered or corrected by the operator during review</td></tr></tbody></table>

When a session includes both an ID verification step and a mapped User questionnaire step, the following precedence applies:

* Document data takes precedence over questionnaire-mapped values for any overlapping field.
* Fields not populated by the document step are filled from the questionnaire-mapped values.
* Both values are stored and visible in session details.

Field change history is accessible via tooltip on each field and is preserved across all edits for audit purposes.

***

#### **Session routing**

Sessions with "Map to Person data" enabled are automatically routed to **Manual check** on completion, regardless of other step outcomes.&#x20;

***

#### **Enabling the feature**

**How to enable:** Turn on **Map to Person data** in the User questionnaire step settings in the Configuration builder.

When enabled, a Person data field selector appears beneath each compatible question. Not every question needs to be mapped — mapping is optional per question.

**Compatible question and field types:**

<table><thead><tr><th width="299.40625">Question type</th><th>Mappable Person Data fields</th></tr></thead><tbody><tr><td>Short answer (Free text or Number)</td><td>First Name, Last Name, Middle Name, Father's Name (Eng./Local), Place of Birth, Document Number, Personal Number, Authority, Address, State</td></tr><tr><td>Date</td><td>Date of Birth, Document Expires On, Document Issuing Date</td></tr><tr><td>Radio</td><td>Sex</td></tr><tr><td>Dropdown</td><td>Citizenship, Nationality, Document Issuing State</td></tr></tbody></table>

Checkbox, File Upload, and Attachment question types cannot be mapped to Person data fields.

A Person Data field can **only be mapped to one question** within the same configuration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.identomat.com/platform-concepts/person-data-mapping.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.