Components and Modules

String matching any pattern from the following list.

String matching any pattern from the following list within a longer textual string.

D+

D+ (DS) D+

D+ [eE] D+

D+ [xX] 10^ D+

D+ [eE] [- ] D

D+ [xX] 10^ [-] D

D+ (DS) D+ [eE] D+

D+ (DS) D+ [xX] 10^ D+

D+ (DS) D+ [eE] [- ] D

D+ (DS) D+ [xX] 10^ [-] D

More than a single measurement unit in the input string.

Values entered as words (for example, "twelve point five").

More than a single value in the input string.

dd.MM.(yy)yy - With dots as separators.

MM/dd/(yy)yy - With forward slashes as separators.

(yy)yy-MM-dd - With dashes as separators.

yyyyMMdd - With no separators.

HH:mm:ss (for example, 18:03:30)

HH:mm:ss{Z|XXX} (for example, 18:03:30+0100, 18:03:30+01:00)

HH:mm:ss.SSS (for example, 18:03:30.001)

HH:mm:ss.SSS{Z|XXX} (for example, 18:03:30.001+0100, 18:03:30.001+01:00)

Only one EAN code of defined length without extensions.

Valid characters in EAN codes are digits, letters, and parentheses (round brackets).

Other characters than those specified here can be present in an EAN code, but they are removed (and scored) before validation.

Several values of an EAN code in the input value (parsing fails as multiple values are considered invalid).

Comments with the EAN input value are not processed (the EAN code value could be processed as expected but the comments would be lost).

Comments with the EAN input value containing numbers are not processed (the EAN code value would be processed as one string with digits from the comment, but the value would be invalid and the comments lost).

Simple EAN codes containing the left parenthesis.

Compound EAN codes without the left parenthesis.

Any character in the input value of the EAN code is allowed (all except digits are deleted from the value before validation).

Null values are processed and scored.

Several values of an EAN code in the input value (parsing fails as, after non-digits are removed, multiple values would be considered to be one EAN code and, hence, invalid).

Comments with the EAN input value are not processed (the EAN code value might be processed as expected, but the comments would be lost).

Comments with the EAN input value containing numbers are not processed (the EAN code value would be processed as one string with digits from the comment, but the value would be invalid and the comments lost).

Standardized value of the email address (score less than 10 000).

Data quality score of the email address.

Data quality imperfection explanations.

Best existing value of the email address (standardized, parsed, or input value).

Standardized value of the email address owner if recognized (person’s name is populated if recognized).

Email address found in the allowlist.

Email address with a valid top-level domain (TLD).

Email address in a valid format.

Email address with a string before <em@il.tld>.

Email address in the upper case - valid with no change (local part is case sensitive).

Email address with special characters, such as !#$%&'\*+-/=?^_`{|}~.

Email address with accents and multiple consequent dots or commas used instead of dots (for example, "john,smith@email.com").

Email address with a leading stopword delimited from the email address by a space or colon (for example, "email: mail@dom.tld").

Valid email address enclosed in angle brackets (<>) having a string before the email.

Valid email in any type of paired enclosing strings: (), {}, <>, [], "", '' (for example, "{email}", "(email)").

Spam-protected versions of the email address with an at sign (@) and/or dot codes (for example, name<dot>surname<at>domain<dot>tld).

Email address with the most common misspellings of TLDs.

Email address with a missing or misspelled TLD in case of well-known email providers.

Email address missing the last dot between the TLD and the second level domain name.

Any string that contains a valid email address as a substring (delimited by characters not supported in email addresses).

Email address with a temporary domain (for example, 5 and 10 minute emails).

Any viable combinations of the previous.

Empty email address (or whitespaces only).

Email address with unsupported characters, such as בײַשפּ@בײַשפּיל.טעסט.

String without an email address.

String with multiple emails.

Email address with only a TLD in the domain part (for example, "john.smith@com" - though RFC-valid, it is considered suspicious).

Email address found in the blocklist (for example, spam addresses, business defined emails).

Standardized value of IBAN.

Data quality score of IBAN.

Data quality imperfection explanations.

Best existing value of IBAN (standardized, cleansed, or input value).

IBAN with a maximum length of 34 characters.

IBAN can contain any character possible. All except digits and letters are removed before verification.

Empty record or input value that does not contain any alphanumeric characters (IBAN is considered NULL).

