Skip to main content

Clean Application


Are you compatible with TLS 1.2?
Test your connections as soon as possible to avoid service disruptions.
From 4th of December all our products and services will only accept TLS 1.2.

.

Overview

As a back office tool, Clean Application is designed to clean and validate the address and email data you have collected from your customers, contacts and prospects. Our postal data is sourced from the official postal authorities of the relevant country, and is updated regularly. Email addresses are checked in real time against the email service providers.As such, Clean Application should be used regularly to ensure that your contact information is always correct and up-to-date.

CleanEnrichValidate

Clean Application cleans postal addresses from your contact database, including corrections and updates to the following:

  • Misspelled and mistyped information
  • Omitted information
  • Incorrect or outdated postal codes
  • Inconsistent and non-standard formatting
  • Standardisation with country-specific preferences

View Sample

DataPlus information can be appended to all cleaned postal addresses, allowing you to enrich the quality of your existing data. DataPlus includes the following information:

  • Contact telephone and fax numbers
  • Geographic coordinates
  • Government catchment areas
  • Business and employment information

 

Clean Application can also validate email addresses alongside cleaning postal addresses, including validating the following:

  • Mailbox or domain exists.
  • Mailbox is deliverable.
  • Mailbox is legitimate.
  • Domain is reachable.
  • Domain is disposable.

The extent to which contact data can be cleaned and enriched may vary depending on the quality of the information you provide.

The jobs page

The Jobs page is Clean's homepage. It acts as a dashboard from which you can view information about all the clean and enrich Jobs you have submitted, and is also the location you should visit to run a new Job.

Run a New Job

Use the Run New Job button to begin configuring a new Job with Clean.

Latest Jobs

If you have used Clean before, the Latest Jobs area will display the details of the last four Jobs you have run.

Jobs fall into one of four categories:

Ready For Download

This Job has finished processing and completed successfully. Select this Job to go to the Results page, where you can download the Job's cleaned address file and reports.

Once you download the results of a Job, the Job's status will change to Download Complete.

In Progress This Job has submitted successfully but is still being processed by Clean. You will receive an email when the Job is complete.
Download Complete This Job completed successfully, and you have already downloaded the results. However, you can still select this Job again to go to the Results page.
Failed This Job was submitted successfully but Clean could not complete the processing. Select this Job to see why.

Job history

If you have used Clean before, the Job History area will display the details of all Jobs you have run in the past.

This area contains the same details as the Latest Jobs area, but also contains more historical information. You can see more details about any of your past Jobs, and access the Results page for successful Jobs, from this area.

Use the Filter list by status drop-down box to show only Jobs of a certain type (such as Jobs which are still in progress), and the Next/Previous buttons to scan through historical and more recent Jobs. You can also reorder the table by clicking the column headers.

Supported countries

For postal address cleaning, Clean Web Service supports the following countries:

  • Australia
  • Canada
  • France
  • Ireland
  • New Zealand
  • United Kingdom
  • United States of America
  • Singapore

Email address cleaning is not geographically restricted.

Licensing

When cleaning postal addresses, the countries, layouts and DataPlus that you have access to are determined by your unique licence agreement.

Email and postal address cleaning require separate licences.

If you need access to more features of Clean than your current licences provide, contact your Experian Account Manager or support.

Example clean

Clean Application is capable of turning limited postal information into full, usable postal addresses by correcting errors and omissions, updating old data and adding postally required information. At the same time, Clean can clean email addresses in real time. This is illustrated in the simple example below.

Sample input addresses

IDNameEmailAddress2Address3Address4Address5Address6
1 The Beer Co. enquiries@beerco.com Old Brewery 2 The Maltings Milton Abbas Blandford DT11OBH
2   joe.bloggs@hotmail.com Brookfield Terrace Higher Foxdale Isle Of Man IM4123  
3 Geometry In hi@geometry-inc.co.uk Euclid Street Swindon      
4 Bark and Berk bark.berk@lawyers.net Charnwood Wokingham Road Bracknell Berkshire RG12 1PB
5 Southbury Sand orders@southburysand.org 8 Southbury Carshalton Beeches Surrey    

Sample cleaned addresses

Match ProfileMatch CodeNameAddress2Address3Address4Address5Address6EmailEmailMatchCodeID  
Good Match R933004010200300000000000000:GBR The Beer Co. 2 The Maltings Milton Abbas BLANDFORD FORUM Dorset DT11 OBH enquiries@beerco.com Verified 1  
Partial Match O903000000280000000000000000:GBR       ISLE OF MAN     joe.bloggs@hotmail.com Verified 2  
Multiple Matches M903000000200600000000000000:GBR Geometry Inc Euclid Street   SWINDON     hi@geometry-inc.co.uk Unreachable 3  
Good Match R933000000201000000000000000:GBR Bark & Berk Charnwood Wokingham Road BRACKNELL Berkshire RG42 1PB bark.berk@lawyers.net Verified 4  
Poor Match R023601a10200103000000000000:GBR Southbury Sand 8 Southbury Lawn Road GUILDFORD Surrey GU2 4DD orders@southburysand.org Verified 5  

As well as cleaning and standardising the postal address in a format tailored for the relevant country (in this case, the United Kingdom), Clean Application has added a match profile and match codes for the postal and email addresses which communicate the exact changes that were made to the data, and why.

Using Clean Application, you can send thousands of postal and email addresses for this kind of cleaning, as well as enriching your existing postal data by appending DataPlus. 

Using

Records are uploaded to Clean Application in a CSV file (up to 2Gb in size), and cleaned results are provided in the same way once all records have been processed.

Each set of records submitted to and processed by Clean is known as a Job. You can run several Jobs at the same time, and will receive notifications by email when each of your Jobs have completed and their results are ready for download.

Each Job can be run using different settings, ranging from the country you want to clean postal addresses against and the DataPlus information you want to append, to the mapping of your input file and the types of report you want to generate.

Running a new job

To run a new Job, select the Run New Job button from the Job History page.

Running a new Job with Clean Application consists of the steps above.

In order to run a Job, you must have the following:

  • An input file containing postal and/or email address details, in CSV (comma-separated value) format. 

    A CSV file stores tabular data as plain text. Columns are separated by a special character, typically a comma, and rows are separated by line breaks. A CSV file can consist of any number of records, which usually have an identical sequence of fields.
    Most database systems are capable of importing and exporting CSV data.

  • A username and password for a Clean Application account. 

    Clean Application accounts can have multiple users, each with their own username and password.
    To set up your Clean Application account, or to create subsequent usernames, visit the Clean Application homepage.

  • Licences for the countries and DataPlus you would like to use. 

    Licences govern the countries you are allowed to clean your address data against, as well as the DataPlus information you can append to your address records.
    For more information, view the available datasets and layouts.

If you have all of the above, log in to Clean Application and select Run New Job to begin.

If you need help configuring your Job, make sure help tips are switched on using the button at the top-right of the page.
You can now hover the mouse cursor over Clean's options and buttons to receive tips at the bottom of the screen.

1. Name

The name you enter here will be used to identify this Job to you again in the future.

It will not be used during processing, but you should enter something here that identifies this Job uniquely. For example, the set of addresses, their country of origin, or the reason that you are processing these addresses.

You will have an opportunity to change this name during the Submit stage.

2. Upload

Select Browse to locate a CSV file containing postal and/or email address information.

The file must be:

  • no larger than 2Gb
  • saved on your computer or local network.

To improve match quality for postal addresses, ensure that your input files have each address element in a separate field.

Select Upload file to send the file to Clean Application. You will see a summary of the information stored in the file:

Select the appropriate header row option. The preview will update to show you the effect that this has on your file.

A header row is always the first record in a CSV file. It is used to give a title to the columns in the data. Clean Application uses these titles, but does not process them as addresses.
If your input file does not contain a header row, select No above the table to make sure that your first record is processed as an address. Clean Application will provide a default title for each column.

As well as the Name you entered earlier, today's date, the number of records and the filename will all be stored for your reference.

3. Mapping

The file mapping stage is used to tell Clean Application what each of the columns in your input file contain.

For each column, there are the following options. However, you can only assign the column types that you are licensed to use. 

  • Organisation (currently only used when processing French addresses) - indicates that this column contains information which should be included in the output file and processed as the name of an organisation. Multiple Organisation columns will be merged into one in your Cleaned Address File.
  • Address - indicates that this column contains elements of a postal address which should be included in processing.
  • Email - indicates that this column contains an email address that should be processed.
  • Keep - indicates that this column contains information which should be included in the output file, but should not be included in processing.
  • Remove - indicates that this column should be ignored, and removed from the output file.

