> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/end-user-and-partner-section/end-user-section/validation-screen/fuzzy-data.md).

# Fuzzy Data

### **Overview**

Fuzzy Data fields allow users to populate related fields based on approximate matches from master data. These fields are identified by a **blue icon** next to them.

<figure><img src="/files/nDa7meUmgBHhSnMt8K4p" alt="Fuzzy Data Field Icon"><figcaption></figcaption></figure>

### **Functionality**

#### **What Do Fuzzy Data Fields Do?**

* They populate related fields based on their value or input.
* The three standard fields using Fuzzy Data are:
  * **Purchase Order**
  * **Supplier**
  * **Vendor ID**

#### **Using Fuzzy Data Fields**

1. **Selecting a Purchase Order**
   * Clicking the **blue icon** next to the Purchase Order field opens a **selection window**.

     <figure><img src="/files/LEOCtURJML9P7c8VESEN" alt="Fuzzy Data Selection Window"><figcaption></figcaption></figure>
   * This window contains a table with all purchase orders from the **master data lookup table**.
   * Enabling the **"Display all columns"** option shows additional details.
   * Select a **Purchase Order** and click **Proceed**:
     * If the system finds a Purchase Order in the document, it filters for it automatically.
     * If no match is found, you can **create custom filters** to find the correct Purchase Order.
     * Multiple filters can be added; enabling **"Match all filters"** ensures that all conditions must be met.
     * Available filter options:
       * **Smart**
       * **Contains**
       * **Exact**
       * **Starts with**
       * **Ends with**
   * A button next to **Proceed** allows users to **create a new task/notification**.
2. **Selecting a Supplier or Vendor ID**
   * The process is the same as for Purchase Orders.
   * The difference is that **Supplier and Vendor ID fields use the Supplier Master Data Table** instead of the Purchase Order Header Master Data Table.

#### **Field Population Hint**

* If a field is populated using Fuzzy Data rather than being extracted from the document, a **small hint or info icon** appears to indicate that the data was **not extracted from the document** but filled based on master data.

### **Administrator Configuration**

{% content-ref url="/pages/CKwzZsqd3KhlNuIyXLhM" %}
[Fuzzy Data Configuration with Master Data](/administration-and-setup/setup/document-types/fuzzy-data-configuration-with-master-data.md)
{% endcontent-ref %}

{% content-ref url="/pages/3M4aw7OUcF1VAFB2uqV7" %}
[Fuzzy Data Configuration with List of Values](/administration-and-setup/setup/document-types/fuzzy-data-configuration-with-list-of-values.md)
{% endcontent-ref %}

{% embed url="<https://www.youtube.com/watch?v=vT5HuGjAYV0>" %}


---

# 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.docbits.com/end-user-and-partner-section/end-user-section/validation-screen/fuzzy-data.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.