All Collections
Online company formation in Estonia
The name of the person does not match the data of the population register
The name of the person does not match the data of the population register
Unicount avatar
Written by Unicount
Updated over a week ago

This error message can appear after you have inserted your company details, reviewed the data, and try to move on to sign the application for company registration.

The error happens because your e-resident card or Smart-ID has an electronic certificate carrying your name that does not match your name in the Estonian Population Register. The Register does include details of e-residents too. Normally your name record in the Register is identical to the passport you used when applying for e-Residency.

Unicount reads your name for the personal details page from your electronic certificate.

It does not matter which method you use for logging in, they all have electronic certificates.

To fix this return to your personal details page and type the name exactly as in your passport including all the unusual letters. If it still does not work you can actually log in to the Estonian Population Register to check your name spelling there. Please follow this link to log in.

You might think that the names are identical, but the devil is in the details. For example, your name on the certificate might not contain exactly the same letters such as Ş, Ņ, Ć or Ł. Seems like a non-sense problem, but when Unicount sends your details via the API to Business Register they do perform a query to the Estonian Population Register. If there is a slight mismatch of names your application is not returned via API for you to sign and you would see this error message.

The problem might also occur when you have several first or last names that are not saved on the certificate but appear in your passport and the Population Register too. Just add these missing names whenever hitting the same error message.

Unicount has recommended Business Register fix the API so that a correct name would be returned via the API query when the personal identification code matches.

Did this answer your question?