Business Identification Guide (BKYC)

This guide explains the integration process of Solaris' Business Know Your Customer (BKYC) as a standalone product, including the mandatory information you must collect from your customers and the necessary endpoints and webhooks you must integrate into your solution.

Introduction

Product overview

What is BKYC?

BKYC is Solaris's digital identification solution that facilitates the Know Your Customer (KYC) process for businesses. It's completely digital and AML compliant, harnessing state-of-the-art RESTful APIs to bring together a series of identification and compliance checks for business customers.

How does BKYC work?

The business identification consists of two simultaneous processes:

  • Legal Identification: Solaris identifies the legal entity and verifies the provided business details and documents in the corresponding Commerce Register (Handelsregister in Germany) to ensure that the disclosed data is complete and accurate. Additionally, this process verifies that all business legal representatives and ultimate beneficial owners are disclosed and linked to the business. This is an internal process carried out by Solaris' Banking Operations team.
  • Video Identification(s): All legal representatives and any authorized person on the business must be identified in a video identification session by our identification partner, IDnow, to validate their details against their identification documents.
Important notes
  • Both identification processes must be successful for the business identification process to be considered successful.
  • Only legal representatives and any natural person authorized to act on the account, such as an authorized person or signee, need to be video-identified. Ultimate Beneficial Owners don't need to go through video identification.

Business identification overview

Onboarding a business involves collecting information and creating multiple resources using Solaris's API. Th's section describes the various legal entities and natural persons engaged in onboarding a business, as well as the information you need to collect.

Business information

When you onboard a business, you must collect two different streams of information:

  • Business information: Information about the legal person (legal entity, e.g., the company itself), including the business name, registration number, tax information, business activities, etc.
  • Person information: Information about all the natural persons running and/or legally representing the business. A business could involve multiple natural persons assigned to different roles. These roles include legal representatives, beneficial owners, signees, and authorized persons.

Business identification

Based on the information provided, businesses go through two types of identifications:

  • Legal identification: Done by Solaris to identify the legal entity.
  • Video identification: Done by our video identification service provider, IDnow, to identify the natural persons behind the business. Please note that only natural persons assigned to specific roles require video identification.

Business entities and roles

Legal person/entity

A legal person (also referred to as a legal entity) is a person or a thing that can perform different actions under the law, such as entering into contracts, owning property, etc. There are two types of legal persons: human and non-human. The non-human legal person is called a juridical person, which could be a corporation or a company, and is treated by law as a person. In contrast, the human legal person is called a natural person.

A company or a business includes a juridical person (the legal entity) and natural person(s) who own and/or legally represent the business.

Business

On Solaris's system, a business is a company's juridical person (the non-human legal person). A business must have at least one natural person attached to it, assigned to a specific role.

The natural persons attached to the business don't own the account. Instead, the business is the account holder, and a business can have multiple accounts.

Roles

The legal persons behind the business are assigned to different roles. Each person attached to a business plays at least one role: a legal representative, a beneficial owner, or both. A person could also act as a signee or an additional authorized person on the account.

The following roles are available on Solaris's system:

  • Legal representative
  • Ultimate beneficial owner
  • Signee
  • Authorized person
Important

The roles of legal representative(s) and ultimate beneficial owner(s) are mandatory in our system.


User journey

Business customers can simply identify with Solaris' BKYC by doing the following:

  1. Consent to the legal and regulatory requirements, such as Solaris' terms and conditions and data terms.
  2. Enter the business' required information.
  3. Upload the required business documents.
  4. Enter the details of the business' legal representative(s).
  5. Enter the details of the business' beneficial owner(s).
  6. Complete the video identification process with IDnow (All legal representatives).

System prerequisites

Before starting the business identification process, you must implement the following requirements:

1. Technical setup:

Set up your environment and get your authentication keys. For step-by-step instructions, check the Technical setup guide.

2. Legal and compliance screens:

Build the necessary legal and compliance screens in your sign-up flow to collect your customers' consent to the necessary legal and compliance requirements. The Legal and compliance screens guide contains step-by-step instructions on how to create these screens and what they must contain.

Record the customer's consent on each screen as a UTC timestamp (e.g., 2019-01-01T00:00:00Z). Afterward, you must pass each timestamp in its respective field to Solarisbank.

  • Collect the customer's consent to Solarisbank's Terms and Conditions and store the timestamp in the terms_conditions_signed_at field.
  • Collect the customer's consent to data processing and store the timestamp in the data_terms_signed_at field.
note

The mentioned fields are part of the person resource in which all the customer data points are stored.


Webhooks

Solarisbank recommends subscribing to the following webhook events to better automate your processes. For detailed instructions on implementing Solarisbank webhooks, check the webhooks documentation.


Integration flow

The following diagram gives an overview of the integration flow for BKYC stand-alone product:

Diagram: Business identification (BKYC) flow

Integration steps:

Important

The required data fields you need to collect depend on different factors, such as the business' legal form, country, etc. This guide explains the standard integration process for business customers in Germany for BKYC standalone solution.

Identify business customers by completing the following steps:

Business registration

  1. Collect the mandatory business data in your sign-up flow, and create a business resource for your customer by completing Step 1.
  2. Upload the required business documents by completing Step 2.

Business natural person(s) registration

  1. Collect the mandatory data from each of the business' legal representatives, including the consent to the legal and regulatory requirements in your sign-up flow, and create a person resource and assign the legal representative role to this person by completing Step 3.
  2. Collect the mandatory data from each of the business' beneficial owner(s) in your sign-up flow, and create a person resource and assign the beneficial owner role to this person by completing Step 4.

Step 1: Collect business data and create business resource

In this step, you must collect the mandatory data points from the customer in your sign-up flow, including all the timestamps of the business's consent to the legal and compliance screens.

Afterward, you pass all the data points to Solaris by creating a business resource to represent your customer.

What is a business resource?

The business resource represents the business's details at Solaris. It contains all mandatory customer data, as well as links to other resources created for the business (e.g., legal representative(s), beneficial owner(s), accounts, tax identifications, etc.).

API reference

Visit the following link to find all the endpoints related to the business resource, including related properties and examples.

Related webhook events

Important points about the business resource
  • The mandatory data points for this endpoint depend on various factors, such as the product, business information, and country.
  • You must submit the information exactly as it appears in official documents.
  • There are certain mappings between the possible values for these fields tax_country, sector, and legal_form.

POST Create business

This endpoint creates a business resource for your customer. Add the following mandatory data points you've collected from the customer in the request body of this endpoint:

Important

You have to submit the information exactly as they appear in official documents.

  • name: The business registered name.
  • legal_form: The business legal form. (Check the appendix for possible values)
  • sector The business sector.
  • nace_code (Check the appendix for possible values)
  • foundation_date: The date the business was founded.
  • address: The business registered address (Street, Number, City, Postal Code, Country, State).
  • tax_information

    • registration_issuer: (Only for Germany) The authority that issued the business' registration. (Check the appendix for possible values)
    • registration_number: The business' registration number.
  • terms_conditions_signed_at (UTC timestamp)
  • business_purpose: Short summary of the purpose of the business. May also include the business' web address.

Request example:

Copy
Copied
POST /v1/businesses
{
  "name": "Example GmbH",
  "sector": "OTHER_COMPANIES",
  "nace_code": "M 70.10",
   "address": {
    "line_1": "Address 1",
    "line_2": "Address 2",
    "postal_code": "10409",
    "city": "Berlin",
    "country": "DE",
    "state": "BE"
  },
  "legal_form": "GMBH",
  "foundation_date": "1990-06-01",
  "tax_information": {
    "tax_country": "DE",
    "tax_confirmation": "SINGLE",
    "registration_number": "HRB 12345",
    "registration_issuer": "Amtsgericht Berlin"
  },
  "business_purpose": "change the world for the better",
  "terms_conditions_signed_at": "2017-01-01T00:00:00Z",
}

Example response

The API call returns a business object with a unique business_id, which will be used to reference the created business in the remaining steps of the onboarding process.

Copy
Copied
{
  "id": "880bbac68a34add190786b9c74f4c82fcbiz",
  "name": "Example GmbH",
  "sector": "OTHER_COMPANIES",
  "nace_code": "M 70.10",
   "address": {
    "line_1": "Address 1",
    "line_2": "Address 2",
    "postal_code": "10409",
    "city": "Berlin",
    "country": "DE",
    "state": "BE"
  },
  "legal_form": "GMBH",
  "foundation_date": "1990-06-01",
  "tax_information": {
    "tax_country": "DE",
    "tax_confirmation": "SINGLE",
    "registration_number": "HRB 12345",
    "registration_issuer": "Amtsgericht Berlin"
  },
  "fatca_relevant": null,
  "fatca_crs_confirmed_at": null,
  "crs_company_type": null,
  "business_purpose": "change the world for the better",
  "terms_conditions_signed_at": "2017-01-01T00:00:00Z",
  "flagged_by_compliance": false,
  "balance_sheet_total": null,
  "number_employees": null,
  "registration_type": "DE_GNR_CD",
  "registration_district": "BERLIN_CHARLOTTENBURG",
  "screening_progress": "NOT_SCREENED",
  "international_operativity_expectation": [],
  "vat_number": null,
  "risk_classification_status": "NOT_SCORED",
  "customer_vetting_status": "NOT_VETTED",
  "purpose_of_account_opening": null,
  "source_of_funds": null,
  "expected_annual_revenue": null,
  "expected_annual_incoming_funds": null,
  "company_status": null
}

Click here to view the full API reference.


Automatic data collection (Optional)

You can facilitate the onboarding process for your customers by opting for the automatic data collection feature. Our external service provider Business Registry simplifies the data collection step by allowing your customers to enter the country and the company's name and the rest of the business data fields are filled out automatically.