Numbers with spaces.

Numbers with one decimal point or decimal comma - in the middle of the number or at the end (for example, 1,2345,3433,).

Numbers with digit grouping - only thousands separators (for example, 1,123,123.00109 and 1.123.123,00109).

Numbers with one plus or minus sign (+ or -) at the beginning.

Numbers can be integer, long, or float.

Numbers containing letters.

Numbers containing more than one comma or dot (except acting as thousands separators).

Empty input.

Numbers in a wrong format (not compliant with the previously stated rules).

in_vin - Input VIN

std_vin - Standardized value of VIN. Meets all rules of the component.

out_vin

std_region

std_manufacturer

std_model_year

exp_vin

sco_vin

in_string (STRING): Input address or string from which you want to extract the country code.

String containing any alphanumeric characters and ,;-_/|..

Country names must be in English.

Country codes must be in upper case, otherwise they are not recognized as country codes.

in_string (STRING): Input address or string.

std_cc_alpha_2 (STRING): Standardized country code in alpha-2 format.

std_cc_alpha_3 (STRING): Standardized country code in alpha-3 format.

std_cc_num_iso (STRING): Standardized numerical country code.

std_country_name (STRING): Standardized country name.

out_country_name (STRING): Names of all countries identified on input (can be used, for example, for data cleansing).

sco_cc (INTEGER): Scoring value of the input address based on extracted alpha-2 country codes.

exp_cc (STRING): Scoring value explanation.

Date in the past.

Today’s date.

Date in the future.

Empty value.

age_unit - Choose output age units (days, weeks, months or years). Default value is "YEARS".

current_date - Set up the baseline in DATE format (yyyy-MM-dd). Default value is "today".

Date in the past.

Today’s date.

Date in the future.

Empty value.

Output language:

Abbreviation flag:

Primary key

Party type (person or company)

Gender code

First name

Middle name

Last name

Person identifier (such as social security number, social insurance number, birth number, ITIN)

Date of birth

Company name

Company identifier from a business registry

Address (permanent or contact address for person, address of company branch or headquarters for companies)

Contacts (such as emails, phone numbers)

Document identifiers (such as driver’s license)

Cleansing score

Delete flag

Date of last modification

Candidate group identifier

Previous candidate group identifier

Matching identifier

Previous matching identifier

Processing status

Processing timestamp

Instance role

Previous instance role

Matching rule name

std_value (FLOAT): Input value converted into target unit of length.

std_unit (STRING): Target unit of length.

out_value (FLOAT): The best value of input value.

out_unit (STRING): The best value of input unit.

out_comment (STRING): Parsed out comment.

sco_length (INTEGER): Data quality score.

exp_length (STRING): Explanation codes.

LGT_VALUE_STANDARDIZED: The input value of length was standardized. Example: "14.999,999,999 meters" to "14.999999999 m".

LGT_UNIT_STANDARDIZED: The input unit of length was standardized. Example: "15 meters" to "15 m".

LGT_COMMENT_FOUND: The input contains additional information other than value and unit of length. Example: "Length is 15 meters".

LGT_CONVERTED: The value of length was converted to its corresponding value in the target unit. Example: "1500 centimeters" to "15 m".

LGT_NOT_PARSED: No valid parsing pattern was found and input was not parsed. Example: "14. m".

LGT_MULTIPLE_SEPARATORS: Input was parsed but more than one decimal separator was found in the value. Example: "14.999.999,999,999 meters".

LGT_EMPTY: No input was submitted.

LGT_VALUE_MISSING: Unit is verified but no value of length was found. Example: "meters".

LGT_UNIT_MISSING: Value of length is parsed but no unit was verified. Example: "15".

LGT_MULTIPLE_UNITS_FOUND: Input contains more than one unit of length. Example: "15 meters kilometer".

LGT_INVALID: No value and no unit of length were parsed. Example: "Length".

Primary key

Address lines 1-4

Country code

Postal code

Out address attributes

Address label

Explanation code

Data quality score

Original loqate address verification code

Primary key

Address lines 1-4

Country code

Postal code

out - Output of Verify (V) and Verify & Geocode service (V+G). Contains major output attributes as defined in the cloud service Field Descriptions and explanation codes (exp_instance).

out_proposals - Output of Search (S) or Search & Geocode service (S+G). Contains the same attributes as the out endpoint plus a primary key identifying the source request.