In the example above, the ID and Name columns contain important information that is required by the database, and therefore it is kept. The other columns contain address and email information which Clean Application will use during processing in order to clean the contact information.

4. Settings

If you mapped one or more columns as Address in the Mapping stage, you can select or create a dataset and layout for your cleaned addresses.

If you did not map any columns as Address, you will not see this step.

The Settings stage is used to select a dataset to clean your addresses against and a layout for your Cleaned Addresses. A layout defines the address elements (such as the street number, town and postal code) which are included in each address record, as well as additional DataPlus elements which you can add to append data to your Cleaned Addresses.

Before selecting a layout, make sure you have selected the right dataset from the list on the left. Hover over each dataset to learn more about it.

You can select layouts from the main panel. Use the View buttons to see each one in full. For more information, see How Layouts relate to Cleaned Addresses.

Adding Layouts

If none of the layouts in this panel meet your needs, you can create a new one by clicking the Add New Layout button. For more information, see Adding or Editing Layouts.

5. Output

Output settings are used to tell Clean Application how to organise your output file, and which reports to generate.

Additional fields to be included in the output

The two checkboxes on this screen let you set which additional fields to include in the output file:

Include original input data – Select this to include your input data in the output file. This will be included as extra columns which can be used as reference against the cleaned fields.

Include best matches – Select this to include additional columns containing the best match. In some cases, these may be your original input fields (if Clean Application has not been able to find a good match). Otherwise, they will be the cleaned fields.

Additional reports to be included with your results

Clean Application generates a Clean Summary report for each Job. This report contains information about the number of records matched and cleaned, as well as the type of processing that took place.

Depending on the Settings you selected earlier, other reports may also be available. Check the box next to each report's name to include it with your results.

Fill out the fields for each report before continuing.

Sample Output

Before your job is submitted, the first ten records of your input file will be processed in order to show you the results of your Job.

Check the sample output to make sure the results are as you expect. If they are, continue to submit your full Job to Clean Application.

6. Submit

The submit screen displays a summary of the settings you selected during the previous stages.

Review these settings, and use the Edit buttons to alter any settings, if necessary. If any fundamental changes are made, you may need to redefine other settings as well.

Once you are happy with all of the settings, and have reviewed the Experian terms and conditions, select Submit Job to send your address file for processing by Clean Application.
You do not have to keep Clean Application open to complete the Job. You will receive an email once the Job is complete, containing a link to the Job History page.

Address datasets and predefined layouts

The following datasets are supported by Clean Application when cleaning postal addresses. 

You can add your own custom layouts during the Settings stage. Custom layouts can include address lines from one of the datasets you are licensed to use, and any of the DataPlus sets you are licensed to use from the same dataset.

Each dataset relates to addresses in a particular country, but some countries are served by more than one dataset. In these cases one of the datasets (AUG for Australia) contains geocoding DataPlus, which is absent from other datasets.

The countries, datasets and DataPlus elements you can use depend on the licences available to you.

Australia

Using the Australia address dataset, Australian addresses can be cleaned against one of the following predefined layouts:

Note that selecting a certified layout ensures that the results returned by Clean are completely in line with Australia Post’s AMAS address matching rules. This may result in a lower matching rate due to the stricter nature of these rules.

AMAS Certified (Postal Address File)

Addresses are returned in an AMAS-Certified layout, and include unique Delivery Point Identifiers (DPIDs). Address barcoding is available.

This layout qualifies for AMAS reports.

LineAddress Element(s)Example
1 [Automatic Line 1] 7 Alexander Street
2 [Automatic Line 2]  
3 [Locality] [State Code] [Postcode] HAMILTON SOUTH NSW 2303
4 Delivery Point Identifier (DPID) 59172312
LineDataPlus ElementExample
5 Barcode Sort Plan Number 017
6 Customer Barcode 1301011230012102100102333123313022013

Certified status

This address layout is Certified by your local carrier. To retain its Certified status, you may not edit the address lines or remove existing DataPlus elements. However, by creating a new layout based on this one, you may add DataPlus elements and retain the benefits of Certification, as long as the DataPlus elements you add are not included as part of a mailing address.

Standard Clean (Postal Address File)

Addresses are returned in a non-certified layout. Address barcoding is available.

LineAddress Element(s)Example
1 [Automatic Line 1] 7 Alexander Street
2 [Automatic Line 2]  
3 [Locality] [State Code] [Postcode] HAMILTON SOUTH NSW 2303

Australia G-NAF

Using the Australia G-NAF address dataset, Australian addresses can be cleaned against the following predefined layout:

Geocoded National Address File (G-NAF)

Addresses are optimised for geocoding. A range of geocoding DataPlus items are available.

LineAddress Element(s)Example
1 [Automatic Line 1] 7 Alexander Street
2 [Automatic Line 2]  
3 [Locality][State Code][Postcode] HAMILTON SOUTH NSW 2303

Canada

Using the Canada address dataset, Canadian addresses can be cleaned against one of the following predefined layouts:

4 Line Standard

Similar to Standard, but supplied as a four-line layout.

LineAddress Element(s)Example
1 [Automatic Line 1] The Greenview
2 [Municipality] KINGSTON
3 [Province code] ON
4 [Postal Code] K7M 7T5

5 Line Standard

Similar to Standard, but supplied as a five-line layout.

LineAddress Element(s)Example
1 [Automatic Line 1] The Greenview
2 [Automatic Line 2] 14 Greenview Dr
3 [Municipality] KINGSTON
4 [Province code] ON
5 [Postal Code] K7M 7T5

5 Line Submitted

Similar to Submitted, but supplied as a five-line layout.

LineAddress Element(s)Example
1 [Automatic Line 1] The Greenview
2 [Automatic Line 2] 14 Greenview Dr
3 [Municipality] KINGSTON
4 [Province code] ON
5 [Postal Code] K7M 7T5

When using Submitted layouts, all capitalisation sent in the request is retained.

Certified

A three-line layout. The language of the province is retained, but fully capitalised (for example, "ONTARIO").

This layout qualifies for SOA reports.

LineAddress Element(s)Example
1 [Automatic Line 1] The Greenview
2 [Automatic Line 2] 14 Greenview Dr
3 [Municipality][Submitted Province]*[Province code] KINGSTON ONTARIO K7M 7T5

* The language and formatting of the province sent in the request is retained by the [Submitted Province] address element. When using the Certified layout, this element is always capitalised.

Certified status

This address layout is Certified by your local carrier. To retain its Certified status, you may not edit the address lines or remove existing DataPlus elements. However, by creating a new layout based on this one, you may add DataPlus elements and retain the benefits of Certification, as long as the DataPlus elements you add are not included as part of a mailing address.

Standard

A three-line layout. The two-letter province code replaces the information supplied (for example, "ON").

LineAddress Element(s)Example
1 [Automatic Line 1] The Greenview
2 [Automatic Line 2] 14 Greenview Dr
3 [Municipality][Province code][Postal Code] KINGSTON ON K7M 7T5

Submitted

A three-line layout. The language and capitalisation of the province is retained (for example, "Ontario").

LineAddress Element(s)Example
1 [Automatic Line 1] The Greenview
2 [Automatic Line 2] 14 Greenview Dr
3 [Municipality][Submitted Province]*[Postal Code] KINGSTON Ontario K7M 7T5

* The language and formatting of the province sent in the request is retained by the [Submitted Province] address element. When using Submitted layouts, capitalisation is also retained.

France

Using the France address dataset, French addresses can be cleaned against one of the following predefined layouts:

AFNOR

This layout is identical to the AFNOR with business names layout, but an organisation name is not required. A maximum of six lines (fields) will be returned, but the first line will be left blank if no organisation information is supplied.

LineAddress Element(s)Example
1 [AFNOR line 1] * TRADUCTEURS NAÏFS
2 [AFNOR line 2] † APPARTEMENT 37, BÂTIMENT 4
3 [AFNOR line 3] † LIEU DIT AU BALIVERNES
4 [Number] [Number Extension] [Street] 10A BOULEVARD GEORGES CLEMENCEAU
5 [PO Box] [Submitted Locality] NORD-PAS DE CALAIS
6 [Postal Code] [Town] [CEDEX Office] 62226 CALAIS CEDEX

* Company or recipient’s name, or blank
† Details such as flat, floor, staircase, entrance, building, and secondary street

