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.
An example match code is broken into its component sections below.
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.
| Match Success Indicator | Description | Explanation |
|---|---|---|
| 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. |
Letters K-R mean that the address was successfully processed. The quality of the match is indicated by the letter returned.
| Match Success Indicator | Description | Explanation |
|---|---|---|
| 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. |
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:
| Confidence Level | Description | Explanation |
|---|---|---|
| 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:
|
| 0 | Low confidence | Indicates that the essential matching rules were not satisfied. These rules include such conditions as:
|
Postal Code Action indicates any action that Clean has performed on the postcode. There are four possible values:
| Postal Code Action | Explanation |
|---|---|
| 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 indicates any action that Clean has performed on the address, other than the postcode. There are three possible values:
| Address Action | Explanation |
|---|---|
| 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 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 Bit | Description |
|---|---|
| 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 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).
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).
| Information Bit | Description |
|---|---|
| 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. |
| Information Bit | Description |
|---|---|
| 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. |
| Information Bit | Description |
|---|---|
| 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). |
| Information Bit | Description |
|---|---|
| 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. |
| Information Bit | Description |
|---|---|
| 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 |
| Information Bit | Description |
|---|---|
| 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. |
| Information Bit | Description |
|---|---|
| 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. |
| Information Bit | Description |
|---|---|
| 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. |
| Information Bit | Description |
|---|---|
| 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. |
| Information Bit | Description |
|---|---|
| 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 |
| Information Bit | Description |
|---|---|
| 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. |
| Information Bit | Description |
|---|---|
| 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. |
