Support 805.461.7300
Sales
Our Technology. Your Success.
Tech Notes

CASS Errno_ Field Error and Warning Codes

CASS Error and Warning Codes

This is a complete list of errors and warning codes that could be attached to a record when you validate it.  Even if a record is determined to be a good address, if any components of the address were altered or added, a warning code will be attached to the record.  If the record is undeliverable, an error code will be attached to the record.  These codes are filled into the field called Errno_.

  • Errors & Warnings Summary List

AccuZIP6 can detect forty different kinds of errors when checking an address.  A single address will often have multiple errors.  Each kind of error is identified by a number, as shown in the following list.

  • Error Summary List

Error group 1:  State not found

1.1 State not found

Error group 2:  City not found

2.1 City not found

Error group 3:  Street not found

3.1 Street not found

Error group 4:  Address not found

4.1 Address not found

Error group 5:  Can’t assign +4

5.1 Incomputable +4 range

5.2 +4 unavailable

Error group 6:  Multiple Matches

6.1 Multiple streets match

6.2 Multiple addresses match

6.3 Cardinal Rule multiple match

Error group 7:  Time/space error

7.1 Time ran out

7.2 Output too long

  • Warning Summary List

Warning group 8:  Company warning

8.1 Company phonetic match used

8.2 First company match used

Warning group 9:  State corrected

9.1 State determined from city

9.2 State determined from ZIP

Warning group 10:  City corrected

10.1 City phonetic match used

10.2 City determined from ZIP

10.3 Acceptable city name used

Warning group 11:  Street corrected

11.0 Address component Chg/Del/Add

11.1 Street phonetic match used

11.2 Pre-direction dropped

11.3 Pre-direction added

11.4 Suffix dropped

11.5 Suffix added

11.6 Post direction dropped

11.7 Post direction added

11.8 Pre-direction standardized

11.9 Street standardized

11.10 Suffix standardized

11.11 Post direction standardized

11.12 Street missing

11.13 Alternate address used

11.14 Address Standardized

11.15 Dual address-Used PO Box

11.16 Dual address-Used Non-PO Box

11.17 Street Alias match-Better delivery address exists

Warning group 12:  Unit/Box warning

12.1 Unit standardized

12.2 Unit missing

12.3 Unit not found

12.4 Unit unverified

12.5 Rural box not found

Warning group 13:  Leftovers found

13.1 Leftovers found

Warning group 14:  ZIP/Route warning

14.1 No ZIP Code Available

14.2 Incorrect ZIP Code was changed to correct ZIP

14.3 +4 changed

14.4 Route changed

14.5 +4 added

14.6 Route added

14.7 ZIP assigned for Multi-matched address

14.8 Unique ZIP match

14.9 Small town default match

Warning group 15:  Address Type warning

15.0 ZIP Code Changed

15.1 Highrise Default

15.2 Highrise Exact

15.3 Rural Route Default

15.4 Rural Route Exact

15.5 Early Warning System match.

15.6 LACSLink Conversion Match

15.7 SuiteLink Match - Suite Returned

15.8 SuiteLink Match - No Suite Returned

Warning A1 to A10: This indicates which Address block was used to code the record

  • Error and Warning Code Groups

Errors in groups 1 to 7 are serious enough to prevent AccuZIP6 from finding a ZIP+4 code for an address.  Errors in groups 8 to 14 are called warnings because they are not serious enough to prevent AccuZIP6 form finding a ZIP+4 code.

  • Error and Warning Codes in Detail

