Address verification jobs are created to assist in verifying address data for validation, allowing you to review suggested corrections and configure automatic approval thresholds based on match level. This allows you to ensure addresses are valid, complete, and standardized.
To create an address verification job:
From the Address Verification Home page, click the Create address job button.
Enter a Name (required) and a short Description (required) for the address verification job.
Select a country from the Default Country list box. This will be used if no country is listed in an input address.
Click the Select from datastore or system button to choose the system or datastore with which the address verification job is associated.
Select a datastore or system from the Datastore or System list box.
Select the table from the list of available tables.
Click Confirm. Data is loaded into the Field Mappings section.
Optionally, toggle the Use Geocode option to the On position to include geocode output fields (accuracy, distance, latitude, and longitude) in the export table for verified addresses with a status of Approved.
Note
The Use Geocode field can be edited after the initial save and run of the address verification job. However, if the job was initially processed with the Use Geocode option off, editing this field and running the job with the option on results in the use of additional Validation Credits. Therefore, it is important to ensure the Use Geocode option is correct before running the job.
In the Field Mappings grid, mark fields as Include to determine which fields to include in address verification.
Once a field is marked as Include, map the field with the appropriate address element by selecting the Field Type.
In the Field Mappings grid, mark one field as the Unique identifier (key field) for the record. There can only be one unique identifier, so a surrogate key (GUID, identify field, concatenated field, etc.) may be required if a dataset does not have a single key field.
In the Result Export Settings section, click the Configure datastore button to select a system or datastore to which results will be exported (optional).
Select a security profile from the Security Profile list box to associate specific user groups and roles with the address verification job. Refer to Security Profiles for more details on how security profiles are used throughout the Syniti Knowledge Platform (SKP).
Click Save to save the address verification job.
Note
Some address verification job settings are not available until after the job is saved. Refer to Manage Status Rules below for details on these fields.
After an address verification job is saved, it can be run by clicking the Run button on the Address Verification Job Details page.
Field Mappings
Use the Field Mappings grid to determine which output fields to generate for the corrected address data. The source mapping is the default mapping for data to populate in the selected column when no address match can be found for the given input. Refer to the table below for a description of available field types.
Field Type | Description |
|---|---|
Company | The company or business name associated with a particular delivery point, should one exist |
AddressLine | The full address can be entered in this field. It is not recommended to use this field unless address line ordering is standard and uniform across the data. |
Address1 - Address8 | These fields can be used to specify input address line data, and on output will contain the correctly formatted address for mailing in the relevant country, split into individual address lines. It is recommended to use these fields when address line data is not in standard order (e.g., Country, City, Zip, State, Street). |
City/Town | The most common population center data element within a country. For example, USA City or Canadian Municipality. |
State/Region | The state or region the address relates to |
Zip/Postcode | The complete, primary postal code for a particular delivery point should such detail be able to be determined. For example, USA zip, Canadian postcode, or Indian PINcode. |
Country | The ISO 3166 official country name |
Other | Fields not marked as Other cannot be included in the address verification. |
For each field, choose whether to include that field in the corrected address by marking Include. Additionally, mark the Unique option for any field that should be treated as a unique reference. You can only mark one field as a unique field.
Note
Field mappings cannot be changed after the initial run of the address verification job. It is important to ensure that fields are mapped correctly before running the job.
Manage Status Rules
Status rules allow you to configure which address changes that meet the configured match level are retained for manual review rather than being auto-approved. For example, suppose an address meets the Premise match level configured in the address verification job settings, but status rules are set to prevent anything with a large change to the company. In that case, the record is marked for manual review instead of being auto-approved. These settings are only available after the initial save of an address verification job. Click the Manage status rules button to manage these manual review settings.
The Match Level list box determines which level an address has to achieve in order to be auto-approved, provided it also conforms to the status rules. Refer to the table below for details on available match levels.
Name | Description |
|---|---|
Sub Premise | A specific unit or subdivision of a premise. For example, a suite/apartment/flat or floor number. |
Premise | The alphanumeric code identifying an individual location, should one exist. |
Thoroughfare | The most common street or block data element within a country. For example, USA street. |
Locality | The most common population center data element within a country. For example, USA city or Canadian municipality. |
Administrative Area | The county/region/state-level element of an address |
Once a match level is selected, choose to toggle on or off the following options for each field:
Small Correction (S)—Prevents auto-approval for an address record with a small correction to the associated field.
Large Correction (L)—Prevents auto-approval for an address record with a large correction to the associated field.
Added Value (A)—Prevents auto-approval for an address record with an added value to the associated field.