info

Automatic data collection is an optional step that provides a good user experience. Contact your Partner Manager for more information about the usage of this feature and its associated prices.

GET Search for business commercial registration

The customer enters the company's name and country on your frontend and you pass this information using the following endpoint to automatically fetch the business' registration_issuer and registration_number:

info

This endpoint may be used free of charge.

Request URL:

Copy
Copied
GET /v1/commercial_registrations/search_by_name?country={{}}&name={{}}

Example response

Copy
Copied
{
  "name": "FLOOR 13 GmbH",
  "registration_number": "HRB 198673",
  "registration_issuer": "AMTSGERICHT MÜNCHEN"
}

Click here to view the full API reference.

GET Automatic business data collection

After getting the business registration_issuer and registration_number from the response of the previous endpoint, you can automatically fetch the remaining business details by calling the following endpoint:

attention
  • This endpoint has an associated cost per request. Contact your Partner Manager for more information.
  • Please note that for companies in Germany, you must add AMTSGERICHT before the value of the registration_issuer, e.g., AMTSGERICHT MÜNCHEN.

Request URL:

Copy
Copied
GET /v1/commercial_registrations/find?registration_number={{}}&registration_issuer={{}}

Example response

Copy
Copied
{
  "name": "FLOOR 13 GmbH",
  "address": {
    "country": "DE",
    "postal_code": "86919",
    "city": "Utting a.Ammersee",
    "line_1": "Seestraße 9",
    "line_2": ""
  },
  "legal_form": "GMBH",
  "tax_country": "DE",
  "registration_number": "HRB 198673",
  "registration_issuer": "AMTSGERICHT MÜNCHEN",
  "registration_date": "2012-05-09",
  "registry_updated_at": "2015-11-17",
  "legal_representatives": [
    {
      "first_name": "Stefan",
      "last_name": "Schneider"
    }
  ]
  "commercial_registry_industry_key": [
      "66190 - Sonstige mit Finanzdienstleistungen verbundene Tätigkeiten",
      "70109 - Sonstige Verwaltung und Führung von Unternehmen und Betrieben",
      "70220 - Unternehmensberatung",
      "73110 - Werbeagenturen"
  ]  
}

Click here to view the full API reference.

Foreign companies examples

If the company is not registered in Germany, you can still use this service for companies in other countries. The following examples describe how to find the business registration details for a French company.

note

The field registration_issuer is only required for companies in Germany.

GET Search for business commercial registration (France)

Request

Copy
Copied
GET v1/commercial_registrations/search_by_name?name=PARISOL&country=FR

Response

Copy
Copied
{
  "name": "PARISOL",
  "registration_number": "513 937359",
  "registration_issuer": null
}

GET Automatic business data collection (France)

Request

Copy
Copied
GET  /v1/commercial_registrations/find?registration_number=513937359&country=FR

Response

Copy
Copied
{
  "name": "PARISOL",
  "address": {
    "country": "FR",
    "postal_code": null,
    "city": "NANTERRE",
    "line_1": "RUE D ARRAS 18",
    "line_2": ""
  },
  "legal_form": null,
  "tax_country": "FR",
  "registration_number": "513 937359",
  "registration_issuer": null,
  "registration_date": "2009-07-27",
  "registry_updated_at": null,
  "legal_representatives": [
    {
      "first_name": "Stefan",
      "last_name": "Schneider"
    }
  ]
}
info

Check the appendix for testing data for these endpoints.


Step 2: Upload business documents

In this step, you must create document resources for all the required documents you've collected from the business in your sign-up flow and attach them to the business. The documents are mandatory for the business identification step.

The required documents depend on different factors, such as the business's legal form, sector, etc. Check the appendix for a list of required documents per legal form.

attention

You have to make a separate API request for each document and specify the document_type. See the appendix for a list of possible values for this field.

API reference

Visit the following links to find all the endpoints related to the business documents resource, including related properties and examples.

POST Upload a document

This endpoint uploads a document and links it to the business with the business_id specified in the request URL.

You have to add the following properties to the request body:

  • document_type: The document type. For a list of possible values, check the API reference.
  • file: The file to be uploaded.
note

The request body of this endpoint is a multipart/form-data content type and parameters are transmitted as form-data and not as a raw JSON string.

Request URL

Copy
Copied
POST /v1/businesses/{business_id}/documents

Example response

The API returns an object with a unique ID, the document_id.

Copy
Copied
{
    "id": "f490f849690995853ee2d3627cffa708cdoc",
    "name": "company_foundation_document.pdf",
    "content_type": "application/pdf",
    "document_type": "FOUNDATION_DOCUMENT",
    "size": 49149,
    "customer_accessible": false,
    "created_at": "2022-09-14T15:24:23.000Z"
}

Click here to view the full API reference..


After creating a business resource and uploading the required documents, you must create the natural person(s) associated with the business and assign them to their respective roles. The natural person(s) are represented in our system by a person resource that contains their data, and then you must assign each person a dedicated role. The mandatory roles are Legal Representative and Ultimate Beneficial Owner.

Important

A business must have at least one natural person attached to it in the capacity of legal representative or beneficial owner or both simultaneously.


Step 3: Create Legal Representative(s)

In this step, you must do the following:

  • Collect the mandatory data points from the business' legal representative(s) and create a person object for each legal representative.
  • Create a legal_representative resource and assign it to its corresponding person object.

What is a legal representative?

The legal representatives are natural persons (individuals) or entities (businesses) legally appointed by a company to act on its behalf. The legal representative(s) of a company may be, for instance, its general manager(s) or its managing director(s). The names of a business' legal representatives (Gesellschafter) are usually recorded in the company's commercial register.

Important
  • A business must have at least one legal representative.
  • If a business has more than one legal representative, make sure to create and link all of them to the business object on our system to avoid any delays during the business identification process.

API reference

Visit the following links to find all the endpoints related to the legal representative resource, including related properties and examples.

Related webhook events


Create person resource(s) for each legal representative

For each of the business' legal representative, you must collect the following mandatory information and pass them to Solaris in the request body of the following endpoint:

Important

You have to create a separate person object for each legal representative associated with the business.

POST Create person

This endpoint creates a person resource for the business' legal representative . Add the following mandatory data points you've collected from the customer in the request body of this endpoint:

Mandatory properties:

  • salutation
  • first_name: (including all middle names as printed on the ID document)
  • last_name: (including all middle names as printed on the ID document)
  • birth_date
  • birth_city
  • birth_country (ISO 3166-1 alpha-2 codes)
  • nationality (ISO 3166-1 alpha-2 codes)
  • address (Street, Number, City, Postal Code, Country, State).
  • mobile_number The mobile number will be verified during the identification process.
Important

You have to submit the information exactly as they appear in official documents.

Request example:

Copy
Copied
POST /v1/persons
{
    "salutation": "MR",
    "first_name": "Peter",
    "last_name": "Mustermann",
    "nationality": "DE",
    "birth_date": "1972-12-14",
    "birth_city": "Berlin",
    "birth_country": "DE",
    "mobile_number": "+49301234567",
    "address": {
        "line_1": "Musterstraße 10",
        "line_2": "",
        "postal_code": "10409",
        "city": "Berlin",
        "country": "DE",
        "state": "BE"
    }
}

Response example

The API returns a person object with a unique id. You will use this id in subsequent API calls as the value of person_id throughout the remainder of this guide.

Copy
Copied
201 Created
{
    "id": "6aeab6ab0146e0914edf335e6c1abce6cper",
    "salutation": "MR",
    "title": null,
    "first_name": "Peter",
    "last_name": "Mustermann",
    "address": {
        "line_1": "Musterstraße 10",
        "line_2": null,
        "postal_code": "10409",
        "city": "Berlin",
        "country": "DE",
        "state": "BE"
    },
    "email": null,
    "mobile_number": "+49301234567",
    "birth_name": null,
    "birth_date": "1972-12-14",
    "birth_city": "Berlin",
    "birth_country": "DE",
    "nationality": "DE",
    "employment_status": null,
    "job_title": null,
    "fatca_relevant": null,
    "fatca_crs_confirmed_at": null,
    "business_purpose": null,
    "industry": null,
    "industry_key": null,
    "terms_conditions_signed_at": null,
    "own_economic_interest_signed_at": null,
    "aml_follow_up_date": "2028-09-23",
    "aml_confirmed_on": "2022-03-23",
    "flagged_by_compliance": false,
    "expected_monthly_revenue_cents": null,
    "vat_number": null,
    "website_social_media": null,
    "business_trading_name": null,
    "nace_code": null,
    "business_address_line_1": null,
    "business_address_line_2": null,
    "business_postal_code": null,
    "business_city": null,
    "business_country": null,
    "screening_progress": "NOT_SCREENED",
    "risk_classification_status": "NOT_SCORED",
    "customer_vetting_status": "NOT_VETTED",
    "annual_income_range": null,
    "data_terms_signed_at": null,
    "branch": null,
    "birth_province": null,
    "birth_post_code": null,
    "socioprofessional_category": null,
    "purpose_of_account_opening": null,
    "main_income_source": null,
    "work_country": null,
    "work_province": null,
    "self_declared_as_pep": null,
    "international_operativity_expectation": [],
    "registration_number": null
}

Click here to view the full API reference


Create legal representative resource(s)

For each person resource you created in the previous step, you must create a legal_representative resource, and set the value of the legal_representative attribute to the id of the person in the body of each request.

Optional attributes

  • type_of_representation: A legal_representative could have a type_of_representation, which indicates whether this legal representative can make decisions alone or jointly with other legal representatives. This attribute is optional. Possible values are ALONE, JOINT, or OTHER.
  • power_of_attorney_confirmed_at: In case of JOINT representation, legal representatives need to confirm the power of attorney's timestamp in the power_of_attorney_confirmed_at attribute.

    POST Create legal representative

