Skip to main content

KYC Responder: Requests

Emmanuel Winkler
Updated

What Requests are

Requests in KYC Responder are used to collect information or documents from internal officers or the company itself. They are different from:

  • Responder Cases, which are used to prepare a response to an external KYC request
  • Collector requests, which are used to collect information from external counterparties

When to use Requests

Use a Request when you need to gather something internally, for example:

  • A passport or proof of address from an officer
  • A company document such as a policy or registration extract
  • Missing information through a questionnaire
  • Confirmation or update of existing information

Where to find it

  1. Open KYC Responder.
  2. Go to Requests.
  3. From there, you can create, open, search, and manage your requests.

How to create a Request

  1. Click Create.
  2. Choose whether it is an Officer request or a Company request.
  3. Add the key details, such as:
    • Title
    • Responsible party
    • Due date
    • Recipient / contact person
  4. Add what you need to collect:
    • Documents for file collection
    • Questionnaires for structured information
  5. Add a short message if needed.
  6. Send the request or share it through the generated link, depending on your workflow.

 

What you can collect

Documents

Use document requests when you need files such as:

  • Passport
  • Proof of address
  • Certificate of incorporation
  • Group policy or other internal company documents

Questionnaires

Use questionnaires when you need structured information, such as:

  • Contact details
  • Address information
  • Tax information
  • Other KYC-related data points

What you can track

Each request gives you visibility into items such as:

  • Request ID
  • Title
  • Responsible party
  • Creation date
  • Due date
  • Status
  • Progress

How to manage Requests

From the Requests area, you can typically:

  • Open a request and review its details
  • Edit the request if something changes
  • Search by request name or ID
  • Sort the list
  • Filter by creator, responsible party, status, or request type
  • Reuse templates for recurring request types

Activity and audit trail

Requests also help you keep track of what happened over time. You can review activity to understand the request history and follow the progress from creation to completion.

Best practices

  • Use Officer requests for person-specific items and Company requests for entity-level items.
  • Use questionnaires when you need data, not just files.
  • Assign a clear responsible party so follow-up is easy.
  • Add realistic due dates to keep the process moving.
  • Save templates for request types you use often.
  • Use Requests for internal collection and Cases for external KYC responses.

Quick example

  1. You are preparing a response to a bank.
  2. You notice that one officer’s proof of address is missing.
  3. You create an Officer request in Responder.
  4. You add the required document, assign the responsible party, and set a due date.
  5. Once the document is received, the team can continue preparing the external KYC response.

Related articles