Result Codes - SmartMover#
Record Level Result Codes#
Address Change#
Code |
Short Description |
Long Description |
|---|---|---|
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
Address Error#
Code |
Short Description |
Long Description |
|---|---|---|
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
Address Status#
Code |
Short Description |
Long Description |
|---|---|---|
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
SmartMover Match Status#
Code |
Short Description |
Long Description |
|---|---|---|
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
SmartMover Status#
NCOA Return Codes#
Code |
Short Description |
Long Description |
|---|---|---|
|
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. |
Transmission Service Error#
Code |
Short Description |
Long Description |
|---|---|---|
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
Record Level Product Codes#
Address Type US#
Code |
Description |
|---|---|
|
Firm or Company |
|
General Delivery |
|
Highrise or Business Complex |
|
PO Box |
|
Rural Route |
|
Street or Residential |
Canada NCOA Move Status#
Code |
Short Description |
Long Description |
|---|---|---|
|
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. |
Carrier Route Type#
Code |
Description |
|---|---|
|
PO Box |
|
City Delivery |
|
General Delivery |
|
Highway Contract |
|
Rural Route |
DPV Type#
Code |
Description |
|---|---|
|
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#
Code |
Description |
|---|---|
|
Family |
|
Business |
|
Individual |
RBDI Address Type#
Code |
Description |
|---|---|
|
Residential |
|
Business |
|
Unknown |