This method creates a legal_representative resource on the business and binds a person to the business as a legal representative."

Request example:

Copy
Copied
POST /v1/businesses/{business_id}/legal_representatives
{
  "legal_representative_id": "6aeab6ab0146e0914edf335e6c1abce6cper",
  "type_of_representation": "ALONE",
}

Response example

The API call returns an object with a unique ID, which is the resource ID, and the details of the legal representative resource. This API call triggers this webhook event LEGAL_REPRESENTATIVE.

Copy
Copied
{
  "id": "a46578f4049f42aba9fe88a2a80fed53",
  "legal_representative_id": "6aeab6ab0146e0914edf335e6c1abce6cper",
  "legal_representative_type": "Person",
  "valid_until": "2022-12-31",
  "power_of_attorney_confirmed_at": null,
  "type_of_representation": "ALONE",
  "business_id": "880bbac68a34add190786b9c74f4c82fcbiz"
}

Click here to view the full API reference.


Step 4: Create Ultimate Beneficial Owner(s)

In this step, you must do the following:

  • Collect the mandatory data points from the business' Ultimate Beneficial Owner(s) and create a person object for each beneficial owner.
  • Create a beneficial_owner resource and assign it to its corresponding person object.
  • Include the definition of the Ultimate Beneficial Owner in your UI.
Important
  • If a business has more than one beneficial owner, make sure to create and link all of them to the business object on our system to avoid any delays during the business identification process.
  • A beneficial owner MUST be a natural person and CANNOT be another company.

What is an Ultimate Beneficial Owner?

The Ultimate Beneficial Owners (UBO) are natural persons who, directly or indirectly, own more than 25% of a company's shares.

According to the German Money Laundering Act (Geldwäschegesetz - GwG), an Ultimate Beneficial Owner is a natural person who:

  • Ultimately owns or controls the business.
  • On whose behalf a transaction is ultimately carried out.
  • On whose behalf a business relationship is ultimately established.
Important notes
  • The Ultimate Beneficial Owner must be a natural person (individual) and not a legal entity (company). If your business is owned by another company (holding or corporate structure), you need to follow the trail of indirect ownership until you find an individual.
  • After a thorough investigation, if no individual owns directly or indirectly more than 25% of the company's voting shares, you must add the legal representative(s) as fictitious beneficial owners.
  • Ultimate Beneficial Owners don't require video identification.
  • For more information about Ultimate Beneficial Owners, check the FAQ in the appendices section

API reference

Visit the following links to find all the endpoints related to the person resource and legal representative resource, including related properties and examples.

Related webhook events

Beneficial owner legal definition

Please ensure that the Ultimate Beneficial Owner's full definitions and the checkbox are available to your customers in your sign-up flow.

Full definition in English

The ultimate beneficial owner in the sense of the German Money Laundering Act (Geldwäschegesetz - GwG) is the natural person who ultimately owns or controls the contracting party, or on whose behalf a transaction is ultimately carried out or a business relationship is ultimately established. This particularly includes: 1. In case of legal persons, foundations without legal capacity and, in the case of other companies, any natural person who directly or indirectly holds more than a 25% share of the capital, controls more than 25% of the voting rights or exercises control in any comparable manner (+). Establishing the identity of the beneficial owner can be waived, though, for companies that are listed in an organised market in the EU with in accordance with Sec on 2 para. 5 of the Securities Trading Act or, in case of listed companies from a third country, if they are subject to EU-equivalent transparency requirements regarding voting rights or equivalent international standards; 2. In case of foundations or other legal arrangements with legal capacity (or similar) used to manage or distribute assets or property as trustee (trust management), or through which third parties are instructed with the management or distribution of assets or property, the ultimate beneficial owner is:

  • any natural person who is a trustor/settlor, trustee or protector, if applicable
  • any natural person who is a member of the board of the foundation,
  • any natural person designated as a beneficiary,
  • the group of natural persons in whose favour the assets are mainly to be administered or distributed, provided that the natural person who is to be the ultimate beneficial owner of the assets or property has not yet been determined
  • any natural person who, by any other means, directly or indirectly exercises control over the asset management or property or the distribution of income.
  1. In the event of acting on behalf of another party, the ultimate beneficial owner includes the party upon whose initiative the transaction is performed. If the contracting party acts as a trustee, he also acts on behalf of another party. (+) Indirect control exists particularly if corresponding shares are held by one or more associations pursuant to Sec on 20 para. 1 GwG which are controlled by a natural person. Control exists particularly if the natural person can directly or indirectly exert a controlling influence on the association pursuant to Sec on 20 para. 1 GwG. Sec on 290 para. 2 to 4 German Commercial Code (Handelsgesetzbuch - HGB) applies mutatis mutandis to the existence of a controlling influence. If, after extensive audits have been performed and without the facts according to Sec on 43 para. 1 GwG applying, no natural person has been identified or if there is any doubt that the identified person is the ultimate beneficial owner, the ultimate beneficial owner shall be the legal representative, managing partner or partner of the contracting party.

Full definition in German

Wirtschaftlich Berechtigter im Sinne des Geldwäschegesetzes, ist die natürliche Person, in deren Eigentum oder unter deren Kontrolle der Vertragspartner letztlich steht, oder auf deren Veranlassung eine Transaktion letztlich durchgeführt oder eine Geschäftsbeziehung letztlich begründet wird. Hierzu zählen insbesondere: 1. Bei juristischen Personen, außerrechtsfähigen Stiftungen und bei sonstigen Gesellschaften jede natürliche Person, welche unmittelbar oder mittelbar mehr als 25 Prozent der Kapitalanteile hält, mehr als 25 Prozent der Stimmrechte kontrolliert oder auf vergleichbare Weise Kontrolle ausübt(2). Auf die Abklärung des wirtschaftlich Berechtigten kann aber verzichtet werden bei Gesellschaften, die innerhalb der EU an einem organisierten Markt im Sinne des § 2 Abs. 5 des Wertpapierhandelsgesetzes notiert sind, oder bei börsennotierten Unternehmen aus einem Drittstaat, wenn sie dem Gemeinschaftsrecht entsprechenden Transparenzanforderungen im Hinblick auf Stimmrechtsanteile oder gleichwertigen internationalen Standards unterliegen; 2. Bei rechtsfähigen Stiftungen und Rechtsgestaltungen, mit denen treuhänderisch Vermögen verwaltet oder verteilt oder die Verwaltung oder Verteilung durch Dritte beauftragt wird, oder diesen vergleichbaren Rechtsformen zählt zu den wirtschaftlich Berechtigten:

  • jede natürliche Person, die als Treugeber, Verwalter von Trusts (Trustee) oder Protektor, sofern vorhanden,
  • jede natürliche Person, die Mitglied des Vorstands der Stiftung ist,
  • jede natürliche Person, die als Begünstigte bestimmt worden ist,
  • die Gruppe von natürlichen Personen, zu deren Gunsten das Vermögen hauptsächlich verwaltet oder verteilt werden soll, sofern die natürliche Person, die Begünstigte des verwalteten Vermögens werden soll, noch nicht bestimmt ist,
  • jede natürliche Person, die auf sonstige Weise unmittelbar oder mittelbar beherrschenden Einfluss auf die Vermögensverwaltung oder Ertragsverteilung ausübt.
  1. Bei Handeln auf Veranlassung zählt zu den wirtschaftlich Berechtigten derjenige, auf dessen Veranlassung die Transaktion durchgeführt wird. Soweit der Vertragspartner als Treuhänder handelt, handelt er ebenfalls auf Veranlassung.

Create person resource(s) for each beneficial owner

For each of the business' beneficial owners, you must collect the following mandatory information and pass them to Solaris in the request body of the following endpoint:

Important

You have to create a separate person object for each beneficial owner associated with the business.

POST Create person

This endpoint creates a person resource for the business' beneficial owner. Add the following mandatory data points you've collected from the customer in the request body of this endpoint:

Mandatory properties:

  • salutation:
  • first_name: (including all middle names as printed on the ID document)
  • last_name: (including all middle names as printed on the ID document)
  • birth_date
  • nationality (ISO 3166-1 alpha-2 codes)
Important

You have to submit the information exactly as they appear in official documents.

Request example:

Copy
Copied
POST /v1/persons
{
    "salutation": "MR",
    "first_name": "Max",
    "last_name": "Mustermann",
    "nationality": "DE",
    "birth_date": "1982-06-20"
}

Response example

The API returns a person object with a unique id. You will use this id in subsequent API calls as the value of person_id throughout the remainder of this guide.

Copy
Copied
201 Created
{
    "id": "dc1a6812a14f6cc338cd084208535bcdcper",
    "salutation": "MR",
    "title": null,
    "first_name": "Max",
    "last_name": "Mustermann",
    "address": {},
    "email": null,
    "mobile_number": null,
    "birth_name": null,
    "birth_date": "1982-06-20",
    "birth_city": null,
    "birth_country": null,
    "nationality": "DE",
    "employment_status": null,
    "job_title": null,
    "fatca_relevant": false,
    "fatca_crs_confirmed_at": "2017-01-01T00:00:00.000Z",
    "business_purpose": null,
    "industry": null,
    "industry_key": null,
    "terms_conditions_signed_at": null,
    "own_economic_interest_signed_at": null,
    "aml_follow_up_date": "2028-09-23",
    "aml_confirmed_on": "2022-03-23",
    "flagged_by_compliance": false,
    "expected_monthly_revenue_cents": null,
    "vat_number": null,
    "website_social_media": null,
    "business_trading_name": null,
    "nace_code": null,
    "business_address_line_1": null,
    "business_address_line_2": null,
    "business_postal_code": null,
    "business_city": null,
    "business_country": null,
    "screening_progress": "NOT_SCREENED",
    "risk_classification_status": "NOT_SCORED",
    "customer_vetting_status": "NOT_VETTED",
    "annual_income_range": null,
    "data_terms_signed_at": null,
    "branch": null,
    "birth_province": null,
    "birth_post_code": null,
    "socioprofessional_category": null,
    "purpose_of_account_opening": null,
    "main_income_source": null,
    "work_country": null,
    "work_province": null,
    "self_declared_as_pep": null,
    "international_operativity_expectation": [],
    "registration_number": null
}

