Skip to main content

Document Validation

Prerequisites

New to Finovox API? Start with the Getting Started guide to learn the basics before diving into document validation.

Document validation provides automated compliance analysis that enables real-time decision-making in your workflows. It processes data extracted from documents to verify business compliance, eligibility criteria, and data consistency against your reference information, including customer files, internal databases, and business rules.

Difference from Fraud Analysis: While fraud analysis detects document manipulation and forgery, document validation verifies that documents meet your business logic and compliance requirements.

Types of Validations​

Correspondence Checks​

Verify data consistency between API input and document content:

  • Document classification matching: Confirm the detected category matches expectations
  • Data presence and accuracy: Verify submitted data matches extracted information

Examples: Name verification, expected category matching

Reference: See Document categories and Extracted fields for complete lists

Eligibility Checks​

Verify time-based and status-based conditions. Rules are automatically applied by Finovox based on the detected document category.

Examples: Is the contract expired? Is the payslip recent enough?

Specific Business Rules​

Custom validations defined during implementation, including external data comparisons.

Example: Is the invoice amount within approved limits?

Configuration

All checks are configurable. Contact your Customer Success representative for setup.

API Usage​

Basic Activation​

Add "document_validation" to analyse_type:

{
  "analyse_type": ["document_validation"]
}

Response Structure:

Each check returns true (passed) or false (failed). The global_document_validation field summarizes all checks: it returns false if at least one check fails, and true only when all checks pass.

{
  "name": "sample.pdf",
  "document_validation": {
    "global_document_validation": false,
    "...": true, // other validation checks
    "...": false
  }
}
note

Make sure that your subscription includes access to the document_validation analysis type.

Advanced Configuration​

To verify document classification or field values (correspondence checks), provide expected data in the extra field:

{
  "analyse_type": ["document_validation"],
  "extra": {
    "expected_category": "invoice",
    "expected_fields": {
      "holder_first_name": "Pierre",
      "holder_last_usual_name": "Dupont"
    }
  }
}

Response Structure:

  • expected_category (boolean): true if detected category matches expectation
  • <field_name>_match (boolean): true if extracted value matches provided value
{
  "name": "sample.pdf",
  "document_validation": {
    "global_document_validation": false,
    "expected_category": true,
    "holder_first_name_match": false,
    "holder_last_name_match": false
  }
}

In this example, the document quality is acceptable and the category matches expectations, but the holder first name and last name don't match the expected values, causing the global validation to fail.

Specific Business Rules​

If custom business rules were configured during your project implementation, provide the required data through the context_data field:

{
  "analyse_type": ["document_validation"],
  "extra": {
    "context_data": {
      "issuer_siren": "878381961",
      "customer_contract_status": "active"
    }
  }
}

Note: context_data is only required when custom business rules are configured. Contact your implementation team for your organization's specific schema.