AEC and AEC II User Guide OCTOBER 2006 AEC and AEC II User Guide Table of Contents The Importance Of Accurate Addresses In Your List 3 AEC Overview 3 AEC II Overview 4 AEC vs. CASS 5 AEC II vs. AEC 5 AEC / AEC II Fees and Payment 6 Requesting AEC/AEC II Processing 6 Electronic File Requirements 6 Cartridge File Requirements 7 CD File Requirements 7 Electronic Transmission Procedures 7 AEC Input File Layout 10 AEC II Processing Results 11 AEC and AEC II Elements Returned 11 File Format of Returned Records 13 AEC / AEC II Resolution Flag 15 AEC Record Type Codes 15 AEC DPV™ Confirmation Codes 15 AEC Return Codes 16 AEC Opinion Codes 18 AEC How Codes 19 Limitation of Liability 24 The Importance Of Accurate Addresses In Your List Cost-effective, consistent, and timely delivery of every mailpiece depends on its address. An accurate address contains only elements that are complete and correct. When you send mailpieces with accurate addresses, you are supporting the mutual goal of the USPS® (United States Postal Service®) and mailers to achieve the lowest combined cost for providing and receiving mail service. You also ensure that your mail is compatible with the USPS automation process putting it on the fast track for delivery. When a mailpiece is missing address elements or contains incorrect address elements, it requires additional handling, including manual processing. This can delay delivery or even make delivery impossible. Caption - USPS has determined up to twenty three percent of all mail contains addressing errors. Below are common errors making up this twenty three percent: Addressee moved 2.4% Directional/Suffix missing 6.0% Street Name/Number incorrect/invalid 5.9% ZIP Code/City incorrect 4.8% Apartment number, Rural Box number missing 4.5% Common Errors Total 23.6% Address Element Correction (AEC) is a quality process developed by the USPS with industry support. AEC focuses on inaccurate addresses, specifically those deliverable addresses that cannot be matched to a USPS ZIP+4® code using commercially available, CASS Certified® (Coding Accuracy Support System) address-matching software. If an address is missing an element, CASS Certified address-matching software may lack sufficient information to determine the correct or most accurate match to ZIP+4 product and, therefore, may not provide a ZIP+4 code. After an address goes through this process and is not resolved, it becomes a candidate for AEC. By correcting or providing missing elements, AEC turns problem addresses into accurate addresses or identifies them as potentially undeliverable. The result is a complete and standardized address that can be matched to a 5-digit ZIP Code® and ZIP+4 code. This greatly improves your efforts to have the mail reach your customers in a timely and consistent manner by allowing the corrected addresses to take full advantage of USPS automation. AEC Overview First, AEC separates each line of the address block into logical elements. Then, it determines if there is a complete address on a line or if the address is split between lines and processes the lines accordingly. Next, AEC determines whether the city, state, and 5-digit ZIP Code are valid and corrects them if they are not. It then uses specialized, USPS-controlled address element programs to perform a series of evaluations and comparisons. Unambiguous addresses are supplied with missing or corrected address elements, and these addresses are standardized and ZIP+4 coded, resulting in USPS automation-compatible records. AEC II Overview AEC II uses a program developed by the USPS to correct Change-of-Address orders submitted by customers. This program, known as eUARS (electronic Unresolved Address Resolution System) provides an electronic process for correcting address records. Records are transmitted to local delivery units to be resolved based on Delivery Force Knowledge. In a user-friendly interface, Delivery Unit personnel correct or identify undeliverable records. Unresolved AEC records are first matched against the encrypted secure hash algorithm AEC II Historical File. Records remaining unresolved after passing through the Historical File are separated into ZIP Code(s) and estimated turn-around times are calculated for resolution by Delivery Force Knowledge. Customers are notified via email of the estimated turn-around time for continued AEC II processing for each ZIP Code(s) where records are presented. If there are no records in one or more of the AEC Hold Queue(s) for the ZIP Code(s) submitted, AEC II processing begins immediately, and the AEC II order cannot be canceled. If records are in the AEC II Hold Queue(s) for all the ZIP Code(s) submitted, customers may elect to continue AEC II processing based on the estimated turn around time or cancel their entire order. Orders in the AEC II Hold Queue are cancelled if processing instructions are not received from customers within one (1) week of notification of the estimated turn around time for their order. Customers may select a processing window of 30, 60 or 90-days for their file. All records not resolved through the AEC II process, within the customer selected processing window, will be permanently deleted when processing is completed. The processing window begins when customer records are released into the eUARS program for resolution through Delivery Force Knowledge. * The USPS reserves the right to apply Delivery Force Knowledge to multiple address corrections/submissions reflecting identical name and address to eliminate and/or reduce redundancy and workload. * All customer provided names and addresses will be retained in clear text only during processing by the USPS. * Resolution of records includes confirmation of: * Address Corrected - The record submitted has been corrected and delivery point confirmed. (Codes Y, N, 1, 3) * Historical File Match - The record submitted has been corrected to one that was previously submitted and retained in the historical file. (Code 4) * PO Box Delivery Exclusion - The record submitted has been corrected or is a valid address but this customer does not receive their mail at the address presented. The USPS is only permitted to correct addresses presented and is not permitted to provide new address information to mailers. This includes valid street addresses where mail is delivered to a PO Box or a valid PO Box address where mail is delivered to the street address. (Code 5) * Address Uncorrectable (Not Recognized - Does Not Exist) - The record submitted can not be corrected to match any existing delivery point using Delivery Force Knowledge. (Code 2, 6) * Correct as Shown – Delivery point matches an existing delivery point and has delivery point confirmed. (Code 7) * Unique Occurrence – The address presented exists or has been corrected within a valid AMS ZIP+4 range identified as deliverable. However, the final delivery for this address is not through the US Postal Service. This may be a college dormitory room number type address or other similar scenario. (Code 8) * Unique ZIP Code – The ZIP Code for the address presented has been corrected to a Unique ZIP Code. (Code 9) AEC vs. CASS What can AEC do for addresses that commercially-available Coding Accuracy Support System (CASS) -certified software doesn’t do? * Expands certain initials to the full spelling of the words and standard and non-standard abbreviations to their full spelling * Contracts a full spelling to abbreviations or initials (if necessary) * Corrects misspellings, fractional primary number variations (e.g., 123 12 becomes 123 1/2), and road designator spellings (e.g., HGY becomes HIGHWAY) * Connects two components to form one or separates one component into two (when necessary) * Converts digits to alphabetic characters (e.g., 21 becomes twenty-one) or vice versa (e.g., twenty-one becomes 21), addresses to locatable addresses (e.g., Locatable Address Conversion (LACS)), and state names to abbreviations or names (e.g., VA becomes Virginia or Virginia becomes VA) * Standardizes school and firm name component spellings and overseas military addresses * Compresses or expands coordinate-type addresses (e.g., W 300 S 125 to W300S125) * Determines and codes unique ZIP Codes * Provides the correct city/state name when the names given do not match the ZIP Code or provides the correct ZIP Code when the one given does not match the city/state name * Properly processes comma- and period-delimited data within fields AEC programs use the ZIP+4 product and Delivery Point Validation (DPV), which are updated weekly to resolve addresses by using Computer Logic Resolution (CLR). CLR is a computer-based program that uses a variety of USPS programs and products to perform a series of evaluations and comparisons in an attempt to correct insufficient addresses. When address analysis yields an unambiguous address, the missing elements are provided and/or the incorrect address elements are corrected. The address is then standardized and ZIP+4 coded. Those addresses that cannot be resolved are flagged as potentially undeliverable. AEC focuses on the following addressing issues: * Incomplete address * Incorrect street name * Missing or incorrect directional * Missing or incorrect suffix * Incorrect city name * Incomplete building name * Rural-style addresses conversion to city-style addresses AEC does not: * Process foreign addresses * Produce missing secondary information * Handle driving directions (i.e. 5 miles south of mile marker 11) AEC II vs. AEC What can AEC II offer mailers that the AEC process can not? * The opportunity for human recognition of errors known about specific “bad” addresses. * The ability for letter carrier recognition of resident names associated with deliveries on their route. * The ability to identify the correct address in the case of multiple responses when provided with resident names. AEC / AEC II Fees and Payment All AEC and AEC II are prepaid services. Files received without payment will not be processed. AEC fees are based on the total number of records submitted. AEC processing fees are calculated per one thousand records and prorated for increments less than a complete thousand. A minimum fee for one thousand records is charged for all files containing less than one thousand records. AEC II processing fees are calculated on the number of resolved records returned to the customer. A minimum fee for one hundred records is charged for all files submitted. This minimum AEC II fee is in addition to the fees for AEC processing. Each resolved record over the first 100 resolved records will be charged the current established fee. AEC customers agree to make their initial payment and all subsequent payments through either a US Postal Service CAPS account or valid credit card. All fees for AEC II resolved records must be prepaid before updated address information is returned to the customer. Customers electing to cancel AEC II processing of their file receive only corrections provided through the AEC process, and will not receive corrections made through the AEC II Historical File. Records will be charged at the standard AEC rate per record submitted. Requesting AEC/AEC II Processing 1. Submit only original, non-foreign, deliverable addresses that could not be matched to a USPS ZIP+4 code using any commercially available CASS-certified address matching software program. 2. Do not submit packed or software-compressed data or records with comma-delimited fields. AEC can process comma- and period-delimited data within fields but cannot process records with delimited fields. 3. Files can contain up to 500,000 addresses per file for AEC Only processing. AEC II processing files may contain no more than 15,000 addresses and are limited to one file per business day. 4. Submit payment and a completed Processing Request to the NCSC. No files will be processed until a completed AEC Processing Request and payment are received by the NCSC. A completed AEC Processing Request and payment in the form of a credit card or CAPS account number must be faxed to 901-681-4409 before electronic files can be processed. 5. Submit addresses on CD-ROM, cartridge, or via electronic transmission. All AEC and AEC II are treated equally and processed on a first-in, first-out basis. Electronic transmission generally allows faster processing since it eliminates the mail in process. Note: You must use the USPS to ship the container. We reserve the right to reject shipments by any carrier other than the USPS. Electronic File Requirements Records within electronically submitted file(s) must be separated by carriage return/line feed, and the file name must be written on your AEC Processing Request. The file can not be a dbase, Access or Excel file. The file must be a flat non-indexed, text file. The file’s name must : 1. Begin with the three letters assigned by AEC following initial AEC registration for the service, (see Electronic Transmission Procedures) 2. Be followed by four numbers, reflecting the date the file was submitted, (ddmm), and 3. End with the file extension .TXT. For example, if your three AEC assigned characters are YYY and the 4 characters you chose were 0925, then YYY0925.TXT would be a valid file name. Files must be compressed with the PKZip compression utility and must include the .ZIP file extension. The first seven characters of the Zip file name must be the same as the first seven characters of the text file name, e.g., if your text file name is YYY0925.TXT, the Zip file name must be YYY0925.ZIP. When we post your processed file, the file name will be the same as the Zip file name with the addition of an “R” before the extension, e.g., YYY0925R.ZIP. Cartridge File Requirements Submit addresses written in ASCII or EBCDIC on a high or low-density cartridge. Each cartridge can contain only one file and no continuation records from another tape or cartridge. Please do not send more than one file per cartridge. All cartridges must be labeled. Do not submit a file having a block size that is not a multiple of its record size. CD File Requirements Submit addresses written in ASCII text form (fixed length, non comma-delimited). Electronic Transmission Procedures If you do not already have an account with us, please call the AEC Department at 1-800-238-3150 to set up a user ID and password to access your files through www.ribbs.usps.gov. 1. UPLOAD - Web Instructions a. Access https://ribbs.usps.gov/files/aec/customers/(your user ID) b. Enter your user name c. Enter your password or d. Select upload.cfm e. Enter the path and filename or click browse to find the correct file f. Select the file, Click open, then click upload file. 2. DOWNLOAD - Web Instructions a. Access https//.ribbs.usps.gov/files/aec/customers/(your user ID) b. Enter you user name c. Enter you password d. Select the zipped file to be downloaded, and double click on the filename e. Click the Save button f. Select the directory to save your file to and click Save. g. Download is complete AEC Input File Layout(FIXED-WIDTH LENGTHS) COLUMN HEADER1 FIELD NAME COLUMN HEADER2 START POSITION COLUMN HEADER3 END POSITION COLUMN HEADER4 LENGTH COLUMN HEADER5 REQUIRED FIELD COLUMN HEADER6 FIELD TYPE FIELD NAME1 NAME START POSITION 1 END POSITION 42 LENGTH 42 REQUIRED FIELD REQUIRED OR "OCCUPANT" FIELD TYPE A/N FIELD NAME2 COMPANY NAME START POSITION 43 END POSITION 108 LENGTH 66 REQUIRED FIELD REQUIRED FIELD TYPE A/N FIELD NAME3 ADDRESS LINE START POSITION 109 END POSITION 174 LENGTH 66 REQUIRED FIELD REQUIRED FIELD TYPE A/N FIELD NAME4 CITY START POSITION 175 END POSITION 202 LENGTH 28 REQUIRED FIELD REQUIRED FIELD TYPE A/N FIELD NAME5 STATE START POSITION 203 END POSITION 204 LENGTH 2 REQUIRED FIELD REQUIRED FIELD TYPE A/N FIELD NAME6 ZIP5 START POSITION 205 END POSITION 209 LENGTH 5 REQUIRED FIELD REQUIRED FIELD TYPE NUMERIC FIELD NAME7 ZIP4 START POSITION 210 END POSITION 213 LENGTH 4 REQUIRED FIELD OPTIONAL FIELD TYPE NUMERIC FIELD NAME8 URBANIZATION START POSITION 214 END POSITION 241 LENGTH 28 REQUIRED FIELD OPTIONAL FIELD TYPE A/N FIELD NAME9 KEY START POSITION 242 END POSITION 251 LENGTH 10 REQUIRED FIELD REQUIRED FIELD TYPE A/N FIELD NAME10 CR/LF START POSITION 252 END POSITION 253 LENGTH 2 REQUIRED FIELD REQUIRED FIELD TYPE TOTAL RECORD LENGTH 253 BYTES NOTE: ALL OPTIONAL FIELDS SHOULD BE LEFT BLANK IF NO DATA EXISTS. Field Definitions Name: Individual customer name (if available), “Occupant” or blank. Company Name: Company name (if available) or blank. Address Line: Address information (directionals, primary numbers, street names, suffixes, secondary information). Urbanization: Applies to Puerto Rican-style addresses only. Key: A customer supplied identification code or record id. Example COLUMN HEADER1 FIELD NAME COLUMN HEADER2 SAMPLE ADDRESS INFORMATION COLUMN HEADER3 LENGTH COLUMN HEADER4 REQUIRED FIELDS INDICATOR COLUMN HEADER5 FIELD TYPE FIELD NAME1 NAME SAMPLE ADDRESS INFORMATION JOHN Q PUBLIC LENGTH 42 REQUIRED FIELDS REQUIRED OR "OCCUPANT" FIELD TYPE A/N FIELD NAME2 COMPANY NAME SAMPLE ADDRESS INFORMATION PRIVATE INVESTIGATIONS INC LENGTH 66 REQUIRED FIELD REQUIRED FIELD TYPE A/N FIELD NAME3 ADDRESS LINE SAMPLE ADDRESS INFORMATION 233 W 110TH ST N LENGTH 66 REQUIRED FIELD REQUIRED FIELD TYPE A/N FIELD NAME4 CITY SAMPLE ADDRESS INFORMATION BIRMINGVILLE LENGTH 28 REQUIRED FIELD REQUIRED FIELD TYPE A/N FIELD NAME5 STATE SAMPLE ADDRESS INFORMATION MN LENGTH 2 REQUIRED FIELD REQUIRED FIELD TYPE A/N FIELD NAME6 ZIP5 SAMPLE ADDRESS INFORMATION 55501 LENGTH 5 REQUIRED FIELD REQUIRED FIELD TYPE NUMERIC FIELD NAME7 ZIP4 SAMPLE ADDRESS INFORMATION 4632 LENGTH 4 REQUIRED FIELD OPTIONAL FIELD TYPE NUMERIC FIELD NAME8 URBANIZATION SAMPLE ADDRESS INFORMATION [BLANK] LENGTH 28 REQUIRED FIELD OPTIONAL FIELD TYPE A/N FIELD NAME9 KEY SAMPLE ADDRESS INFORMATION PUBLICJQD5 LENGTH 10 REQUIRED FIELD REQUIRED FIELD TYPE A/N FIELD NAME10 CR/LF SAMPLE ADDRESS INFORMATION [INSERT CARRIAGE RETURN LINE FEED] LENGTH 2 REQUIRED FIELD REQUIRED FIELD TYPE AEC Processing Results After processing your addresses through AEC, the USPS’s National Customer Support Center will return the original address file in the same medium that you provided. (Note: We do not return cartridges unless otherwise instructed.) A summary data report that lists the number of addresses processed and elements corrected and a diagnostic report that lists information about the content of your original mailing file will be included with the return address file. The returned address file will contain: 1. The standardized delivery address and other data if resolved; if unresolved the data fields will be blank. > Delivery addresses returned are parsed into individual address elements; however, addresses with military, unique, or general delivery ZIP Codes will not be parsed because AEC does not produce or return standardized addresses for addresses having these types of ZIP Codes. > For rural routes, the term “RR #” will appear in the Street Name field, the word “Box” will appear in the Suffix field, and the box number will appear in the Primary Name field. > For PO box addresses, the words “PO Box” will appear in the Street Name field, and the box number will be listed in the Primary Number field. > Elements for all other addresses will be entered into the field reflected in Returned Record table. 2. The original, unaltered record as submitted. Note: All returned files will be compressed. AEC II Processing Results Customers will be provided with access to a secured customer folder on the USPS RIBBS website. Resolved records will be placed in the customer folder weekly. All fees for AEC II resolved records must be pre-paid before updated address information is returned to the customer. Customers may access and download their resolved records at their convenience. Files will remain in the customer folder for 60 days. AEC and AEC II Elements Returned In AEC, when an address is resolved, the following is returned in positions 1 through 336: AEC Assigned Customer Number (byte 1) AEC Assigned Sequence Number (byte 6) Resolution Flag (byte 13) Standardized Firm Name if the match is made using the firm name in the address (byte 14) Standardized Delivery Address (byte 54) Standardized City spelling (byte 104) Standardized State two-character abbreviation (byte 132) 9-digit ZIP Code (byte 134) Delivery Point Code (DPC) (byte 143) Check Digit for 9-Digit Zip Code and the Delivery Point Code (byte 145) Carrier Route ID (byte 146) Record Type Code (byte 150) Puerto Rican Urbanization Name if the address is Puerto Rican and ZIP+4 product contains an urbanization name (byte 151) Standardized Address DPV Confirmation Code (byte 193) Customer Original Data (unaltered) (byte 451) If resolved: Parsed Standardized Address if Resolved records will be parsed into specific components, i.e., pre-directional, street name, suffix, post-directional, secondary unit designator, and secondary number (if applicable), beginning in byte 337 through 444. How Code Resolution Flag describes which specific elements were changed in the input delivery address to make a match to ZIP+4 product (byte 445) If unresolved: When an address cannot be resolved, it is parsed and returned in a nine-item table beginning in byte 337 thru 444. Each item contains the following: * The first ten characters of each unresolved component. If the component is longer than ten characters, the rightmost characters are lost * A code identifying what the component was interpreted as and whether or not it matched ZIP+4 product (see Unresolved Return Codes) * A code that offers an opinion as to why the address could not be matched to ZIP+4 product is also returned. File Format of Returned Records FIELD REF NO 1 FIELD CONTENTS AEC ASSIGNED CUSTOMER NUMBER LOGICAL LENGTH 5 RELATIVE POSITION FROM/THRU 01-05 CONTENT NOTES FIELD REF NO 2 FIELD CONTENTS AEC ASSIGNED SEQUENCE NUMBER LOGICAL LENGTH 7 RELATIVE POSITION FROM/THRU 06-12 CONTENT NOTES SEE RESOLUTION FLAGS FIELD REF NO 3 FIELD CONTENTS RESOLUTION FLAG LOGICAL LENGTH 1 RELATIVE POSITION FROM/THRU 13-13 CONTENT NOTES FIELD REF NO 4 FIELD CONTENTS STANDARDIZED FIRM NAME LOGICAL LENGTH 40 RELATIVE POSITION FROM/THRU 14-53 CONTENT NOTES FIELD REF NO 5 FIELD CONTENTS STANDARDIZED DELIVERY ADDRESS LOGICAL LENGTH 50 RELATIVE POSITION FROM/THRU 54-103 CONTENT NOTES FIELD REF NO 6 FIELD CONTENTS STANDARDIZED CITY LOGICAL LENGTH 28 RELATIVE POSITION FROM/THRU 104-131 CONTENT NOTES FIELD REF NO 7 FIELD CONTENTS STANDARDIZED STATE LOGICAL LENGTH 2 RELATIVE POSITION FROM/THRU 132-133 CONTENT NOTES FIELD REF NO 8 FIELD CONTENTS 9 DIGIT ZIP CODE LOGICAL LENGTH 9 RELATIVE POSITION FROM/THRU 134-142 CONTENT NOTES FIELD REF NO 9 FIELD CONTENTS DELIVERY POINT CODE (DPC) LOGICAL LENGTH 2 RELATIVE POSITION FROM/THRU 143-144 CONTENT NOTES FIELD REF NO 10 FIELD CONTENTS CHECK DIGIT FOR 9-DIGIT ZIP CODE AND DPC LOGICAL LENGTH 1 RELATIVE POSITION FROM/THRU 145-145 CONTENT NOTES FIELD REF NO 11 FIELD CONTENTS CARRIER ROUTE ID LOGICAL LENGTH 4 RELATIVE POSITION FROM/THRU 146-149 CONTENT NOTES FIELD REF NO 12 FIELD CONTENTS RECORD TYPE CODE LOGICAL LENGTH 1 RELATIVE POSITION FROM/THRU 150-150 CONTENT NOTES SEE RECORD TYPE CODES FIELD REF NO 13 FIELD CONTENTS PUERTO RICAN URBANIZATION NAME LOGICAL LENGTH 28 RELATIVE POSITION FROM/THRU 151-178 CONTENT NOTES FIELD REF NO 14 FIELD CONTENTS FILLER LOGICAL LENGTH 14 RELATIVE POSITION FROM/THRU 179-192 CONTENT NOTES FIELD REF NO 15 FIELD CONTENTS STANDARDIZED ADDRESS DPV CONFIRMATION CODE LOGICAL LENGTH 2 RELATIVE POSITION FROM/THRU 193-194 CONTENT NOTES SEE DPV CONFIRMAION CODES FIELD REF NO 16 FIELD CONTENTS FILLER LOGICAL LENGTH 142 RELATIVE POSITION FROM/THRU 195-336 CONTENT NOTES FIELD REF NO 17 FIELD CONTENTS PARSED ADDRESS INFORMATION LOGICAL LENGTH 108 RELATIVE POSITION FROM/THRU 337-444 CONTENT NOTES These 108 bytes will contain EITHER the Parsed Standardized Address if Resolved OR the Parsed Original Address if Unresolved FIELD REF NO 18 FIELD CONTENTS HOW CODE RESOLUTION FLAG LOGICAL LENGTH 2 RELATIVE POSITION FROM/THRU 445-446 CONTENT NOTES SEE HOW CODES FIELD REF NO 19 FIELD CONTENTS FILLER LOGICAL LENGTH 4 RELATIVE POSITION FROM/THRU 447-450 CONTENT NOTES FIELD REF NO 20 FIELD CONTENTS CUSTOMER ORIGINAL DATA (UNALTERED) LOGICAL LENGTH 450 RELATIVE POSITION FROM/THRU 451-900 CONTENT NOTES IF RESOLVED 108 BYTES Primary Number 10 337-346 Pre-directional 2 347-348 Street Name 28 349-376 Suffix 4 377-380 Post-directional 2 381-382 Secondary Designator 4 383-386 Secondary Number 8 387-394 Filler 50 395-444 IF UNRESOLVED 108 BYTES See Unresolved Return Codes Unresolved Component 1 10 336-346 Unresolved Return Code 1 1 347-347 Unresolved Component 2 10 348-357 Unresolved Return Code 2 1 358-358 Unresolved Component 3 10 359-368 Unresolved Return Code 3 1 369-369 Unresolved Component 4 10 370-379 Unresolved Return Code 4 1 380-380 Unresolved Component 5 10 381-390 Unresolved Return Code 5 1 391-391 Unresolved Component 6 10 392-401 Unresolved Return Code 6 1 402-402 Unresolved Component 7 10 403-412 Unresolved Return Code 7 1 413-413 Unresolved Component 8 10 414-423 Unresolved Return Code 8 1 424-424 Unresolved Component 9 10 425-434 Unresolved Return Code 9 1 435-435 Unresolved City Flag 1 436-436 Unresolved State Flag 1 437-437 Unresolved ZIP5 Flag 1 438-438 Unresolved Opinion code 2 439-440 Filler 4 441-444   AEC/AEC II Resolution Flags Code Description Y Address matched USPS ZIP+4 engine (AEC) N Address has not been resolved to a specific delivery point (AEC) 1 Address resolved to a highrise or rural route default (AEC) 2 *Address has not been resolved due to an invalid format (AEC II) 3 Address corrected (AEC II) 4 *Historical file match (AEC II) 5 *PO Box delivery exclusion (AEC II) 6 Address uncorrectable (not recognized) (AEC II) 7 *Correct as shown (AEC II) 8 Unique Occurrence (AEC II) 9 Unique ZIP Code (AEC II) 0 Invalid ZIP Code (AEC II) H *Corrected to highrise default (AEC II) M *APO/FPO Military Post Office (AEC II) U *Unique Occurance – correct as presented (AEC II) RESOLUTION FLAG DESCRIPTION (BYTE 13 IN RETURN REC) *INDICATES NO CHARGE FOR THIS RETURN CODE AEC Record Type Codes Code Record Type F Firm G General H Highrise > Highrise Default M Military P PO Box R Rural/Highway Contract Route S Street U Unique L LACs < Rural/Highway Contract Route Defaults AEC DPV™ Confirmation Codes Code DPV™ Confirmation SS Exact Match P1 Secondary Address Invalid P2 Secondary Address Missing AEC Return Codes The following unresolved return codes represent a fairly accurate analysis of the individual address elements. The codes listed below are in the following positions of the unresolved components: #1 - Byte 347 for one byte #2 - Byte 358 for one byte #3 - Byte 369 for one byte #4 - Byte 380 for one byte #5 - Byte 391 for one byte #6 - Byte 402 for one byte #7 - Byte 413 for one byte #8 - Byte 424 for one byte #9 - Byte 435 for one byte Code Description A This component, which was interpreted as part of the street name, matched to one of the following in ZIP+4 product: 1. Exact match to a street name component. 2. Abbreviation match type 1 (e.g., JACK to JACKSON) 3. Abbreviation match type 2 (e.g., LNCLN to LINCOLN) 4. Spelling correction (e.g., CARLINGTON to ARLINGTON) 5. Matched to two words (e.g., KNOLLCREST to KNOLL CREST) 6. This component plus the adjacent component matched to one component in ZIP+4 product (e.g., KNOLL CREST to KNOLLCREST) 7. Matched to a suffix in ZIP+4 product (e.g., SQUARE to SQ) 8. Matched to a directional in ZIP+4 product (e.g., SOUTHWEST to SW) B This component, interpreted as a pre-directional, matched to one of the following in ZIP + 4 Product (there must also be a street name match): 1. Pre-directional to pre-directional (e.g., N MAIN ST to N MAIN ST) 2. Pre-directional to post-directional (e.g., N MAIN ST to MAIN ST N) 3. Pre-directional to street name (e.g., NORTH HAMPTON ST TO NORTHHAMPTON ST or N HAMPTON ST to NORTHHAMPTON ST) C This component, interpreted as a post-directional, matched to one of the following in ZIP + 4 Product (there must also be a street name match): 1. Post-directional to post-directional (e.g., MAIN ST N to MAIN ST N) 2. Post-directional to pre-directional (e.g., MAIN ST N to N MAIN ST) 3. Post-directional to street name (e.g., BAY NORTH to BAYNORTH or BAY N to BAYNORTH) D This component, interpreted as a suffix, matched to one of the following in ZIP+4 Product (there must also be a street name match): 1. Suffix to suffix (e.g., MAIN ST to MAIN ST) 2. Suffix to street name (e.g., HERO BLVD to HERO BOULEVARD) E This component, interpreted as a road number, matched to a road number in ZIP+4 Product (e.g., 123 RT 75 to 123 US HIGHWAY 75) F This component was interpreted as a part of a PO box address. 1 This component was interpreted as the PO box number in a PO box address. G This component was interpreted as the box number in a highway contract (HC), rural route (RR), or military address. H This component was interpreted as the box element of an HC, RR, or military address. I This component was interpreted as the HC, RR, PSC, CMR, or unit element of an HC, RR, or military address. J This component was interpreted as the route number in an HC, RR, or military address. K This component immediately follows what was interpreted as the primary number and contains digits. Possible fragmented primary number or misplaced secondary number. L This component, which was interpreted as part of the street name, did not match any component in any ZIP+4 record to which a match was attempted. M This component, which was interpreted as a suffix, did not match any component of any ZIP+4 record to which a match was attempted. N This component, which was interpreted as a pre-directional, did not match any component of any ZIP+4 record to which a match was attempted. O This component, which was interpreted as a post-directional, did not match any component of any ZIP+4 record to which a match was attempted. P This component, which was interpreted as a road designator, did not match any component of any ZIP+4 record to which a match was attempted. Q This component, which was interpreted as a secondary designator, did not match any component of any ZIP+4 record to which a match was attempted. R This component, which was interpreted as a secondary number, did not match any component of any ZIP+4 record to which a match was attempted. S This component, which was interpreted as the primary number, did not match any range of numbers in any ZIP+4 record to which a match was attempted. T This component, which was interpreted as a PO box number, did not match any PO box number range in any ZIP+4 record to which a match was attempted. U This component, which was interpreted as a road number, did not match any component of any ZIP+4 record to which a match was attempted. V This component, which was interpreted as a Puerto Rican urbanization code, did not match any urbanization code of any ZIP+4 record to which a match was attempted. W This component was interpreted as part of a firm name. X This component was interpreted as part of a school name. Y This component was interpreted as part of a building name. Z This component could not be defined. AEC Opinion Codes These codes offer the most accurate indication as to why the address did not match ZIP+4 product (byte 439 for two bytes). Code Description PA The post office matching the 5-digit ZIP Code only has PO Box and General Delivery. PB Matching the address to ZIP+4 product produced a multiple response that could not be resolved. PC The address matched to the ZIP+4 product but appears in more than one urbanization code. We could not determine the correct address based on the address given. PD The address matched to the ZIP+4 product but is a non-delivery point. The 4-digit add -on returns “ND.” PE Some parts of the address matched some parts of one or more addresses in the ZIP+4 Product but none of the ZIP+4 addresses coded using what was interpreted as the primary number. PF No element of the street name matched any street name in the ZIP+4 product. PG All components of the input address matched exact components in the ZIP+4 product except what was interpreted as the primary number. PH The PO Box address given does not match any in the ZIP+4 product. PI The rural route or military address given does not match any in the ZIP+4 product. PJ The address contains no digits. PK The city/state/ZIP Code are invalid. PL No opinion could be formed from the data in the address. PM Address does not match the ZIP+4 file and has been identified as a foreign address. AEC How Codes These codes provide a fairly accurate description of what was done to the address to enable a match to ZIP+4 product. The address is parsed into individual components before a match to ZIP+4 product is attempted, and identification of the individual components is attempted. The address is then submitted unaltered to the USPS Coding Accuracy Support System (CASS) -certified address-matching engine. If it does not match, the actions described in the codes below produced a match to ZIP+4 product (byte 445 for two bytes). Code Description A No changes were made to the address to produce a match to ZIP+4 product, because our files were more current than those of the CASS-certified address-matching engine through which you passed the addresses before sending them to AEC, or a problem exists with the CASS-certified address-matching engine through which the addresses were passed. D Compressed dash (–) from a Puerto Rican primary number. E Inserted dash (–) in a Puerto Rican primary number. F Fabricated the primary number in a Puerto Rican address from fragments found. H Added secondary designator and secondary number from an address line other than the delivery address line. I Remove dash (-) from Puerto Rican PO box or rural route address. J Removed undefined data to the left of the Puerto Rican address. K Compressed a coordinate-type address (W 300 S 125 to W300S125). L Reversed a coordinate-type address (W300S125 to S125W300). M Expanded a coordinate-type address (W300S125 to W 300 S 125). N Converted an Illinois-type address (0W125 to 0W125). O Converted an abbreviation to a full spelling. P Joined secondary address to delivery address to form the address matched to ZIP+4 Product. Q Joined delivery address to secondary address to form the address matched to ZIP+4 Product. R Converted alphabetic to numeric look-alikes in the primary number (e.g., b to 8, o to zero, etc.) S Combined adjacent numbers to form the primary number. T Removed “#” symbol attached to the left of primary number. U Converted primary number fractions (e.g., 12312 to 123 1/2, 1231 2 to 123 1/2, 123 12 to 123 1/ 2). V Moved secondary number to the right of address (e.g., 123 45 MAIN ST to 123 MAIN ST # 45). W Converted joined alpha/numeric to numeric/alpha (e.g., M123 to 123M). X Removed ordinal abbreviation (i.e., “st” “nd” “rd” “th”) from primary number (e.g., 123rd MAIN ST to 123 MAIN ST). Y Separated possible secondary number from primary number (e.g., 1234 to 123 4). Z Separated primary number and street name (e.g., 123MAIN to 123 MAIN). 0 Converted numbers separated by a dash (–) (e.g., 123-456 to 123 456). 1 Combined primary number and adjacent single alpha character (e.g., 123 A to 123A). 2 Separated pre-directional from street name (e.g., SMAIN to S MAIN). 3 Rearranged misplaced components (e.g., MAIN 123 ST to 123 MAIN ST). 4 Separated numeric street name from primary number (e.g., 123-7 MILE RD to 123 7 MILE RD). 5 Connected single alpha character immediately preceding what was interpreted as the street name (e.g., A SPEN to ASPEN). 6 Separated single alpha character from what was interpreted as the street name (e.g., JMAIN to J MAIN). 7 Connected apparent primary number and the single number immediately to its right (e.g., 123 4 to 1234). 8 Separated and attached to the primary number a single number from the apparent street name (e.g., 123 4MAIN to 1234 MAIN). 9 Combined possible secondary number with apparent primary number to form the primary number (e.g., 123 MAIN ST 45 to 45-123 MAIN ST). ! Combined possible primary number with apparent secondary number to form the primary number (e.g., 123 MAIN ST 45 to 123-45 MAIN ST). @ Separated pre-directional “S” from the primary number (e.g., 123S to 123 S) or separated “5” from the primary number and convert it to its alpha look alike “S” (e.g., 1235 to 123 S). # Reversed the apparent primary and secondary numbers (e.g., 123 MAIN ST 45 to 45 MAIN ST 123). $ Separated the possible secondary number from the address and moved it to the right of the address (e.g., 123A MAIN ST to 123 MAIN ST A). % Removed alpha character from the right of the primary address (e.g., 123A MAIN ST to 123 MAIN ST). & Converted alpha/numeric look-alikes in the primary number (e.g., IZSGB to 12568). ( Converted numeric/alpha look-alikes in street name (e.g., 12568 to IZSGB). - Converted last digit of apparent primary number to its alphabetic equivalent (1236 FLAGS ST to 123 SIX FLAGS ST). _ Removed alpha from the box number in PO box or rural route addresses (e.g., PO BOX 123CLYDE to PO BOX 123). + Standardized a rural route address (e.g., RT1 BOX 123 to RR 1 BOX 123 or 123 MAIN ST RR 1 BOX 123 to RR 1 BOX 123). \ Expanded the PO box number to 5-digits using the last two digits of the 5-digit ZIP Code with zeros as filler (e.g., PO BOX 1 to PO BOX 85001 where the ZIP Code is 12385). : Expanded the PO box number to six digits using the last two digits of the 5-digit ZIP Code and zeros as filler (e.g., PO BOX 1 to PO BOX 850001 where the ZIP Code is 12385). “ Rearranged a PO box address (e.g., 12 PO BOX to PO BOX 12). < Converted addresses like HWY 45 & 37 to HWY 45/37, HWY 45.37 to HWY 45/37, HWY 45.37 to HWY 45-37, etc. > In an address containing a road designator and road number (such as Highway, County Road, etc.) tried different highway designators. If only one matched ZIP+4 product, resolved it (e.g., 123 HWY 61 to 123 HIGHWAY 61; 123 HWY 61 to 123 US HIGHWAY 61; 123 HWY 61 to 123 COUNTY ROAD 61; 123 HWY 61 to 123 STATE ROUTE 61). , If an address contained an apparent primary number as the first component of the address and the last two components were both numeric, combined the longer of the two with the primary number (e.g., 123 HWY 61 567 to 123 567 HWY 61). AA Corrected misspellings of “highway” (e.g., HGY to HWY, HIGHWAY). AC For Texas addresses, changed FM to FARM MARKET. AD Converted abbreviations RR, RD, RT in a highway address to HIGHWAY. AE Converted abbreviations RR, RD, RT in a highway address to COUNTY. AF Separated US designator from the highway number (e.g., US12 to US 12). AG Rearranged misplaced highway designator and highway number (123 HIGHWAY to HIGHWAY 123). AH Corrected school abbreviations to full spellings (e.g., SCH to SCHOOL, UNIVER to UNIVERSITY, etc.). AK Removed secondary address on a school-name only address (e.g., NEW YORK UNIVERSITY, PROFESSOR CLYDE BARROW to NEW YORK UNIVERSITY). AL On an indicated multiple response in which the number of responses was only one, resolved the address. AM Removed the delivery address when a school name is in the Secondary Address field (same as AK above in reverse). AN Separated suffix and secondary designator (e.g., BLVDSTE 12 to BLVD STE 12). AO Combined two adjacent street name elements into one name (e.g., VALLEY VIEW to VALLEYVIEW). AP Separated post-directional from last street name element (e.g., MAINSOUTH to MAIN S or MAIN SOUTH). AQ Removed dashes (-) , slashes (/) , and periods (.) from the address. AR The delivery address line had a suffix, and an unsuccessful attempt has been made to match the address on that line to ZIP+4 product. The secondary address also contained a suffix, and the attempt to match to ZIP+4 product using only the secondary address resolved it. AS An unsuccessful attempt to match to ZIP+4 product with an address line containing a pound sign (#) had been made by removing the pound sign. AT Moved an embedded suffix to the right address (123 ST MAIN to 123 MAIN ST). AU Connected the apparent last piece of the street name and the apparent post-directional (e.g., 123 DUE SOUTH to 123 DUESOUTH). AV Separated suffix from the last piece of the street name (e.g., 123 MAINST to 123 MAIN ST). AW Converted a directional abbreviation to its full spelling (e.g., 123 W BEND to 123 WESTBEND). AX Corrected non-standard abbreviations to their correct full spellings (e.g., CTH to COUNTY ROAD, COUNTY ROUTE, etc.). AY Separated a pre-directional from the first element of a street name (e.g., NORTHHAMPTON to N HAMPTON). AZ Converted divided numbers to equivalents (e.g., HWY 22.5 to 22/5, 22-5 etc.). BC Rearranged address components (e.g., 123 RED ST BUD to 123 RED BUD ST). BD Converted US to United States. BE Added HIGHWAY after US in an address in which it was not present. BF Separated secondary unit designator from the secondary number (e.g., APT12 to APT 12). BG Converted firm name abbreviations to the full spellings. BH The address produced a multiple response and was resolved using DPV confirmation (or the urbanization code in Puerto Rican address). BI Standardized a PO box address (e.g., POBOX 123 to PO BOX 123, PO BX 123 to PO BOX 123, etc.). BJ Removed elements to the right of the suffix because the elements were not a secondary designator or secondary number (e.g., 6060 PRIMACY PKWY LAKECREST CENTER). BK Removed elements to the left of the primary number (C/O ACLU 123 MAIN ST to 123 MAIN ST). BM Used only the first number in an apparent range of numbers because it appears to be the primary number (e.g., 25-27 MAIN ST to 25 MAIN ST). BN Corrected the street name spellings (e.g., DARLINGTON to ARLINGTON). BO Swapped delivery and secondary address positions (e.g., HUDSUCKER INDUSTRIES 123 MAIN ST to 123 MAIN ST, HUDSUCKER INDUSTRIES). BP The input city/state was invalid for the 5-digit ZIP Code. Corrected city/state and address resolved. BQ Combined multiple single alpha characters (probable initials) immediately following the primary number (e.g., 123 J F K PKWY to 123 JFK PKWY). BR The input 5-digit ZIP Code was a unique ZIP Code. The information in the Delivery Address field was returned unaltered as the resolved address. BS The address was a non-domestic military address (e.g., APO to FPO). BT The post office represented by the input 5-digit ZIP Code only has general delivery. BU Removed undefined alphabetic characters attached to the left of the apparent primary number (e.g., XYZ123 MAIN ST to 123 MAIN ST). BV Where the apparent primary number was numeric/alpha, used the numeric as the primary number and the entire apparent primary number as the secondary number (e.g., 15A3 SPA CREEK LANDING to 15 SPA CREEK LANDING 15A3). BX What was interpreted as the delivery address was parsed and EACH element of the street name was matched to a special file containing the parsed street names in ZIP+4 Product. This facilitated location of street names in which parts of the name, pre- directional, suffix, or post-directional had been omitted from the input address. BY The correct address was found using the process in BX. It was then determined that the address has been LACS converted. The converted address was returned as the resolved address. Limitation of Liability The Postal Service™ makes no warranty or representation, express or implied, with respect to the returned AEC file, nor will the Postal Service be liable for direct, indirect, special, incidental, consequential, or other similar damages arising out of use or inability to use the AEC return media, even if advised of the possibility of such damages. NOTE: All address lists submitted for AEC and/or AEC II are considered confidential between the United States Postal Service and the list owner. SUBMISSION INFORMATION AEC and AEC II USER GUIDE OCTOBER 2006