Click here to view the full API reference

Additionally, you need to clarify whether there is an additional agreement that allows any external person or business to have a right of ownership. To collect this information, display the following question to your customers as a check box during the sign-up process:

Are there contracts or agreements concluded outside the company register which reflect a possible ownership based on voting rights distributions?

If the customer checks this box, they must provide supplementary documentation to reflect the ownership. The required documents have the document type: SHARE_HOLDERS_AGREEMENT. Additionally, you need to store the response and timestamp of the customer's response and provide it when requested by Solaris.


Create beneficial owner resource(s)

For each person resource you created in the previous step, you must create a beneficial_owner resource. Set the value of the person_id attribute to the id of the person in the body of each request, along with the following properties:

  • voting_share
  • fictious

POST Create beneficial owner(s)

This method creates a beneficial_owner resource on the business and binds a person to the business as a beneficial owner.

Request example:

Copy
Copied
POST /v1/businesses/{business_id}/beneficial_owners
{
  "person_id": "dc1a6812a14f6cc338cd084208535bcdcper",
  "voting_share": "70.50",
  "fictitious": "false",
  "relationship_to_business": "DOMINANT_INFLUENCE_OVER_SHARE_CAPITAL"
}

Response example

The API call returns an object with a unique ID, which is the resource ID, and the details of the beneficial owner resource. This API call triggers this webhook event BENEFICIAL_OWNER.

Copy
Copied
{
  "id": "a9d0975ce42e38dc8e4da435786dce8dcbeow",
  "beneficial_owner_id": "dc1a6812a14f6cc338cd084208535bcdcper",
  "person_id": "dc1a6812a14f6cc338cd084208535bcdcper",
  "valid_until": null,
  "voting_share": "70.5",
  "business_id": "880bbac68a34add190786b9c74f4c82fcbiz",
  "fictitious": "false",
  "relationship_to_business": "DOMINANT_INFLUENCE_OVER_SHARE_CAPITAL"
}

Click here to view the full API reference.


Step 5: Complete the business identification (BKYC)

In this step, you will trigger the business identification process to identify the business legal entity and the legal representative(s) on the business account.

API reference

API reference

Visit the following link to find all the endpoints related to the business identification resource, including related properties and examples.

Related webhook events

POST Initiate business identification

In this step, you initiate the business identification process, referred to as solarisident, which automatically triggers both the legal identification of the business and the video identification of all applicable natural person(s).

You can trigger the business identification process by calling the following endpoint and specifying the identification method in the request body. The default method is idnow.

Request example

Copy
Copied
POST /v1/businesses/{business_id}/identifications
{
  "method": "idnow"
}

Response example

The API response returns an identification object with a unique id, which is the ID of the business identification resource, as well as the status of the identification process (as a whole).

Additionally, the payload includes individual identification objects for the video identification sessions for legal representative(s), including the id of the person identification resource, IDnow status and IDnow reference and url to which you must redirect the legal representative to complete the identification process.

The payload also includes information about the legal identification process, including its dedicated status. You also need to track the progress of this process, particularly the missing information field. Solaris will highlight through this field if there are compliance questions that require answers from the business.

Copy
Copied
{
  "id": "4c74c804eaea5d2a2d64ef400a27a4d3bid",
  "method": "idnow",
  "reference": null,
  "status": "created",
  "completed_at": null,
  "legal_representatives": [
    {
      "person_id": "992de312a545bb24a88ddbf57ae8b1ffcper",
      "identifications": [
        {
          "id": "79c98baa85904c668981855f07f03216cidt",
          "reference": "TST-SMFKT",
          "url": "https://go.test.idnow.de/solarisbankvideoidentstaging/identifications/79c98baa85904c668981855f07f03216cidt",
          "status": "pending",
          "completed_at": null,
          "method": "idnow"
        }
      ]
    },
    {
      "person_id": "7606b518e71be9c2adf72a811f9fae6fcper",
      "identifications": [
        {
          "id": "1bb49f9dec3a57ae69ad3c3183316c9dcidt",
          "reference": "TST-VWKRA",
          "url": "https://go.test.idnow.de/solarisbankvideoidentstaging/identifications/1bb49f9dec3a57ae69ad3c3183316c9dcidt",
          "status": "pending",
          "completed_at": null,
          "method": "idnow"
        }
      ]
    }
  ],
  "legal_identification_status": "created",
  "legal_identification_reason": null,
  "legal_identification_missing_information": [],
  "business_id": "880bbac68a34add190786b9c74f4c82fcbiz"
}

Click here to view the full API reference.


Manual video identification

In the following cases, your solution might need to manually trigger video identification for the legal representatives or other applicable natural person(s):

1. New legal representatives found

During the legal identification of the business, our operations team might find additional legal representatives related to the business which have not been disclosed at the beginning of the onboarding process. In this case, the team creates the new persons on our system and assigns them to the business.

Afterward, your solution must manually trigger the video identification of the newly added legal representative(s) by completing the following steps:

  1. You'll receive a webhook notification from the event legal_representative, which includes the legal_representative_id of the discovered legal representative.
  2. Initiate a video identification with idnow for the new person.
  3. Trigger the identification session. The API response will return the identification URL to which you must redirect the legal representative to complete the video identification.

2. Failed video identification(s)

If any of the initially triggered video identification(s) failed for whatever reason, and you want to create a new identification, you also have to trigger the video identification manually.

API reference

Visit the following link to find all the endpoints related to the different methods of customer identification (KYC), including related properties and examples.

note

The previous link includes all endpoints for different KYC methods. This section includes the relevant endpoints required for video identification with IDnow.

Related webhook events


POST Create identification

This endpoint creates an identification resource for the person specified in the request URL. You must add the following properties in the request body:

  • method: The identification method, select idnow.
  • language: The customer's preferred language for the identification process. Possible values are EN and DE.
  • proof_of_address_type: The type of document submitted by the customer as a proof of address. This field is mandatory if the customer's identification document does not include their address.
  • proof_of_address_issued_at: The date when the proof of address document was issued. This field is mandatory if the customer's identification document does not include their address. It must NOT be older than 6 months.
attention

This endpoint does not send a request to the identification provider to start the identification process.

Request example

Copy
Copied
POST /v1/persons/{person_id}/identifications
{
  "method": "idnow",
  "language": "DE",
  "proof_of_address_type": "GAS_BILL",
  "proof_of_address_issued_at": "2022-03-03"
}

Response example

The API call returns an identification object with a unique id, the identification_id, as well as the identification status, set initially to created.

Copy
Copied
{
    "id": "6dc54352d6793a892e0702850d07b831cidt",
    "reference": null,
    "url": null,
    "status": "created",
    "completed_at": null,
    "method": "idnow",
    "proof_of_address_type": "GAS_BILL",
    "proof_of_address_issued_at": "2022-03-03",
    "language": "DE",
    "iban": null,
    "terms_and_conditions_signed_at": null,
    "authorization_expires_at": null,
    "confirmation_expires_at": null
}

Click here to view the full API reference.

GET List supported documents for a person identification

Prior to redirecting your customer to complete the identification process, you can fetch the supported documents to share it with the customer beforehand.

This endpoint returns an array of document types that a customer may use to identify themselves along with a list of allowed issuing countries. The issuing_countries are provided as ISO country codes (ISO-3166-1 alpha 2). If the customer does not provide a supported document type in the identification process, then their identification will eventually fail.

Request URL

Copy
Copied
GET /v1/persons/{person_id}/identifications/{id}/supported_documents

Click here to view the full API reference

PATCH Request person identification

This endpoint triggers the identification flow with IDnow for the specific customer. The status of the identification will change to pending after calling this endpoint.

Request URL

Copy
Copied
PATCH /v1/persons/{person_id}/identifications/{id}/request

Response example

The API call returns the identification object with the status pending. The status remains pending until the customer completes the identification. Additionally, the payload includes the url (valid for 14 days), which the customer can use to identify via the web browser, and the reference, which is the identification token (format: ABCDEFGH ), an internal IDnow identifier.

Copy
Copied
{
    "id": "6dc54352d6793a892e0702850d07b831cidt",
    "reference": "TST-KCCEY",
    "url": "https://go.test.idnow.de/solarisbankvideoidentsandbox/identifications/6dc54352d6793a892e0702850d07b831cidt",
    "status": "pending",
    "completed_at": null,
    "method": "idnow",
    "proof_of_address_type": "GAS_BILL",
    "proof_of_address_issued_at": "2022-03-03",
    "language": "DE",
    "iban": null,
    "terms_and_conditions_signed_at": null,
    "authorization_expires_at": null,
    "confirmation_expires_at": null,
    "estimated_waiting_time": 60
}

Click here to view the full API reference.

You must trigger the KYC flow in your application via the IDnow SDK and the customer must complete the identification with the IDnow agent. You can also share with the customer the supported documents that they must present during the session.

