Reviewing the NCOA or ANK Changes

After processing a job with NCOALink, there are several ways to identify the changes that were returned by the service.  The simplest method involves using the "Look In" and "Find" features from the List View.  For more information on querying the data, see Basic Searching and Advanced Searching.  For the purposes of this guide, we'll use the methods described in Basic Searching.

• From the Look In pull-down menu, select the matchflag_ field.

• Type the letter "M" into the Find text box.

This will display all records in the database that returned a valid move.  This selection of records only contains records that had a valid return, however.  There are other codes in the matchflag_ field that may be returned from NCOALink as well:

M - Moved
G - PO Box Closed
K - Moved, left no forwarding address
F - Moved to a Foreign Country

Other NCOALink Fields
 

FFAPPLIED_ - Contains the YYYYMMDD the record was processed and matched through NCOALink.
MOVETYPE_ - Contains the type of match:  I - Individual Match, F - Family Match, B - Business Name Match
MOVEDATE_ - The date the move was filed with the USPS, in YYYYMM format.
 

Nxi_ Field Descriptions
 

A - Matched record and a new address has been provided (NCOAlink 18Month Service code only)
New move indicator is provided in Movetype field under B (business),I (individual), or F (family).

00 - No Match (NCOAlink 18 month Service code only)

01 - Found COA: 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.

02 - Found COA: Moved Left No Address (MLNA) - The input record matched to a business, individual or family type master file record and the new address was not provided to USPS.

03 - Found COA: 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.

04 - Cannot match COA: 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.

05 - Found COA: 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.

06 - Cannot Match COA: 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.
 

07 - Cannot Match COA: Conflicting Directions: Gender Related -There is more than one COA (individual or family type) record for the match algorithm and the genders of the names on the COAs are different. Therefore, a single match result could not be determined.
 

08 - Cannot Match COA: 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.
 

09 - Cannot Match COA: 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.
 

10 - Cannot Match COA: 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.
 

11 - Cannot Match COA: Individual 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.
 

12 - Cannot Match COA: 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.
 

13 - Cannot Match COA: 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.
 

14 - Found COA: New Address Would Not Convert at Run Time - 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.
 

15 - Cannot Match COA: 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.
 

16 - Cannot Match COA: 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.
 

17 - Cannot Match COA: 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.
 

18 - Cannot Match COA: 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.
 

19 - Found COA: New Address not ZIP+4 coded - 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.
 

20 - Cannot Match COA: 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.
 

66 - 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.
 

91 - Found COA : 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. A new address was provided.
 

92 - Found COA : 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. A new address was provided.

Reviewing the ANKLink Returns

There are also returns that can be identified when using the ANKLink service.  Much like NCOALink, ANKLink queries the USPS' national change-of-address database.  Unlike NCOALink's 0-to-18 month window, ANKLink queries the 19-to-48 month time frame.  To query the ANKLink returns, perform the following steps:

• From the Look In pull-down menu, select Ank_.

• Type the number "77" into the Find text box.

That displays all records that ANKLink returned a match on.  There is only one value that will populate that field:

77 - The record was found in the 48 month ANKLink service.   You should suppress these records from your database or flag these records for deletion and not mail to them.