This is early beta for now! Can't handle all templates properly
Hankkija
| Vastaanotettu Hilmaan | 2024-02-15 |
| Ilmoituksen numero | 2024-142386 |
| TED numero | |
| Ostajaorganisaatio | Finnvera plc (1484332-4 ) Porkkalankatu 1 FI-00180 Helsinki http://www.finnvera.fi |
| Hankinnan otsikkotiedot | Request for information: KYC and ESG -database |
| Hankinnan yhteenlaskettu kokonaisarvo koko ajalle (ilman alv:ta) arvio | |
| Hankinnan yhteenlaskettu kokonaisarvo koko ajalle (ilman alv:ta) lopullinen | |
| Alkuperäinen ilmoitus | https://www.hankintailmoitukset.fi/fi/public/procurement/96929/notice/142386/overview |
| Originaali JSON tietue | 142386.json |
Ostettava
| Hankinnan lyhyt kuvaus | This document is not a contract notice or an invitation to tender and the purpose of the publication of the document is not to start a tendering process. Participating to a potential future tendering process does not require giving information to this request. This document is an invitation to participate in a market dialogue regarding KYC and ESG -databases. The objective of the dialogue is to improve our understanding of the market offering regarding KYC and ESG -databases. Companies interested in the matter are requested to send descriptions of the solutions that would match the above mentioned requirements as well as other information that will increase Finnvera’s understanding of market offering. The planned object of procurement is a customer due diligence database for the purpose to meet KYC-requirements set in the anti-money laundering regulations as well as to deliver successfully reviews and assessments in relation to environmental and social risks. However we are aware that many of the database suppliers are specialized in some field when providing information, therefore alternatively if noticed one database-solution can’t deliver all our requirements set both to KYC-information as well to ESG, we shall consider purchasing two separate databases. The database should contain comprehensive KYC-information about these areas: • Information about entities, including but not limited information about entity’s identification (address, identification number, registration number, possible previous names or trading names etc.), business data and entity’s ownership; including beneficial owners, management, ownership structure or global family tree. • Information about natural persons, such as biographical and executive information • Sanction lists and anti-corruption related debarment lists (including but not limited U.S. Sanctions, U.N. Security Council sanctions, EU sanctions, World bank debarment list, Wolfsberg Group, Asian Development Bank and African Development Bank) • Legal cases and administrative sanctions • Politically exposed persons (PEPs) • Adverse media, including news about such topics like corruption, extortion, money laundering, • Executive compensation issues, misleading communication, fraud, tax evasion, tax optimization, anti-competitive practices as well as environmental and human right issues. In terms of ESG- information needs, database should provide information for identification of the potential ESG risk level and nature and the probability of severe environmental and social risks of the target country, industry sector and the parties in a transaction (e.g. buyer, end-user, owner and borrower companies as well as the specific project site/case). The database should also provide information for monitoring the cases Finnvera is involved in by having an ESG risk alert system. The ESG database should contain comprehensive information about these areas: - adverse media, including news, scientific/non-scientific articles, studies/statements of civil society organization (CSO), non-governmental organizations (NGO) and other organizations, as well as social media, about ESG-issues focusing on the environmental and social (including human rights) topics like o environmental, health and safety accidents and incidents, human rights violations, protests, negative environmental impacts, and incapability of the management to manage and mitigate environmental and social risks. - risk scoring, or other similar way to show in an analyzed way how severe the ESG-risks of a particular company/project are, and a particular combination of a country and industry. o scorings/analysis based on information like negative news, accident rate, relevant lawsuits, regulation gaps (e.g., in workers’ rights) in the country and overall ability to protect, respect and remedy human rights according to UNGPs telling us how risky a certain company/project and the business sector is in a particular country. The aim is to get sufficient information from the database to pinpoint quickly those applications from the incoming application flow that have a high probability of significant environmental, social and human rights risks. - information about climate change risks and mitigation o GHG emissions at least company level and preferably also asset/facility level to support our carbon footprint calculations of financed emissions, as well as the information about companies’ science based- and net zero targets and alignment against targets. Information about physical climate risks. Database(s) should allow making a customer due diligence investigation to at least natural persons and entities. Database(s) should contain built-in reporting tool that have versatile features to build, edit, save, download, print and email customer due diligence reports that consist only information needed. The database should also provide audit trail, so that all searches are time and date stamped. Database(s) should also provide direct links to information sources. All information should contain a clear dates, when the news is published or when the sanction is come in force. In case the database includes information in different languages, the database should have built-in translator or similar kind of solution to translate all the information at least to English. Adverse media should contain short news summaries as well as the whole article. The user interface must be in either Finnish or English. The customer support during contract period may be in either Finnish or English. A user friendliness in a form of clear search results and fewer clicks when using the system is also a valued feature. The database(s) is planned to be used as a separate system and integration option to Finnvera’s other systems is not required. However, possibility to download e.g. entity, country and sector specific risk scorings directly to a spreadsheet for automatic use of Finnvera’s internal systems is valued. The number of users is 5-10 persons. Finnvera reserves the right to increase the number of users (understandably with additional charge) during the agreement period. The estimated amount of entities to be searched during a year is approximately 700-1 000 for environmental and social risk management purposes. If the database provides data for other KYC purposes, the number of searched entities can be about 2 000. |
| Hankintanimikkeistö (CPV) pää | Data services (72300000) |
| Hankintanimikkeistö (CPV) muut | |
| Aluekoodi | FI |
| Pääasiallinen suorituspaikka |