IDnow Video-identification process

  • Before being put in touch with a video identification agent, your customer is redirected to an IDnow-branded landing page, where they are asked to give their consent to IDnow's Terms & Conditions and confirm that they have a valid ID document at hand. This ID document will be shown via webcam to the agent during the video identification.
  • Additionally, your customer must also provide their valid mobile number during their identification. IDnow agent will verify this mobile number by sending an SMS OTP, which the customer will need to provide during the call. Solaris will re-use the verified mobile number of a successful IDnow video identification as the customer's verified mobile number.
  • Once connected with an IDnow agent, your customer is greeted on behalf of Solaris ( « You are identifying for a service of Solaris » ) or on your behalf ( « You are identifying for a service of /Your Brand Name/, empowered by Solaris » ), depending on the setup you have agreed upon with Solaris.
  • The call takes place either in English or in German. The agent goes on to verify the customer's mobile number and the customer's data, such as first_name and last_name. In addition, the agent populates specific additional attributes of the person resource during the call.
note

While most video identifications are immediately set to successful, an identification status could be set to an intermediary status pending_successful. In such cases, a second-line agent at IDnow reviews the outcome of the video identification. This process typically takes minutes but can take up to 24 hours before the identification status is updated to a final successful status. However, you can already offer services to the customer until the review results.

GET Retrieve person identification

This endpoint returns a completed person identification (i.e., the person identification process was successful). If you use the include_documents filter, this method will also return the documents submitted by the customer during the identification process.

To download any of the documents submitted during the identification process, you can use the document unique id and download the files using the Document resource endpoints.

Request URL

Copy
Copied
GET /v1/persons/{person_id}/identifications/{id}

Response example

Copy
Copied
{
  "id": "6dc54352d6793a892e0702850d07b831cidt",
  "reference": "TST-KCCEY",
  "url": "https://go.test.idnow.de/solarisbankvideoidentsandbox/identifications/6dc54352d6793a892e0702850d07b831cidt",
  "status": "successful",
  "completed_at": "2022-07-14T18:18:28.000Z",
  "method": "idnow",
  "proof_of_address_type": "GAS_BILL",
  "proof_of_address_issued_at": "2022-03-03",
  "language": "DE",
  "person_id": "7cf09c3c5547b974a664201f24b454eecper",
  "address": {
    "line_1": "Amrumerstrasse",
    "line_2": "14",
    "postal_code": "13353",
    "city": "Berlin",
    "country": "DE"
  },
  "documents": [
    {
      "id": "448b75fa1c57eecda41d91c66c22faa6cdoc",
      "name": "file1.pdf",
      "content_type": "application/json",
      "document_type": "KYC_REPORT",
      "size": 803580
    },
    {
      "id": "94eb22a9311be9a1fbb698c448b0b337cdoc",
      "name": "file2.jpg",
      "content_type": "image/jpeg",
      "document_type": "SIGNATURE",
      "size": 25349
    }
  ]
}

Click here to view the full API reference.

Other identification endpoints


Compliance questions

Our legal and compliance team might have additional questions or require further information from your customers during the legal identification process.

For this purpose, you have to implement the following additional endpoints in your solution:

  • Get the compliance questions posted by Solaris.
  • Redirect the questions to your customers and collect their answers.
  • Forwards the answers to Solaris.
  • Mark the identification as ready for review to resume the legal identification process.

In cases where Solaris requires more clarity on certain topics during the business identification, you will receive a notification on the BUSINESS_IDENTIFICATION webhook. Afterward, you need to call the GET Retrieve a business identification to get the details.

If Solaris has compliance questions for the business, the payload will have the following fields with these values:

  • legal_identification_status = information_required
  • legal_identification_missing_information = COMPLIANCE_QUESTIONS

These questions are created by Solaris, and you are required to redirect them to your business customer and provide the ability for them to answer those questions.

GET Retrieve compliance questions

To get the compliance questions, call the following endpoint:

Request URL

Copy
Copied
GET /v1/businesses/{business_id}/identifications/{business_identification_id}/legal_identification/questions

Response example

The API call returns an object, including the question(s) with a unique ID and the question text. You have to redirect these questions to your customers and get their answers in your workflow.

Copy
Copied
{
  "question_id": "ebb463137becc09788dfe21fc066e670qstn",
  "question_text": "Please provide the license for security / guarding services (Bewachungsgewerbe): § 34a GewO",
  "legal_identification_id": "14eb210435e09ab7f6a06c8b9b86ce27lid",
  "business_identification_id": "4c74c804eaea5d2a2d64ef400a27a4d3bid",
  "business_id": "880bbac68a34add190786b9c74f4c82fcbiz",
  "answer_id": null,
  "answer_text": "string",
  "asked_at": "2021-07-16T13:38:06.000Z",
  "answered_at": null
}

Click here to view the full API reference.

You should provide your customers with a dedicated page to answer all the questions separately.

Create answers for compliance questions

After getting the answers to the compliance questions from your customer, call the following endpoint to share the answers with Solaris.

note

You have to make a separate API call for each answer.

Request URL

You have to provide the question's answer in the request body of this endpoint.

Copy
Copied
POST /v1/businesses/{business_id}/identifications/{business_identification_id}/legal_identification/questions/{question_id}/answers

Click here to view the full API reference.

PATCH Update business legal identification

After adding all answers to the compliance questions, use this method to update the legal identification and mark it as ready to resume the identification process. Calling this endpoint changes the legal_identification_status from information_required to pending.

Request URL

Copy
Copied
PATCH /v1/businesses/{business_id}/identifications/{id}/legal_identification/mark_as_ready

Click here to view the full API reference.


Identification statuses

There are three different statuses related to the business identification process:

1. Solarisident status

The Solarisident process includes both legal identification and the video-identification. It's represented on the system with the property status, which is automatically set to created when creating a business identification.

Successful legal identification and video identification(s) set the status of the business identification (solarisident) to successful.

Check the appendix section for more information about the different status values and descriptions.

2. Legal identification status

The legal identification process is represented by the property legal_identification_status. When a business identification is created, this value is automatically set to created.

Check the appendix section for more information about the different status values and descriptions.

Video identification process

For each natural person undergoing video identification, a unique video-identification object is returned in the API response, including status, which is IDnow status, initially set to pending as long as the corresponding legal representative has not video-identified with idnow.

Check the appendix section for more information about the different status values and descriptions.


What's next?

Congratulations! You've successfully completed the business identification process (BKYC).

Check the following appendices section for additional information on enums and testing data.

For an overview of Solaris' Customer KYC products, check the overview page.

Useful resources

Check the following links for additional related guides and API reference documentation:


Appendix I: Enums

CRS company type

The field crs_company_type is required to collect the mandatory tax information and create the business tax_identification resource. The following table includes the possible values for this field and their descriptions:

Enum Description
FE_REPORTING Reporting financial institution.
FE_NON_REPORTING Non-reporting financial institution.
NFE_ACTIVE_OTHER Active NFE - A corporation whose shares are regularly traded on at least one recognized stock exchange (or a company affiliated with it), a government entity, an international organization, a central bank, or a legal entity wholly owned by NFE
NFE_PASSIVE Passiver NFE Passive NFE - Non-active NFE
NFE_PASSIVE_INVESTMENT Inactive NFE/NFFE or an Investment Entity that is a Financial Institution in a jurisdiction not participating in the CRS and that is managed by another Financial Institution

Document types

The following table includes the possible values for the field document_type and their descriptions.

Enum Description
ANNUAL_FINANCIAL_STATEMENT A business or a company's annual financial statement.
KYC_REPORT The KYC report generate after a successful customer identification.
ID_DOCUMENT An person's identification document, such as passport or ID.
SIGNATURE A signature example.
PICTURE A picture or a scanned document of any other type.
QES_DOCUMENT A document related to a Qualified Electronic Signature (QES).
SIGNED_CONTRACT A signed contract of any kind.
SIGNED_QES_DOCUMENT A document signed by a Qualified Electronic Signature (QES).
REGISTER_CHECK A register check.
REGISTER_EXTRACT A business or a company's commercial register excerpt or a similar document.
FOUNDATION_DOCUMENT The foundation document of a company or business.
SCHUFA_COMPACT_REPORT A compact SCHUFA report.
SCHUFA_GWG_REPORT A GWG SCHUFA report.
SCHUFA_FULL_REPORT A full SCHUFA report about a person.
SCHUFA_SHORT_REPORT A short SCHUFA report about a person.
CREDIT_AGENCY_REPORT A report issued by a credit agency.
SHARE_HOLDERS_AGREEMENT A business or a company's shareholders agreement.
SHAREHOLDERS_LIST A business or a company's shareholders list.
TRADING_LICENSE A business or a company's trading license.
TRANSPARENCY_REGISTER_EXTRACT An extract of a transparency register.
INVOICE An invoice of any kind.
OTHER Any other type of document.
VIDEO A video of any kind.
VAT_CERTIFICATE VAT registration certificate

Idnow status

The following table includes the possible values for the field status for the video identification process carried out by IDnow and the related description of each status.

Status Description
created The identification resource has been created for the customer.
pending The identification process has been triggered and the video identification URL and reference are generated. You must redirect the customer to the URL to complete the identification process with IDnow.
pending_successful The video identification was successful, but will be reviewed by the identification provider. You can already offer banking services to the customer at this stage. Once reviewed by the provider, the identification will be marked either as resolved positively (successful) or negatively (failed or canceled). A bank account will be automatically blocked if the identification is eventually marked as failed or canceled.
pending_failed The identification is currently under review. You cannot offer banking services to the customer at this stage. The identification might eventually turn to successful, but it is unlikely.
successful The video identification was successful. The customer can be onboarded. Please note that the customer's data might have been updated during the identification session.
aborted The customer aborted the identification process. The customer can still video-identify using the same URL.
canceled The provider canceled the video identification. The customer should video-identify again using the same URL.
failed The identification was unsuccessful. You *cannot onboard the customer or offer any banking services to them.