Examples of valid input:

Examples of invalid input:

Component does not mask several email addresses in one record (everything up to the last at sign (@) is considered the local part and is transliterated).

Inputs with domain names containing spaces are incorrectly parsed: everything after the space is considered a suffix (not part of the email address) and remains unchanged. Spaces are allowed only in the local part.

Inputs with email address and suffix starting with a letter without any separator between them are incorrectly parsed: everything after the at sign is considered a domain part. Text suffix has to be separated from the value by a non-alphanumeric character.

A single valid currency code, with or without comments (not containing any ambiguous country name), for example, "My currency is CZK".

A single non-ambiguous country name, with or without comments (not containing any ambiguous country name), for example, "My currency is Barbados".

If the code differs by a single letter from a standardized currency code and can be corrected uniquely, then the corrected value is output into out_currency and std_currency columns.

If the code cannot be corrected uniquely or at all, it is put into out_currency column; std_currency is left empty.

Number in the national format. Trunk prefix is required, for example, in Slovakia it is 0, in Czech Republic there is none.

Number in a correct international format: begins with a plus sign (+) or the exit code followed by the country code. Only two exit codes are supported: 00 (Europe) and 011 (North America).

ISO 3166-1 alpha-2 - Two-letter country codes.

ISO 3166-1 alpha-3 - Three-letter country codes.

ISO 3166-1 numeric - Three-digit country codes.

Phone numbers which contain any other characters than +(only at the beginning)[:digit:][:space:]-().

Phone numbers longer than 15 digits (after transformation into the international format).

Phone numbers shorter than 6 digits (without the country code).

Empty phone number or country column.

String truncated to the maximum length (out_string).

String with the rest after truncation (out_rest).

All country names in Dutch, English, French, Spanish, Portuguese, Russian, English (British), Italian, and German.

Country names in other languages - up to 30 (depending on the country).

ISO 3166-1 alpha-2 - Two-letter country codes.

ISO 3166-1 alpha-3 - Three-letter country codes.

ISO 3166-1 numeric - Three-digit country codes.

nl, en, fr, es, pt, ru, uk, it, de, cz_iso, en_iso.

Empty or not allowed to en_iso.

_iso preferred language parameter - official ISO country short name.

Empty country name and country code.

Invalid country name and/or invalid country code.

Country name and country code filled in and valid but inconsistent.

Standardized value of the email address (score less than 10 000).

Data quality score of the email address.

Data quality imperfection explanations.

Best existing value of the email address (standardized, parsed, or input value).

Standardized value of the email address owner, if recognized (a person’s name is populated if recognized).

Email address with a known TLD.

Email address in a valid format.

Email address with a string before <email>.

Valid email address in angle brackets (<>).

Email address in upper case - valid with no change.

Email address with special characters, such as !$%&'*+-/=?^_`\{|}~.

Empty email address (or whitespaces only).

Email address in an invalid format.

Email address with accents (ˇ´).

Email address with an unknown TLD.

Email address with a string before the email address (with email address not being inside angle brackets <>).

Valid email address in quotation marks.

Invalid email address inside apostrophes and square brackets.

Email address with unsupported characters, such as בײַשפּ@בײַשפּיל.טעסט.

Valid IDC code.

Explanation of data discrepancies in the IDC.

Data quality score of IDC code.

IDC (phone number) containing only numbers and having an indication of a foreign dialing code (+, 00, or 011 - the most common codes). Other codes can be found at International Dialling Codes.

Numbers or IDCs with alphanumeric comments (numbers in comments are considered to be part of the number or IDC).

Multiple values in one column.

Name is not parsed - out_ and std_ values are empty.

Name is parsed and the whole name is verified - out_ and std_ values are the same. Both are capitalized.

Name is parsed and part of the full name is not verified - all out_ columns and some std_ columns are populated. std_ is populated only when all words in its corresponding out column are verified.

Initials go to the output without dots. If there are two initials and the first name is empty, then the first initial is set to the first name and the second initial is set to the middle name.

If the parsed last name contains a dash, then output values don’t contain spaces around (for example, John - William would be John-William). Other special characters are not allowed in the output except apostrophe.

std values are set if the parsed value is verified in the lookup but std is set from the parsed original value and not from the lookup value.

out columns have output in same alphabet as the input.

out lat columns have only Latin values.