This layout is identical to the 'AFNOR with business names' layout, but an organisation name is not required. A maximum of six lines (fields) will be returned, but the first line will be left blank if no organisation information is supplied.

AFNOR with business names

This layout is compliant with AFNOR standard XPZ10-011 (May 1997). Each address will be returned on a maximum of six lines (fields), with a maximum of 38 characters per line.

To use this layout successfully you should supply business names in one or more fields, and map the columns they occupy as Organisation.

LineAddress Element(s)Example
1 [AFNOR line 1] * TRADUCTEURS NAÏFS
2 [AFNOR line 2] † APPARTEMENT 37, BÂTIMENT 4
3 [AFNOR line 3] † LIEU DIT AU BALIVERNES
4 [Number] [Number Extension] [Street] 10A BOULEVARD GEORGES CLEMENCEAU
5 [PO Box] [Submitted Locality] NORD-PAS DE CALAIS
6 [Postal Code] [Town] [CEDEX Office] 62226 CALAIS CEDEX

* Company or recipient’s name, or blank
† Details such as flat, floor, staircase, entrance, building, and secondary street

This layout is compliant with AFNOR standard XPZ10-011 (May 1997). Each address will be returned on a maximum of six lines (fields), with a maximum of 38 characters per line.

Standard

This layout is similar to the AFNOR layout, but the last line contains the addresses' département and postal code, in that order (rather than the postal code, town and CEDEX office). Organisation names are not required or expected.

LineAddress Element(s)Example
1 [AFNOR line 1] * TRADUCTEURS NAÏFS
2 [AFNOR line 2] † APPARTEMENT 37, BÂTIMENT 4
3 [AFNOR line 3] † LIEU DIT AU BALIVERNES
4 [Number] [Number Extension] [Street] 10A BOULEVARD GEORGES CLEMENCEAU
5 [PO Box] [Submitted Locality] NORD-PAS DE CALAIS
6 [Département] [Postal Code] PAS-DE-CALAIS 62226

* Company or recipient’s name, or blank
† Details such as flat, floor, staircase, entrance, building, and secondary street

This layout is similar to the AFNOR layout, but the last line contains the addresses' département and postal code, in that order (rather than the postal code, town and CEDEX office). Organisation names are not required or expected.

Ireland

Using the Ireland address dataset, Irish addresses can be cleaned against one of the following predefined layouts:

Resident Preferred

This layout returns the format of addresses commonly preferred by residents, as indicated by the address elements that are present in the input address. For example, 'Co Dublin' will be retained if present in the input address, rather than being replaced with an official equivalent (such as 'Dublin 22').

LineAddress Element(s)Example
1 [Automatic Line 1]  Meneen
2 [Automatic Line 2]  Achadh Ghobhair
3 [Automatic Line 3]  Cathair na Mart
4 [Automatic Line 4]  Maigh Eo
5 [Automatic Line 5]  

Resident Preferred Gaelic

Returns the format of addresses commonly preferred by residents (as above), but with address elements returned in their Gaelic format (where available).

LineAddress Element(s)Example
1 [Automatic Line 1]  Meneen
2 [Automatic Line 2]  Achadh Ghobhair
3 [Automatic Line 3]  Maigh Eo
4 [Automatic Line 4]  
5 [Automatic Line 5]  

Standard

This is the official An Post format of a given address. This format varies depending on whether a building group is present in the address.

LineAddress Element(s)Example
1 [Automatic Line 1] Meneen
2 [Automatic Line 2] Aghagower
3 [Automatic Line 3] Westport
4 [Automatic Line 4] Co Mayo
5 [Automatic Line 5]  

Gaelic

This is the official An Post format of a given address (as above), but with address elements returned in their Gaelic format (where available).

LineAddress Element(s)Example
1 [Automatic Line 1] Meneen
2 [Automatic Line 2] Achadh Ghobhair
3 [Automatic Line 3] Maigh Eo
4 [Automatic Line 4]  
5 [Automatic Line 5]  

New Zealand

Using the New Zealand address dataset, New Zealand addresses can be cleaned against the following predefined layout:

SendRight Certified (Postal Address File)

The city of the address is returned as the [Locality] element. Address identification and coding DataPlus information is available.

This layout qualifies for SOA and SOA Log reports.

LineAddress Element(s)Example
1 [Automatic Line 1] Villa 105
2 [Automatic Line 2] Summerset Retirement Village
3 [Automatic Line 3] 15 Aotea Drive, Aotea
4 [City][Postcode] Porirua 5024

Certified status

This address layout is Certified by your local carrier. To retain its Certified status, you may not edit the address lines or remove existing DataPlus elements. However, by creating a new layout based on this one, you may add DataPlus elements and retain the benefits of Certification, as long as the DataPlus elements you add are not included as part of a mailing address.

Singapore

Using the Singapore address dataset, Singaporean addresses can be cleaned against the following predefined layout:

Standard

A standard address format for Singapore addresses.

LineAddress Element(s)Example
1 [Automatic Line 1] Window Delivery 2
2 [Building Number][Street] 2 Raffles Link
3 [Floor][Unit][Building Name] #03-04 Marina Bayfront
4 [Locality][Postal code] Singapore 039392

United Kingdom

Using the United Kingdom address dataset, British addresses can be cleaned against one of the following predefined layouts:

Royal Mail Standard

Similar to the Standard layout, but a Delivery Point Suffix is supplied as an additional address field. DataPlus fields are not available using this layout.

LineAddress Element(s)Example
1 [Automatic Line 1] 26 Stokesby Road
2 [Automatic Line 2]  
3 [Town] Chessington
4 [County] Surrey
5 [Postcode] KT9 2DU
6 [Delivery Point Suffix]* 1A

* A Delivery Point Suffix, in conjunction with a postcode, can be used to programmatically create a RM4SCC (Royal Mail 4-state) barcode.

Standard

A standard address format for British addresses.

LineAddress Element(s)Example
1 [Automatic Line 1] 26 Stokesby Road
2 [Automatic Line 2]  
3 [Town] Chessington
4 [County] Surrey
5 [Postcode] KT9 2DU

United States

Using the United States address dataset, United States addresses can be cleaned against one of the following predefined layouts:

Note that selecting a certified layout enables CASS-accredited output and ensures the results returned by Clean conform to the CASS rules, including the mandatory use of Delivery Point Validation (DPV). This may result in a lower matching rate due to the stricter nature of these rules.

4-line Non-Certified

Identical to the Non-Certified layout, but supplied as a four-line layout.

LineAddress Element(s)Example
1 [Automatic Line 1] The White House
2 [City Name] Washington
3 [State Code] DC
4 [ZIP Code] [ZIP +4 Code] 20500 0003

5-line Certified

Identical to the Certified layout, but supplied as a five-line layout.

This layout qualifies for CASS reports.

Note that if you encounter a seed address whilst using Clean, your account will be DPV locked and you will no longer be able to use certified cleaning.

LineAddress Element(s)Example
1 [Automatic Line 1] The White House
2 [Automatic Line 2] Pennsylvania Ave Nw
3 [City Name] Washington
4 [State Code] DC
5 [ZIP Code] [ZIP +4 Code] 20500 0003
LineDataPlus ElementExample
6 DPV: DPV Footnotes AAN1
7 DPV: DPV Confirmation Indicator D
8 DPV: CMRA Confirmation Indicator N
9 DPV: Seed Address Indicator  
10 DPV: Vacant Address Indicator N
11 DPV: No-Mail Indicator N

DPV (Delivery Point Validation) DataPlus elements return information about the validity of address records in accordance with USPS guidelines.

Note that if you encounter a seed address whilst using Clean, your account will be DPV locked and you will no longer be able to use certified cleaning.

Certified status

This address layout is Certified by your local carrier. To retain its Certified status, you may not edit the address lines or remove existing DataPlus elements. However, by creating a new layout based on this one, you may add DataPlus elements and retain the benefits of Certification, as long as the DataPlus elements you add are not included as part of a mailing address.

5-line Non-Certified

Identical to the Non-Certified layout, but supplied as a five-line layout.

LineAddress Element(s)Example
1 [Automatic Line 1] The White House
2 [Automatic Line 2] Pennsylvania Ave Nw
3 [City Name] Washington
4 [State Code] DC
5 [ZIP Code] [ZIP +4 Code] 20500 0003

5-line Secondary Non-Certified

As above, but supplied as a five-line layout including a secondary building number (such as an apartment number).