IDnow provides a reason for the canceled and aborted status. No reason can be disclosed for the final failed status.

Identification documents

  1. List of the accepted passports for videoIdent: here
  2. List of accepted passports for postIdent: here
  3. Search for a identification document: here

List of passports with address

The following table shows the list of documents, that has the address included in the identification document, and allows you to perform identification without the proof of address document.

Document Issuer Country Type (ID/PP)
MLT-BO-02001 Malta ID
MLT-BO-03001 Malta ID
SVK-BO-02001 Slovakia ID
SVK-BO-05001 Slovakia ID
SVK-BO-04001 Slovakia ID
ITA-BO-04003 Italy ID
ITA-BO-03004 Italy ID
ITA-BO-03002 Italy ID
ITA-BO-03001 Italy ID
ITA-BO-03003 Italy ID
DEU-BO-01003 Germany ID
DEU-BO-02001 Germany ID
SGP-BO-01001-A Singapore ID
SGP-BO-01001 Singapore ID
CZE-BO-04001 Czech Republic ID
CZE-BO-04002 Czech Republic ID
IND-AO-01001 India Passport
CHN-AO-04003 China Passport
BGR-AO-01005 Bulgaria Passport
SVN-AO-02001-02003 Slovenia Passport
SVN-AO-02004 Slovenia Passport
SVN-BO-02001 Slovenia ID
SVN-AO-01004 Slovenia Passport
POL-BO-02001-02003 Poland ID
ESP-BO-03001 Spain ID
ESP-BO-05001 Spain ID
HRV-BO-02001 Croatia ID
HRV-AO-02001 Croatia Passport
FRA-BO-02002 France ID
FRA-AO-03001-03003 France Passport
MAR-AO-02001 Morocco Passport

Tax country

The following tables includes the possible values for the field tax_country:

Enum Country
DE Germany
IT Italy
AT Austria
GB United Kingdom
CZ Czech Republic
FR France
BE Belgium
LU Luxembourg
NL The Netherlands
ES Spain
PT Portugal

Sector

The following are the possible values for the field sector.

  • ECONOMICALLY_SELF_EMPLOYED
  • ECONOMIC_DEPENDENT
  • FOREIGN_COMPANIES
  • FOREIGN_ECONOMIC_DEPENDENT
  • FOREIGN_PRIVATE_INDIVIDUAL
  • FOREIGN_SELF_EMPLOYED_PRIVATE_PERSON
  • GERMAN_BANKS
  • MUNICIPALITY_AND_MUNICIPALITY_ASSOCIATION
  • OTHER_COMPANIES_WORKMAN
  • OTHER_COMPANIES
  • OTHER_PRIVATE_INDIVIDUAL

Legal form

The selected value for the field tax_country influences the accepted values for the field legal_form. The following are the possible values for the field legal_form per each tax_country.

Austria (AT)

  • AT_SE
  • AT_OHG
  • AT_KG
  • AT_AG
  • AT_GESMBH
  • AT_EG
  • AT_GBR
  • AT_EV
  • AT_SOLE_PROPRIETORSHIP
  • AT_SELF_EMPLOYED

Belgium (BE)

  • BE_SNC
  • BE_SCS
  • BE_SA
  • BE_SPRL
  • BE_SE
  • BE_SCA
  • BE_SC
  • BE_SCRI
  • BE_SEP
  • BE_SF
  • BE_SPRLU
  • BE_SOLE_PROPRIETORSHIP
  • BE_SELF_EMPLOYED

Czech Republic (CZ)

  • CZ_AS
  • CZ_SRO
  • CZ_KS
  • CZ_VOS
  • CZ_DRUZSTVO
  • CZ_FYZICKA_OSOBA
  • CZ_SOLE_PROPRIETORSHIP
  • CZ_SELF_EMPLOYED

France (FR)

  • FR_SNC
  • FR_SCS
  • FR_SA
  • FR_SAS
  • FR_SARL
  • FR_SE
  • FR_SCA
  • FR_EURL
  • FR_SC
  • FR_SCOP
  • FR_SELARL
  • FR_SOLE_PROPRIETORSHIP
  • FR_SELF_EMPLOYED

Germany & others

Solaris accepts the following legal forms for companies in Germany and other countries that are not specified in our system:

  • AG
  • EG
  • EK
  • GBR
  • GMBH
  • GMBH_CO_KG
  • GMBH_I_GR
  • KG
  • KGAA
  • LTD
  • MUNICIPALITY
  • MUNICIPAL_COMPANY
  • NONE
  • OHG
  • PARTG
  • PRIVATE_PERSON
  • SAVINGS_BANK
  • SE
  • SELF_EMPLOYED
  • SOLE_PROPRIETORSHIP
  • UG
  • UG_I_GR
  • FOREIGN_CORPORATION

Italy (IT)

  • IT_SE
  • IT_SNC
  • IT_SAS
  • IT_SPA
  • IT_SRL
  • IT_SAPA
  • IT_SCPA
  • IT_SCARL
  • IT_SCOP
  • IT_SS
  • IT_SOLE_PROPRIETORSHIP
  • IT_SELF_EMPLOYED

Luxembourg (LU)

  • LU_SNC
  • LU_SCS
  • LU_SA
  • LU_SARL
  • LU_SE
  • LU_SCA
  • LU_SCSP
  • LU_SARLS
  • LU_SC
  • LU_SCOP
  • LU_SOLE_PROPRIETORSHIP
  • LU_SELF_EMPLOYED

Portugal (PT)

  • PT_SNC
  • PT_SC
  • PT_SA
  • PT_LDA
  • PT_SE
  • PT_SUNI
  • PT_EIRL
  • PT_SCIV
  • PT_COP
  • PT_SOLE_PROPRIETORSHIP
  • PT_SELF_EMPLOYED

Spain (ES)

  • ES_SRC
  • ES_SC
  • ES_SA
  • ES_SAS
  • ES_SRL
  • ES_SE
  • ES_SCA
  • ES_SLNE
  • ES_SAU
  • ES_SLU
  • ES_SPRO
  • ES_SCOP
  • ES_SOLE_PROPRIETORSHIP
  • ES_SELF_EMPLOYED

The Netherlands (NL)

  • NL_VOF
  • NL_CV
  • NL_NV
  • NL_BV
  • NL_SE
  • NL_CVOA
  • NL_COPV
  • NL_MTS
  • NL_SOLE_PROPRIETORSHIP
  • NL_SELF_EMPLOYED

United Kingdom

  • GB_SE
  • GB_PARTNERSHIP
  • GB_LP
  • GB_PLC
  • GB_LTD
  • GB_COPS
  • GB_UAS
  • GB_PRCU
  • GB_PUCU
  • GB_SOLE_PROPRIETORSHIP
  • GB_SELF_EMPLOYED

Sector, tax country, and legal form mapping

Please note that there are certain dependencies between the fields tax_country, sector, and legal_form. For example, based on the value selected for the field tax_country, certain values will be accepted for the field sector, and based on the value selected for the field sector, certain values will be accepted for the field legal_form.

The following sections give an overview of the mapping between these fields.

Tax country and sector mapping

The selected value for the field tax_country influences the accepted values for the field sector. The following table gives an overview about the mapping of values between the field tax_country and sector.

Tax country Allowed values for sector
DE
  • ECONOMICALLY_SELF_EMPLOYED
  • ECONOMIC_DEPENDENT
  • GERMAN_BANKS
  • MUNICIPALITY_AND_MUNICIPALITY_ASSOCIATION
  • OTHER_COMPANIES_WORKMAN
  • OTHER_COMPANIES
  • OTHER_PRIVATE_INDIVIDUAL
All other countries
  • FOREIGN_COMPANIES
  • FOREIGN_ECONOMIC_DEPENDENT
  • FOREIGN_PRIVATE_INDIVIDUAL
  • FOREIGN_SELF_EMPLOYED_PRIVATE_PERSON

Sector and legal form mapping

The selected value for the field sector influences the accepted values for the field legal_form. The following table gives an overview about the mapping of values between the field sector and legal_form.

Sector Allowed values for legal form
OTHER_COMPANIES
  • AG
  • EG
  • GBR
  • GMBH_CO_KG
  • GMBH_I_GR
  • GMBH
  • KG
  • KGAA
  • LTD
  • OHG
  • PARTG
  • SE
  • UG_I_GR
  • UG
OTHER_COMPANIES_WORKMAN
  • EK
  • GBR
  • LTD
  • SELF_EMPLOYED
  • SOLE_PROPRIETORSHIP
FOREIGN_COMPANIES
  • FOREIGN_CORPORATION
  • NONE
GERMAN_BANKS
  • SAVINGS_BANK
MUNICIPALITY_AND_MUNICIPALITY_ASSOCIATION
  • MUNICIPALITY
  • MUNICIPAL_COMPANY
ECONOMICALLY_SELF_EMPLOYED
  • EK
  • GBR
  • SELF_EMPLOYED
  • SOLE_PROPRIETORSHIP
NON_PROFIT_ORGANIZATION
  • EV
  • NEV

Legal identification status

The following table includes the possible values for the field legal_identification_status for the legal identification process of the business legal entity carried out by Solaris and the related description of each status.

Status Description
created The legal identification was initiated and will be conducted shortly.
information_required The legal identification cannot be conducted because Solaris is missing one or more required documents. Refer to the legal_identification_missing_information array to determine which document(s) is/are missing.
blocked_internally The legal identification is put on hold due to additional internal checks
successful The legal identification was conducted successfully.
failed The legal identification was marked as failed. Refer to the legal_identification_reason to find out why.
expired The legal identification was not updated to terminal status in 90 days

