Skip to content

Get corporate account files ready for KYC review

Duvo checks a corporate application against the bank’s checklist for that entity type and jurisdiction, and sends one consolidated request for the documents still missing.

Corporate onboarding evidence

Needs review

Onboarding CO-101

Ownership file
Chart missing
Present
Registry extract
Reviewer
Onboarding owner

The registry extract identifies the applicant, but the checklist for this entity type also requires an ownership chart, which is absent from the file.

Next action

Request chart: the relationship manager is asked for the chart and its receipt is recorded on CO-101.

Refer ownership gap: a specialist reviewer receives the extract with the missing chart noted.

Onboarding owner approval

The onboarding owner approves the recipient, the request and the case update together before Duvo sends anything.

View the wider product queue

Corporate onboarding evidence

Corporate application with the ownership chart missing.

Adds cases
Corporate application queue
Processes cases
Corporate onboarding evidence
Total

24

Pending

5

Postponed

2

In progress

4

Needs input

3

Failed

0

Completed

10

Add filter
Case
Case Status
Ownership document gap
Scope
Decision
Exceptions
Next action
Onboarding CO-101
Needs Input
Ownership chart missing
Holding company application
Request chart
1
Onboarding CO-102
In Progress
Signatory not on list
Board resolution
Request signatory list
0
Onboarding CO-103
Completed
Company names differ
Registry extract
Refer discrepancy
0
Onboarding CO-104
Pending
Certification missing
Director identity copy
Request certified copy
1
Onboarding CO-105
Postponed
Review pack ready
Versioned file
Prepare handoff
0

Showing 5 of 24 cases

  1. 1

    Approval

    Exceptions pause for the named owner

    Each exception carries the source records, applied rule, recommended action, and the person authorised to decide.

  2. 2

    Ownership document gap

    Ownership document gap is visible before the action

    The registry extract identifies the applicant, but the ownership chart the checklist requires is absent, so the gap shows before the next request.

From corporate application to a documented review handoff

When a holding company applies for an operating account, the relationship manager uploads the registry extract and articles of association, but the ownership chart stops at the parent and the board resolution names a signatory who is not on the signatory list. The customer then receives separate emails asking for overlapping documents.

  1. 0101

    Index the company file

    Duvo links the application to the registry extract, constitutional documents, ownership chart and signatory records, with each document’s date and version.

  2. 0202

    Check the entity checklist

    Duvo compares the file with the checklist for that entity type and jurisdiction, and flags missing certification, unreadable copies and company names that differ between documents.

  3. 0303

    Draft one targeted request

    Duvo drafts a single request listing only the missing documents, naming the recipient and the onboarding case status to record.

  4. 0404

    Your team decides

    Approve the request or refer

    The onboarding owner approves the request, recipient and case update, or sends a discrepancy to a specialist reviewer.

  5. 0505

    Send and record

    The relationship manager or client contact receives the approved document request, and the onboarding case records it with the message reference. Returned documents go back through the same checks.

Link the application to the ownership documents

Systems and control details

Your onboarding checklists by entity type and jurisdiction drive the checks, first run against masked company files. Contact permissions, document retention and the case fields Duvo may update are agreed before any request is sent.

Corporate application queue, Company document repository, Entity document checklist, Onboarding case register

  • Onboarding owner approval

    The onboarding owner approves the recipient, the request and the case update together before Duvo sends anything.

  • No KYC decisions

    Duvo does not verify identity, determine beneficial ownership, clear screening results, accept the customer or activate the account. Ambiguous ownership and name discrepancies go to qualified reviewers.

  • Record document and action history

    Source versions, the checklist version, the owner’s decision and the delivery acknowledgement are kept together. Failed deliveries and failed case updates stay visible.

What teams ask about Corporate onboarding evidence

  • Can the document checklist differ by entity type and jurisdiction?

    Yes. Duvo applies the checklist your bank supplies for each entity type and jurisdiction in scope, and flags any application it cannot place.

  • Does Duvo decide who the beneficial owners are?

    No. It checks that the ownership documents your checklist requires are present and consistent. Identifying and verifying beneficial owners stays with your KYC team.

  • Who receives the document request, the customer or the relationship manager?

    Whichever recipient your process uses and the onboarding owner approves. Many banks route requests through the relationship manager.

  • What should we bring to test corporate onboarding checks?

    A few masked applications and your current checklists for those entity types and jurisdictions.