out cyr columns have only Cyrillic values.

out_value (STRING) - Transformed value.

sco_value (INTEGER) - Data quality score.

exp_value (STRING) - Explains data transformations.

DDDDDDDDDLLDDDD

DDDDDDDDD*LL*DDDD

DDDDDDDDD LL DDDD

DDD DDD DDD LL DDDD

DDD-DDD-DDD-LL-DDDD

std_business_number - Valid business number. This value is set only if the number matches all critical validation conditions (score < 10000).

out_business_number - Best business number value that we can get. Major corrections are considered as not safe and in that case only out_ value is present.

std_major_program_account

exp_business_number

sco_business_number

std_company_name - Standardized value of company name (score < 10000).

out_company_name - Best known value of company name.

out_company_name_base - Company name without legal element.

std_legal_form - List of standardized legal forms found in company name.

exp_company_name - Explanation column.

sco_company_name - Score column.

std_company_name column contains the input form of legal entity; the component only standardizes the case and adds periods to legal elements if needed (for example, CORPORAtioN to Corporation, CORP to Corp., Ltd to Ltd.).

std_legal_form column contains a single standardized form of legal entity (full text, without abbreviations: for example, CORPORAtioN to Corporation, Corp. to Corporation, Ltd to Limited).

Standardized value of number.

Data quality score of number.

Data quality imperfection explanations.

Best existing value of number (standardized, foreign, or parsed value).

Best existing IDC (standardized or parsed value).

Best existing value of area code (value verified in the lookup file or parsed).

Best existing value of central office code (value verified in the lookup file or parsed).

Best existing value of station number (parsed value).

Comments.

Pattern of the valid output phone number (more in chapter Attribute Details, the out_pattern attribute).

Number with Canadian IDC(1) or without IDC.

Number with extension (1- to 5-digit long number).

Number with interval in the format <number>-<interval>.

Foreign numbers indicated by trunk code 00 or a plus sign (+) in front of the number. IDC 1 is not considered a foreign number; numbers from Canada and other countries in the North American numbering system are considered invalid Canadian numbers; to standardize these numbers, use us_phone_number_cleanse component.

Number with textual comment before and after the number.

Number can contain only digits, letters, dashes, round brackets, plus signs, hashes, white spaces, dots, colons, commas.

Foreign numbers not indicated by 00 or a plus sign (+) in front of the number. These numbers are considered Canadian and might even match some lookup file values.

Numbers with period where the period number has more than two digits.

Standardized value of number.

Data quality score of number.

Data quality imperfection explanations.

Best existing value of number (standardized, parsed, or input value)

Best existing IDC (parsed value).

Best existing value of area code (value verified in the lookup file or parsed).

Best existing value of central office code (value verified in the lookup file or parsed).

Best existing value of station number (parsed value).

Number with a Canadian IDC (in the form +1, 1, or 001) or without IDC.

Number can contain any character possible. All except digits are removed before parsing.

Number with comment is parsed but the comment is lost.

Empty record or input value that does not contain any characters - number is considered NULL.

If comments do not contain any digit, less strict format requirements apply:

If comments contain digits, only SINs in the ddddddddd (nine digits) or ddd-ddd-ddd format are searched for in the input string. If there are multiple SINs, all except the first one are considered as comments.

UNIT_NUMBER NUMBER STREET_NAME STREET_TYPE DIRECTION

NUMBER STREET_NAME STREET_TYPE DIRECTION UNIT_TYPE UNIT_NUMBER

STREET_NAME STREET_TYPE DIRECTION NUMBER UNIT_TYPE UNIT_NUMBER RR_IDENTIFIER RR_NUMBER

POBOX_IDENTIFIER POBOX_NUMBER INSTALLATION_TYPE INSTALLATION_NAME

RR_IDENTIFIER RR_NUMBER INSTALLATION_TYPE INSTALLATION_NAME

GD_IDENTIFIER INSTALLATION_TYPE INSTALLATION_NAME

{1}\{area code}\{central office code}\{station number}

\{+1}\{area code}\{central office code}\{station number}

{001}\{area code}\{central office code}\{station number} \{area code}\{central office code}\{station number}

{1} \{area code} \{central office code} \{station number}

\{+1} \{area code} \{central office code} \{station number}

{001} \{area code} \{central office code} \{station number} \{area code} \{central office code} \{station number}