LineAddress Element(s)Example
1 [Automatic Line 1] The White House
2 [Secondary number] Apt 34
3 [City Name] Washington
4 [State Code] DC
5 [ZIP Code] [ZIP +4 Code] 20500 0003

6-line County Non-Certified

As above, but supplied as a six-line layout including the county name.

LineAddress Element(s)Example
1 [Automatic Line 1] The White House
2 [Automatic Line 2] Pennsylvania Ave Nw
3 [City Name] Washington
4 [County Name] Washington D.C.
5 [State Code] DC
6 [ZIP Code] [ZIP +4 Code] 20500 0003

Certified

A standard three-line layout. Delivery Point Validation (DPV) is available, as well as LACSLink and SuiteLink data.

This layout qualifies for CASS reports.

Note that if you encounter a seed address whilst using Clean, your account will be DPV locked and you will no longer be able to use certified cleaning.

LineAddress Element(s)Example
1 [Building/firm name] [Urbanization] The White House
2 [Primary number] [Automatic Line 2] 1600 Pennsylvania Ave Nw
3 [City Name] [State Code] [ZIP Code] [ZIP +4 Code] Washington DC 20500 0003
LineDataPlus ElementExample
6 DPV: DPV Footnotes AAN1
7 DPV: DPV Confirmation Indicator D
8 DPV: CMRA Confirmation Indicator N
9 DPV: Seed Address Indicator  
10 DPV: Vacant Address Indicator N
11 DPV: No-Mail Indicator N

DPV (Delivery Point Validation) DataPlus elements return information about the validity of address records in accordance with USPS guidelines.

Note that if you encounter a seed address whilst using Clean, your account will be DPV locked and you will no longer be able to use certified cleaning.

Certified status

This address layout is Certified by your local carrier. To retain its Certified status, you may not edit the address lines or remove existing DataPlus elements. However, by creating a new layout based on this one, you may add DataPlus elements and retain the benefits of Certification, as long as the DataPlus elements you add are not included as part of a mailing address.

Non-Certified

Identical to the Certified layout, but DPV, LACSLink and SuiteLink data is not available.

LineAddress Element(s)Example
1 [Building/firm name] [Urbanization] The White House
2 [Primary number] [Automatic Line 2] 1600 Pennsylvania Ave Nw
3 [City Name] [State Code] [ZIP Code] [ZIP +4 Code] Washington DC 20500 0003

Specialised font files

Some Clean DataPlus sets return values which can only be properly interpreted using specialised font files.

If you plan to use any of the DataPlus sets listed below, you should download the associated font files in order to use the data as intended.

CountryDataPlus SetDownload
Australia Customer Barcode AUS4STSTE.TTF
Singapore Barcode RM4SCC.TTF
United Kingdom Barcode RM4SCC.TTF
United States of America USPS POSTNET Barcode POSTNET.TTF

To use these font files, first install them in your operating system.

In your database or word processor, set the barcode portion of your cleaned addresses to display in the appropriate barcode font. You should make sure the barcodes are displayed correctly on screen before printing. For example, a RM4SCC-format barcode looks like this before and after the font is applied:

(BX11LT1AI)   

Adding custom layouts

Layouts define how cleaned postal addresses are formatted. They are unique to each dataset, and you can create and store as many Layouts for each dataset as you require. Existing Layouts for each dataset can be viewed and deleted from the Settings screen.

To add a new Layout, select the appropriate dataset and click the Add New Layout button. 

  • Select a Layout to use as a starting point, or select None to start from a blank Layout.
  • If you are creating a new Layout based on a certified Layout, the Retain certified status by preserving address elements box will be checked by default.

    This will preserve the address elements of the predefined Layout. As a result, you will retain the certified status of the predefined Layout that your new layout will be based on. You will, therefore, only be able to edit the DataPlus elements in your new Layout.

    If the predefined Layout changes in the future, your new Layout will inherit the changes automatically.

    If you do not want to link your new Layout to the predefined Layout it's based on, uncheck this box.

  • If you are creating a new Layout based on a non-certified layout, the Maintain predefined address format (only allow DataPlus changes) box will be checked by default.

    This will maintain the address format of your predefined Layout. You will, therefore, only be able to edit the DataPlus elements in your new Layout.

    If the predefined Layout changes in the future, your new Layout will inherit the changes automatically.

    If you do not want to link your new Layout to the predefined Layout it's based on, uncheck this box.

  • Click Go to start editing the new Layout, or Close to use an existing Layout instead.

Any layouts you create will be available to everyone who uses this Clean account.

Address lines

An address layout is constructed from individual address elements across multiple lines. To add address elements to a line, simply drag them from the Address panel to the desired position. 

You can add multiple address elements to a line if required, and remove any you don't need using the buttons.

If an element has a button, it can be split into multiple sub-components. Click the button to show them – you can now drag the sub-components onto an address line.

If you can't find the address element you need, try typing its name into the search box.

DataPlus lines

If you have access to DataPlus elements, you can add these to DataPlus lines below the address lines.

First, click the button of a DataPlus group to see the available elements, then drag the elements you require onto one or more DataPlus lines:

You can add one DataPlus element to each line, and remove them using the buttons. You can also add new DataPlus lines and drag DataPlus elements between them.

If you can't find the DataPlus element or group you need, try typing its name into the search box.

Modifying lines

As well as adding elements to lines, you can add and remove lines, move lines up and down within a section, and set the maximum width of each line.

 

1   Click this button to add a new empty line to the bottom of this section (either the Address Elements section or the DataPlus section).
2 If this section has more than one line, click and drag one of these icons to move lines up or down in the Layout.
3

Use the up and down arrows in the Width column to adjust the maximum width of each line. This number is measured in characters. If a Cleaned Address line exceeds its maximum width, the text on that line will be clipped to this amount of characters.
If you want to restrict an address line's width without clipping its contents, insert an address line below it containing just the element. Note that this technique cannot be used with DataPlus lines.

4 If this section has more than one line, click this button to delete a line. If the line contains any elements, they will be removed from the Layout.

How layouts relate to cleaned addresses

In Clean, Layouts are used to control the format that postal addresses would traditionally be displayed on an envelope. For example:

‎Example Layout in Clean

Example Cleaned Address


However, in most cases Clean is used to edit records within a database, and it does so via a plain text file in .csv format. This means the address in the Cleaned Address File (which you will download once your Job is complete) will actually more like this:

So, the lines that you create in a Layout are transposed to a horizontal format in your Cleaned Address File, but they remain in the order you stipulate.

Reports

The reports available to you depend on your chosen settings and whether you are Cleaning postal or email addresses.

Postal Addresses

All Countries

Overall Summary Report 

A more detailed version of the information found in the Results Summary pane of the Results screen, including a statistical breakdown of the Job's results.

If you are cleaning French addresses, this will be called 'French Clean Summary Report', as French Match Profiles will be used.

Australia

Your Job must be configured to use the AMAS Certified (Postal Address File) layout to qualify for this report.

AMAS Certification Report

The Address Matching Approval System (AMAS) Certification Report an be used to qualify for reduced postage rates from Australia Post. Read more.

Canada

Your Job must be configured to use the Canada  layout to qualify for this report.

SERP Certification Report

The Software Evaluation and Recognition Program (SERP) Certification Report can be used to qualify for reduced postage rates from Canada Post. 

New Zealand

Your Job must be configured to use the New Zealand  layout to qualify for these reports.

New Zealand Statement of Accuracy Report

The Statement of Accuracy (SOA) Report can be used to qualify for reduced postage rates from New Zealand Post. 

New Zealand Log Report

The New Zealand Log Report maintains a running record of the Statement of Accuracy reports that you produce over time. Include this report to see a record of your current and previous SOAs.

United States

Your Job must be configured to use one of the United States  layouts to qualify for this report.

CASS Certification Report

The Coding Accuracy Support System (CASS) Certification Report can be used to qualify for reduced postage rates from USPS. 

Email Addresses

Overall/Email Summary Report 

A more detailed version of the information found in the Results Summary pane of the Results screen, including a statistical breakdown of the Job's results.

If you ran a Job which included French postal addresses, this report will be called 'Email Summary Report'. Otherwise, this information will be contained within the 'Overall Summary Report'.

Job results

When you submit a Job to Clean, a new entry appears in the Job History. You will receive an email once the Job is complete; if your Job is marked as Ready for download or Download complete, follow the link to view detailed information on the Results page.

Results summary

The Job Summary pane contains a visual summary of your results, and the statistics of your Clean broken down by Match Profile or Result. The example below breaks down the results of an address clean:

