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

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.affinda.com/feedback

```json
{
  "path": "/configuration/machine-validation",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Overview of Machine Validation

> Use Affinda's machine validation to automatically approve high-confidence documents and route low-confidence cases to human reviewers for full automation.

Validating the data extracted from documents is a critical part of the Affinda workflow, ensuring the accuracy and reliability of data sent downstream. Machine Validation assesses whether extracted data meets predefined conditions and ensures that user review is only required by exception to deliver significant efficiency gains.

## Key Components of Machine Validation

Affinda utilizes two primary methods for machine validation, often most effective when combined.

<Card title="Data Mapping">
  Data mapping is a powerful capability aimed at enhancing the quality and accuracy of data extracted from documents. With data mapping configured, the extracted data can be mapped against a list of known options from the customer's own data to validate that it meets expected values. This provides greater confidence in the data extracted by the model and ensures seamless integration with downstream systems.

  Unmatched data triggers user review, prompting manual correction or alternative actions.

  See [Picklists](/configuration/picklists) for more information.
</Card>

<Card title="Validation Rules">
  Business-specific rules and logic can be customized based on document type, fields extracted, and unique use cases. Validation rules offer flexibility, accommodating criteria such as:

  * Mandatory fields
  * Model confidence thresholds
  * Expected data formats
  * Relationships between document fields
  * Other custom business logic

  See [Validation Rules](/configuration/validation-rules) for more information.
</Card>

## Machine Validation Settings

Auto-confirmation can be enabled at a Workspace level in the **Workflow Settings.** When enabled, documents that pass all validation rules are automatically confirmed, eliminating the need for manual review.

<img className="block dark:hidden border-2 border-gray-300 rounded-lg" src="https://mintcdn.com/affinda-44/MRSqPveAb_A2ktlh/images/validationsettinglight.png?fit=max&auto=format&n=MRSqPveAb_A2ktlh&q=85&s=4de3970b3ce1d817f09bed20942a09f2" alt="Validation Settings" style={{ width:"70%" }} width="1668" height="1026" data-path="images/validationsettinglight.png" />

<img className="hidden dark:block border-2 border-gray-300 rounded-lg" src="https://mintcdn.com/affinda-44/MRSqPveAb_A2ktlh/images/validationsettingdark.png?fit=max&auto=format&n=MRSqPveAb_A2ktlh&q=85&s=2ee28c9bbdc5baa36c7c494ff5b02eae" alt="Validation Settings" style={{ width:"70%" }} width="1668" height="1024" data-path="images/validationsettingdark.png" />

<Info>
  Auto-confirmed documents are not used in Model Memory.
</Info>
