# CheckFile.ai — Comprehensive Technical Documentation

> AI-powered document validation platform for regulated industries. Cross-document validation, fraud detection, and compliance automation.

Last updated: 2026-03-03

---

## 1. Overview

CheckFile.ai is a European B2B SaaS platform that automatically validates complex business files composed of multiple interdependent documents. The platform is designed for regulated industries where document verification is critical: banking, insurance, leasing, legal, real estate, and more.

### Mission

Eliminate manual document verification errors, reduce compliance costs by 50x, and accelerate business processes from days to seconds — while maintaining the highest standards of data privacy and regulatory compliance.

### Core Value Proposition

Traditional document verification solutions (OCR tools, single-document verifiers) check documents in isolation. CheckFile is fundamentally different: it validates the relationships BETWEEN documents within a business file. For example, it verifies that the company name on a KBIS matches the company name on a contract, that contract amounts match quote amounts, and that identity documents belong to authorized signatories.

### Key Numbers

- 93% time saved vs manual document verification
- ~0.30 EUR per file processed (vs 5-15 EUR manual cost)
- 100+ document types supported
- <2s average processing time per document
- 99.7% accuracy on standard document types
- 99.9% API uptime SLA
- 24/7 availability
- 1-3 week deployment time
- EU-hosted (AWS Paris), GDPR native

---

## 2. Architecture

### Design Principles

CheckFile is built on an API-first, cloud-native architecture designed for security, scalability, and compliance.

### Deployment Options

1. **Cloud (SaaS)**: Fully managed, hosted on AWS Paris (eu-west-3). No infrastructure management required. Default for Starter and Business plans.

2. **On-premises / Private Cloud**: Enterprise customers can deploy CheckFile within their own infrastructure (AWS, Azure, GCP, or bare metal). Full data sovereignty. Dedicated support for deployment and maintenance.

3. **Hybrid**: Cloud processing with on-premises document storage. Documents never leave the customer's infrastructure; only extracted metadata is processed in the cloud.

### Technology Stack

- AI engine: Anthropic Claude for document understanding and reasoning
- OCR pipeline: Multi-engine approach for maximum extraction accuracy
- Business rules engine: Configurable, partner-specific validation rules
- External enrichment: Real-time API calls to official registries
- Infrastructure: AWS (Paris), AES-256 encryption, TLS 1.3
- API: RESTful, JSON responses, webhook support, batch processing

### Processing Pipeline

1. Document ingestion (multi-format: PDF, JPEG, PNG, TIFF, scans, photos)
2. Document classification and type detection
3. OCR and data extraction
4. Named Entity Recognition (NER) for key fields
5. Cross-document validation against business rules
6. External enrichment via official APIs
7. Fraud pattern analysis
8. Confidence scoring and anomaly reporting
9. Structured result delivery (JSON API response or webhook)

---

## 3. Document Types

CheckFile supports 100+ document types, organized into the following categories:

### Identity Documents
- National identity cards (French CNI, German Personalausweis, Dutch ID, etc.)
- Passports (all EU countries)
- Residence permits (titre de sejour, Aufenthaltstitel, etc.)
- Driver's licenses
- Visa documents