{1} (\{area code}) \{central office code} \{station number}

\{+1} (\{area code}) \{central office code} \{station number}

{001} (\{area code}) \{central office code} \{station number} (\{area code}) \{central office code} \{station number}

Not parsed phone number.

Incomplete Canadian phone number.

Multiple phone numbers.

When the street, street number, and city are specified, then the postal code is not required.

When the city district, number, and postal code are unambiguous enough, then the city is not required.

All of the input address attributes are filled: the street and number on the first address line, city on the second, and postal code on the third.

Two of the input address attributes are filled while the third is empty: the street and number on the first address line, city on the second.

Only the first input address attribute is filled while the rest is empty: the city, street, and number on the first address line.

Set of standardized address attributes (including std_address_code). These attributes are filled for the identified addresses and remain empty for unidentified addresses.

Best existing value of the address lines values. For the identified addresses, it includes standardized values in the envelope-ready printable form. For unidentified addresses, it is a copy of the input address lines.

Standardized registration number, company name, and legal form (they all have to be verified in RES lookup).

Best existing value of registration number (verified, valid, parsed, or input), company name, legal form, and active flag.

Matching value of company name without legal form. It can be used for matching of unidentified companies.

Score and explanation of data discrepancies. Input record gets score 0 when it has verified or valid registration number and a corresponding company name and city with RES values.

First name and middle name can contain only one word (letters only).

Last name can have multiple words separated by a space or dash. However, only the last word is declined.

Gender and at least one name part are populated.

If the name is parsed and the whole name is verified, then out_ and std_ values are the same. Both are capitalized.

If the name is parsed and part of the name is not verified, then all out_ columns and some std_ columns are populated. std_ values are populated only when all words in the corresponding out column are verified.

Initials go to the output without dots. If there are two initials and the first name is empty, then the first initial is set to the first name and the second initial is set to the middle name.

If the parsed last name contains a dash, then the output values do not contain spaces around (for example, Shantel - Leroy would be Shantel-Leroy). Other special characters are not allowed in the output, except for the apostrophe.

If the parsed last name contains more than two last names separated with dashes, then the dashes are not shown in the output values (for example, Ladois-Bourgois-Delage would be Ladois Bourgois Delage).

std values are set if the parsed value is verified against the lookup. Capitalized source (original-parsed) values are used.

Standardized value of NSS (cleansed and valid NSS).

Standardized value of the owner’s place of birth.

Standardized value of the owner’s gender.

Standardized value of the owner’s year of birth.

Standardized value of the owner’s month of birth.

Standardized value of the department where the owner was born.

Standardized value of the commune where the owner was born.

Standardized value of the postal code where the owner was born.

Standardized value of order number (owner’s birth order, in the specified location, year, and month).

Standardized value of control key (last two digits of the NSS).

Standardized value of proposed control key (proposed in case that the control key is empty or different than the computed one).

Best known value of NSS (standardized, cleansed, or input value).

Comments found before or after the NSS.

Data quality imperfection scoring.

Data quality imperfection explanations.

std_company_name - Company name which meets all the rules (score is < 10000).

out_company_name - Best existing value of company name.

std_legal_form - Legal form derived from company name.

out_company_name_base - Company name without the legal element.

exp_company_name - Explanation column.

sco_company_name - Score column.

std_company_name column contains the input form of legal entity; the component only standardizes the case and adds periods to legal elements if needed (for example, CORPORAtioN to Corporation, CORP to Corp., Ltd to Ltd.).

std_legal_form column contains a single standardized form of legal entity (full text, without abbreviations: for example, CORPORAtioN to Corporation, Corp. to Corporation, Ltd to Limited).

If the name is parsed and the whole name is verified, then out_ and std_ values are the same. Both are capitalized.

If the name is parsed and part of the name is not verified, then all out_ columns and some std_ columns are populated. std_ is populated only when all words in the corresponding out column are verified.

Initials go to the output without dots. If there are two initials and the first name is empty, then the first initial is set to the first name and the second initial is set to the middle name.

If the parsed last name contains a dash, then the output values do not contain spaces around (for example, John - William would be John-William). Other special characters are not allowed in the output, except apostrophe.

std values are set if the parsed value is verified in the lookup. Capitalized source (original-parsed) values are used.

Phone number with or without trunk code.

Phone number with or without IDC code.