NACE code

The Statistical Classification of Economic Activities in the European Community, commonly known as NACE, is the industry standard classification system used in the European Union.

NACE uses four hierarchical levels:

  • Level 1: 21 sections identified by alphabetical letters A to U;
  • Level 2: 88 divisions identified by two-digit numerical codes (01 to 99);
  • Level 3: 272 groups identified by three-digit numerical codes (01.1 to 99.0);
  • Level 4: 629 classes identified by four-digit numerical codes (01.11 to 99.00).

The first four digits of the code, which is the first four levels of the classification system, are the same in all European countries. National implementations may introduce additional levels. The fifth digit might vary from country to country and further digits are sometimes placed by suppliers of databases.

For example, if the NACE code A 01.11 (Growing of cereals (except rice), leguminous crops and oil seeds) would apply to the person/business, supply the value like such:

nace_code = "A 01.11"
info

Please note that using NACE codes replaces using the fields industry and industry_key.

Please see the following resources for a complete list of NACE codes:

Solarisident status

The following table includes the possible values for the field status, which refers to the overall status of the business identification process (BKYC), including the legal identification of the business legal entity carried out by Solaris and the video identification of the business's natural persons.

Status Description
created The legal identification was initiated and will be conducted shortly.
pending A business identification (solarisIdent) is mark_as_successful by partner
successful Both steps of the business identification process (solarisIdent) were completed successfully.
failed The business identification process (solarisIdent) will not continue. The business couldn't be identified. A reason will not be provided. Verify the status of either the legal identification or the individual video identifications instead.
expired The business identification process (solarisIdent) was not completed within six months of being initiated. Either the legal identification or one of the individual video identifications was not finished on time.

Registration district and registration issuer

The following are the possible values for the fields registration_district and registration_issuer. These fields are only relevant for customers in Germany.

  • AACHEN
  • ALTENBURG
  • AMBERG
  • AMTSGERICHT
  • ANSBACH
  • APOLDA
  • ARNSBERG
  • ARNSTADT
  • ARNSTADT_ZWEIGSTELLE_ILMENAU
  • ASCHAFFENBURG
  • AUGSBURG
  • AURICH
  • BAD_HERSFELD
  • BAD_HOMBURG_VDH
  • BAD_KREUZNACH
  • BAD_OEYNHAUSEN
  • BAD_SALZUNGEN
  • BAMBERG
  • BAYREUTH
  • BERLIN_CHARLOTTENBURG
  • BIELEFELD
  • BOCHUM
  • BONN
  • BRAUNSCHWEIG
  • BREMEN
  • CHEMNITZ
  • COBURG
  • COESFELD
  • COTTBUS
  • DARMSTADT
  • DEGGENDORF
  • DORTMUND
  • DRESDEN
  • DUISBURG
  • DUEREN
  • DUESSELDORF
  • EISENACH
  • ERFURT
  • ESCHWEGE
  • ESSEN
  • FLENSBURG
  • FRANKFURT_AM_MAIN
  • FRANKFURT_ODER
  • FREIBURG
  • FRIEDBERG
  • FRITZLAR
  • FULDA
  • FUERTH
  • GELSENKIRCHEN
  • GERA
  • GIESSEN
  • GOTHA
  • GOETTINGEN
  • GREIFSWALD
  • GREIZ
  • GUESTROW
  • GUETERSLOH
  • HAGEN
  • HAMBURG
  • HAMM
  • HANAU
  • HANNOVER
  • HEILBAD_HEILIGENSTADT
  • HILDBURGHAUSEN
  • HILDESHEIM
  • HOF
  • HOMBURG
  • INGOLSTADT
  • ISERLOHN
  • JENA
  • KAISERSLAUTERN
  • KASSEL
  • KEMPTEN_ALLGAUE
  • KIEL
  • KLEVE
  • KOBLENZ
  • KOELN
  • KOENIGSTEIN
  • KORBACH
  • KREFELD
  • LANDAU
  • LANDSHUT
  • LEBACH
  • LEIPZIG
  • LEMGO
  • LIMBURG
  • LUEBECK
  • LUDWIGSHAFEN_A_RHEIN_LUDWIGSHAFEN
  • LUDWIGSLUST
  • LUENEBURG
  • MAINZ
  • MANNHEIM
  • MARBURG
  • MEININGEN
  • MEMMINGEN
  • MERZIG
  • MOENCHENGLADBACH
  • MONTABAUR
  • MUEHLHAUSEN
  • MUENCHEN
  • MUENSTER
  • NEUBRANDENBURG
  • NEUNKIRCHEN
  • NEURUPPIN
  • NEUSS
  • NORDHAUSEN
  • NUERNBERG
  • OFFENBACH_AM_MAIN
  • OLDENBURG_OLDENBURG
  • OSNABRUECK
  • OTTWEILER
  • PADERBORN
  • PASEWALK
  • PASSAU
  • PINNEBERG
  • POESSNECK
  • POESSNECK_ZWEIGSTELLE_BAD_LOBENSTEIN
  • POTSDAM
  • RECKLINGHAUSEN
  • REGENSBURG
  • RIBNITZ_DAMGARTEN
  • ROSTOCK
  • RUDOLSTADT
  • RUDOLSTADT_ZWEIGSTELLE_SAALFELD
  • SAARBRUECKEN
  • SAARLOUIS
  • SCHWEINFURT
  • SCHWERIN
  • SIEGBURG
  • SIEGEN
  • SOEMMERDA
  • SONDERSHAUSEN
  • SONNEBERG
  • ST_INGBERT_ST_INGBERT
  • ST_WENDEL_ST_WENDEL
  • STADTHAGEN
  • STADTRODA
  • STEINFURT
  • STENDAL
  • STRALSUND
  • STRAUBING
  • STUTTGART
  • SUHL
  • TOSTEDT
  • TRAUNSTEIN
  • ULM
  • VOELKLINGEN
  • WALSRODE
  • WAREN_MUERITZ
  • WEIDEN_ID_OPF
  • WEIMAR
  • WETZLAR
  • WIESBADEN
  • WISMAR
  • WITTLICH
  • WUPPERTAL
  • WUERZBURG
  • ZWEIBRUECKEN

Registration type

  • AT_FB_CD
  • AT_GEM_CD
  • AT_IDENT_CD
  • AT_LAE_CD
  • AT_ZVR_CD
  • BE_OND_CD
  • BG_BULSTAT_CD
  • BG_OTHER_CD
  • BG_UIC_CD
  • BG_VAT_CD
  • CY_DRCOR_CD
  • CY_NOTAP_CD
  • CY_TIC_CD
  • CY_VAT_CD
  • CZ_ICO_CD
  • CZ_NID_CD
  • DE_GNR_CD
  • DE_HRA_CD
  • DE_HRB_CD
  • DE_NOTAP_CD
  • DE_PR_CD
  • DE_VR_CD
  • DK_CVR_CD
  • DK_FT_CD
  • DK_NOTAP_CD
  • EE_FON_CD
  • EE_RG_CD
  • ES_NIF_CD
  • FI_ALV_CD
  • FI_NOTAP_CD
  • FI_SIRA_CD
  • FI_Y_CD
  • FR_CIB FR_SIREN_CD
  • GEN_IPF_CD
  • GEN_NBR_ENTTY_CD
  • GEN_NCB_ENTTY_CD
  • GEN_NSA_ENTTY_CD
  • GEN_NSI_ENTTY_CD
  • GEN_OTHER_CD
  • GEN_PS_CD
  • GEN_TAX_CD
  • GEN_TRD_RGSTR_ENTTY_CD
  • GEN_VAT_CD
  • GR_AFM_CD
  • GR_IMO_CD
  • HR_MB_CD
  • HR_MBS_CD
  • HR_OIB_CD
  • HU_CEG_CD
  • HU_FB_CD
  • HU_KOZ_CD
  • HU_TOR_CD
  • IE_CRO_CD
  • IE_VAT_CD
  • IT_CCIAA_CD
  • IT_CF_CD
  • IT_UCITS_CD
  • LT_INV_CD
  • LT_JAR_CD
  • LU_RSC_CD
  • LV_FON_CD
  • LV_NBR_CD
  • LV_VAT_CD
  • MT_CNUM_CD
  • MT_OLE_CD
  • MT_VAT_CD
  • NL_KVK_CD
  • NL_RSIN_CD
  • PL_KRS_CD
  • PL_NIP_CD
  • PL_REGON_CD
  • PL_VAT_CD
  • PT_FSA_CD
  • PT_NIF_CD
  • RO_CUI_CD
  • RO_TAX_CD
  • RO_TRN_CD
  • SE_FIN_CD
  • SE_MOM_CD
  • SE_ORG_CD
  • SI_DAV_CD
  • SI_DDV_CD
  • SI_MAT_CD
  • SK_ICO_CD

Appendix II: BKYC required documents

The following table includes the required documents for identification for each legal form:

Legal form Required documents Description Notes
GbR
  • SHARE_HOLDERS_AGREEMENT
  • SHARE_HOLDERS_AGREEMENT
  • FOUNDATION_DOCUMENT
  • Shareholder Lists (of Beneficial Owner Companies, possibly also an overview of shareholder/owner structure, insofar as the structure extends over several levels)
  • Articles of association (Gesellschaftsvertrag)
  • Certificate of incorporation (Gründungsurkunde)