This information appears in more detail in the Clean Summary Report.

What do the different Match Profiles and Results mean?

In the Results Summary, each of the processed records are grouped into different categories depending on the level of success that Clean was able to match them with a correct postal or email address.

Are Match Profiles related to Match Codes?

Yes. Address Match Profiles are derived from the most pertinent Match Code information for each address. Each address in your Cleaned Address File is assigned a unique Match Code. 

Why is there a difference between the number of Records Processed and Records Cleaned?

Records Processed

This is a count of the number of address records which Clean was able to process. Typically, this will be all of the records you provide.

  • For Clean, this is the number of records processed by Clean. Any records with a Match Success Indicator of A to D do not count as Records Processed.
  • For Enrich, this is the number of records for which DataPlus was returned. Any blank DataPlus fields do not count towards Records Processed.

Records Cleaned

This is similar to Records Processed, but only counts for 'Good' matches.

  • For Clean, a record only counts towards Records Cleaned if the Confidence Level is Intermediate (5) or High (9).
  • For Enrich, a record only counts towards Records Cleaned if the Confidence Level is High (9).

Why were some of my input addresses Unmatched?

Clean may fail to match input addresses which contain no usable information, or which contain so little information that a matching address is not able to be found.

For more information, see the description of the Match Success Indicator that was returned with your unmatched address in your Clean Address File.

Files available for download

To download your Cleaned Address File (the .csv file containing the results of your Job), select the Cleaned Address File button.
The Cleaned Address File will be downloaded to your computer, and will contain the fields you previewed during the Output stage.

To download reports (in .pdf format), select the relevant Report button.

Reports will be downloaded to your computer, and correspond to the reports you requested during the Output stage.

Job settings

The settings you used to configure the Job are shown here for reference. These are the same as the overview of settings displayed during the Submit stage.

You may want to refer back to these in the future when you configure a new Job.

Sample clean

Although the results of address cleaning vary according to the country and datasets you clean your addresses against, as well as the quality of your input data, the results of address cleans are always returned in the same order:

Postal address fields

If you marked any fields as 'Address' during the Mapping stage, these fields will appear as the first set of columns in your cleaned address file.

Match Profiles

  • The first cleaned address field is always a Match Profile.
  • Each of the processed addresses are grouped into different categories depending on the level of success that Clean was able to match them with a correct address.

Match Codes

  • The next cleaned address field is always a Match Code.
  • Match codes describe the differences between input postal addresses and their corresponding cleaned addresses.
  • Changes such as updated postal codes, corrected spellings, insertion of missing address components are indicated here, as well as reasons why a matching address could not be found.

Input Address Fields (optional)

  • If (during the Output configuration stage) you choose to include your input address fields with your cleaned addresses, these will be returned after the Match Code.
  • These fields will be identical to the input address fields you submit to Clean, and can be used to directly compare your input and cleaned addresses.

Cleaned Address Fields

  • Cleaned address fields appear after your input address fields (if you choose to include input addresses during the Output configuration stage) or after the Match Code (if you do not).
  • Cleaned address fields are the end result of Clean's address cleaning process, and represent the corrected and completed version of the input address fields you submitted.
  • In the event that Clean cannot clean an address with high confidence (generally because of a very low quality input address), the cleaned address fields may be blank or incomplete. In this situation, including the best address fields may be useful.

Best Address Fields (optional)

  • If (during the Output configuration stage) you choose to include best address fields, these will be returned after the cleaned address fields.
  • Best address fields represent the most useful address: this will usually be identical to the cleaned address, but if no matching address was found, or if vital elements of the address are missing, the input address that you submitted may appear here instead.
  • Best matches fields are intended to compile the results of the cleaning process for you, keeping manual processing of the results to a minimum.

Enrichment Fields (optional)

  • Enrichment fields contain any DataPlus elements you requested during the Settings configuration stage. Each DataPlus element is returned in its own field, as shown here.
  • In situations where Clean was unable to match an address to the accuracy required (either household-level or street-level, depending on the DataPlus set), the enrichment fields for that address will be blank.

Email address fields

If you marked any fields as 'Email' during the Mapping stage, these fields will appear as the second set of columns in your cleaned address file.

Input Email (optional)

  • If (during the Output configuration stage) you choose to include your original input data with your output, these will be returned as the first email address field.
  • These will be identical to the input email addresses you submit to Clean, and can be used to directly compare your input and cleaned email addresses.

Cleaned Email Address Fields

  • Cleaned email address fields appear after your input email address fields (if you choose to include input addresses during the Output configuration stage) or as the first email address field (if you do not).
  • As email addresses are not cleaned in the same way as postal addresses, the cleaned email address fields will always be identical to the email addresses you supply.
  • To see whether an email address should be used, consult the corresponding Email Match Code.

Best Email Address Fields (optional)

  • If (during the Output configuration stage) you choose to include best matches, these will be returned after the cleaned email address fields.
  • As email addresses are not cleaned in the same way as postal addresses, the best email address fields will always be identical to the email addresses you supply.
  • To see whether an email address should be used, consult the corresponding Email Match Code.

Email Match Codes

  • The last email address field is always an email match code.

Placeholders are used for the Email match codes in the Sample Output stage, but real match codes will appear in your Cleaned Address File.

Keep fields (optional)

If you marked any fields as 'Keep' during the Mapping stage, these fields will appear as the last columns in your cleaned address file.

These fields will be identical to the versions in your input file.

Match profiles

In the Results Summary, each of the processed results are grouped into different categories depending on the level of success that Clean was able to match them with a correct postal or email address.

Each of the possible Match Profiles (postal addresses) and Email Match Codes (email addresses) are defined below.

All addresses (except French)

If you are cleaning addresses from any country other than France, the possible Match Profiles are as follows.

Match ProfileMeaningRelated Match Codes
Verified Correct Clean verified the input address as a good-quality match to a complete address. No corrections or formatting changes were necessary.


Success: R or Q
Confidence: 9
Generic Infobit: 00000040

Good Match Clean verified the input address as a good-quality match to a complete address, although minor corrections or formatting changes may have been applied.

Success: R or Q
Confidence: 9

Good Premise Partial Clean was not able to find a full match to a correct address, but found a good match to premise level by excluding organisation or sub-premise details.

Success: O or P
Confidence: 9
Generic Infobit: 00000002

Tentative Match Clean found a match to a complete address, but the overall differences between the input and Cleaned addresses are significant enough to reduce Clean's confidence in the match.

Success: R or Q
Confidence: 5

Multiple Matches Clean found more than one correct address which matched the input address. This generally means that no single address could be matched with high confidence. Success: M or N
Poor Match Clean found a match to an address, but with low confidence. This often means that the Cleaned address is not deliverable.

Success: R or Q
Confidence: 0

Partial Match Clean was unable to find a full correct address which matched the input address. This often occurs when the property number is missing from the input address. Success: O or P
Foreign Address Clean could not find a matching address because the input address referred to a country other than that which you ran your clean against. Success: C
Unmatched Clean was unable to match the input address to any correct address. For more detail, see the Match Success Indicator assigned to this address. Success: ABDK or L

French addresses

If you are cleaning French addresses, the possible Match Profiles match the La Poste Match Categories, as follows.

Match ProfileMeaningRelated Match Codes
Address already correct The address was deemed to be correct as supplied. All address elements were supplied on the correct lines, and in the correct format.

Confidence: 9
Country Infobit: 10000000

Address corrected or modified The address was matched with a high degree of confidence, but some corrections were made. For example, spelling or formatting may have been corrected, or missing address elements may have been added.

Confidence: 9
Country Infobit: 20000000

Address to be checked A match was found, but Clean cannot be certain that the returned address is the correct one. For example, the returned address may be very different from the input, important address elements may have been changed, or other equally good matches may exist in the data. The match has been downgraded to intermediate confidence, and the user should check the returned address manually.

Confidence: 5
Country Infobit: 40000000

No match No address could be returned at all. Unmatched addresses will return low confidence. Confidence: 0

Emails

If you are cleaning email addresses, the possible Email Match Codes are as follows:

Email Match CodeMeaning
Verified Mailbox exists, is reachable, and not known to be illegitimate or disposable.
Undeliverable Mailbox or domain does not exist, or mailbox is full, suspended or disabled.
Unknown We were unable to conclusively verify or invalidate this address.
Unreachable Domain has no reachable mail exchangers.
Illegitimate Seed, spamtrap, black hole, technical role account or inactive domain.
Disposable Domain is administered by a disposable email provider (e.g. Mailinator).

