Problem
How Location address cleanse AVC codes works and how to configure depending on the requirement
Solution
The AVC (Address Verification Code) is a string of characters separated by hyphen character which represents the level of accuracy of cleansed address based on input fields. There are four categories of verification codes
- Verified (Code starts with V)
- Ambiguous (Code starts with A)
- Unverified (Code starts with U)
- Partially Verified (Code Starts with P)
Locations which are returned with verified or ambiguous codes are added with Reltio Data Cleanser Crosswalk to the entity, for other 2 verification codes a crosswalk shall not be added by Reltio
Based on the AVC codes returned by the Loqate, Reltio provides a way to configure and customize the behavior of setting "Verification Status" attribute value. This configuration can be made at 2 levels
- Environment Level - This is for all tenants in a particular environment and this is the default behavior which Reltio configures. This cannot be changed according to the customer business use cases
- Tenant Level - This is at the tenant level and supersedes environment level configuration. This configuration can be made at 2 places: physical configuration and metadata configuration. If Reltio finds the configuration in metadata L3 level, it supersedes the configuration given in physical configuration
Below is the sample configuration and can be customized. More details about this AVC code can be found on this web site - https://support.loqate.com/documentation/reportcodes/address-verification-code/
"verificationStatusMapping": {
"Ambiguous": [
"A(0|1|2|3).*"
],
"Verified": [
"V(4|5).*",
"P(4|5).*",
"A(4|5).*"
],
"Partially Verified": [
"V(0|1|2|3).*",
"P(0|1|2|3).*"
],
"Reverted": [
"R.*"
],
"Conflict": [
"C.*"
],
"Unverified": [
"U.*"
]
}
Comments
0 comments
Please sign in to leave a comment.