KvK company data enrichment: what to agree before commissioning a tool

Want to combine KvK data with your own company records? KvK is the Dutch Chamber of Commerce. Start with the file you already have and the information it lacks. Explain what you intend to use the result for; that helps define the work you commission.

At Monad, this falls under data enrichment: combining your records with external information and preparing it for your system. We assess the possible source and access to it when defining the project. This article covers preparing that brief, rather than a specific KvK integration or permission to use data.

Define what you need to add

List the fields you are missing. For each one, note the intended source and where you need the result. Decide whether you need a file for analysis or records delivered into existing software before commissioning the complete process.

• Bring a sample of your current file.
• Identify the fields that need adding or standardising.
• Describe how duplicate records should be handled.
• State how often the information needs updating.

Assess the source and access first

A field you want to add does not establish that a usable source is available. Our approach starts with source access and data quality. Discuss where the information would come from and what is available for a working sample. Bring the source address if you have one in mind.

Use that sample to show the input you have and the output you expect. Discuss what should happen when records are missing or unexpected. Our service page describes checks for those cases and agreements on who responds to failures.

Agree how the records reach your system

An API is an interface through which software can exchange data. Depending on the receiving system, we can use an existing API, build a custom access point or deliver files in an agreed format. We assess the options before choosing an approach.

Bring information about the receiving system too. Agree the data structure using a representative dataset before connecting the complete process. That gives you a sample to assess against the intended use.

Keep legal questions separate from build decisions

Include the AVG, the Dutch name for the General Data Protection Regulation, and the Databankenwet, the Dutch database law, as separate points for assessment. This article gives no legal judgement on a source, dataset or intended use. It names the rules without deciding what is permitted in your situation.

Include maintenance in the brief

Connecting the data is not the last agreement to make. Our data approach also covers monitoring, source changes and maintenance. Agree who reviews missing or unexpected records and who responds to a failure. Discuss update frequency at the same time.

Bring a concrete task to the intake

If you want to commission data enrichment, bring your sample file and missing fields, together with a description of the system that should receive the result. At Monad, a project starts with a free intake conversation, followed by a fixed quote for a first working version.

Read about data collection and API integrations or describe your project through the contact form. Include your company and the information you want to add.