Match codes

Match codes describe the differences between input postal addresses and their corresponding cleaned addresses. They can be used to achieve an in-depth analysis of the changes that have been applied. They can also be used to programmatically select addresses to be added back into your database.

If you have processed postal address data, Match Codes are always included as the first field of each address in your Cleaned Address File. See an example of what this looks like.

An example match code is broken into its component sections above. 

Match success indicator

The Match Success Indicator is always one upper case letter and describes how well the input address matched to the output address returned by Clean.

Letters A-D mean that the address was not processed. The reason for this is indicated by the letter returned.

A Unprocessed Results could not be returned for the input address. This reflects an internal processing issue, and should not occur during normal usage.
B Blank This means that Clean could either find no data in the input address or too insignificant an amount of data to return an address.
C Country not available This match letter is returned when your input address contains the name of an unsupported country.
D Unidentified Country A match letter of D is assigned to the address record when Clean is unable to ascertain the country of origin.

The Information Bit sections of unprocessed addresses will always be empty (represented by a series of uninterrupted zeros).

Letters K-R mean that the address was successfully processed. The quality of the match is indicated by the letter returned.

K No address or postcode could be derived This match letter is used when Clean cannot find any data which matches your input address. For example, if you processed 42 Durlston Square, Clean would return a K match. This is because there are no matching street names within the United Kingdom, and Clean has no other information (such as a locality or postcode) to search on.
L Postcode found, but no address could be derived This match letter is returned if Clean derives a valid postcode from your input address information but did not find a matching address
M Multiple addresses found, but no postcode

Clean returns this match letter if the input address matches more than one address in the dataset. For example, the address below returns four matches:
146 High Street, Cambridge
As the address exists in the localities of Sawston, Cottenham, Chesterton and Landbeach, Clean cannot determine what is the desired match. As all four potential matches have different postcodes and no single postcode can be returned, Clean marks the address as an M match.

N Multiple addresses found with postcode This type of match is returned when Clean finds more than one matching address within a postcode.
O Partial address found, but no postcode

In this case Clean has found a partial address which matched your input. However, it cannot return a full postcode with it, because the partial address is covered by more than one postcode. This might occur if your input address has a missing or invalid property number. Clean cannot determine the correct property number, and returns as much of the address as it can. For example, in this address, number 70 does not exist:
70 Glebe Road, Long Ashton, Bristol
As no postcode is included in the input address, Clean does not know which of two possible postcodes to return, and produces this output:
Glebe Road, Long Ashton, Bristol

P Partial address found with postcode

Clean has found a partial address which matches your input. In addition, either the input postcode was valid, or Clean has managed to find a single postcode for the partial address. For example, if this address is searched on:
Tooting Bec Rd, London
Clean is able to add a postcode and state code, but the lack of property number prevents the return of a full address.

Q Full address found, but no postcode This occurs when Clean finds a full address which matches your input data, but cannot find a full postcode to go with it.
R Full address and postcode found

In this case, Clean has made a full match, either by simply verifying a correct input address, or by locating a full address from the partial input data. The following example returns an R match:
14 Carnaby St, London
However, an R match only signifies that a full address and postcode have been returned; it does not necessarily mean that the address is the one you want. You can gauge the likelihood of a correct match from the match confidence level.

Confidence level

The Confidence Level is always one single digit and indicates the level of confidence which Clean has in each match. There are three possible values:

9 High confidence Indicates that the output address matches the input address.
5 Intermediate confidence

Indicates that the less important rules were not satisfied, such as:

  • There must be some form of match with a street name.
  • If none of the place elements have been matched, the postcode must be matched.
0 Low confidence

Indicates that the essential matching rules were not satisfied. These rules include such conditions as:

  • There must be an input element defining the location of the address (a town, a postcode etc).
  • There must be an element defining property information.

Postal code action

Postal Code Action indicates any action that Clean has performed on the postcode. There are four possible values:

0 No action was taken (usually because no postcode was found, or the address was not processed).
1 The existing postcode was already correct.
2 A postcode has been added.
3 The existing postcode has been corrected.

Address action

Address Action indicates any action that Clean has performed on the address, other than the postcode. There are three possible values:

0 No action was taken (usually because the input address could not be matched to a correct address).
2 The existing address was enhanced. No significant information has been removed, but some information has been added.
3 A partial or complete address was returned. The amount of address is signified by the match success indicator.

Generic information bits

Generic Information Bits are used to communicate general changes to your address information.

Information Bits are added together to make up a hexadecimal code. The example above is a combination of 00002000 (change of key premises number) and 00000020 (non-trivial cleaning).

Information BitDescription
10000000 The elements in the input address were not in the expected order. For example, the address "7 Old Town, SW4 0JT, London", would be changed to place the postcode at the end of the address.
20000000 Preferred matching rules were not satisfied, and the match will be, at best, intermediate confidence.
40000000 The address has been marked with, at best, intermediate confidence because close matching rules have been satisfied.
80000000 Conditional formatting has taken place. Some address elements in the specified output format were not present in the matched address record and have been replaced with equivalent address elements.
01000000 Extra numbers were found in the address. An example might be "Flat 2, 12 10, Abbeville Road, London".
A full match was achieved, (Flat 2, 10 Abbeville Road, London, SW4 9NJ) but the additional number(s) (i.e. "12" in the above example) may reduce the confidence level to Intermediate.
02000000 Additional text between a number and its expected adjacent component has been found, for example between a property number and a street name. The confidence level has been reduced to Intermediate.
04000000 No place element was found in the address, so the confidence level may be reduced.
08000000 An item associated with a number is missing. For example, in the address "4, South Marston, Swindon, SN3 4XX" should include the street name "Ash Gardens" after the building number.
00100000 One or more essential matching rules were not satisfied, so the confidence level has been reduced to low.
00200000 A timeout has occurred and the address has not been matched. This error should occur extremely rarely; if you encounter this problem, please let us know.
00400000 The input address was a superset of the address found by Clean.
For example, the input address "Village Arcade, 5 Hillcrest Road, Pennant Hill, NSW, 2120" contains more information than the official version, which does not contain the "Village Arcade" element.
00800000 The input address contained leading information which was not matched in the return address.
For example, the input address "8 Piermark Drive, PO Box 1116, London, SE1 7AG" contains more information than the official version, which does not contain the "8 Piermark Drive" element.
00010000 There was ambiguity in the supplied range in the input address.
For example, the address "138-140 Tooting Bec Road, London" has an ambiguous range because there are premises numbered 138, 139 and 140 on Tooting Bec Road and the input address cannot be matched to a specific property.
00020000 A street descriptor has been added or has changed. For example, given "4 Oamaru Street, Devizes", the correct descriptor "Way", is returned instead of "Street".
00040000 Additional text in the input address was too significant to ignore. This returns intermediate confidence.
00080000 There was an error in the input street name that Clean has amended.
00001000 There was an error in an input place name. This has been corrected by Clean.
00002000 Clean has added or changed a key premises number or range compared with the input address.
00004000 An exact street level match cannot be made, and there is more than one possibility of matching by changing either the street or the place. Due to this ambiguity at the street level, Clean cannot safely match the input address.
00008000 A name was used to secure an address match.
00000100 The address line settings of the currently configured layout are of an insufficient width to contain each address element. Widen the address lines to ensure that the address elements are not truncated.
00000200 Complete address element(s) are unable to fit on the address line. Widen the address lines to ensure that all of the address elements are visible.
00000400 Clean failed to generate one or more non-address items. Address matching is unaffected.
00000800 When in enhanced cleaning mode, Clean cannot fill the unmatched address elements back into the database. To resolve this, widen the address lines or add additional lines.
00000010 Address elements have been moved to the right or downwards to allow unmatched elements to be incorporated, to produce an enhanced address.
00000020 Clean has determined that the supplied address has been non-trivially cleaned. This means that spelling may have been corrected, capitalisation changed, or the input address elements could have been reformatted in some way. Note that quotes and spaces are ignored during Clean's comparison process.
00000040 Key input address elements were judged effectively correct as supplied, although note that the output address's representation or formatting may differ (for example, address elements may have been expanded or abbreviated, or capitalisation changes may have been made).
00000080 The amount of input lines specified during configuration does not match the number of lines found in the input file. This Information Bit does not affect the confidence level.
00000001 An unambiguous match has been found, but stricter checks have resulted in the confidence level being reduced to, at best, intermediate.
00000002 Clean has found a premises level partial address match.
00000004 Clean has found a street level partial address match.
00000008 Clean has found a place level partial address match.

