Understanding Address Verification Code

Learn about Address Verification Codes (AVC) and their role in data accuracy.

When the system cleanses the location, it adds a corresponding Address Verification Code (AVC) and Verification Status.

When a location is either added, updated, or merged within Reltio, the key address attributes are updated.

The accuracy code is made up of the following values:

Verification Status
Post-Processed Verification Level
Pre-Processed Verification Level
Parsing Status
Lexicon Identification Level
Context Identification Level
Postcode
Match Score

Note: The Verification Status, Post-Processed Verification Level and Match Score are the primary values.

For example, V55-I55-P7-100 implies:

Verification Status = V (Verified)
Post-Processed Verification Level = 5 (Delivery Point)
Pre-Processed Verification Level = 5 (Delivery Point)
Parsing Status = I (Identified and Parsed)
Lexicon Identification Level = 5 (Delivery Point)
Context Identification Level = 5 (Delivery Point)
Postcode = P7 (Added)
Match Score = 100 (Complete similarity)

Verification Status

Verification statuses of locations are mapped by considering the following points.

V: Verified - Indicates that there was a complete match between the input data and a single record from the available reference data.
P: Partially Verified - Indicates that there was a partial match between the input data and a single record from the available reference data.
U: Unverified - Unable to verify; the output fields contain input data.
A: Ambiguous - Indicates that there are more than one close reference data match.
C: Conflict - Indicates that there are more than one close reference data matches with conflicting values.
R: Reverted - Indicates that the record did not meet the specified minimum acceptable level. The output fields contain input data.
Note: Addresses with P: Partially Verified or A: Ambiguous statuses, even if they have a Post-Verification Level ≥ 4 (Premise or Building Level) and a match score ≥ 90 aren't automatically considered V: Verified.
The Verification Status depends on additional validation criteria beyond these attributes. For full verification, the Verification Status must be V: Verified and meet the required data accuracy and reference match criteria.

Post-Processed Verification Level

The post-processed verification level indicates the level to which the input data matches the available reference data, once all the changes and additions performed during the verification process are considered.

5: Delivery Point (PostBox or SubBuilding)
4: Premise (Premise or Building)
3: Thoroughfare
2: Locality or PostalCode
1: AdministrativeArea
0: None

Pre-Processed Verification Level

The pre-processed verification match level indicates the level to which the input data matches the available reference data, prior to any changes or additions performed during the verification process.

5: Delivery Point (PostBox or SubBuilding)
4: Premise (Premise or Building)
3: Thoroughfare
2: Locality or PostalCode
1: AdministrativeArea
0: None

Note: If the pre-processed verification level is 0, the platform intentionally ignores the cleansed output and keeps the input values.

For example, AVC P10-I13-P1-100 has a third character of 0. Even reprocessing the input won’t improve the result because no useful pre-processing occurred.

To receive the cleansed output in this scenario, set the ignoreUnverifiedResults option to false in your tenant’s Level 1 / Physical configuration on the Tenant Configuration page of the Tenant Management app, see View and edit tenant configuration.

Parsing Status

I: Identified and Parsed - Indicates that all the input data is identified and placed into components.
U: Unable to Parse - Indicates that not all the input data is identified and parsed.

Lexicon Identification Match Level

The lexicon identification match level gives the level to which the output data has some recognized form, through the use of pattern matching (for example, a numeric value can be a premise number) and lexicon matching (for example, ‘rd’ can be a Thoroughfare, ‘Road’; ‘London’ can be a Locality).

5: Delivery Point (PostBox or SubBuilding)
4: Premise (Premise or Building)
3: Thoroughfare
2: Locality or PostalCode
1: AdministrativeArea
0: None

Context Identification Match Level

This is the least accurate form of matching and is based on identifying a word as is. For example, a Thoroughfare based on it being preceded by something that can be a Premise, and followed by something that can be a Locality. The later items are identified by a match against the reference data or the lexicon.

5: Delivery Point (PostBox or SubBuilding)
4: Premise (Premise or Building)
3: Thoroughfare
2: Locality or PostalCode
1: AdministrativeArea
0: None

Postcode Status

P8: PostalCodePrimary and PostalCodeSecondary verified
P7: PostalCodePrimary verified and PostalCodeSecondary added or changed
P6: PostalCodePrimary verified
P5: PostalCodePrimary verified with small change
P4: PostalCodePrimary verified with large change
P3: PostalCodePrimary added
P2: PostalCodePrimary identified by lexicon
P1: PostalCodePrimary identified by context
P0: PostalCodePrimary empty

Match Score

The match score indicates if the input data has changed during the verification process in order to achieve the post-processed verification match level. 100% indicates that no changes are made. Only data changes measured by the match score, data additions are not.

Generally, a match score of 95 or above indicates that only a character or two were changed during the process. If the input data is less clean, a threshold of 80 is considered. Significantly larger changes to the input data are then allowed.

Note: This value does not give any indication of the level of verification, that is given by the post-processed verification match level.

Unify and manage your data