> For the complete documentation index, see [llms.txt](https://finext.gitbook.io/one-kyc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://finext.gitbook.io/one-kyc/releases/release-may-05-may-25.md).

# Release: May 05 - May 25

#### 1. Document Cross-Check During KYB Verification

The system supports cross-checking documents uploaded during KYB verification against the company data found during the verification process.

This step supports uploading any types of documents, photos, and archives. After upload, the system classifies the files, extracts text data, and performs OCR recognition for data contained in images.

Additionally, all files are checked for malware. If viruses or malicious files are detected, the upload is blocked for internal security purposes.

The system also checks:

* document validity;
* signs of Photoshop usage or editing;
* correctness of stamps and seals;
* anti-fraud indicators and potential forgery attempts.

An additional database check is performed to assess document reliability, forgery risk, and the overall level of trust.

Based on AI analysis, the system generates one of the following verification results:

* approve
* reject
* manual review

Validation parameters are configurable and can be adjusted depending on the process requirements.

<br>

#### 2. Linking the KYB Process with the Beneficiary’s KYC

A mechanism has been implemented to verify the beneficiary through KYC within the KYB process, with the ability to link the company verification results to a specific company representative.

The new step is launched after the document upload and company data completion stages within the KYB flow.

The flow supports the following scenarios:

* the KYB initiator can send a KYC link to the company beneficiary or director;
* the beneficiary can complete KYC separately, either immediately or later;
* KYC results are automatically linked to the corresponding KYB process.

Additionally, the system verifies that the person completing KYC matches the data specified in the company documents uploaded as part of KYB. The system compares information about the director / beneficiary from corporate documents with the data of the user completing KYC. This helps confirm that the verification is being completed by an authorized person rather than an unrelated third party.

Both mandatory and optional beneficiary KYC scenarios are supported:

* if the step is enabled as mandatory, KYB can be completed only after KYC has been successfully passed;
* if the step is disabled, KYB can be completed regardless of the KYC status.

The implementation ensures a correct KYB and KYC linkage, prevents data loss between the processes, and supports compliance requirements.

#### 3. Implemented user document retrieval by external\_id

\ <br>