Documents must be signed by all business partners. Solaris may request additional information based on the document contents (e.g., all shareholders, distribution of shares, etc). For GmbH/UG & Co. KGs, these requirements apply for the entity that is registered in the trade register as shareholder (i.e., Komplementär-Gesellschafter).
GmbH_CO_KG
  • SHAREHOLDERS_LIST; if not available, then:
  • SHARE_HOLDERS_AGREEMENT; if not available, then:
  • FOUNDATION_DOCUMENT
  • Shareholder Lists (of Beneficial Owner Companies, possibly also an overview of shareholder/owner structure, insofar as the structure extends over several levels)
  • Articles of association (Gesellschaftsvertrag)
  • Certificate of incorporation (Gründungsurkunde)
Document must include a notarial stamp, seal, and signature.
UG_I_GR
  • SHAREHOLDERS_LIST
  • SHARE_HOLDERS_AGREEMENT
  • FOUNDATION_DOCUMENT
  • Shareholder Lists (of Beneficial Owner Companies, possibly also an overview of shareholder/owner structure, insofar as the structure extends over several levels)
  • Articles of association (Gesellschaftsvertrag)
  • Certificate of incorporation (Gründungsurkunde)
Document must include a notarial stamp, seal, and signature.
UG & Co. KG
  • SHAREHOLDERS_LIST; if not available, then:
  • SHARE_HOLDERS_AGREEMENT; if not available, then:
  • FOUNDATION_DOCUMENT
  • Shareholder Lists (of Beneficial Owner Companies, possibly also an overview of shareholder/owner structure, insofar as the structure extends over several levels)
  • Articles of association (Gesellschaftsvertrag)
  • Certificate of incorporation (Gründungsurkunde)
Document must include a notarial stamp, seal, and signature.
AG (not listed)
  • SHAREHOLDERS_LIST
  • SHARE_HOLDERS_AGREEMENT
  • FOUNDATION_DOCUMENT
  • Shareholder Lists (of Beneficial Owner Companies, possibly also an overview of shareholder/owner structure, insofar as the structure extends over several levels)
  • Articles of association (Gesellschaftsvertrag)
  • Certificate of incorporation (Gründungsurkunde)
Document must include a notarial stamp, seal, and signature.
SE (not listed)
  • SHAREHOLDERS_LIST
  • SHARE_HOLDERS_AGREEMENT
  • FOUNDATION_DOCUMENT
  • Shareholder Lists (of Beneficial Owner Companies, possibly also an overview of shareholder/owner structure, insofar as the structure extends over several levels)
  • Articles of association (Gesellschaftsvertrag)
  • Certificate of incorporation (Gründungsurkunde)
Document must include a notarial stamp, seal, and signature.
e.V.
  • SHAREHOLDERS_LIST
  • SHARE_HOLDERS_AGREEMENT
  • FOUNDATION_DOCUMENT
  • Liste der Vorstandsmitglieder
  • Vereinsregisterauszug (no older than three months)
  • Vereinssatzung

Appendix III: Testing samples for GET Search for business commercial registration

The following table includes testing samples for the GET Search for business commercial registration endpoint, including values for the fields country, registration_number, registration_issuer, and name.

Country Registration number Registration issuer Company name
DE HRB198673 MÜNCHEN FLOOR 13 GMBH
DE HRA23670 BERLIN OHG Erich-Steinfurth-Strasse 7
DE HRA4029 WITTLICH SG-AUTO-WASCHTREFF WERNER KG
DE HRB571744 STUTTGART Klima Investment GmbH & Co. KGaA
DE HRB18686 Bonn Tekcor 1. V V UG (haftungsbeschraenkt)
DE HRB54636 DUESSELDORF AF Azurit AG
DE HRA204605 Stiftung St., Joseph Stift, Stiftung kirchlichen Rechts
DE HRA94238 HAMBURG PR-AUTO Peter Reimann e.K.
ES A46103834 ---- MERCADONA SA
ES N00434391 ---- HYUNDAI MOTOR EUROPE SE
ES B17262213 ---- AUTOLINE SOCIEDAD LIMITADA
ES B19202969 ---- SEIJAS ALONSO YA CIA, S.R.C.
ES G91487967 ---- CASAS Y CAMPOS S.C.
ES W2501222J ---- COLLIERS INTERNATIONAL INVESTMENT & ASSET MANAGEMENT
ES D81586729 ---- COLGATE PALMOLIVE HOLDING S COM P A
FR 513937359 ---- PARISOL
FR 332199462 ---- NATIOCREDIMURS - SOCIETE EN NOM COLLECTIF
FR 582051843 ---- GASTINNE RENETTE SOCIETE EN COMMANDITE SIMPLE
FR 304463284 ---- AVENTIS PHARMA S.A.
FR 807956966 ---- MENTION PARC AUTO
FR 539358994 ---- SOCIETE EN COMMANDITE PAR ACTIONS ETCHE ONA
FR 438755092 ---- SOC EUROPEEN DE BREVETS AUTOMOBILES SE
IT TO824350 ---- BUSINESS NETWORK S.P.A.
IT ME247881 ---- TORO S.C.R.L.
IT GE447187 ---- SOCIET SEMPLICE MONT BLANC
IT PN51072 ---- S.N.C. GEFCO DI LUIGI DAL BON & C
IT AO43300 ---- CALDARELI SERVIZI ASSICURATIVI S.A.A DI VALTER CALDARELLI
IT MI1712979 ---- LUIGI DE PRA S.A.P.A
IT AN146244 ---- FIAT SERVIZI PER L'INDUSTRIA S.C.P.A O SEMPLICEMENTE SE.P.IN
IT FI514669 ---- SCLE DELTA TRAZIONE SOCIETA' CONSORTILE A RESPONSABILITA
IT TO1215674 ---- S.R.L. SPORTIVA DILETTANTISTICA SPORT LAB
IT TP131030 ---- MAIORANNA GIUSEPPE PICCOLO IMPRENDITORE EDILE
note

For non DEcompanies, the registration_issuer is not necessary.


Appendix IV: FAQ

Legal Representative FAQs

The company I am about to register is a „Gesellschaft mit beschränkter Haftung“ (GmbH) – who is my legal representative?

The easiest and surest way to figure that out is to check your current register excerpt (Handelsregisterauszug). In there you'll find all the official legal representatives which you would need to tell us. As a further indication, these people also need to be listed in the Imprint of your website (Impressum).

The Legal Representative has sole representations rights – do I need to add the other legal representatives as well?

Yes. Even though this legal representative could conclude the process on behalf of the company alone in the following steps, Solaris would need the complete set of information for regulatory purposes. Therefore, please enter the information about all legal representatives associated with the business.

One of our legal representatives is currently unavailable – do we need to reach them to complete the process?

Yes. All legal representative(s) must be identified in a video identification session to complete the business identification process(BKYC).

Our legal representatives are about to change soon – shall I include the new ones already?

No; please submit the information as it is currently written in the official register. If you already know that these individuals will change, then please inform your Onboarding manager accordingly, and they will help sort things out.

Why do I have to submit all legal representatives here?

As a bank, Solaris is obliged to keep a record about the companies it works with and check whether the provided information is correct. Solaris makes every effort to keep the flow as smooth as possible. Nevertheless, the law stipulates that Solaris must collect this information for all legal representatives.

Ultimate Beneficial Owner FAQs

What is a “Beneficial Owner”?

A so-called “Beneficial Owner” is a natural person (a human) who owns directly or indirectly more than 25% of the voting shares of a legal entity today. Ultimately it is the person who benefits from the entered agreement and has the eventual decision power. It can never be another company, as Solaris would need to look up the owner of that company. There is a more detailed (legally-worded) definition here as well. It may significantly help cases with beneficial owners incorporated as trusts or other non-commercial entity types.

The company has no beneficial owners – how should I proceed?

It might be the case after a thorough investigation that nobody has directly or indirectly enough voting shares of the business. In that case, Solaris is required to take the legal representatives instead. Please enter their information accordingly.

I don't know the ownership structure of the company – how shall I proceed?

Ultimately, the ownership structure of a company is determined in the shareholder agreement (Gesellschaftervertrag), which has been signed at least when founding the entity. In the meantime, this may have changed but would need to be noted in an amendment or update of this contract.

Another company owns the company – what shall I do now?

Please submit the information of the natural person (human) owning your shareholders. If this is also another company (holding- or corporate-structure), you would need to follow the trail of indirect ownership until you either find an individual or the ownership is diluted under 25% ownership (through indirect ownership).

What do you mean by direct or indirectly & how do I calculate that?

Direct ownership refers to a natural person (individual) owning him-/herself voting shares in the business. Indirect ownership refers to somebody owning one entity that then owns a specific part of the business. It also qualifies if the entities are stacked into each other (several companies in between). Also, if one individual holds voting shares via different entities in the business, you would need to add up his/ her total indirect ownership to see whether the total engagement reaches more than 25%. When the shareholding structure is stacked over several hierarchies, you multiply the ownership-quotas of each entity to get the ultimate quota for the respective person.

Example:

Adello GmbH needs to provide its beneficial owners. Adello's shareholders are Peter 30% of shares, Susi 10% of shares, Anne 10% of shares, and Toscana GmbH 50% of shares. Toscana's shareholders: Hugo 75% of shares and Marie 25% of shares Direct beneficial owners of Adello: Peter Indirect beneficial owners of Adello: Hugo with 37,5% of shares (Toscana's share in Adello 50% x Hugo's ownership quota in Toscana 75%). Please note that Marie is not a beneficial owner as she has indirectly only 12,5% in Adello.

We have different kinds of shares – which shares are the decisive ones?

Please refer to the shares with decisive voting power as the beneficial owner is ultimately the person deciding the significant strokes of the company.

Does the UBO need to do something, for instance, sign something or perform a video identification?

No, please only submit the information of that person as stated in his/her official documents (ID card or passport). There is no further double-checking of that information. Therefore, the beneficial owner does not need to do anything during this identification process.