Result Codes - SmartMover#
Record Level Result Codes#
Code |
Short Description |
Long Description |
---|---|---|
AS - Address Status |
||
|
Address Fully Verified |
The address is valid and deliverable according to official postal agencies. |
|
Valid Building Address |
The building address was verified but the suite/apartment number is missing or invalid. |
|
Non USPS Address Match |
US Only. This US address is not serviced by the USPS but does exist and may receive mail through third party carriers like UPS. |
|
Proprietary Address Format |
The address uses a proprietary addressing scheme where only the format could be validated. |
|
Foreign Address |
The address is in a non-supported country. |
|
SSN Found in our Records |
US Only. The address is a Commercial Mail Receiving Agency (CMRA) like a Mailboxes Etc. These addresses include a Private Mail Box (PMB or #) number. |
|
PBSA Address |
A PO Box formatted as a street address for package and mail delivery. |
|
Address Updated By LACS |
US Only. The address has been converted by LACSLink® from a rural-style address to a city-style address. |
|
Suite Appended |
US Only. A suite was appended by SuiteLink™ using the address and company name. |
|
Apartment Appended |
An apartment number was appended by AddressPlus using the address and last name. |
|
Vacant Address |
US Only. The address has been unoccupied for more than 90 days. |
|
No USPS Mail Delivery |
This address is classified as not receiving mail by the USPS via their No-Stat flag. Delivery might still be possible by third party carriers but that cannot be counted on. |
|
DPV Locked Out |
US Only. DPV processing was terminated due to the detection of what is determined to be an artificially created address. |
|
Deliverable only by USPS |
US Only. This address can only receive mail delivered through the USPS (i.e. PO Box or a military address). |
|
Extraneous Suite Information |
Extraneous information not used in verifying the address was found. This information was returned in the suite field. |
|
USPS Door Not Accessible |
Address identified by the USPS where carriers cannot physically access a building or door for mail delivery. |
|
Unique ZIP code |
The address contains a USPS unique ZIP code which means any address may be marked as deliverable. |
|
Unknown Data Moved to ParsedGarbage |
The input contains data that could not be identified. That data is returned in the ParsedGarbage/AddressExtras field |
|
Phantom Route address |
Addresses that are assigned to a phantom route of R777 or R779. |
AE - Address Error |
||
|
General Error |
The address could not be verified. This is likely due to a missing or invalid locality or postal code. |
|
Unknown Street |
Could not match the input street to a unique street name. Either no matches or too many matches found. |
|
Component Mismatch Error |
The combination of directionals (N, E, SW, etc) and the suffix (AVE, ST, BLVD) is not correct and produced multiple possible matches. |
|
Non-Deliverable Address |
US Only. A physical plot exists but is not a deliverable addresses. One example might be a railroad track or river running alongside this street, as they would prevent construction of homes in that location. |
|
Multiple Match |
The address was matched to multiple records. There is not enough information available in the address to break the tie between multiple records. |
|
Early Warning System |
US Only. This address currently cannot be verified but was identified by the Early Warning System (EWS) as belonging to a upcoming area and will likely be included in a future update. |
|
Missing Minimum Address |
Minimum requirements for the address to be verified is not met. Address must have at least one address line and also the postal code or the locality/administrative area. |
|
Sub Premise Number Invalid |
The thoroughfare (street address) was found but the sub premise (suite) was not valid. |
|
Sub Premise Number Missing |
The thoroughfare (street address) was found but the sub premise (suite) was missing. |
|
Premise Number Invalid |
The premise (house or building) number for the address is not valid. |
|
Premise Number Missing |
The premise (house or building) number for the address is missing. |
|
Box Number Invalid |
The PO (Post Office Box), RR (Rural Route), or HC (Highway Contract) Box number is invalid. |
|
Box Number Missing |
The PO (Post Office Box), RR (Rural Route), or HC (Highway Contract) Box number is missing. |
|
PMB Number Missing |
US Only. The address is a Commercial Mail Receiving Agency (CMRA) and the Private Mail Box (PMB or #) number is missing. |
|
Sub Premise Not Required (Deprecated - See AS23) |
A sub premise (suite) number was entered but the address does not have secondaries. (Deprecated - See AS23) |
AC - Address Change |
||
|
Postal Code Change |
The postal code was changed or added. |
|
Administrative Area Change |
The administrative area (state, province) was added or changed. |
|
Locality Change |
The locality (city, municipality) name was added or changed. |
|
Alternate to Base Change |
US Only. The address was found to be an alternate record and changed to the base (preferred) version. |
|
Alias Name Change |
US Only. An alias is a common abbreviation for a long street name, such as “MLK Blvd” for “Martin Luther King Blvd.” This change code indicates that the full street name (preferred) has been substituted for the alias. |
|
Address1/Address2 Swap |
Address1 was swapped with Address2 because Address1 could not be verified and Address2 could be verified. |
|
Address1 & Company Swapped |
Address1 was swapped with Company because only Company had a valid address. |
|
Plus4 Change |
US Only. A non-empty plus4 was changed. |
|
Dependent Locality Change |
The dependent locality (urbanization) was changed. |
|
Thoroughfare Type Change |
The thoroughfare (street) leading or trailing type was added or changed, such as from “St” to “Rd.” |
|
Thoroughfare Directional Change |
The thoroughfare (street) pre-directional or post-directional was added or changed, such as from “N” to “NW.” |
|
Sub Premise Type Change |
The sub premise (suite) type was added or changed, such as from “STE” to “APT.” |
|
Sub Premise Number Change |
The sub premise (suite) unit number was added or changed. |
CS - SmartMover Satus |
||
|
Move with New Address |
The record is a ‘move’ and a new ‘moved to’ address was provided. |
|
Standardized Address |
The record is not a ‘move’ but was standardized. |
|
Move Input Requirements not Satisfied |
The record is matched to change of address file but did not satisfy all requirements to produce a ‘moved to’ address. |
|
Move but No New Address |
The record is a ‘move’ but could not provide a ‘moved to’ address. |
|
Individual Move |
The record is classified as an individual. |
|
Family Move |
The record is classified as a family. |
|
Business Move |
The record is classified as a business. |
|
Daily Delete |
The record is a Daily Delete address. COA with this address is pending deletion from the master file and no mail may be forwarded from this address. |
CM - SmartMover Match Satus |
||
|
COA Match |
A COA was found for an Individual, Business, or Family. |
|
Foreign Move |
A COA was found for a Foreign Move. No forwarding address was provided. |
|
Moved no Forwarding |
A COA was found. The customer moved and left no forwarding address (MLNA). |
|
Box Closed |
A COA was found. The Post Box was closed with no order filed by the customer (BCNO). |
|
Cannot Match Secondary |
The COA could not be matched because the street address does not match with the secondary number. |
|
DPBC Ambiguous |
The COA could not be converted to a deliverable address because the 11-digit zip code represents more than one delivery point. |
|
Conflicting Middle Name |
The COA could not be matched because there is more than one COA record for the match and the middle names or initials on the COAs are different. |
|
Conflicting Gender |
The COA could not be matched because there is more than one COA record for the match and the genders of the names on the COAs are different. |
|
Conflicting Instructions |
The COA could not be matched because two potential matches were compared and had differences in the new addresses. |
|
Cannot Match High-rise Default |
The COA could not be matched because the input record is a potential match to a family COA record from a multi-unit building, but the address zip + 4 coded to the building default. This requires individual name matching logic to obtain a match and the individual names did not match. |
|
Cannot Match Rural Default |
The COA could not be matched because the input record is a potential match to a family COA record from a Rural Route or Highway Contract Route address. This requires individual name matching logic to obtain a match and the individual names did not match. |
|
Insufficient Name |
The COA could not be matched because there is a COA record with the same surname and address but there is insufficient first/middle name information on the COA record to product a match using individual matching logic. |
|
Middle Name Test Failed |
The COA could not be matched because the input name contains a conflict with the middle name or initials on the COA record. |
|
Gender Conflict |
The COA could not be matched because the gender of the name on the input record conflicts with the gender of the name on the COA record. |
|
Cannot Convert Address |
The COA was found but the new address would not convert at run time. |
|
Individual Name Insufficient |
The COA could not be matched because the input middle initial/name is missing or does not equal the middle initial/name on the potential COA match. |
|
Secondary Discrepancy |
The COA could not be matched because there is conflicting secondary information on the input and COA record or the input record contained secondary information and matched to a family record that does not contain secondary information. |
|
Other Insufficient Name |
The COA could not be matched because the input middle initial/name is missing or different from the middle name on the COA. A match cannot be made because the first name on the COA was truncated and the middle names must be equal in order to make this match. |
|
Cannot Match General Delivery |
The COA could not be matched for general delivery. |
|
No ZIP + 4, Not Confirmable, or Temporary |
The COA was found but the new address either: does not have a ZIP+4 coded and therefore there is no 11-digit DPBC, the primary number cannot be confirmed on DPV, or is temporary. |
|
Conflicting Directions |
The address could not be updated due to multiple matches. |
NCOA Return Codes |
||
|
COA Match |
The input record matched to a business, individual or family type master file record. A new address could be furnished. |
|
No Match |
The input record COULD NOT BE matched to a master file record. A new address could not be furnished. |
|
Foreign Move |
The input record matched to a business, individual or family type master file record but the new address was outside USPS delivery area. |
|
Moved Left No Address |
The input record matched to a business, individual or family type master file record and the new address was not provided to USPS. |
|
Box Closed No Order (BCNO) |
The Input record matched to a business, individual or family type master file record which contains an old address of PO BOX that has been closed without a forwarding address provided. |
|
Street Address with Secondary |
In the STANDARD mode utilizing Family matching logic the input record matched to a family record type on the master file with an old address that contained secondary information which obtained a ZIP+4 street level match. The input record does not contain secondary information. This address match situation requires individual name matching logic to obtain a match and individual names do not match. |
|
New 11-digit DPBC is Ambiguous |
The input record matched to a business, individual or family type master file record. The new address on the master file record could not be converted to a deliverable address because the DPBC represents more than one delivery point. |
|
Conflicting Directions: Middle Name Related |
There is more than one COA (individual or family type) record for the match algorithm and the middle names or initials on the COAs are different. Therefore, a single match result could not be determined. |
|
Other Conflicting Instructions |
The input record matched to two master file (business, individual or family type) records. The two records in the master file were compared and due to differences in the new addresses, a match could not be made. |
|
High-rise Default |
The input record matched to a family record on the master file from a High-rise address ZIP+4 coded to the building default. This address match situation requires individual name matching logic to obtain a match and individual names do not match. |
|
Rural Default |
The input record matched to a family record on the master file from a Rural Route or Highway Contract Route address ZIP+4 coded to the route default. This address situation requires individual name matching logic to obtain a match and individual names do not match. |
|
Insufficient COA Name for Match |
There is a master file (individual or family type) record with the same surname and address but there is insufficient name information on the master file record to produce a match using individual matching logic. |
|
Middle Name Test Failed |
The input record matched to an individual or family record on the master file with the same address and surname. However, a match cannot be made because the input name contains a conflict with the middle name or initials on the master file record. |
|
Gender Test Failed |
The input record matched to a master file (individual or family type) record. A match cannot be made because the gender of the name on the input record conflicts with the gender of the name on the master file record. |
|
New Address Would Not Convert |
The input record matched to a master file (business, individual or family type) record. The new address could not be converted to a deliverable address. |
|
Individual Name Insufficient |
There is a master file record with the same address and surname. A match cannot be made because the input record does not contain a first name or contains initials only. |
|
Secondary Number Discrepancy |
The input record matched to a street level individual or family type record. However, a match is prohibited based on I of the following reasons: 1) There is conflicting secondary information on the input and master file record; 2) the input record contained secondary information and matched to a family record that does not contain secondary information. In item 2, this address match situation requires individual name matching logic to obtain a COA match and individual names do not match. |
|
Other Insufficient Name |
The input record matched to an individual or family master file record. The input name is different or not sufficient enough to produce a match. |
|
General Delivery |
The input record matched to a family record on the master file from a General Delivery address. This address situation requires individual name matching logic to obtain a match and individual names do not match. |
|
New Address not ZIP + 4 coded or DPV confirmed. |
There is a change of address on file but the new address cannot be ZIP + 4 coded and therefore there is no 11-digit DPBC to store or return, the new address primary number cannot be confirmed on DPV or the new address is temporary. |
|
Conflicting Directions after re-chaining |
Multiple master file records were potential matches for the input record. The master file records contained different new addresses and a single match result could not be determined. |
|
Daily Delete |
The input record matched to a business, individual or family type master file record with an old address that is present in the daily delete file. The presence of an address in the daily delete file means that a COA with this address is pending deletion from the master file and that no mail may be forwarded from this address. |
|
ANKLink Primary Return Code |
Indicates that ANKlink has provided the move date, but not address, for a move that occurred between 19 and 48 months ago. |
|
Secondary Number dropped from COA |
The input record matched to a master file record. The master file record had a secondary number and the input address did not. Please Note: This return code is derived from Individual matching logic only. If this return code is achieved then no other matching attempts are permitted regardless of the PROCESSING mode. |
|
Secondary Number Dropped from input address |
The input record matched to a master file record, but the input address had a secondary number and the master file record did not. The record is a ZIP + 4 street level match. Please Note: This return code is derived from individual matching logic only. If this return code is achieved then no other matching attempts are permitted regardless of the PROCESSING mode. |
SE - Transmission Service Error |
||
|
Unexpected Error |
Your request could not be processed due to an unexpected error. Please retry your request. |
|
Record Number Mismatch |
Total Records numbers do not match with the records array. |
|
Month Range Exceeded |
Months to allow for NCOALink products ranges from 6 to 48. |
|
Records Array Error |
Records array is empty, un-allocated, or out of bounds. |
|
Requesting Record Range Exceeded |
Requesting records must in the range of 1 to 100. |
|
No Summary Reports |
Summary reports do not exist. |
|
ProcessingType Error |
ProcessingType is empty or incorrect type. |
|
FreqProcessing Range Exceeded |
ListOwnerFreqProcessing ranges from 1 to 52. |
|
ListName Character Limit |
OptSmartMoverListName cannot contain over 30 characters. |
|
ListName Invalid Character |
OptSmartMoverListName cannot contain any of the following characters \ / * : ? ” ” < > | or non-printing characters. |
|
Invalid Link |
Invalid link. |
|
License Key Error |
License Key is not valid or customer’s Paf is not on file. |
|
SmartMover Service Disabled |
Smart Mover Service package(s) is/are not enabled. Please contact your sales representative! |
|
Long JobID |
JobID cannot contain over 50 characters. |
|
JobID Invalid Character |
JobID cannot contain any of the following characters \ / * : ? ” ” < > |, non-printing characters or spaces. |
|
No JobID |
JobID required to open summary reports. |
|
Customer PAF Expired |
The Customer PAF is expired. |
|
Broker PAF Expired |
The Broker PAF is expired. |
|
NO PAFID Match |
The PAFID does not match. |
|
No PAFID |
The under broker customer required a PAFID. |
|
Unconfirmed PAFID |
The PAFID is unconfirmed. |
|
Empty XML |
Incorrect or empty XML/JSON structure. |
|
Empty Record Structure |
Incorrect or empty record structure. |
|
Incorrect Action |
The attempted action(s) was incorrect. |
Record Level Product Codes#
Code |
Description |
---|---|
Address Type US |
|
|
Firm or Company |
|
General Delivery |
|
Highrise or Business Complex |
|
PO Box |
|
Rural Route |
|
Street or Residential |
Code |
Short Description |
Long Description |
---|---|---|
Canada NCOA Move Status (NCOAMS) |
||
|
Moved Back |
COA Match - Moved back |
|
Deceased |
COA Match - Individual deceased. |
|
COA Match |
COA Match - A business, individual, or family. |
|
Recursive Match |
COA Match - Recursive - A business, individual, or family. |
|
Moved, No Address |
COA Match - Moved and left no address. |
|
No Name Match |
No COA match for name. |
|
Unidentified |
Address could not be identified. |
|
No Address Match |
No COA match for address. |
Code |
Description |
---|---|
Carrier Route Type |
|
|
PO Box |
|
City Delivery |
|
General Delivery |
|
Highway Contract |
|
Rural Route |
DPV Type |
|
|
Input address matched to the Zip+4 file. |
|
Input address not matched to the Zip+4 file. |
|
Input address matched to DPV (all components). |
|
Input address primary number (street number) matched to DPV but secondary number not matched. |
|
Input address primary number matched, secondary number not matched; secondary number required. |
|
Address was coded to a military address. |
|
Address was coded to a General Delivery address. |
|
Input address primary number matched to DPV but secondary number missing. |
|
Input address primary number missing. |
|
Input address primary number invalid. |
|
Identified PO Box Street Address. |
|
Input address PO, RR or HC box number missing. |
|
Input address PO, RR or HC box number invalid. |
|
Input address matched to CMRA. |
|
Input address matched to CMRA but secondary number not present. |
|
Addresses that are assigned to a phantom route of R777 or R779. |
|
Input address primary number matched by dropping trailing alpha. |
|
Address was coded to a unique Zip Code. |
Move Type |
|
|
Family |
|
Business |
|
Individual |
RBDI Address Type (RBDI) |
|
|
Residential |
|
Business |
|
Unknown |