Country information bits

Country Information Bits are used to communicate detailed changes to your address information.

Country Information Bits are added together to make up a hexadecimal code. The example above (which relates to USA data) is a combination of 1000000 (ZIP+4 has been assigned) and 08000000 (Address converted using LACS).

Asia-Pacific

Australia

Information BitDescription
10000000 An exact street level match is not possible as more than one non-exact match is possible by changing either a supplied street element or the supplied locality. If this information bit is set, no match is returned.
20000000 Multiple street type(s) or invalid street type(s) are supplied in the input address, and there is more than one match with the equivalent match quality. If this information bit is set, match confidence is reduced.
40000000 Multiple PO Box types were supplied in the input address, or the changes required to obtain a match makes the input postal delivery type invalid. If this information bit is set, match confidence is reduced.
80000000 A bordering locality match is prohibited because a match is already available in the locality that was entered, and can be returned by changing the street type or street type suffix
01000000

No additional valid secondary information has been supplied in the input address given a real or phantom primary point reference address match.

02000000 A match has been made to a real primary point, a holding premises which is a valid delivery point in itself.
04000000

A match has been made to a phantom primary point. These are holding premises which cannot be a valid delivery point without valid additional secondary information.
If the address is cleaned in the AMAS certified mode, match confidence will be reduced to intermediate if information bit 01000000 is also set.

00100000 The supplied Customer Barcode Info field is blank.
00200000

Invalid characters are present in the supplied Customer Barcode Info field. The valid characters are letters, numbers, spaces and hashes.

00400000

The 52 digit extended barcode (AUSBAR.Ext52) can convert a maximum of 5 Customer Barcode Info characters. If your Customer Barcode Info contains more than 5 characters, this information bit is returned and the field is treated as blank when generating the barcode.

00800000

The 67 digit extended barcode (AUSBAR.Ext67) can convert a maximum of 10 Customer Barcode Info characters. If your Customer Barcode Info contains more than 10 characters, this information bit is returned and the field is treated as blank when generating the barcode.

00010000

The building number has been amended. For example, a single number in the input address has been matched to a range containing that number.

00020000 There was an error in the building name.
00040000

Floor/Level information has been added or amended.

00080000 Flat/Unit information has been added or amended.
00001000 There was an error in the street name.
00002000 The street type has been added or changed.
00004000 The street type suffix has been added or changed.
00008000 A street alternate form has been matched and may be retained in the output address (where the ‘Street alias’ output item has been fixed during configuration).
00000100 There was an error in the locality information supplied in the input address.
00000200 There was an error in the state information supplied in the input address.
00000400 The flat/unit number or the sub-premise number that was entered did match that in the data, but the type/descriptor did not match. In this case, the type or descriptor entered by the user will be retained in the output address.
00000800 A valid bordering locality and postcode combination has been matched.
00000010 Street level (DID) address matched.
00000020 Locality level (DID) address matched.

Australia G-NAF

Information BitDescription
10000000 A street alias has been matched and may be retained in the output address if the street alias output item has been fixed during configuration.
20000000 A locality alias has been matched and may be retained in the output address if the locality alias output item has been fixed during configuration.
40000000 A bordering locality has been matched and may be retained in the output address.
01000000

A match has been made to premises-level, specifically building number, only. No sub-premises item has been matched.

02000000 No additional valid secondary information has been supplied in the input address. A building number has been supplied and matched.
04000000 A building number and valid secondary information have been supplied in the input address but neither matched. The unmatched secondary information may be retained in the output address.
00100000 A valid PO Box type has been supplied in the input address.

New Zealand

Information BitDescription
10000000 Unique match - matches to a unique delivery address.
20000000 Base Address match - matches to a street number.
40000000 Invalid match - does not match to a delivery address.
01000000

Sub-premise information added.

02000000 Street Type difference in matched address.
04000000 Street Name difference in matched address.
08000000 Street Direction difference in matched address.
00200000

Rural delivery difference in matched address.

00400000

An invalid match caused by matching a suburb alias. This bit will only be set if other elements were valid.
Records with this information bit will be excluded from the SOA report, if you requested one.

00800000

Rural address match with missing or unmatched premise info.
Records with this information bit will be excluded from the SOA report, if you requested one.

00010000

This bit will be set for Poste Restante addresses.
Records with this information bit will be excluded from the SOA report, if you requested one.

00020000

This bit will be set for Private Bag addresses.
Records with this information bit will be excluded from the SOA report, if you requested one.

00040000

Lobby added or corrected in matched address.

00080000 Suburb added or corrected in matched address.
00001000 City added or corrected in matched address.
00002000 A valid suburb alias has been matched and may be retained in the output address if the suburb alias output item has been fixed during configuration.
00004000 A valid city alias has been matched and may be retained in the outputp address if the city alias output item has been fixed during configuration.
00000100 Unambiguous match to an address with ‘deleted’ status with no alterations to any of the PAF address elements.

Singapore

Information BitDescription
10000000 Floor/unit numbers were supplied, but not matched in the data. The supplied floor/unit numbers have been returned as part of the address.
20000000 Additional unit information was supplied, but is not available in the dataset. The supplied additional unit information has been returned as part of the address.

North America

Canada

Information BitDescription
10000000 Premises number optimized, changed or inserted.
20000000 Route number optimized, changed or inserted.
40000000 Extraneous data optimized, changed, inserted or removed.
80000000 Street suffix optimized, changed, inserted or removed.
01000000 Station name optimized, changed, inserted or removed.
02000000 Station type optimized, changed, inserted or removed.
04000000 Station qualifier optimized, changed, inserted or removed.
08000000 Province optimized, changed, inserted or removed.
00100000 Street type optimized, changed, inserted or removed.
00200000 Street direction optimized, changed, inserted or removed.
00400000 Community optimized, changed, inserted or removed.
00800000 Street name optimized, changed, inserted or removed.
00010000 Apartment keyword optimized, changed, inserted or removed.
00020000 Route/Box keyword optimized, changed, inserted or removed.
00040000 Foreign record keyword optimized, changed, inserted or removed. 
00080000 Apartment number optimized, changed, inserted or removed.
00001000 Box number optimized, changed, inserted or removed.
00002000 Street number outside valid range.
00004000 Route Number outside valid range.
00008000 Invalid '#' symbol in address.
00000100 Valid Postal CodeOM.
00000200 Postal CodeOM changed from Rural to Urban.
00000400 Postal CodeOM corrected.
00000800 Local Delivery Unit (LDU) changed.
00000010 Forward Sortation Area (FSA) changed.
00000020 Postal CodeOM inserted.
00000040 Postal CodeOM changed.
00000080 A better Postal CodeOM exists.
00000001 Address considered Valid for SERP (no changes required to input).
00000002 Address considered Correctable for SERP (input has been corrected and a unique match supplied).
00000004 Address considered Non-Correctable for SERP (input could not be corrected or is too ambiguous to supply a unique match).

United States

Information BitDescription
10000000 ZIP+4 has been assigned.
20000000 DPBC has been assigned.
40000000 5-digit ZIP has been assigned.
80000000 Address is a High Rise Default.
01000000 Address is a High Rise Exact.
02000000 Address is a Rural Route Default.
04000000 Address is a Rural Route Exact.
08000000 Address converted using LACS.
00100000 USPS footnote A: 5-digit ZIP Code has been corrected.
00200000 USPS footnote B: City/State spelling has been corrected.
00400000 USPS footnote C: City/State/ZIP are invalid.
00800000 USPS footnote D: No ZIP+4 has been assigned.
00010000 USPS footnote E: ZIP Code has been assigned for multiple response.
00020000 USPS footnote F: Address not found in the dataset with City/State/ZIP provided.
00040000 USPS footnote G: Part of the firm was moved to address.
00080000 USPS footnote H: Secondary number was missing for this address.
00001000 USPS footnote I: Insufficient/incorrect address data supplied.
00002000 USPS footnote J: PO Box address used for dual address.
00004000 USPS footnote K: Non-PO Box address used for dual address.
00008000 USPS footnote L: Delivery address component has been changed.
00000100 USPS footnote M: Street name has been changed.
00000200 USPS footnote N: Delivery address has been standardised.
00000400 USPS footnote P: Delivery address is known by a preferred name.
00000800 USPS footnote R: Address is not in current data, but will be added in the future.
00000010 USPS footnote S: Secondary number does not match.
00000020 USPS footnote T: Address has magnet street syndrome (multiple).
00000040 USPS footnote U: City or PO name supplied was not an official last line name.
00000080 USPS footnote V: City or state could not be verified as corresponding to the ZIP code.
00000001 USPS footnote W: Address was identified as a small town default.
00000002 USPS footnote X: Address has a unique ZIP code default.
00000004 USPS footnote Z: Match made using ZIPMOVE data.
00000008 USPS footnote Q: Match has been made to a unique ZIP.