### Financial Documents
- Bank statements (relevés de compte, Kontoauszüge)
- Tax returns (avis d'imposition, Steuerbescheid)
- Pay slips (bulletins de paie, Gehaltsabrechnung)
- Profit & loss statements
- Balance sheets
- Cash flow statements
- Audit reports
- VAT declarations

### Corporate Documents
- KBIS / company registration extracts (France)
- Handelsregisterauszug (Germany)
- KVK uittreksel (Netherlands)
- Articles of association (statuts)
- Beneficial ownership declarations (Declaration des beneficiaires effectifs)
- Powers of attorney (procurations)
- Board resolutions (proces-verbaux)
- Annual reports
- Shareholders agreements

### Address Proof
- Utility bills (electricity, gas, water, internet)
- Tax notices (taxe fonciere, taxe d'habitation)
- Insurance certificates
- Bank correspondence
- Government correspondence

### Professional Documents
- Professional licenses
- Diplomas and certifications
- Insurance attestations (RC Pro)
- Kbis artisan / registre des metiers
- URSSAF attestations
- Certificates of good standing

### Contracts & Agreements
- Leasing agreements
- Loan contracts
- Insurance policies
- Rental agreements (baux)
- Sales contracts
- Service agreements
- Quotations and invoices

---

## 4. Verification Process

### Step-by-Step Workflow

#### Step 1: Upload
Documents are uploaded via the REST API (multipart/form-data), the web dashboard (drag-and-drop), or through integrated connectors (Salesforce, Google Drive, SharePoint, etc.). All common formats are accepted: PDF, JPEG, PNG, TIFF, scanned documents, and photos.

#### Step 2: Classification
CheckFile's AI automatically identifies the document type (identity card, bank statement, KBIS, contract, etc.) without requiring manual labeling. This classification step uses a trained model with 99%+ accuracy on supported document types.

#### Step 3: OCR & Data Extraction
Multi-engine OCR extracts text and structured data from each document. Named Entity Recognition (NER) identifies key fields: names, dates, amounts, addresses, company identifiers (SIREN/SIRET), and more. Extraction works across all supported EU languages.

#### Step 4: Cross-Document Validation
This is CheckFile's core differentiator. The platform validates consistency BETWEEN documents in the file:
- Does the company name on the KBIS match the contract?
- Does the contract amount match the quote?
- Is the signatory listed as an authorized representative?
- Are dates consistent across documents?
- Do financial figures reconcile between bank statements and declarations?

#### Step 5: External Enrichment
CheckFile verifies extracted data against official registries and APIs:
- Pappers: Company information, financial data, legal status (France)
- INSEE / SIRENE: Company registration validation (France)
- Infogreffe: Legal proceedings, company status (France)
- National registries in Germany, Netherlands, and other EU countries
- Sanctions lists and PEP databases (via partners)

#### Step 6: Fraud Detection
AI-powered fraud analysis checks for:
- Document alteration (modified amounts, dates, or names)
- Synthetic documents (AI-generated or fabricated)
- Template inconsistencies (wrong fonts, layout anomalies)
- Metadata anomalies (creation dates, software signatures)
- Cross-document fraud patterns (coordinated falsifications)

#### Step 7: Result Delivery
A structured JSON response is returned with:
- Overall status: compliant / non_compliant / needs_review
- Confidence score (0-1)
- List of anomalies with severity levels (high, medium, low)
- Detailed explanation for each anomaly
- Documents involved in each anomaly
- Processing time
- Full audit trail

---

## 5. Use Cases with Examples

### Banking KYC Onboarding

**Scenario**: A bank needs to onboard a new corporate client. The compliance team receives identity documents, company registration, proof of address, and beneficial ownership declarations.

**Without CheckFile**: An analyst manually verifies each document (15-30 minutes), checks company status on Infogreffe, cross-references names between documents, and files a compliance report. Error rate: 8-15%.

**With CheckFile**: The entire file is uploaded via API. In under 60 seconds, CheckFile verifies all documents, cross-references company names, checks beneficial ownership against registries, validates addresses, and returns a structured compliance report with anomaly details. Error rate: ~0%.

**Regulations addressed**: AMLD6, KYC/AML, RGPD/GDPR

---

### Insurance Claims Verification

**Scenario**: An insurer receives a claim with a police report, medical certificates, repair estimates, and identity documents.

**Without CheckFile**: A claims handler manually reviews each document, checks for consistency between the police report and repair estimate, verifies the insured's identity, and flags suspicious claims. Processing time: 20+ minutes per claim.

**With CheckFile**: The claims file is processed in under 1 minute. Cross-validation detects inconsistencies between the incident description and repair estimates, flags documents with alteration patterns, and verifies the insured's identity. The claims handler receives a pre-analyzed report, focusing only on flagged items.

**Regulations addressed**: RGPD/GDPR, insurance regulation compliance

---

### Real Estate Rental Applications

**Scenario**: A property management company receives rental applications with identity documents, employment contracts, pay slips, tax returns, and bank statements.

**Without CheckFile**: Staff manually verifies 10-15 documents per application, calculating debt-to-income ratios, checking employment status, and verifying identity. Each application takes 20-40 minutes.

**With CheckFile**: The entire application file is validated in under 1 minute. CheckFile verifies income consistency between pay slips and tax returns, validates employment status, checks identity documents, calculates affordability ratios, and flags any forgery indicators (common in rental fraud).

**Regulations addressed**: RGPD/GDPR, French rental law (loi ALUR)

---

### Equipment Financing & Leasing

**Scenario**: A leasing company (GRENKE, SIEMENS, LEASECOM) receives financing applications with contracts, quotes, KBIS, identity documents, and financial statements.

**Without CheckFile**: Back-office analysts verify each document against partner-specific requirements. Each partner has different rules (required documents, amount thresholds, eligibility criteria). Processing time: 15-30 minutes per file.

**With CheckFile**: Partner-specific rule sets are pre-configured. CheckFile validates the complete file against the correct partner's requirements, cross-references contract amounts with quotes, verifies company eligibility, and flags missing or non-compliant documents. Processing time: under 1 minute.

**Regulations addressed**: AMLD6, KYC/AML, partner-specific compliance

---

### Legal Due Diligence

**Scenario**: A law firm conducts KYC on a new client for a corporate transaction. Documents include identity documents, beneficial ownership structures, company registrations, and financial statements.

**Without CheckFile**: An associate or paralegal manually compiles and verifies the KYC file, checking each document against anti-money laundering requirements while maintaining professional secrecy. Time: 30-60 minutes per client.

**With CheckFile**: The KYC file is processed with professional secrecy protections (isolated processing, no staff access to documents, immediate deletion). CheckFile verifies all documents, cross-references beneficial ownership, and generates a compliance report that the lawyer can review and sign off on.

**Regulations addressed**: AMLD6, professional secrecy (Art. 226-13 French Penal Code), RGPD/GDPR

---

### HR Employment Verification

**Scenario**: An HR department needs to verify documents for a new hire: identity, diplomas, previous employment certificates, and social security attestations.

**Without CheckFile**: HR staff manually checks each document, verifies diploma authenticity when possible, and files the employee record. Time: 15-20 minutes per hire.

**With CheckFile**: All employment documents are validated in under 1 minute. CheckFile verifies document authenticity, cross-references identity information, and flags any inconsistencies. HR receives a structured report for the employee file.

**Regulations addressed**: RGPD/GDPR, French labor law

---

### Public Procurement Compliance

**Scenario**: A public entity receives bids for a tender. Each bid includes company registration, financial statements, insurance certificates, professional certifications, and the technical proposal.

**Without CheckFile**: Procurement officers manually verify administrative compliance for each bidder — checking that all required documents are present, valid, and consistent. For a tender with 10 bidders, this takes days.

**With CheckFile**: Each bid file is processed automatically. CheckFile verifies administrative completeness, validates document authenticity, checks company status against registries, and flags non-compliant bids. Procurement officers focus on technical evaluation.

**Regulations addressed**: French public procurement code (Code de la commande publique), RGPD/GDPR

---

## 6. Regulatory Compliance Matrix

### AMLD6 (EU 6th Anti-Money Laundering Directive)
| Requirement | CheckFile Feature |
|---|---|
| Customer Due Diligence (CDD) | Identity verification, cross-document validation |
| Enhanced Due Diligence (EDD) | Additional document checks for high-risk clients |
| Beneficial Ownership Verification | Cross-reference with official registries |
| Ongoing Monitoring | Periodic re-verification via API |
| Record Keeping | Complete audit trail, exportable reports |
| Suspicious Activity Reporting | Anomaly detection and flagging for human review |

### DORA (Digital Operational Resilience Act)
| Requirement | CheckFile Feature |
|---|---|
| ICT Risk Management | EU-hosted, encrypted infrastructure |
| Third-Party Provider Oversight | Transparent subprocessor list, DPA available |
| Operational Resilience Testing | 99.9% uptime SLA, redundant infrastructure |
| Information Sharing | Structured incident reporting |

### RGPD/GDPR
| Requirement | CheckFile Feature |
|---|---|
| Data Minimization | Only necessary data extracted, automatic deletion |
| Right to Erasure | Immediate deletion on request |
| Data Processing Agreement | DPA available on request |
| EU-Only Hosting | AWS Paris (eu-west-3), no extra-EU transfers |
| Data Protection Impact Assessment | DPIA documentation available |
| No AI Training on Customer Data | Customer documents never used for model training |

### KYC/AML
| Requirement | CheckFile Feature |
|---|---|
| Identity Verification | Multi-document identity validation |
| Sanctions Screening | Integration-ready with screening providers |
| PEP Checks | Integration-ready with PEP databases |
| Source of Funds | Financial document cross-validation |
| Ongoing Monitoring | Periodic re-verification via API |

### eIDAS 2.0
| Requirement | CheckFile Feature |
|---|---|
| Electronic Identification | Support for eID-backed documents |
| Cross-Border Recognition | Multi-country document support |
| Trust Services | Timestamped audit trail |

### MiCA (Markets in Crypto-Assets Regulation)
| Requirement | CheckFile Feature |
|---|---|
| Customer Onboarding | Full KYC document verification |
| Crypto Service Provider Compliance | Identity and corporate document validation |
| Travel Rule Support | Cross-referencing sender/receiver identity documents |

### Country-Specific Regulations

**France — TRACFIN**
- Compliance with Monetary and Financial Code (Code monetaire et financier)
- Support for suspicious transaction identification
- Document-level anomaly detection for reporting

**Germany — BaFin / GwG**
- GwG (Geldwaeschegesetz) compliance support
- German document types supported (Personalausweis, Handelsregisterauszug, etc.)
- Regulatory reporting integration-ready

**Netherlands — DNB / Wwft**
- Wwft (Wet ter voorkoming van witwassen) compliance support
- Dutch document types supported (KVK uittreksel, etc.)
- Transaction monitoring support

---

## 7. Comparison vs Alternatives

### CheckFile vs Onfido

| Aspect | CheckFile | Onfido |
|---|---|---|
| Primary Focus | Multi-document business file validation | Single-document identity verification |
| Cross-Document Validation | Yes — core feature | No — documents checked in isolation |
| Business Rules Engine | Yes — configurable per partner | No — fixed verification checks |
| External Registry Enrichment | Yes (Pappers, INSEE, Infogreffe, etc.) | Limited |
| Target Market | Regulated B2B (banking, insurance, leasing, legal) | Consumer-facing identity verification |
| Document Types | 100+ (identity, financial, corporate, contracts) | Primarily identity documents |
| EU Hosting | Yes (AWS Paris) | Yes (EU option available) |
| On-Premises Option | Yes (Enterprise) | No |
| Pricing Model | Per-file (~0.30 EUR) | Per-verification |

### CheckFile vs Veriff

| Aspect | CheckFile | Veriff |
|---|---|---|
| Primary Focus | Business file validation with cross-document logic | Video-based identity verification |
| Verification Method | Document analysis + cross-validation + registry checks | Video selfie + document capture |
| Cross-Document Validation | Yes — validates relationships between documents | No |
| Business Rules Engine | Yes — partner-specific rules | No |
| Use Case | Back-office compliance automation | Customer-facing onboarding |
| Document Types | 100+ across all categories | Primarily identity documents |
| Biometric Verification | No (document-focused) | Yes (facial recognition) |

### CheckFile vs Jumio

| Aspect | CheckFile | Jumio |
|---|---|---|
| Primary Focus | Multi-document compliance automation | Identity proofing & AML |
| Cross-Document Validation | Yes — core differentiator | No |
| Business Rules Engine | Yes — configurable per client/partner | Limited |
| Target Market | European regulated industries | Global identity verification |
| Fraud Detection | Document-level + cross-document patterns | Document-level + biometric |
| Biometric Verification | No | Yes (facial recognition, liveness) |
| EU Data Residency | Yes (AWS Paris, mandatory) | Available on request |

### Summary: When to Choose CheckFile

Choose CheckFile when you need to:
- Validate COMPLETE business files (not just single identity documents)
- Enforce business-specific rules per partner, product, or process
- Cross-reference data between multiple documents in a file
- Enrich verification with official registry data
- Automate back-office compliance workflows
- Maintain EU data residency with no exceptions

Choose identity verification specialists (Onfido, Veriff, Jumio) when you need:
- Consumer-facing identity onboarding with biometrics
- Video-based liveness detection
- Single-document identity verification at scale

Note: CheckFile can complement identity verification tools. Use an IDV provider for customer-facing onboarding, then use CheckFile for back-office file validation and cross-document compliance.

---

## 8. API Integration

### Base URL

Production: `https://api.checkfile.ai/v1`
Sandbox: Available on request

### Authentication

All API requests require a Bearer token in the Authorization header:

```
Authorization: Bearer sk_live_your_api_key_here
```

API keys are provided per environment (live / test). Keys can be rotated from the dashboard.

### Rate Limits

| Plan | Rate Limit |
|---|---|
| Starter | 100 requests/min |
| Business | 1,000 requests/min |
| Enterprise | Unlimited |

### Example: Submit a File for Validation

**Request:**
```
POST /api/v1/validate
Content-Type: multipart/form-data
Authorization: Bearer sk_live_your_api_key_here

{
  "file_type": "financing",
  "partner": "grenke",
  "documents": [
    { "type": "contract", "file": "contract.pdf" },
    { "type": "identity", "file": "id_card.pdf" },
    { "type": "kbis", "file": "kbis.pdf" },
    { "type": "rib", "file": "rib.pdf" }
  ]
}
```

**Response (200 OK):**
```json
{
  "file_id": "file_abc123",
  "status": "non_compliant",
  "confidence": 0.97,
  "anomalies": [
    {
      "type": "amount_mismatch",
      "severity": "high",
      "detail": "Contract amount (15,200 EUR) does not match quote amount (12,860 EUR)",
      "documents": ["contract.pdf", "quote.pdf"],
      "rule": "grenke_amount_consistency"
    },
    {
      "type": "missing_document",
      "severity": "medium",
      "detail": "Required document 'attestation_assurance' is missing for GRENKE financing files",
      "documents": [],
      "rule": "grenke_required_docs"
    }
  ],
  "checks_passed": 12,
  "checks_failed": 2,
  "checks_total": 14,
  "processing_time_ms": 4200,
  "created_at": "2026-01-15T10:30:00Z"
}
```

### Webhooks

Register a webhook URL to receive real-time notifications:

```
POST https://your-domain.com/webhook
Content-Type: application/json
X-CheckFile-Signature: sha256=hmac_signature_here

{
  "event": "analysis.completed",
  "file_id": "file_abc123",
  "status": "non_compliant",
  "anomalies_count": 2,
  "processing_time_ms": 4200,
  "created_at": "2026-01-15T10:30:00Z"
}
```

Webhook signatures use HMAC-SHA256 for verification. The signing secret is provided in your dashboard.

### Batch Processing

Process multiple files in a single API call:

```
POST /api/v1/batch
Content-Type: application/json
Authorization: Bearer sk_live_your_api_key_here

{
  "files": [
    { "file_type": "financing", "partner": "grenke", "documents": [...] },
    { "file_type": "insurance", "documents": [...] },
    { "file_type": "real_estate", "documents": [...] }
  ],
  "webhook_url": "https://your-domain.com/webhook"
}
```

Batch responses are delivered asynchronously via webhook.

### Error Codes

| Code | Meaning |
|---|---|
| 400 | Bad request — missing parameters or incorrect format |
| 401 | Missing or invalid API key |
| 403 | Access denied — insufficient plan for this resource |
| 422 | Unprocessable document — unsupported format or corrupted file |
| 429 | Rate limit exceeded — retry after the indicated delay |
| 500 | Server error — contact support if persistent |

### SDKs and Libraries

- REST API: Available — API-first architecture, integrate with any language
- Interactive documentation (Swagger): Available at app.checkfile.ai/docs
- Sandbox environment: Available on request

---

## 9. Pricing Model

### Plans

#### Starter — For SMBs & Startups
- Up to 100 files/month
- 1 file type
- Custom validation rules
- Tracking dashboard
- PDF export
- Email support
- Up to 20 documents per file

#### Business — For Mid-Market & Growing Teams (Most Popular)
- Up to 500 files/month
- Unlimited file types
- REST API & webhooks
- Advanced workflows
- Priority support
- Multi-user
- Up to 50 documents per file
- All Starter features included

#### Enterprise — For Large Orgs & Regulated Industries
- Unlimited volume
- Business rules consulting
- Full SI integration (SAP, Salesforce, custom)
- Dedicated account manager
- Guaranteed SLA
- Training & audit
- SSO / SAML
- Unlimited documents per file
- On-premises deployment option
- All Business features included

### Pricing Details

- Usage-based pricing starting at ~0.30 EUR per file
- Price per file decreases with volume (volume discounts)
- Pricing depends on: file volume, number of document types, business rule complexity
- No minimum commitment period
- Cancel anytime with one month notice
- Overage: additional files billed at agreed unit rate, no service interruption

### Free Pilot

All new customers are offered a free pilot:
- Use your own documents (real business files)
- Results delivered in 48 hours
- Full demonstration of cross-validation, enrichment, and fraud detection
- No commitment required

### All Plans Include

- European hosting (AWS Paris)
- Data encryption (AES-256 at rest, TLS 1.3 in transit)
- Continuous updates
- PDF export
- Real-time dashboard
- GDPR compliance

---

## 10. Glossary

**AML (Anti-Money Laundering)**: Set of laws, regulations, and procedures designed to prevent criminals from disguising illegally obtained funds as legitimate income. CheckFile supports AML compliance through document verification, cross-validation, and anomaly detection.

**AMLD6 (6th Anti-Money Laundering Directive)**: EU directive that strengthens AML requirements, including extended criminal liability, mandatory beneficial ownership verification, and enhanced cooperation between member states.

**API (Application Programming Interface)**: A set of protocols that allows software applications to communicate. CheckFile provides a REST API for programmatic document validation.

**BaFin (Bundesanstalt fuer Finanzdienstleistungsaufsicht)**: German federal financial supervisory authority. Oversees compliance with GwG (Geldwaeschegesetz) for anti-money laundering.

**CDD (Customer Due Diligence)**: The process of verifying a customer's identity and assessing their risk level. Required by AMLD6 and national AML laws.

**DNB (De Nederlandsche Bank)**: Dutch central bank and financial regulator. Oversees Wwft compliance.

**DORA (Digital Operational Resilience Act)**: EU regulation requiring financial entities to ensure they can withstand, respond to, and recover from ICT-related disruptions.

**DPA (Data Processing Agreement)**: A legally binding contract between a data controller and a data processor, required by GDPR. CheckFile provides DPAs on request.

**EDD (Enhanced Due Diligence)**: Additional verification measures required for high-risk customers under AML regulations.

**eIDAS 2.0 (Electronic Identification, Authentication, and Trust Services)**: EU regulation on electronic identification and trust services. Establishes a framework for cross-border recognition of electronic identities and documents.

**GDPR / RGPD (General Data Protection Regulation)**: EU regulation on data protection and privacy. CheckFile is natively GDPR compliant with EU-only hosting, automatic data deletion, and no AI training on customer data.

**GwG (Geldwaeschegesetz)**: German Anti-Money Laundering Act. Implements EU AML directives in German law.

**IDP (Intelligent Document Processing)**: Technology that uses AI to capture, extract, and process data from documents. CheckFile goes beyond IDP by adding cross-document validation and business rules.

**KBIS**: Official extract from the French Trade and Companies Register (Registre du Commerce et des Societes). Proves a company's legal existence.

**KYC (Know Your Customer)**: Process of verifying the identity of clients. A core requirement in banking, insurance, and other regulated industries.

**MiCA (Markets in Crypto-Assets Regulation)**: EU regulation for crypto-asset markets, including requirements for crypto service provider compliance and customer onboarding.

**NER (Named Entity Recognition)**: AI technique for identifying and classifying named entities (persons, organizations, dates, amounts) in text. Used by CheckFile for data extraction from documents.

**OCR (Optical Character Recognition)**: Technology that converts images of text into machine-readable text. CheckFile uses multi-engine OCR for maximum extraction accuracy.

**PEP (Politically Exposed Person)**: An individual who holds or has held a prominent public function. AML regulations require enhanced due diligence for PEPs.

**SLA (Service Level Agreement)**: A commitment between CheckFile and the customer defining the expected level of service, including uptime guarantees and response times.

**SIREN / SIRET**: French company identification numbers. SIREN is the 9-digit company identifier; SIRET is the 14-digit establishment identifier.

**SOC 2 (System and Organization Controls 2)**: An auditing framework for service organizations covering security, availability, processing integrity, confidentiality, and privacy. CheckFile has SOC 2 aligned processes with Type II certification in progress.

**TRACFIN (Traitement du Renseignement et Action contre les Circuits Financiers Clandestins)**: French financial intelligence unit responsible for combating money laundering and terrorist financing.

**Wwft (Wet ter voorkoming van witwassen en financieren van terrorisme)**: Dutch Anti-Money Laundering and Anti-Terrorist Financing Act.

---

## 11. Frequently Asked Questions

**Q: What types of documents can CheckFile verify?**
A: CheckFile supports 100+ document types organized into six categories: identity documents (ID cards, passports, residence permits), financial documents (bank statements, tax returns, pay slips, P&L), corporate documents (KBIS, articles of association, beneficial ownership declarations), address proofs (utility bills, tax notices), professional documents (licenses, certifications, insurance attestations), and contracts (leasing, insurance, rental, sales agreements).

**Q: How does CheckFile detect document fraud?**
A: CheckFile employs multiple fraud detection layers: (1) cross-document validation to detect inconsistencies between related documents, (2) alteration detection for modified amounts, dates, or names, (3) synthetic document identification for AI-generated fakes, (4) template analysis for layout and font anomalies, (5) metadata analysis for suspicious creation dates or software signatures, and (6) cross-document fraud patterns for coordinated falsifications. Every detection includes a confidence score and full explanation.

**Q: Is CheckFile GDPR compliant?**
A: Yes, CheckFile is natively GDPR compliant. Key measures include: EU-only hosting (AWS Paris, eu-west-3), no data transfer outside the EU, automatic document deletion after analysis, no use of customer data for AI training, data processing agreements (DPA) available on request, right to erasure fully supported, complete audit trail of all data processing operations, and data encryption (AES-256 at rest, TLS 1.3 in transit).

**Q: How long does verification take?**
A: Average processing time is under 2 seconds per individual document. A complete business file with 10+ documents is typically analyzed in under 60 seconds. This includes OCR extraction, cross-document validation, external enrichment via official registries, and fraud analysis. The platform is available 24/7.

**Q: Can CheckFile integrate with existing systems?**
A: Yes. CheckFile offers a REST API (Business and Enterprise plans) with webhook support, batch processing, and native connectors. Supported integrations include CRM (Salesforce, HubSpot, Pipedrive, Zoho), ERP/Accounting (SAP, Cegid, Sage, Pennylane), Automation (Zapier, Make), and Storage (Google Drive, SharePoint, Dropbox, Box). Integration typically takes 1-3 weeks with dedicated team support.

**Q: What languages does CheckFile support for documents?**
A: CheckFile processes documents in all major EU languages including French, English, German, Dutch, Spanish, and Italian. The platform automatically detects the document language and applies the appropriate OCR and extraction models. The platform interface is available in French and English.

**Q: How does pricing work?**
A: CheckFile uses usage-based pricing starting at approximately 0.30 EUR per file processed. A "file" is a set of related documents processed together (e.g., a financing application with contract, ID, KBIS, and RIB = 1 file). Pricing decreases with volume. There is no minimum commitment period. A free pilot with your own real documents is offered to all new customers, with results delivered in 48 hours.

**Q: How does CheckFile differ from OCR tools like ABBYY or Kofax?**
A: OCR tools extract text from documents. CheckFile goes several steps further: it classifies documents, extracts structured data, validates data BETWEEN documents (cross-document validation), enforces business-specific rules per partner, enriches data from official registries, and detects fraud. OCR is one component of CheckFile's pipeline, not the end product.

**Q: How does CheckFile handle professional secrecy (lawyers, notaries)?**
A: CheckFile is designed for regulated professions. Each document is processed in strict isolation. No CheckFile staff has access to customer documents. Strict compartmentalization between client files is enforced. Documents are immediately deleted after processing. Dedicated environments per client are available on request. This is compliant with French professional secrecy laws (Art. 226-13 Penal Code, Art. 66-5 Law of 1971).

**Q: Can CheckFile be deployed on-premises?**
A: Yes. Enterprise customers can deploy CheckFile within their own infrastructure (AWS, Azure, GCP, or bare metal) for maximum data sovereignty. A hybrid option is also available where documents remain on-premises and only extracted metadata is processed in the cloud. Contact the team for details.

**Q: What happens when CheckFile finds an anomaly?**
A: Each anomaly is returned with: (1) anomaly type (amount_mismatch, missing_document, identity_inconsistency, etc.), (2) severity level (high, medium, low), (3) detailed human-readable explanation, (4) list of documents involved, (5) the business rule that triggered the anomaly, and (6) a confidence score. The human reviewer can then decide how to handle each anomaly — CheckFile assists, it does not replace human judgment on final decisions.

**Q: Is there a sandbox environment for testing?**
A: Yes. A sandbox environment is available on request for Business and Enterprise customers. It allows you to test API integration with sample documents before going live. Contact the team to get sandbox access.

---

## 12. Links and Resources

- Website: https://checkfile.ai
- API Documentation: https://checkfile.ai/api-documentation
- Pricing: https://checkfile.ai/tarifs
- Security & Compliance: https://checkfile.ai/securite
- Blog: https://checkfile.ai/blog
- Contact / Demo Request: https://checkfile.ai/contact
- Comparison (Manual vs CheckFile): https://checkfile.ai/comparatif
- Case Studies: https://checkfile.ai/cas-client
- About: https://checkfile.ai/a-propos
- Privacy Policy: https://checkfile.ai/legal/politique-confidentialite
- Legal Notice: https://checkfile.ai/legal/mentions-legales
- Quick Reference: https://checkfile.ai/llms.txt

---

Document version: 1.0
Last updated: 2026-03-03
Copyright 2026 CheckFile.ai — All rights reserved.