Match Codes
Match Codes indicate the portions of the address that matched or did not match to the
reference file. If a match could not be made, the Match Code begins with
"E
" and the remaining digits indicate why the address
did not match (see Match Codes for No Match - Definitions for "Ennn" return codes).
The digits do not specifically refer to which address elements did not match, but
rather why the address did not match. These fields are always included in the output
from AssignGeoTAXInfo.
Match Code Definitions
Response Element | Description |
---|---|
|
Same as |
Chh |
Street address did not match, but located a street segment based on the input ZIP Code or city. |
D00 |
Matched to a small town with P.O. Box or General Delivery only. |
Ghh |
Matched to an auxiliary file. |
Hhh |
House number was changed. |
Qhh |
Matched to USPS range records with unique ZIP Codes. CASS rules prohibit altering an input ZIP if it matches a unique ZIP Code value. |
Rhh |
Matched to a ranged address. |
Shh |
Matched to USPS data. This is considered the best address match,
because it matched directly against the USPS list of addresses.
S is returned for a small number of addresses
when the matched address has a blank ZIP + 4. |
Thh |
Matched to a street segment record. Street segment records do not contain ZIP Code information. If you enter a ZIP Code, the application returns the ZIP Code you entered. If the input city and state has only one ZIP Code, the application returns that ZIP Code. |
Uhh |
Matched to USPS data but cannot resolve the ZIP + 4 code without the firm name or other information. |
Xhhh |
Matched to an intersection of two streets, for
example, “Clay St & Michigan Ave.” The first hex digit refers to
the last line information, the second hex digit refers to the first
street in the intersection, and the third hex digit refers to the
second street in the intersection. Note: The USPS does not allow
intersections as a valid deliverable address
|
Yhhh |
Same as Xhhh , but an alias name record was used for
one or both streets. |
Z |
No address given, but verified the provided ZIP Code. |
Hex digit decoding
The table below contains the description of the hex digits for the Match Code values.
Code | In first hex position means: | In second and third hex position means: |
---|---|---|
|
No change in last line. |
No change in address line. |
|
ZIP Code changed. |
Street type changed. |
|
City changed. |
Predirectional changed. |
|
City and ZIP Code changed. |
Street type and predirectional changed. |
|
State changed. |
Postdirectional changed. |
|
State and ZIP Code changed. |
Street type and postdirectional changed. |
|
State and City changed. |
Predirectional and postdirectional changed. |
|
State, City, and ZIP Code changed. |
Street type, predirectional, and postdirectional changed. |
|
ZIP + 4 changed. |
Street name changed. |
|
ZIP and ZIP + 4 changed. |
Street name and street type changed. |
|
City and ZIP + 4 changed. |
Street name and predirectional changed. |
|
City, ZIP, and ZIP + 4 changed. |
Street name, street type, and predirectional changed. |
|
State and ZIP + 4 changed. |
Street name and postdirectional changed. |
|
State, ZIP, and ZIP + 4 changed. |
Street name, street type, and postdirectional changed. |
|
State, City, and ZIP + 4 changed. |
Street name, predirectional, and postdirectional changed. |
|
State, City, ZIP, and ZIP + 4 changed. |
Street name, street type, predirectional, and postdirectional changed. |
Match Codes for No Match - Definitions for "Ennn" return codes
The table below describes the values returned when the application cannot find a match or an error occurs.
Code | "nnn" values | Description |
---|---|---|
|
Indicates an error, or no match. This can occur when the address entered does not exist in the database, or the address is badly formed and cannot be parsed correctly. The last three digits of an error code indicate which parts of an address the application could not match to the database. |
|
|
No match made. |
|
|
Low level error. |
|
|
Could not find data file. |
|
|
Incorrect GSD file signature or version ID. |
|
|
No city and state or ZIP Code found. |
|
|
Input ZIP not in the directory. |
|
|
Input city not in the directory. |
|
|
Input city not unique in the directory. |
|
|
Out of licensed area. Only occurs if using Group 1 licensing technology. |
|
|
Record count is depleted and license has expired. |
|
|
No matching streets found in directory. |
|
|
No matching cross streets for an intersection match. |
|
|
No matching segments. |
|
|
Unresolved match. |
|
|
No matching segments. (Same as 022.) |
|
|
Too many possible cross streets for intersection matching. |
|
|
No address found when attempting a multiline match. |
|
|
Invalid directional attempted. |
|
|
Record also matched EWS data, therefore the application denied the match. |
|
|
No matching range, single street segment found. |
|
|
No matching range, multiple street segments found. |