Phone number with or without a preceding or following comment.

When the street, street number, and city are specified, then the postal code is not required.

When the city district, number, and postal code are unambiguous enough, then the city is not required.

All of the input address attributes are filled: the street and number on the first address line, city on the second, and postal code on the third.

Two of the input address attributes are filled while the third is empty: the street and number on the first address line, city on the second.

Only the first input address attribute is filled while the rest is empty: the city, street, and number on the first address line.

Set of standardized address attributes (including std_address_code). These attributes are filled for the identified addresses and remain empty for unidentified addresses.

Best existing value of the address lines values. For the identified addresses, it includes standardized values in the envelope-ready printable form. For unidentified addresses, it is a copy of the input address lines.

The name is not parsed - out_ and std_ values are empty.

The name is parsed and the whole name is verified - out_ and std_ values are the same. Both are capitalized.

The name is parsed and part of the full name is not verified - all out_ columns and some std_ columns are populated. std_ is populated only when all words in the corresponding out column are verified.

Initials go to the output without dots. If there are two initials and the first name is empty, then the first initial is set to the first name and the second initial is set to the middle name.

If the parsed last name contains a dash then the output values don’t contain spaces around (for example, John - William would be John-William). Other special characters are not allowed in the output except apostrophe.

Information from the lookup - company name, country code, lookup source, ID in source, address, phone, email, etc. (depending on the columns present in the lookup).

Scoring and explanations of all discrepancies in the data.

The output contains information from the lookup.

If the company name is not found in the lookup, the output columns are empty.

Some columns might contain several values (for example, phone, email, and the like).

Each value is enclosed by single quotes and values are separated by semicolons.

Company name

Company identification number (optional)

Company name (standardized, best existing value, and value without the legal form) with a scoring and explanation of all discrepancies in the data.

Legal form (standardized, best existing value, and value derived from the company name in the full text version).

Company identification number (standardized and best existing value).

Standardized value:

Best existing value:

Matching value recommendation:

Standardized value:

Best existing value:

Standardized value:

Best existing value:

Ten digits only. For example, 1234567890.

Ten digits with the same separators (spaces or dashes) at correct positions (between 3th-4th and 6th-7th digit). For example, 123-456-7890 or 123 456 7890.

Ten digits with different separators (space, dash or no separator) at correct positions (between 3th-4th and 6th-7th digit). For example, 123-4567 890.

Ten digits with spaces anywhere in between. For example, 12 34 56 7 8 9 0.

Ten digits only. For example, 1234567890.

Ten digits with the same separators (spaces or dashes) at correct positions (between 3th-4th and 6th-7th digit). For example, 123-456-7890 or 123 456 7890.

Two letters and six digits and one letter (for example, AB123456C).

Two letters and six digits and one letter with whitespace separators anywhere (for example, AB12 3 4 5 6C).

Neither of the first two letters can be D, F, I, Q, U, or V. The second letter also cannot be O.

After the two prefix letters, the six digits are issued sequentially from 00 00 00 to 99 99 99.

The suffix letter is either A, B, C, or D, although F, M, and P have been used for temporary numbers in the past.

Temporary insurance numbers have "TN dd mm yy x" format where 'dd' is day, 'mm' is month, 'yy' is year, and 'x' is suffix letter (F, M, or P).

If the name is parsed and the whole name is verified, then out_ and std_ values are the same. Both are capitalized.

If the name is parsed and part of the name is not verified, then all out_ columns and some std_ columns are populated. std_ is populated only when all words in the corresponding out column are verified.

Initials go to the output without dots. If there are two initials and the first name is empty, then the first initial is set to the first name and the second initial is set to the middle name.

If the parsed last name contains a dash, then the output values do not contain spaces around (for example, John - William would be John-William). Other special characters are not allowed in the output except apostrophe.

std values are set if the parsed value is verified in the lookup. Capitalized source (original-parsed) values are used.

Phone number with or without trunk code ('0' in GB).

Phone number with or without IDC code ('44' in GB).

Phone number with or without a preceding or following comment.

Address line 1: Street preferred.

Address line 2: City preferred.

Address line 3: State preferred.

std_company_name - Standardized company name (score < 10000).

out_company_name - Best existing value of company name.

out_company_name_base - Company name without the legal element.

std_legal_form - Legal form derived from company name. If more than one legal form is found, a list of standardized forms is returned.