Europe

France

Information BitDescription
10000000 The address was deemed to be correct as supplied. All address elements were supplied on the correct lines and in the correct format.
20000000 The address was matched with a high degree of confidence, but some corrections were made. For example, spelling or formatting may have been corrected, or missing address elements may have been added.
40000000 A match was found, but Clean cannot be certain that the returned address is the correct one. For example, the returned address may be very different from the input, important address elements may have been changed, or other equally good matches may exist in the data. The match has been downgraded to intermediate confidence, and the user should check the returned address manually.
80000000 As well as the returned address, Clean found one or more alternative addresses of similar quality. For example, the supplied street does not exist but there are two very similar streets to choose from. When this situation arises, the information bit 4000000 is also set.
01000000 The returned address is in a format that conforms to the AFNOR standard. This specifies which address line should be used for each address element, the maximum length of each line, and the abbreviations that should be used.
00001000 A secondary street name was supplied but was not matched in the data. This has been returned as part of the address.
00000100 A premises number was supplied for the secondary street but was not matched in the data. This has been returned as part of the address.
00000200 A premises suffix was supplied for the secondary street but was not matched in the data. This has been returned as part of the address.
00000010 A primary street name was supplied but was not matched in the data. This has been returned as part of the address.
00000020 A locality name was supplied but was not matched in the data. This has been returned as part of the address.
00000040 A PO Box number was supplied for the primary street but was not matched in the data. This has been returned as part of the address.
00000080 An organisation name was supplied for the primary street but was not matched in the data. This has been returned as part of the address.
00000001 A premises number was supplied for the primary street but was not matched in the data. This has been returned as part of the address.
00000002 A premises suffix was supplied for the primary street but was not matched in the data. This has been returned as part of the address.

Ireland

Information BitDescription
10000000 English Primary Locality added that was not supplied in the input address
20000000 Gaelic Primary Locality added that was not supplied in the input address
40000000 English Secondary Locality added that was not supplied in the input address
80000000 Gaelic Secondary Locality added that was not supplied in the input address
01000000 Street retained from the input address that is not in the data
02000000 Street added that was not supplied in the input address
00100000 Match to bordering locality
00200000 Match to bordering Dublin district number
00400000 Wrong Dublin district number supplied
00800000 Match to bordering county
00020000 Posttown added
00001000 Gaelic Primary Thoroughfare available
00002000 Gaelic Secondary Thoroughfare available
00004000 Gaelic Primary Locality available
00008000 Gaelic Secondary Locality available
00000100 English Posttown has been removed
00000200 Gaelic Posttown has been removed
00000400 English Resident Preferred Posttown has been removed
00000800 Gaelic Resident Preferred Posttown has been removed
00000010 Non-trivial change applied as a result of referencing An Post data

United Kingdom

Information BitDescription
10000000 Postcode has been recoded.
20000000 Multiple recodes exist for supplied postcode.
01000000 Town added or altered.
02000000 County added or altered.
04000000 PNR county form present for matched address.
00100000 Dependent locality added or altered.
00200000 Double dependent locality added or altered.
00400000 Postally non-required locality alias is retainable in the output address.
00010000 Thoroughfare name difference.
00020000 Thoroughfare descriptor added or changed.
00040000 Dependent thoroughfare name difference.
00080000 Dependent thoroughfare descriptor added or changed.
00001000 Building number corrected (for example, a single premises number corrected to a range).
00002000 Building name amended.
00004000 Sub-building number corrected (for example, a single premises number corrected to a range).
00008000 Sub-building name amended.
00000100 Organisation name altered.
00000200 Organisation name matched to reference initials.
00000400 Organisation department name added or changed.

Extended country information bits

Extended Country Information Bits are used to communicate detailed changes to your address information. They are not available for all countries.

Information Bits are added together to make up a hexadecimal code. The example above (which relates to USA data) is a combination of 0020000 (address was DPV confirmed) and 00004000 (business address improved using SuiteLink data).

Australia Extended Information Bits

Information BitDescription
10000000 BSP assigned state as NSW
20000000 BSP assigned state as ACT
40000000 BSP assigned state as VIC
80000000 BSP assigned state as QLD
01000000 BSP assigned state as SA
02000000 BSP assigned state as WA
04000000 BSP assigned state as TAS
08000000

BSP assigned state as NT

Canada Extended Information Bits

Information BitDescription
10000000 Postal CodeOM not found.
20000000 Province not found.
40000000 Community not found.
80000000 Street name not found.
01000000 Street type not found or invalid.
02000000 Street direction not found or invalid.
04000000 Street suffix range error.
08000000 Street number not found or invalid.
00100000 Suite keyword invalid.
00200000 Suite number range error or exceeds 6 characters.
00400000 Route/box keyword not found.
00800000 Route service not found/range error.
00010000 Box number not found or invalid.
00020000 Delivery installation name not found.
00040000 Delivery installation keyword not found.
00080000 Delivery installation qualifier not found.
00001000 General delivery keyword not found.
00002000 Invalid '#' symbol in address.
00004000 Other/unknown reason for unmatched address.
00008000 Rural Route (RR) or Large Volume Receiver (LVR) address (addresses identified as RR or LVR may not be checked but still return valid matches).
00000100 Rural Route (RR) or Large Volume Receiver (LVR) address corrected.
00000200 Rural address questionable. The address may be valid, but appears to be inconsistent or missing key address elements.
00000400 Apartment address questionable. The address may be valid but appears to be inconsistent or missing key address elements.

United States Extended Information Bits

Information BitDescription
10000000 Primary information in the input address was unmatched but has been included in the output address.
20000000 Secondary information in the input address was unmatched but has been included in the output address.
40000000 Unmatched additional secondary information in the input address has been included in the output address.
80000000 The address matched an alternative firm/organisation, but the input organisation was used in the output address.
01000000 The input street address matched a PO Box record in a unique ZIP code area. Confidence has been reduced to low.
02000000 The input PO Box matched a street record in a unique ZIP code area. Confidence has been reduced to low.
04000000 A street level match without primary information has been found in a unique ZIP code area. Confidence has been reduced to low.
08000000 Unidentified additional numeric information in the input address has been omitted from the output address.
00100000 USPS footnote Y: Input address matched a military record.
00200000 The address was DPV confirmed (for the purposes of CASS mailing discounts).
00400000 The address was DPV confirmed as a high-rise default but secondary information was not matched.
00800000 The address was DPV confirmed, but secondary number provided was not matched.
00010000 USPS footnote F1: matched ZIP+4 Military record.
00020000 USPS footnote G1: matched ZIP+4 General Delivery record.
00040000 USPS footnote U1: matched ZIP+4 unique zipcode record.
00080000 USPS footnote P3: invalid PO, RR, or HC box number.
00001000 USPS footnote AA: input address matched to ZIP+4 file.
00002000 USPS footnote A1: input address not matched to ZIP+4 file.
00004000 Business address improved using SuiteLink data.
00008000 Address updated using NCOALink data.
00000100 USPS footnote BB: input address fully matched (all components).
00000200 USPS footnote CC: primary number match but secondary number not matched (present but invalid).
00000400 USPS footnote N1: primary number match to high-rise or box type address, but secondary information missing.
00000800 USPS footnote M1: primary number missing from input address.
00000010 USPS footnote M3: supplied primary number invalid - could not confirm address.
00000020 USPS footnote P1: box type address (i.e. PO/RR/HC) missing box number.
00000040 USPS footnote RR: CMRA (Commercial Mail Receiving Agent) address match.
00000080 USPS footnote R1: CMRA (Commercial Mail Receiving Agent) address match, but secondary number not present.
00000001 DPV system is enabled at the point after the search.
00000002 DPV system has been disabled.
00000004 DPV search was a seed address, disabling the system from this point onwards until it is successfully unlocked.

Country

A Country identifier is appended to all match codes, and indicates the country which Clean cleaned (or attempted to clean) the address against.

Copyright ©, 2014-2017. All rights reserved.