The Veridion API aims to resolve to the right entity, in other words, to match your input with the company details best fit to the input. This process depends on the quality and freshness of the input, so the API leverages various mechanisms to make sure we resolve the input record, in almost whatever way it's structured, to the corresponding company.

This brings a series of challenges. It means the API needs to work with outdated input data. Or with partially true information, for example an incomplete address or a company name without a legal termination, or a website wrongly associated with a company.

Legal vs. operational

Broadly, there are two main cases the API handles:

1. Same legal and operational details

When the company is registered and operates in the same jurisdiction and Veridion is able to find clear proof of connection between the two entities ( legal and operational ), the API will return both legal and operational details, regardless if the input received is a legal name or a commercial name.

2. Significantly different legal and operational details

This means there are potentially several legal entities in multiple jurisdiction, and the operational location is different from the legal/registration address.

In this case, the API will match the company details that best fit the provided input. Some of the most common inputs and entity resolution scenarios are listed below.

Input as legal information

( i.e. legal company name and legal address, optionally a registry ID )

The API will aim to resolve to an exact legal entity and return operational information whenever available. For example, a company might be registered in Delaware jurisdiction, but operational in New York. In this case, the following scenarios apply:

If the input entity represents the legal entity registered in Delaware ( alongside a Delaware address ), the API will return the legal entity data of the entity registered in Delaware
If the input legal entity is associated with the operational entity active in New York ( meaning the Delaware entity is a unique entity in that jurisdiction or is the parent entity of the operational entity ), the API will also return the operational data of the commercial entity
If the associated operational entity is mainly located in New York, but also operates in Delaware, the API will also return the operational data of the commercial entity
If the Delaware legal entity is only a subsidiary and the company doesn't operate in Delaware, the API will return only the legal entity data for the Delaware incorporated entity
If the API cannot validate the legal presence of the entity in the Delaware jurisdiction, but the operational entity also operates in Delaware, the API will return the operational data of the commercial entity

Input as operational information

( i.e. operational company name and operational address, optionally a website )

The API will find the most likely operational entity, and will return the operational details associated with it. If Veridion has clear proof of the connection between the commercial entity and a legal entity in the same jurisdiction, the API will provide the legal details of that entity.

Input as a mix of legal and operational information

( e.g. Website, Legal Company Name and Legal Address )

The Website will always match to an operational entity.
Legal Company Names and Legal Addresses can match to both legal and operational entities:

If we know that the legal entity and the commercial one associated with the website are connected, we return both legal and operational datapoints
If the operational entity is active in the input jurisdiction, but the legal entity is not registered in the input jurisdiction, we return operational data points
If the legal entity is active in the input jurisdiction, but the commercial entity linked to the website is not active in the same jurisdiction:
- If we have a commercial entity tied to the legal entity from the input, the Veridion API will return the details of that commercial/operational entity, but with a lower match score
- If there are no clearly connected commercial/operational entities, the Veridion API returns only the legal entity details. In this case the Veridion API will consider it is not clear which actively operational entity should the match resolve to, and we optimize for accuracy in those cases.

( or e.g. Legal Company Name and Operational Address ; Operational Company Name and Legal Address )

The API will find the most likely operational entity, and return the operational details associated with it. If Veridion has clear proof of the connection between the commercial entity and a legal entity in the same jurisdiction, the API will provide the legal details of that entity.

Refining for match accuracy

Returned matches are refined through methodologies that account for:

Completion and accuracy of provided input:
- e.g. if the input includes an incomplete address ( for example, only Country ) , the API will rely more on additional information ( for example the company name and/or a website/phone number, if provided ) to return a better match.
- Similarly, if the API detects a website has been wrongly associated with the rest of company details, it will optimize for matching against provided company name and address
Relevance of matched input attribute: e.g. Website or Registry ID matches can be more relevant than Company Name matches, due to the uniqueness of these values across the entire data domain
Match types: e.g. Company Name Exact matches are typically stronger than Fuzzy Matches, unless additional information is present and matched
Match sources: e.g. Information extracted from a Company Website can be more reliable than Social media information

Each returned company profile includes a Confidence score and detailed information on Matched attributes. The values of these attributes determine the level of match confidence and provide information about the criteria used to match the input data with the company information in the Veridion database.

📘
Analyze a Company match
Please refer to the How to analyze a match section for more information on Confidence scores and Matched attributes.