|
|
ListWare® Error and Information Codes
Address Error Codes
Code
| Definition
|
| C | Canadian Address
| L
| The field is too short to accommodate new data (length error).
| M
| The National Database found two or more ranges for your address (multiple
addresses).
| R
| The address is not within the delivery range (address out of range).
| | S | Either the input address is
missing a suite number, or it has an invalid one. | | T | Multiple Components. More than
one component of your address is in error. Address components are the
pre-direction, post-direction, and suffix.
| U
| No street exists within the city that matches the street name given in the
address field (unknown street).
| | W | EWS. This address has been
identified in the Early Warning System (EWS) data file, and should be
included in the next national database update.
| | X | Non-delivery Address. The
location given in the address field physically exists in the city but
the post office has indicated that there are no houses there. This may
occur when one side of the street has railroad tracks or a river along
side it.
| Z
| The ZIP Code is invalid or does not match the city name.
|
Area Code Update Codes
Code
| Definition
| A
| The area code does not exist in the database or the area code, prefix, or
suffix contains a character in the numeric pattern.
| B
| The phone number is blank.
| D
| This distance error indicates that the area code and ZIP locations are too far
apart as specified on the Phone Check Options screen.
| E
| The numerical phone number format is incorrect.
| F
| The field length for the chosen phone number format is incorrect.
| M
| This multiple match error indicates that there is a duplicate phone number.
| P
| The prefix does not exist in the database.
| Z
| The ZIP Code does not exist in the database.
|
Business Codes
|
Number of Employees Range
|
| Code |
Definition
| A
| 1000+
| B
| 500-999
|
D
|
50-99
|
E
|
20-49
| F
| 10-19 |
G
|
5-9
|
H
|
1-4
|
| J | 100-249
| | K | 250-499
|
Z
| NOT AVAILABLE |
|
Annual Sales Volume Range
|
| Code |
Definition
| A
| 1,000,000,000+
| B
| 500,000,000 -
999,999,999
|
C
|
100,000,000 - 499,999,999
|
| D |
10,000,000 - 99,999,999
| E
|
5,000,000 - 9,999,999
| F
| 2,500,000 - 4,999,999 |
G
|
1,000,000 - 2,499,999
|
H
|
500,000 - 999,999
| |
I | Under 500,000
|
Z
| NOT AVAILABLE |
|
Headquarters / Branch (Field Name: BusinessStatusCode)
|
| Code |
Definition
| 0
|
Single Location |
1
|
Headquarters
|
2
|
Branch |
Consumer Enhancement Codes
| Head
of Household Age Code (HOH_AGE) | Blanks
A
B
C
D
E
F
G
H
I
J
K
L
M |
18 - 24 (Inferred, Derived, or Reported)
25 - 29 (Inferred, Derived, or Reported)
30 - 34 (Inferred, Derived, or Reported)
35 - 39 (Inferred, Derived, or Reported)
40 - 44 (Inferred, Derived, or Reported)
45 - 49 (Inferred, Derived, or Reported)
50 - 54 (Inferred, Derived, or Reported)
55 - 59 (Inferred, Derived, or Reported)
60 - 64 (Inferred, Derived, or Reported)
65 Plus (Inferred or Reported)
65 - 69 (Inferred or Reported)
70 - 74 (Inferred or Reported)
75 Plus (Inferred or Reported) |
Selected
Household Member Age (in Years) (Name_Age)
The input name age | Household
Member Section Count (PERS_IN_HH)
Actual number in house hold 0 - 8 |
Number
Of Named (No_Adults)
Actual number of Adults 0 - 8 |
Number
Of Children (Pres_Child)
Actual number of Children 0 - 8 |
Length
Of Residence In Years (Len_Res)
Actual number of Years 0 - 43 |
Likelihood
Home Is Owned Or Rented (Own_Rent)
0 Reported Renter via Questionnaire Data
1 Most Likely Renter
2 Likely Renter
3 Likely Renter
4
5
6 Least Likely Renter
7 Likely Home Owner
8 Most Likely Home Owner
9 Reported Home Owner via Questionnaire Data |
Household Member 1 Marital Status Code (Mari_Stat)
blanks: Member is not Present
M: Married
S: Single
U: Unknown |
Family Income Detector Code (Income)
blanks
A:$0 - $10,000
B:$11,000 - $15,000
C:$16,000 - $20,000
D:$20,000 - $25,000
E:$26,000 - $30,000
F:$31,000 - $35,000
G:$36,000 - $40,000
H:$41,000 - $45,000
I:$46,000 - $50,000
J:$51,000 - $55,000
K $56,000 - $60000
L:$61,000 - $70,000
M:$71,000 - $80,000
N:$81,000 - $90,000
O:$91,000 - $100,000
P:$101,000 - $110,000
Q:$111,000 - $120,000
R:$121,000 - $130,000
S:$131,000 - $150,000
T:$141,000 - $150,000 |
Bank Card (Mastercard Or Visa) Holder (Bankcard)
No
Yes |
Address
Location Type (Dwell_Type)
blanks:
M: Multi - Family Dwelling Unit
S: Single - Family Dwelling Unit |
Delivery Drop (DEL_DROP)
Code
| Definition
| C
| Commercial Mail Box Company
| N
| Delivery Point is not a Drop
| Y
| Delivery Point is a Drop
|
Delivery Type (DEL_TYPE)
Code
| Definition
| A
| mail delivery to Residential
| I
| mail delivery to Business
| | N | Business Contract
Box -
A PO Box for a business customer who is
located in a contract unit.
|
DSF Type (DSF_TYPE)Code
| Definition
| F
| The matched record contains Firm data.
| G
| The matched record contains General Delivery data.
| H
| The matched record contains Highrise data.
| P
| The matched record contains PO Box data.
| R
| The matched record contains Rural Route or Contract Route data.
| S
| The matched record contains Street data.
|
Match Level Codes for D&B Appends
| Level 1 |
This level is based on a tight match of
address and company information.
|
| Level 2 |
This level is based on a tight match of
address information and a somewhat looser match of company name
elements. This level will capture matches where there are minor
variations or errors in the spelling of company name.
|
| Level 3 |
This level is based upon a very tight
company name match and a somewhat looser address match.
|
| Level 4 |
This level is based on a tight match of
address information, where the company information does not readily
match. This level will catch companies doing business under
differing names.
|
| Level 5 |
This level is based on close matches of
address and company information. In addition, some of these records
have also been flagged as having secondary address errors such as
missing or incorrect suite numbers. It may capture different
companies at the same address. |
Name Parse Codes
| Code |
Gender |
| M |
Male |
| F |
Female |
| N |
Neutral (Pat, Chris etc.) |
| U |
Unknown |
GeoCoding Error Codes
| Code |
Definition |
| Z |
Incomplete, incorrect, or missing
ZIP+4 Code. |
| N |
No data available for the ZIP+4 Code |
Mail Score
Code
| Definition
|
1 |
The address is accurate as it matches the Delivery Sequence File (DSF). This applies primarily to Address Correction services but NCOA updated addresses also match the DSF file. |
2 |
The address is seasonal and it matches the Delivery Sequence File (DSF). This only applies to Address Correction services. |
3 |
The address is accurate enough to match the ZIP+4 file. |
4 |
This address might be ZIP+4 coded but an existing secondary address problem could prevent mail delivery (NCOA processed records have a NIXIE code and are possible moves). |
5 |
The primary address has errors that prevent it from matching the Delivery Sequence File (DSF) and ZIP+4. |
6 |
The address is accurate as it matches the Delivery Sequence File (DSF), but it is undeliverable (these records are considered vacant). This only applies to Address Correction services. |
7 |
Serious problems prevent the address from matching the Delivery Sequence File (DSF) and ZIP+4.
Or Possible Canadian/Foreign Address, Record Not Processed |
NCOALink Codes
|
Move Type Codes
| | Code
| Definition
| I
|
Individual Moved, new address provided |
F
| Family
Moved, new address provided
| B
| Firm
Moved, new address provided
|
|
Return Codes
|
| Code |
Definition
| |
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. New
address not supplied.
| | 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. New address not supplied. |
|
Residential Phone Append Codes
| | Code
| Definition
|
A
| Phone number
is on the DMA's Do-Not-Call List |
B
| Phone
number is on the FTC's Do-Not-Call List |
C
|
Phone number is on both the DMA's FTC's
Do-Not-Call List | |
D |
State provides DNC list, but MelissaData does not currently have it | |
E |
Phone Number is on the DMA's Do-Not-Call List and State provides DNC
list, but MelissaData does not currently have it. | |
F |
Phone Number is on the FTC's Do-Not-Call List and State provides DNC
list, but MelissaData does not currently have it. | |
G |
Phone Number is on both the DMA and FTC's Do-Not-Call List and State
provides DNC list, but Melissa Data does not currently have it. | |
H |
Phone number is not on an available state DNC list | |
I |
Phone number is on The DMA’s Do Not Call list but Phone number is not on
an available state DNC list | |
J |
Phone number is on the FTC’s Do Not Call list but Phone number is not on
an available state DNC list | |
K |
Phone number is on both The DMA’s and the FTC’s Do Not Call lists but
Phone number is not on an available state DNC list | |
L |
Phone number is on a state DNC list | |
M |
Phone number is on The DMA’s Do Not Call list and Phone number is on a
state DNC list | |
N |
Phone number is on the FTC’s Do Not Call list and Phone number is on a
state DNC list | |
O |
Phone number is on both The DMA’s and the FTC’s Do Not Call lists and
Phone number is on a state DNC list | |
P |
This Phone number is not on the State, DMA, or FTC do not call list | |
|
|
|
|
|
|
|