The following is a description of the AccuZIP6 error and warning messages in detail:

  • Error number 1.1:  State not found.  The input record state is not a valid two-character abbreviation.

  • Error number 2.1:  City not found.  The input record city is not in AccuZIP6’s list of cities for the input record state.

  • Error number 3.1:  Street not found.  The input record street is not in AccuZIP6’s list of streets for the input record city; usually caused by misspelled street names that AccuZIP6 can’t determine how to correctly spell.

  • Error number 4.1:  Address not found.  The input record has an address not found in AccuZIP6’s list of addresses for the input record street.  Caused by an out-of-range (including even/odd mismatched) house or apartment number.

  • Error number 5.1:  Uncomputable +4 range.  AccuZIP6 can’t compute the ZIP+4 code for the address because of non-numeric characters in the input record house number or in the LOW to HIGH or LO+4 to HI+4 fields of the database as shown in the address window.  AccuZIP6 will output the correct five-digit ZIP code.

  • Error number 5.2:  +4 unavailable.  As shown in the addresses window, a complete LO+4 add-on code is unavailable; usually because the database thinks this address is still an undeveloped lot.  AccuZIP6 will output the correct five-digit ZIP code.

  • Error number 6.1:  Multiple streets match.  The input record is ambiguous, because more than one street name in the database matches the input address, and there is not enough information to let AccuZIP6 choose between the multiple choices.  For example, if the database lists only and E MAIN ST and a W MAIN ST, then the input MAIN ST causes multiple matches.

  • Error number 6.2:  Multiple addresses match.  The ZIP+4 database is ambiguous, because more than one ZIP+4 database record matches the input address.  For example, if a street has an address record for houses numbered from 100 to 500, and another record for houses numbered from 300 to 600, then the address 400 is a multiple match to both records.

  • Error number 6.3:  Cardinal Rule Multiple Match.  The input record had a street name that was also the suffix.  For example, 100 Road Street would have the wrong suffix, and in that case, the address matching engine is not allowed to add the correct suffix.

  • Error number 7.1:  Time ran out.  The optional maximum time limit for processing this address was set too low.

  • Error number 7.2:  Output too long.  An output record (the length of all fields and field delimiters) exceeds 2000 characters.  Fields at the end of the record will be lost.

  • Warning number 8.1:  Company phonetic match used.  AccuZIP6 was able to match the input address in the ZIP+4 database that included a company name, but the input company name and the database company name only matched phonetically, not exactly.

  • Warning number 8.2:  First company match used.  There are multiple records in the ZIP+4 database at one address that match the company and address in the input record.  AccuZIP6 used the first of the multiple records to determine the ZIP+4 code.

  • Warning number 9.1:  State determined from city.  The input record state is not a valid two-character abbreviation, but AccuzIP6 could determine a valid state from the input record’s city name.

  • Warning number 9.2:  State determined from ZIP.  The input record state is not a valid two-character abbreviation, but AccuZIP6 could determine a valid state from the input record’s ZIP code.

  • Warning number 10.1:  City phonetic match used.  The input record city is not correct, but was matched to a phonetic equivalent city name by AccuZIP6.

  • Warning number 10.2:  City determined from ZIP.  The input record city is not correct, but AccuZIP6 could determine a valid city from the input record’s ZIP code.

  • Warning number 10.3:  Acceptable city name used.  The Postal Service does not consider that the input record city designation acceptable for addressing purposes.  AccuZIP6 has standardized the city to an allowable name.

  • Warning number 11.0:  Address component chg/del/add.  This warning indicates that at least one component of the input address was changed, deleted, or added.

  • Warning number 11.1:  Street phonetic match used.  The input record street is not correct, but was matched to a phonetic equivalent street name by AccuZIP6.  AccuZIP6 often has to ignore words in the original input address for standardization or matching purposes, so be sure to check the address leftovers output field to find what original data was left out of the final address.

  • Warning number 11.2:  Pre-direction dropped.  A street name like N MAIN ST was standardized to MAIN ST.

  • Warning number 11.3:  Pre-direction added.  A street name like MAIN ST was standardized to N MAIN ST.

  • Warning number 11.4:  Suffix dropped.  A street name like BROADWAY AVE was standardized to BROADWAY.

  • Warning number 11.5:  Suffix added.  A street name like MAIN was standardized to MAIN ST.

  • Warning number 11.6:  Post direction dropped.  A street name like MAIN ST N was standardized to MAIN ST.

  • Warning number 11.7:  Post direction added.  A street name like MAIN ST was standardized to MAIN ST N.

  • Warning number 11.8:  Pre-direction standardized.  A street name like NORTH MAIN ST  was standardized to  N MAIN ST.

  • Warning number 11.9:  Street standardized.  Non-directional, non-suffix words in a street name were standardized.  For example:  THIRD ST to 3RD ST, BOX TO PO BOX, RURAL RT TO RR.  Also occurs when an alternate street name is used in place of an alias.

  • Warning number 11.10:  Suffix standardized.  A street name like MAIN STREET was standardized to MAIN ST.

  • Warning number 11.11:  Postdirection standardized.  A street name like  MAIN ST NORTH was standardized to MAIN ST N.

  • Warning number 11.12:  Street missing.  The input record’s address field was empty.

  • Warning number 11.13:  Alternate address used.  The input record had both an address and an alternate address, and AccuzIP6 found the best match to the ZIP+4 database by using the alternate address.

  • Warning number 11.14:  Address standardized.  The input address was formatted in accordance to CASS standards, DMM A950.

  • Warning number 11.17:  Street Alias Match.  AccuZIP compares the input address to the USPS City/State product to determine if a better delivery address exists for the input record.

  • Warning number 12.1:  Unit standardized.  As address like 5 MAIN ST SUITE A was standardized to 5 MAIN ST STE A.

  • Warning number 12.2:  Unit missing.  The ZIP+4 database indicates that the address should have a unit like an apartment or suite, but none was specified in the input record.

  • Warning number 12.3:  Unit not found.  A unit such as an apartment or suite was specified in the input record, but not was found in the ZIP+4 database.

  • Warning number 12.4:  Unit unverified.  A unit such as an apartment of suite was specified in the input record, and the ZIP+4 database indicates units exist at the address, but there is insufficient detail in the database to verify the input unit as valid.

  • Warning number 12.5:  Rural box not found.  The input record includes a rural route box number not found in the ZIP+4 database.

  • Warning number 13.1:  Leftovers found.  The input record address contained words AccuZIP6 could not match to the ZIP+4 database.  These "leftovers" can be found in a field called Leftout_.  Leftovers are any words from the address that were not used.  This is useful for creating a "department" field for the second line of the address.

  • Warning number 14.1:  No ZIP Code Available.  Indicates that the address (exactly as submitted) is not in the city, state, or ZIP code provided.

  • Warning number 14.2:  ZIP changed.  The input record has a ZIP code, but the correct five-digit ZIP code for the address is different.

  • Warning number 14.3:  +4 changed.  The input record has a +4 code, but the correct +4 code for the address is different.

  • Warning number 14.4:  Route changed.  The input record has a carrier route number, but the correct carrier route number for the address is different.

  • Warning number 14.5:  +4 added.  The input record did not have a +4 code, and the correct +4 code for the address was added.

  • Warning number 14.6:  Route Added.  The input record did not have a carrier route number, and the correct carrier route number for the address was added.

  • Warning number 14.7:  ZIP assigned for multi-matched address.  The input address was considered a multiple streets match, e.g. warning number 6.1, but a correct 5-digit ZIP was added to the record to improve delivery.

  • Warning number 14.8:  Unique ZIP match.  Some entities are assigned an entire 5-digit ZIP code.  These ZIPs are flagged as "unique" in the USPS Database.  If a street match cannot be made but the City/ZIP indicate a unique ZIP match, then this correction code will be used.

  • Warning number 14.9:  Small town default match.  If the location indicated by the City/ZIP contains a single general delivery record and nothing else, then any input street may be assigned to the general delivery ZIP+4.  The input street is preserved.

  • Warning number 15.1:  High-rise Default.  The input address matched to a high-rise record in the USPS Database and a unit number was not provided in the input address.

  • Warning number 15.2:  High-rise Exact.  The input address matched to a high-rise record in the USPS database and the unit number matched exactly to one found in the USPS database.  

  • Warning number 15.3:  Rural Route Default.  The input address matched to a Rural Route record in the USPS database and a box number was not provided in the input address.

  • Warning number 15.4:  Rural Route Exact.  The input address matched to a Rural Route record in the USPS database and the box number matched exactly one found in the USPS database.

  • Warning number 15.5:  Early Warning System match.  The record matched to a record in the Early Warning System file.  A value of "W" means that this address was found in the USPS Early Warning System (EWS).  The EWS file includes addresses that will be added to the USPS ZIP+4 Code Master File in the coming months, such as housing developments and new construction.  EWS ensures that addresses not on the USPS Master File will not be eliminated, or coded inaccurately.

  • Warning number 15.6:  LACSLink Conversion Match.  The Input address matched a record in the LACS Conversion table and has been updated with a new address.

  • Warning number 15.7:  There was a SuiteLink match on the company and address fields for that record.  The suite value was returned.  In this case, the "Stelink_" field will be populated with an "A".

  • Warning number 15.8:  here was a Firm match on the company and address fields for that record, however the input record could not be matched to a record in the Master SuiteLink file. An Improved Business address could not be furnished.  In this case, the "Stelink_" will be populated with a "00".

  • Warning A1 to A10: This indicates which Address block was used to code the record.  The number after the A indicates which Address field contained the good address.  For example, if the database contained eight address fields and the good address was located in the Address5 field, then the Address5 information would be moved to the Address field and the Address info would be moved to the Address5 field and the result Warning code would be A5.  If the good address was found in the Company field, then the result would be A0, otherwise the result would be the number of the Address field matched.

« Back to Tech Notes

Vince [in support] took the time and spent about 2 hours on the phone with me as we walked through an issue and figured out the problem. To me he went above and beyond normal support and really thought outside the box to figure out the solution. Thank you again Vince for all your help.
M.K., Aurora, IL