std_vulgar_words - Vulgar words found in company name.

sco_company_name - Score column for company name.

exp_company_name - Explanation column for company name.

std_company_name column contains the input form of legal entity; the component only standardizes the case and adds periods to legal elements if needed (for example, CORPORAtioN to Corporation, CORP to Corp., Ltd to Ltd.).

std_legal_form column contains a single standardized form of legal entity (full text, without abbreviations: for example, CORPORAtioN to Corporation, Corp. to Corporation, Ltd to Limited).

out_ein_itin - Best value of EIN/ITIN. This number can be invalid.

out_ein_itin_type - Input type, if it was provided. Else it is derived type, if derivation was possible.

std_ein_itin - Standardized output, verified EIN prefix, or ITIN validity rules (score < 10000).

exp_ein_itin - Explanation column.

sco_ein_itin - Score column.

If the name is not parsed, then out_ name columns are populated with input values without stop words. If names are the same as the full value of stop words, then the output value is empty. std_ columns are empty.

If the name is parsed and the whole name is verified, then out_ and std_ values are the same. Both are capitalized.

If the name is parsed and part of the name is not verified, then all out_ columns and some std_ columns are populated. std_ is populated only when all words in the corresponding out column are verified.

Initials go to the output without dots. If there are two initials and the first name is empty, then the first initial is set to the first name and the second initial is set to the middle name.

If the parsed last name contains a dash, then the output values do not contain spaces around (for example, John - William would be John-William). Other special characters are not allowed in the output except apostrophe.

std values are set if the parsed value is verified in the lookup, but std is set from the parsed original value and not from the lookup value.

Standardized value of number.

Data quality score of number.

Data quality imperfection explanations.

Best existing value of number (standardized, foreign, or parsed value).

Best existing IDC (standardized or parsed value).

Best existing value of area code (value verified in the dictionary or parsed).

Best existing value of central office code (value verified in the dictionary or parsed).

Best existing value of station number (parsed value).

Comments.

Number with US IDC (1) or without IDC.

Number with extension (1- to 5-digit long number).

Number with interval in the format <number>-<interval>.

Foreign numbers indicated by trunk code 00 or a plus sign (+) in front of the number. IDC 1 is not considered a foreign number; numbers from Canada and other countries in the North American numbering system are considered invalid US numbers; to standardize these numbers, use ca_phone_number_cleanse component.

Number with textual comment before and after the number.

Number can contain only digits, letters, dashes, round brackets, plus signs, hashes, white spaces, dots, colons, commas.

Foreign numbers not indicated by 00 or a plus sign (+) in front of the number. These numbers are considered Canadian and might even match some lookup file values.

Numbers with period where the period number has more than two digits.

Standardized value of number.

Data quality score of number.

Data quality imperfection explanations.

Best existing value of number (standardized, parsed, or input value).

Best existing IDC (parsed value).

Best existing value of area code (value verified in the lookup file or parsed).

Best existing value of central office code (value verified in the lookup file or parsed).

Best existing value of station number (parsed value).

Number with Canadian IDC (in the form +1, 1, or 001) or without IDC.

Number can contain any character. All except digits are removed before parsing.

Number with comment is parsed but the comment is lost.

Empty record or input value that does not contain any characters - number is considered NULL.

Foreign numbers (considered invalid).

Numbers with extension or interval (considered invalid).

Source SSN (mandatory).

Date when SSN was issued (optional).

Standardized value of SSN (cleansed and valid SSN).

Best known value of SSN (standardized, cleansed, or input value).

Standardized value of SSN area code (area where SSN was issued).

Standardized issued date.

Data quality imperfection explanations.

{1}\{area code}\{central office code}\{station number}

\{+1}\{area code}\{central office code}\{station number}

{001}\{area code}\{central office code}\{station number}

\{area code}\{central office code}\{station number}

{1} \{area code} \{central office code} \{station number}

\{+1} \{area code} \{central office code} \{station number}

{001} \{area code} \{central office code} \{station number}

\{area code} \{central office code} \{station number}

{1} (\{area code}) \{central office code} \{station number}

\{+1} (\{area code}) \{central office code} \{station number}

{001} (\{area code}) \{central office code} \{station number} (\{area code}) \{central office code} \{station number}

Not parsed phone number.

Incomplete US phone number.

Multiple phone numbers.