[um_loggedin]
Brief Description of U.S. Correction Codes
Code |
Definition |
| AA / A2 / A3 / A5 / A6 / A9 /AU / BB / CC
/ DD / D1 / D2 / EE / E1 / E2 /E3 / E4 / E5 / FF / F1 / G1 / II / I1/ HH / H1/ RR / S1 / S1 / S2 / S3 / UA / UB / UC / UD / U1 / X1 / Z0 |
Address Corrected / Valid |
| KK / Z1 / Z2 | Address Uncorrectable |
| A1 | No Zip + 4 match |
| A7 | Rejected due to EWS |
| A8 | Address not specified |
| AC | Multiple County’s defined |
| G4 | Street Number out of Range of alias street match. |
| JJ | Failed to Match last line of address |
| K1 | Missing / Incorrect street Directional(s) |
| K2 | Missing / Incorrect street suffix |
| MA / MC / M1 / M3 | Missing Street Number |
| MB | Street Name Not Found |
| MD | Firm Name not matched |
| NA / NB / NC / N1 / R1 | Missing / Incorrect Secondary Number |
| P1 / P2 / P3 / Q1 / Q2 | Missing / Incorrect RR/HC/PO Box Number |
Extended Description of Error Codes
| Code | Definition |
| AA | Record Matched to the ZIP+4 File This footnote is set any time that a record is matched. This is the equivalent of having a return code of 31 or 32. |
| A1 | Record Not Matched to the ZIP+4 File This footnote is set every time that a record does not match to the ZIP4 file, but makes it through basic parse and last line validation. This is the equivalent of having a return of 21 or 22. |
| A2 | Alias Street Name Matched This footnote is set every time a match is made to an alias street name. |
| A3 | Alternate Record Matched on the ZIP+4 File This footnote is set every time a match is made to an alternate ZIP4 record. An alternate record contains a different presentation a street name for a ‘base’ ZIP4 record. The addon code is the same for the alternate and the base record. |
| A4 |
Match to Small Town Default |
| A5 | Match to Unique ZIP Default A Unique ZIP code is a ZIP code set up by an institution (like a university) or a business that handles its own mail delivery. The USPS collects the mail at the post office, and the institution picks it up and distributes it internally. Even though it is possible to have ZIP4 records for Unique ZIP code, most institutions have addressing schemes that are not fully populated in the database. Therefore, when an input Unique ZIP code is found, and the input address is not found, a return code of ’31’ is given back, along with a ‘default’ addon of ‘0001’. |
| A6 | Match to a Highrise Default Alternate record This footnote is set when a Highrise Default Alternate style address match is made. This condition exists when an input address contains the secondary number (an apartment, suite, etc.) along with a building name. No primary number or street name is given. For example: 456 FEDERAL BUILDING The coder will take this address and turn it back into a street-style presentation. 123 MAIN ST STE 456 |
| A7 | Address rejected due to EWS See the chapter titled ‘EWS System’ for information on how EWS works. |
| A8 | Possible dual address detected This footnote is set when a ‘dual address’ may be present, such as: RR 3 BOX 123 456 MAIN ST Since there are 2 possible addresses available, the Coder will not choose which one to parse and return. This address construct results in a 21 return code. |
| A9 | DPV used to break ZIP4 multiple response In some cases when a multiple-response is found during ZIP4 address processing, the DPV engine can be used to break the tie. During this process, all the candidate records are queried against the DPV database. If one and only one record is found to have a positive DPV confirmation, then this record will be chosen for the match, and a single response code is given back from the address lookup process. This footnote is turned on under this condition. |
| AC | ZIP+4 Level county name is different than the ZIP Code level Note: This footnote will only be returned if the ZIP4_COUNTY parameter is specified in either the configuration file or the AC_OPEN_T structure. See the ‘Configuration File’ chapter for details on when this footnote is set. |
| AU | Unique ZIP default information returned. |
| BB | DPV match, all components. A DPV match was made using all the components of the address (primary and secondary number). |
| CC | DPV match primary number, not secondary number A DPV match was made with the primary number only. A secondary number was present on the input address, but was not used for DPV. |
| DD | Corrected City Name and/or State Information The city or the state was changed. |
| D1 | Input city name was non-mailing, corrected (AC) The input city name was a non-mailing name for the matched ZIP code. The output address contains the corrected city name. |
| D2 | ZIP+4 State code different than ZIP Code default This footnote indicates that the state code on a matched ZIP4 record differs from the state code assigned to the ZIP code of the output address. This can happen when a physical address exists in one state, but the mail is delivered to that address from another state. In some geographical situations, it is better for a post office in one state to deliver mail to addresses that are in a neighboring state. In these situations, the output address of the Coder will still show the state code of the delivering post office. The state code of the physical address will be shown in the matching ZIP4 record (the matched_rec field of the AC_OUTPUT_ADDR_T structure. |
| EE | Corrected Primary Address (E1 or E2 is on) The primary address line was corrected. |
| E1 | Corrected primary address component (AC) A directional or suffix address component was added, deleted, or changed. |
| E2 | Corrected primary street name (AC) Set if the street name spelling was changed. |
| E3 | Primary address line standardized (AC) Set if any portion of the primary address line was standardized. |
| E4 | A questionable address standardization was made. This can happen when an input address looks like 123 MAIN ST BOX 123 (a possible dual address), and it gets standardized to 123 MAIN ST # 123. |
| E5 | The first letter of the street name has been added or changed. |
| FF | Corrected Secondary Address Data Set when the secondary number or unit designator was changed. Examples of allowable secondary number changes are reversing alpha-numerics, and adding or deleting dashes: A5 => 5A A5 => A-5 |
| F1 | Military match A match was made to a ZIP Code that has been determined to be a Military ZIP Code. |
| G1 | General Delivery match A match was made to a General Delivery ZIP+4 record. |
| G4 | Out of range alias match A match was made to an alias street name, but the primary number did not match the allowable range for the alias street name. This is a ‘no-match’ condition and a return code of ’21’ is given back. |
| II | Firm and address swapped (AC) The firm line and the address line were swapped to make the match. |
| I1 | Urb moved from address line (AC) A PR Urbanization was found in the address line and moved to the Urbanization line. |
| HH | ZIP Code Changed The input ZIP code was changed. |
| H1 | ZIP code added (AC) No ZIP code was in the input address, and one was added. |
| JJ | Failure to Match Last Line of Address The last line was not able to be matched. This is equivalent to the return code ’11’. |
| KK | Multiple Match in Primary Address Field |
| K1 | Multiple Match due to Missing/Incorrect Directional(s) |
| K2 | Multiple Match due to Missing/Incorrect Suffix |
| MA | ZIP4 -Missing Street Number A primary number is missing from the input address. |
| MB | ZIP4 – Street Name Not Found The input street name could not be found in the ZIP+4 data file. |
| MC | ZIP4 – No Such Primary Number This is set when the input street name was found in the ZIP+4 file, but the input primary number could not be found with the given street name. |
| MD | ZIP4 – Firm Name Not Matched |
| M1 | DPV -Missing Street Number A primary number is missing from the input address. |
| M3 | DPV – No Such Primary Number This is set when DPV cannot validate the primary number, even though the address matched to a valid ZIP+4 range. |
| NA | ZIP4 -Missing Secondary Address Number A match was made to a ZIP+4 Highrise record, but no secondary number was present on the input address. |
| NB | ZIP4 – Secondary Number not found A match was made to a ZIP+4 record, but the input secondary number could not be found. |
| NC | Multiple Match in Secondary Address Field Set when a ‘multiple response’ condition occurs with highrise specific records, and one cannot be picked. The Coder returns the highrise default or street level record. For example: Input address is ‘123 MAIN ST # 4’ and both APT 4 and STE 4 are present. NOTE: This footnote used to be called L. |
| N1 | Missing Secondary Address Number for an Address located within a highrise For DPV, a match was made to a Highrise record, but the secondary number was not present on the input address. |
| P1 | Missing RR/HC Box Number for rural-route style addresses,
the BOX number was missing on input. |
| P2 | RR/HC Box Number not found Currently not being set. |
| P3 | Invalid RR/ HC/ PO BOX number. |
| Q1 | Missing PO Box Number |
| Q2 | PO Box Number not found |
| RR | DPV – CMRA match The CMRA flag was set in DPV. |
| R1 | DPV – CMRA, no secondary number |
| S1 | Seasonal record information present This footnote indicates that seasonal information is present. The seasonal information is in the ‘seasonal’ field of the AC_MATCH_INFO_T structure. Certain addresses receive mail only during part of the year. The ‘seasonal’ field contains a 12-character, NULL-terminated string indicating which months have mail delivery for the given output address. The field is a string of ‘Y’ and ‘N’ flags. Each of the 12 positions correspond to the 12 months of the year. A ‘Y’ value in a position indicates that the mail is delivered for that month. For example, the string ‘NNNNYYYYNNNN’ shows that mail is only delivered in the months ofMay, June, July, and August. |
| S2 | SUITE Link information added to the address. |
| S3 | Address matched to STOP Link. |
| UA | No PR Urbanization was given with the input address, but an Urbanization was found in the matched ZIP4 record. This Urbanization was returned on output. |
| UB | The input PR Urbanization was verified to be valid according to the ZIP4 record that was matched. |
| UC | The input PR Urbanization was not verified with the matched ZIP4 record, because the matched record contained a blank Urbanization field. The input Urbanization was retained in the output address. |
| UD | The input PR Urbanization was not verified with the matched ZIP4 record, because the matched record contained a different Urbanization name. The Urbanization from the matched ZIP4 record was returned with the output address. |
| U1 | Unique ZIP Code Match A match was made to a ZIP Code that has been determined to be a Unique ZIP Code. See footnote A5 for more information on Unique ZIP Codes. |
| X1 | IntelliZIP match This footnote indicates that a match was made using IntelliZIP logic. If a match is not made through normal address matching procedures, and if the input address contains a 9-digit ZIP code, then a reverse 9-digit lookup is performed. If the ZIP+4 record corresponding to the input 9-digit ZIP code closely matches the input address, then a match will be returned and this footnote will be set. |
| Z0 | ZIPMOVE match A match was made to a ZIP Move address. ZIP Move represents a collection of addresses that have been affected by a ZIP code realignment (i.e. the boundaries for a ZIP code were redrawn).When this happens, some street segments will move from one ZIP code to another. This can cause problems when an input address contains the ‘old’ ZIP code, and the address matching software tries to change the address to keep it in the old ZIP code instead of moving to a new ZIP code. To help out, the USPS keeps a separate file of these situations that are used by address matching software. This footnote is set when the input address contains the old ZIP code, and the Coder changed it to the new ZIP code. An exact match must be made to the address in order for this to happen. |
| Z1 | ZIPMOVE no match due to component change The best match available was to a ZIP Move address, but the input address was changed to get there. This is not allowed, so a no-match condition is made with a return code of ’21’. |
| Z2 | ZIPMOVE no match due to invalid new ZIP+4 This represents a data inconsistency with the USPS ZIP4 and ZIP Move files. The address was no-matched with a return code of ’21’ |
[/um_loggedin]
