A E S Direct - Reduce Exporting Stress with A E S

Home

Press enter to skip left navigation bar
Log In
AESDirect
Certification Quizzes

Account Set-up & Management
Register New Account
Registration Help
Re-Activate an Account
Terms & Conditions
Privacy Policy

Vendor Account Set-up
Developers Center
Register Vendor Account

Training
AESDirect Tutorial
User Guides
Online Training
Workshops
AES Compliance

Using AESDirect
Who to Contact
Support Center
Browser Support
Developers Center
News

AESPcLink
About AESPcLink
Getting Started
Terms & Conditions

AESDirect VPN
About AESDirect VPN
Set up AESDirect VPN

Related Sites
Government Sites
Partner Sites

A E S Direct Support Center

AES Response Message Descriptions
[Support Center Home][Developers Center Home]

001 FATAL ERR - INVALID FILER ID TYPE

Data Elements: Filer ID, Filer ID Type
Reason: The translation error message occurs when the Filer ID Type is not S for Social Security Number, D for D-U-N-S Number or E for Employers ID Number.
Resolution: The filer must report the valid Filer ID Type that corresponds to the Filer ID.


002 FATAL ERR - INVALID EXPORTER ID TYPE

Data Elements: Exporter ID Number, Exporter ID Type
Reason: The translation error message occurs when the Exporter ID Number is entered and the Exporter ID Type is invalid or missing.
Resolution: Provide or correct the Exporter ID Type. The Exporter ID Type is a one digit alphabetic code that identifies the type of number reported to identify the exporter. Valid codes are D for D-U-N-S Number, S for Social Security Number (SSN), E for Employer Identification Number (EIN) and T for Foreign Entity code. NOTE: The number reported as T (Foreign Entity) may be an identification number contained in an official document such as a border crossing number, passport number, an alien registration card number or if an embassy is making the shipment, an embassy code. An embassy code is made up of the ISO country code followed by the word EMBASSY (Example: GBEMBASSY).


003 FATAL ERR - INVALID APPLICATN IDENTIFIER

Data Elements: Application Identifier
Reason: A warning message occurs when the Application Identifier is missing or invalid. The valid Application Identifiers are XP = Exporter Data Input, XT = Output from Customs, XN = Transaction Status.
Resolution: Provide the correct Application Identifier as listed above.


004 FATAL ERR - INVALID PARTY ID

Data Elements: Party ID, Party ID Type, Party Type
Reason: The translation error message occurs when the Party ID is missing or invalid when reporting Party Type F for forwarding agent. The message also occurs when the Party Type is C for consignee or I for intermediate consignee and the Party ID Type is not D for D-U-N-S.
Resolution: The transmitter must provide a valid Party ID. Acceptable Party ID includes E for EIN, D for D-U-N-S or S for SSN. The Party ID is an 11 position alphanumeric field. The two positions at the end signify the location of the party. If these two positions are not needed, the transmitter must enter 00 as the suffix. If the Party ID Type is T (foreign entity) all positions in the Party ID can be alphanumeric. If Party ID is D, S, or E then only the 10 and 11 positions can be alphanumeric. Party ID is not required for Consignee or Intermediate Consignee, however a D-U-N-S number may be reported if known. Otherwise, Party ID and Party ID Type should not be reported for Consignee or Intermediate Consignee.


005 FATAL ERR - INVALID PARTY ID TYPE

Data Elements: Party ID Type, Party Type
Reason: The translation error message occurs when the Party ID Type is not valid and the Party ID is reported for Party Type F for forwarding agent. Party ID Type can be S for SSN, E for EIN, D for D-U-N-S, X for Data Entry Center or T for Foreign Entity code. The message will also be generated if the Party ID is reported for Party Types C for consignee or I for intermediate consignee and the Party ID Type is not D for D-U-N-S.
Resolution: The transmitter must provide a valid Party ID Type (S, E, D, X or T) that corresponds to the Party ID.


006 FATAL ERR - INVALID EXPORT/ARRIVAL DATE

Data Elements: Date of Exportation, Date of Arrival [for exports to Puerto Rico]
Reason: The warning message occurs when the date format is invalid or missing. Note: The thirty-first day of the month cannot be reported for shortened months.
Resolution: Commercial documentation or other competent information should be examined to verify the proper date of exportation (or date of arrival for exports to Puerto Rico) is reported. The Date must be numeric and the format must be in century/year/month/day or YYYYMMDD.


007 FATAL ERR - INVALID PARTY TYPE

Data Elements: Party Type
Reason: The translation error message occurs when the Party Type is missing or invalid.
Resolution: The transmitter must provide a valid Party Type. Valid Party Types are E (Exporter), F (Forwarding Agent), C (Consignee), I (Intermediate Consignee), or D (Data Entry Center).


009 FATAL ERROR - NOT AUTHORIZED TO TRANSMIT

Data Elements: Filer ID, Transmitter ID
Reason: The translation error occurs when the transmitter and filer reported do not match, or the filer is not authorized to report to AES utilizing the services of the transmitter reported. This message is also generated when a non-authorized Data Entry Center (DEC) is indicated.
Resolution: The transmitter and filer identification numbers in the header records must be verified and compared to the profile of the filer. Only authorized parties can transmit as a DEC. This message only goes back to internal users. External users are unable to receive this message because the error occurs in the header.


014 FATAL ERR - HDR "A" TRAILER "Z" NO MATCH

Data Elements: Batch Control Number
Reason: The translation error message occurs when the batch control number in the "A" and "Z" records do not match.
Resolution: Verify that the batch control numbers in records "A" and "Z" match.


015 FATAL ERR - NON-NUMERIC LINE NUMBER
016 FATAL ERR - NON-NUMERIC NET FIRST QTY
017 FATAL ERR - NON-NUMERIC NET SECOND QTY
018 FATAL ERR - NON-NUMERIC VALUE OF GOODS
019 FATAL ERR - NON-NUMERIC GROSS SHIP WGHT

Data Elements: Line Number, Net First Quantity, Net Second Quantity, Value of Goods, Gross Shipping Weight
Reason: The translation error message occurs when the Line Number, Net First Quantity, Net Second Quantity, Value of Goods, or Gross Shipping Weight is transmitted in an invalid non-numeric format.
Resolution: The transmitter of the data must verify that the Line Number, Net First Quantity, Net Second Quantity, Value of Goods, or Gross Shipping Weight is reported in a numeric format, round to a whole number, omit decimals.


020 FATAL ERR - DATA RECORDS OUT OF SEQUENCE

Data Elements: Affects all CATAIR records (A, B, SC1, SC2, SC3, N01, N02, N03, CL1, CL2, CL3, EV1, Y, AND Z.), Filing Option Indicator
Reason: The translation error message occurs when the data records listed above are transmitted out of sequence. This message is also generated when the shipment is filed Pre-departure Option 3 and the Filing Option Indicator is missing or invalid.
Resolution: The transmitter of the data must report the data records in the following sequence: A, B, SC1, SC2, SC3, N01, N02, N03, CL1, CL2, CL3, EV1, Y, AND Z.


021 FATAL ERR-INVALID EXPRTER IRS NUM FORMAT

Data Elements: Exporter IRS Number, Exporter ID Type
Reason: The fatal error occurs when the Exporter IRS Number contains less than 9 positions or contains alphanumeric characters when the Exporter ID Type is not T for foreign entity code.
Resolution: The transmitter of the data must report a valid 9 digit Exporter IRS Number in the B record.


023 FATAL ERR - SHIPMENT CANNOT BE DELETED

Data Elements: Correction Flag
Reason: The fatal error message occurs when an attempt is made to delete a shipment that cannot be deleted.
Resolution: Contact your AES Client Representative.


024 FATAL ERR - MISSING EXPORTER ID NUMBER

Data Elements: Exporter ID Number
Reason: The fatal error message occurs when the Exporter Identification Number is missing.
Resolution: Commercial documentation or other competent information should be examined to verify the Exporter ID Number is correctly reported in the form of an EIN, SSN, D-U-N-S or Foreign Entity code.


025 FATAL ERR -COMMODITY CANNOT BE DELETED

Data Elements: Line Correction Flag
Reason: The fatal error occurs when an attempt is made to delete a Commodity line that cannot be deleted.
Resolution: Contact your AES Client Representative.


026 FATAL ERR - MISSING EXPORTER IRS NMBR TYPE
027 FATAL ERR - INVALID EXPORTER IRS NMBR TYPE

Data Elements: Exporter IRS Number, IRS Number Type, Exporter ID Number, Exporter ID Type
Reason: The fatal error message occurs when the Exporter IRS Number Type is missing and a) the Exporter IRS Number is entered or b) the Exporter identification information was left blank.
Resolution: Commercial documentation or other competent information should be examined to verify the one-digit alphabetic IRS Number Type is reported as S, for SSN, or E, for EIN.


028 FATAL ERR - MISSING EXPORTER IRS NUMBER

Data Elements: Exporter IRS Number
Reason: The fatal error message occurs when the IRS Number is missing and the Exporter ID Number has not been entered.
Resolution: Commercial documentation or other competent information should be examined to verify the IRS Number is correctly reported. Note: the IRS Number is nine alphanumeric characters, the letter O, I, and Z cannot be used in an IRS suffix (however, there are some exceptions for numbers assigned prior to this ACS rule), and dashes are not required.


029 FATAL ERR - EXPORTER IRS NUMBR NOT ON FILE

Data Elements: Exporter IRS Number, Exporter Name, Address, City, State, Postal Code
Reason: The fatal error message occurs when the Exporter IRS Number is not on file in AES.
Resolution: The transmitter must verify the Exporter IRS Number. If AES does not recognize the Exporter IRS Number, then it is not on file in AES, and the transmitter must establish a new profile in the Party Profile Information Records (N01, N02, and N03). Submit Company Name, IRS Number, Street Address, City, State, Postal Code, Contact Person, and Contact Person's Phone Number. If a D-U-N-S Number has been submitted as the Exporter ID Number, the reported IRS Number must correspond to only one D-U-N-S.


030 FATAL ERR - MISSING EXPORTER NAME

Data Elements: Exporter Name, Exporter ID Number
Reason: The fatal error message occurs when the Exporter ID Number is missing or not on file in AES and the Name is missing.
Resolution: Commercial documentation or other competent information should be examined to verify the Name of the exporter is correctly submitted.


031 FATAL ERR - MISSING EXPORTER STR ADDRESS

Data Elements: Exporter Street Address, Exporter ID Number
Reason: The fatal error message occurs when the Exporter ID Number is missing or not on file in AES and the Street Address is missing.
Resolution: Provide the Street Address of the exporter.


032 FATAL ERR - MISSING EXPORTER CITY

Data Elements: Exporter City, Exporter ID Number
Reason: The fatal error message occurs when the Exporter ID Number is missing or not on file in AES and the City is missing.
Resolution: Provide the City of the exporter.


033 FATAL ERR - MISSING EXPORTER STATE
034 FATAL ERR - INVALID EXPORTER STATE

Data Elements: Exporter State, Exporter ID Number, Exporter ID Type
Reason: The fatal error message occurs when the Exporter ID Number is missing or not on file in AES and the two-character abbreviation for U.S. state is missing or invalid.
Resolution: The transmitter must provide the two-character abbreviation for the U.S. state, territory or possession where the Exporter, Forwarder, Foreign Entity or DEC resides. If the Exporter resides in Puerto Rico, report PR as the state code and US as the country. If the Exporter ID Type is T for Foreign Entity, report the state of the temporary residence being used at the time of export.


035 FATAL ERR - MISSING EXPORTER POSTAL CODE

Data Elements: Postal Code, Party Type, Exporter ID Number
Reason: The fatal error message occurs when the Exporter ID Number is missing or not on file in AES and the Postal Code is missing.
Resolution: Provide the Postal Code (maximum nine-digits) which pertains to the city and state of the exporter.


036 FATAL ERR - MISSING EXPORTER CONTCT PERSON

Data Elements: Contact Name, Exporter ID Number
Reason: The fatal error message occurs when the Exporter ID Number is missing or not on file in AES and the Contact Name is missing.
Resolution: Provide the Name of the person to contact for verification of the export shipment.


037 FATAL ERR - MISSING EXPORTER PHONE NUMBR

Data Elements: Contact Phone, Exporter ID Number
Reason: The fatal error message occurs when the Exporter ID Number is missing or not on file in AES and the Contact Phone number is missing.
Resolution: Provide the phone number of the Contact Person.


038 FATAL ERR-INVALID EXPORTER ID NUM FORMAT

Data Elements: Exporter ID Number, Exporter ID Type
Reason: The fatal error message occurs when the Exporter ID Number contains less than 11 positions or contains alphanumeric characters in invalid positions. When the Exporter ID Type is a D, S, or E, the first 9 positions must be numeric. The 10 and 11 positions can be alphanumeric. If the Exporter ID Type is T for Foreign Entity, any of the 11 positions can be alphanumeric.
Resolution: The transmitter of the data must report a valid Exporter ID Number in the correct format in the B record.


042 FATAL ERR - INVALID EXPORTER ISO CTRY

Data Elements: Exporter Country
Reason: The Exporter reported is not subject to the jurisdiction of the United States. The Exporter must always have a U.S. address.
Resolution: AN U.S. address must be reported for the exporter.


050 FATAL ERR - MISSING ULT CONSIGNEE NAME

Data Elements: Consignee Name
Reason: The fatal error message occurs when the Consignee identification number is not reported or is not on file in AES when reported, and the Name is missing.
Resolution: Commercial documentation or other competent information should be examined to verify the Name of the Consignee is correctly submitted.


051 FATAL ERR - MISSING ULT CONSIG STR ADDRESS

Data Elements: Consignee Street Address
Reason: The fatal error message occurs when the Consignee identification number is not reported or not on file in AES when reported, and the Street Address is missing.
Resolution: Provide the Street Address of the consignee.


052 FATAL ERR - MISSING ULT CONSIGNEE CITY

Data Elements: Consignee City
Reason: The fatal error message occurs when the Consignee identification number is not reported or not on file in AES when reported, and the City is missing.
Resolution: Provide the City of the consignee.


053 FATAL ERR - MISSING ULT CONSIGNEE STATE
054 FATAL ERR - INVALID ULT CONSIGNEE STATE

Data Elements: Consignee State, Country of Ultimate Destination
Reason: The fatal error message occurs when the Consignee resides in Mexico (MX) and the consignee identification number are not on file in AES or not reported, and the Mexican State is either missing or invalid.
Resolution: When the Consignee resides in Mexico, report the Mexican State Code. Commercial documentation or other competent information should be examined to verify the correct Mexican State of the Consignee is reported when the Country of Ultimate Destination is "MX" for Mexico.


058 FATAL ERR - MISSING ULT CONSIGNEE ISO CTRY
059 FATAL ERR - INVALID ULT CONSIGNEE ISO CTRY

Data Elements: Consignee Country
Reason: The fatal error message occurs when the Consignee identification number is not reported, or is not on file in AES when reported, and the Country code is missing or invalid.
Resolution: Provide the two-position alpha ISO standard international country code, as given in the Harmonized Tariff Schedule or Schedule B, or Appendix C of this document.


070 FATAL ERR - MISSING AGENT NAME

Data Elements: Forwarding Agent Name (if any)
Reason: The fatal error message occurs when the Forwarding Agent identification number is not on file in AES when reported, and the Name is missing.
Resolution: Commercial documentation or other competent information should be examined to verify the Name of the forwarding agent is correctly submitted.


071 FATAL ERR - MISSING AGENT STREET ADDRESS

Data Elements: Forwarding Agent Street Address (if any)
Reason: The fatal error message occurs when the Forwarding Agent identification number is not on file in AES when reported, and the Street Address is missing.
Resolution: Provide the Street Address of the forwarding agent.


072 FATAL ERR - MISSING AGENT CITY

Data Elements: Forwarding Agent City (if any)
Reason: The fatal error message occurs when the Forwarding Agent identification number is not on file in AES when reported, and the City is missing.
Resolution: Provide the City of the forwarding agent.


073 FATAL ERR - MISSING AGENT STATE
074 FATAL ERR - INVALID AGENT STATE

Data Elements: Forwarding Agent State (if any)
Reason: The fatal error message occurs when the Forwarding Agent identification number is not on file in AES when reported, and the two-character abbreviation Postal State Code or Province is invalid or missing.
Resolution: Provide the State code. The Exporter and Agent must provide the two-character abbreviation U.S. State Code or two-character Province.


075 FATAL ERR - MISSING AGENT POSTAL CODE

Data Elements: Forwarding Agent Postal Code (if any)
Reason: The fatal error message occurs when the Forwarding Agent identification number is not on file in AES when reported, and the Postal Code (maximum nine-digits) is missing.
Resolution: Provide the Postal Code (maximum nine-digits) which pertains to the city and state of the Forwarding Agent.


076 FATAL ERR - MISSING AGENT CONTACT PERSON

Data Elements: Forwarding Agent Contact Name (if any)
Reason: The fatal error message occurs when the Forwarding Agent identification number is not on file in AES when reported, and the Contact Name is missing.
Resolution: Provide the Name of the person to contact for verification of the export shipment.


077 FATAL ERR - MISSING AGENT CONTACT PHONE NO

Data Elements: Forwarding Agent Contact Phone Number (if any)
Reason: The fatal error message occurs when the Forwarding Agent identification number is not on file in AES when reported, and the Contact Phone Number is missing.
Resolution: Provide the Phone Number of the Contact Person.


078 FATAL ERR - MISSING AGENT ISO COUNTRY
079 FATAL ERR - INVALID AGENT ISO COUNTRY

Data Elements: Forwarding Agent Country (if any)
Reason: The fatal error message occurs when the Forwarding Agent identification number is not on file in AES when reported, and the Country code is missing or invalid.
Resolution: Provide the two-character alpha ISO standard international country code of the Harmonized Tariff Schedule or Schedule B, or Appendix C of this document.


090 FATAL ERR - MISSING INT CONSIGNEE NAME

Data Elements: Intermediate Consignee Name (if any)
Reason: The fatal error message occurs when the Intermediate Consignee identification number is not on file in AES when reported, and the Name is missing.
Resolution: Commercial documentation or other competent information should be examined to verify the Name of the intermediate consignee is correctly submitted.


091 FATAL ERR - MISSING INT CONSIG STR ADDRESS

Data Elements: Intermediate Consignee Street Address (if any)
Reason: The fatal error message occurs when the Intermediate Consignee identification number is not on file in AES when reported, and the Street Address is missing.
Resolution: Provide the Street Address for the intermediate consignee.


092 FATAL ERR - MISSING INT CONSIGNEE CITY

Data Elements: Intermediate Consignee City (if any)
Reason: The fatal error message occurs when the Intermediate Consignee identification number is not on file in AES when reported, and the City is missing.
Resolution: Provide the City of the intermediate consignee.


093 FATAL ERR - MISSING INT CONSIGNEE STATE
094 FATAL ERR - INVALID INT CONSIGNEE STATE

Data Elements: Intermediate Consignee Country (if any), Intermediate Consignee State (if any)
Reason: If the Intermediate Consignee Country is "MX" for Mexico, the fatal error message occurs when the Intermediate Consignee identification number is not on file in AES when reported, and the Mexican State is either missing or invalid.
Resolution: Commercial documentation or other competent information should be examined to verify the correct Mexican State of the Intermediate Consignee is reported when the Intermediate Consignee Country is "MX" for Mexico.


098 FATAL ERR - MISSING INT CONSIGNEE ISO CTRY
099 FATAL ERR - INVALID INT CONSIGNEE ISO CTRY

Data Elements: Intermediate Consignee Country Code (if any)
Reason: The fatal error message occurs when the Intermediate Consignee identification number is not on file in AES when reported, and the Country Code is missing or invalid.
Resolution: Provide the two-position alpha ISO standard international country code of the Harmonized Tariff Schedule or Schedule B, or Appendix C of this document.


105 FATAL ERR - MISSING SCAC/IATA NUMBER
106 FATAL ERR - SCAC/IATA NUMBER NOT ON FILE

Data Elements: SCAC/IATA
Reason: The fatal error message occurs when the SCAC or IATA number is missing or not on file in AES. The SCAC for vessel and truck is issued by the NMFTA (National Motor Freight Traffic Association). The SCAC for rail is issued by the AAR (American Association of Railroads). IATA (International Air Transport Association) issues air carrier codes.
Resolution: The NMFTA, AAR or IATA should be contacted or other competent information should be examined to verify that the SCAC or IATA is correctly reported. The SCAC is the standard identification for vessel, rail, and truck carriers. The IATA is the standard identification for air carriers. *F, *C, * U, or *M will be accepted in cases where the IATA or SCAC codes are not known for air and truck shipments. If the ultimate carrier is unknown, report the consolidator’s SCAC or IATA.


108 FATAL ERR - INVALID CONSIGNEE CORRECTION FLAG

Data Elements: Consignee Correction Flag, Party Flag
Reason: The fatal error message occurs when the Consignee Correction Flag on the N02 record is invalid. The valid values for the Consignee Correction Flag is ‘C’ for change or ‘blank’. The add and delete functions are not available here.
Resolution: Verify that the Consignee Correction Flag contains a valid value.


109 FATAL ERR – VALUE EXCEEDS $2501 (LC or LV)

Data Elements: Export Information Code, Value of Goods
Reason: The fatal error message occurs when the Export Information Code (Appendix E) is "LC" or "LV" identifying shipments valued $2500 or less per classification number and the value of the goods is over $2501.
Resolution: Review the value of the goods and determine if the appropriate Export Information Code was reported. Correct as necessary.


110 FATAL ERR - MISSING SHIPMENT REF NUMBER

Data Elements: Shipment Reference Number
Reason: The fatal error message occurs when the Shipment Reference Number is incomplete or missing.
Resolution: Provide the Shipment Reference Number that uniquely identifies the export shipment with the transmitter. This number, created by the transmitter, may consist of a Bill of Lading Number, an Invoice Number, or a Company's Internal Reference Number. The transmitter is the company responsible for transmitting the data and can verify the shipment by this unique Shipment Reference Number.


111 FATAL ERR - DUP EXPORT TRANSACTION NUMBER

Data Elements: Transmitter ID, Shipment Reference Number
Reason: The fatal error message occurs for new shipments when the Transmitter ID plus the Shipment Reference Number created an Export Transaction Number which already exists on file in AES. This number must be unique for FIVE years.
Resolution: For a new shipment, provide a different Shipment Reference Number in order to create a unique Export Transaction Number.


112 FATAL ERR - EXPORT TRANS NUMBER NOT FOUND

Data Elements: Transmitter ID, Shipment Reference Number, Shipment Correction Flag
Reason: The fatal error message occurs when the Header or Line Correction Flag is reported as C, for change or D, for delete, but the Export Transaction Number is invalid or not on file in AES.
Resolution: When changing or deleting a line or shipment the Transmitter ID and Shipment Reference Number (referred to as the Export Transaction Number) must match the number on the original "ADD" line or shipment.


113 FATAL ERR - INVALID HEADER CORRECTION FLAG

Data Elements: Correction Flag
Reason: The fatal error message occurs when the Correction Flag on the SC1 record is invalid.
Resolution: Commercial documentation or other competent information should be examined to verify the one-character alphabetic Correction Flag is reported as “blank” when adding a shipment, “C” when changing a shipment, or “D” when deleting a shipment. For pre-departure Option 3, valid correction flags are “P” for Add, “Q” for Change, or “R” for Delete.


114 FATAL ERR - INVALID LINE CORRECTION FLAG

Data Elements: Line Correction Flag
Reason: The fatal error message occurs when the Line Correction Flag on the CL1 record is invalid.
Resolution: Commercial documentation or other competent information should be examined to verify the one-character alphabetic Line Correction Flag is reported as “blank” when adding a line, “C” when changing a line, or “D” when deleting a line.


115 FATAL ERR - LINE NUMBER NOT FOUND
116 FATAL ERR - DUPLICATE LINE NUMBER

Data Elements: Line Number, Line Correction Flag
Reason: The fatal error message occurs for a new line item when the Line Number being reported already exists on file, or for an update to a line item when the Line Number is not found as part of the specific shipment. The Line Number reported for Pre-departure and Post-departure Option 3 lines must match.
Resolution: Commercial documentation or other competent information should be examined to verify that each line number is unique per shipment and the correct line number exists in AES for update.


117 FATAL ERR - MISSING MODE OF TRANSPORTATION
118 FATAL ERR - INVALID MODE OF TRANSPORTATION

Data Elements: Mode of Transportation
Reason: The fatal error message occurs when the Mode of Transportation is invalid or missing.
Resolution: The transmitter must provide the mode of transportation as indicated by the two position numeric code. The codes are 10-vessel (non-containerized), 11-vessel (containerized), 12-vessel barge, 20-rail (non-containerized), 21-rail (containerized), 30-truck (non-containerized), 31-truck (containerized), 40-air (non-containerized), 41-air (containerized), 32-auto, 33-pedestrian, 34-road, other, 50-mail, 60-passenger-hand carried, 70-fixed transport (pipeline, electrical powerhouse).


119 FATAL ERR - MISS CNTRY OF ULT DESTINATION
120 FATAL ERR - INVALID CNTRY OF ULT DESTINATION

Data Elements: Country of Ultimate Destination, Port of Exportation
Reason: The fatal error message occurs when the ISO Country Code is invalid or missing. The Country of Ultimate Destination is the country in which the merchandise is to be consumer, manufactured or further processed at the time of shipment. The Country of Ultimate Destination must be reported using the two-character alphabetic ISO Country Code, as provided in the Harmonized Tariff Schedule or Appendix C of this document. The country of ultimate destination cannot be the U.S. unless the Port of Exportation is Puerto Rico.
Resolution: Commercial documentation or other competent information should be examined to verify the correct Country of Ultimate Destination. Resubmit the shipment with the correct ISO Country Code.


121 FATAL ERR - MISSING PORT OF UNLADING
122 FATAL ERR - INVALID PORT OF UNLADING

Data Elements: Port of Unlading, Mode of Transportation, Country of Ultimate Destination
Reason: The fatal error message occurs when the Mode of Transportation is 10, 11 or 12 and the Port of Unlading is invalid or missing. For ocean shipments, if the Country of Ultimate Destination is not the U.S. or Puerto Rico, the Port of Unlading must be a five-digit Schedule K code. For ocean and air shipments between the U.S. and Puerto Rico, report the four-digit Schedule D code (Left justified). If the MOT is other than vessel, and the trade is not between the U.S. and Puerto Rico, the port of unlading must be blank.
Resolution: Commercial documentation or competent information should be examined to determine the Method of Transportation and the Port of Unlading (representing the foreign port and country where the merchandise will be unladen from the exporting carrier) are correctly reported as presented in Schedule K. For trade between U.S. and Puerto Rico, the Schedule D Customs Port code must be submitted. Schedule K codes can be obtained by calling the Foreign Trade Division, Bureau of the Census, Washington, DC (301) 457-3539 or by referencing Appendix H of this document. The Schedule D codes can be obtained from the Harmonized Tariff Schedule or Schedule B, AES file, or Appendix D of this document.


123 FATAL ERR - MISSING PORT OF EXPORTATION
124 FATAL ERR - INVALID PORT OF EXPORTATION

Data Elements: Port of Exportation, Mode of Transportation, Country of Ultimate Destination
Reason: The fatal error message occurs when the Port of Exportation code is invalid or missing or the port is inactive for exports. If the Country of Ultimate Destination is U.S., the Port of Exportation must be a port of Puerto Rico. If the Country of Ultimate Destination is PR, you cannot have a PR port of exportation. If the Method of Transportation is Code 50 (mail), report Schedule D code ‘8000’ or any valid Port code is acceptable.
Resolution: Commercial documentation or other competent information should be examined to verify the U.S. port of exportation. The four position numeric port codes are presented in Schedule D of the Harmonized Tariff Schedule and Schedule B, in AES, or in Appendix D of this document.


125 FATAL ERR - MISSING HAZMAT INDICATOR
126 FATAL ERR - INVALID HAZMAT INDICATOR

Data Elements: Hazmat Indicator, HS or Schedule B Number
Reason: The fatal error message occurs when the Hazardous Materials Indicator is missing or anything other than Y for Yes or N for No.
Resolution: Commercial documentation or other competent information should be examined to verify whether or not the shipment contains Hazardous Material. The only acceptable values are Y for Yes or N for No.


127 FATAL ERR - MISSING INBOND CODE
128 FATAL ERR - INVALID INBOND CODE

Data Elements: In Bond Code
Reason: The fatal error message occurs when the In Bond Code reported is invalid or missing. The Default code "70 for not in bond" should be reported here.
Resolution: The two-digit numeric code should be entered to specify whether or not an In Bond shipment exists. The codes are as follows: 70=Not In Bond; 62=(T&E) Transportation and Exportation; 63=(IE) Immediate Exportation; 36=Warehouse Withdrawal for IE; 37=Warehouse Withdrawal for T&E; 67=IE from a (FTZ) Foreign Trade Zone; 68=T&E from a (FTZ) Foreign Trade Zone. At this time AES does not close out any in bond shipments.


129 FATAL ERR - MISSING ENTRY NUMBER
130 FATAL ERR - INVALID ENTRY NUMBER FORMAT

Data Elements: Entry Number, In Bond Code, Export Information Code
Reason: The fatal error message occurs when an In Bond Code (other than ‘70’) is reported or when the Export Information Code for Drawback (‘DB’) is reported and the Entry Number has too few numbers, inserted dashes, spaces or other special characters, or is missing entirely.
Resolution: Commercial Documentation or competent information should be examined to verify when the In Bond Code is reported or for Drawback Exports, a valid fifteen-digit Import Entry Number or Drawback Entry Number is correctly reported.


131 FATAL ERR - MISSING EQUIP/BOOKING NUMBER

Data Elements: Equipment Number, Transportation Reference Number, Mode of Transportation
Reason: The fatal error message occurs when the Mode of Transportation is 11, 21, 31, or 41 and the equipment number or booking number is missing.
Resolution: When the Mode of Transportation is reported as 11, 21, 31, or 41 (for containerized cargo), correctly report the container number in the Equipment Number field or report the Booking Number in the Transportation Reference Number field. If both are available, the filer should report both. However only one is required for containerized cargo.


132 FATAL ERR - MISSING EXP INFORMATION CODE
133 FATAL ERR - INVALID EXP INFORMATION CODE

Data Elements: Export Information Code
Reason: The fatal error message occurs when the Export Information Code is invalid or missing.
Resolution: Commercial documentation or other competent information should be examined to verify that a correct alphanumeric Export Information Code is correctly reported. The Export Information Codes are presented in Appendix E of this document.


134 FATAL ERR - MISSING HS OR SCHED B NUMBER
135 FATAL ERR - INVALID HS OR SCHED B NUMBER

Data Elements: HS/Schedule B Number, Commodity Description, Export Information Code, Filing Option Indicator
Reason: The fatal error message occurs when the HS/Schedule B Number is missing, or is improperly formatted. The HS/Schedule B Numbers are 10-digit numeric codes that represent the commodity being exported. This error does not apply to the Export Information Codes that require limited information. Pre-departure Option 3 filings may report the commodity description in lieu of the HS or Schedule B number.
Resolution: Commercial documentation or other competent information should be examined to verify the HS or Schedule B Number is correctly reported. For assistance, consult the Harmonized Tariff Schedule or the Schedule B - Classification of Exports, AES file, or call the Foreign Trade Division, Bureau of the Census, Washington, DC (301) 457-2981 for classification assistance.


136 FATAL ERR - OUTDATED HS OR SCHED B NUMBER

Data Elements: HS or Schedule B Number
Reason: The error message occurs when the HS or Schedule B Number being reported expired over 30 days from the date of export.
Resolution: Commercial documentation or other competent information should be examined to verify that the HS or Schedule B Number is correctly reported. Classification numbers change from time to time. An up-to-date HS or Schedule B Number must be reported. For assistance, consult the Harmonized Tariff Schedule or the Schedule B - Classification of Exports, AES file, or call the Foreign Trade Division, Bureau of the Census, Washington, DC (301) 457-2981 for classification system.


137 FATAL ERR - ZERO VALUE UNACCEPTABLE

Data Elements: Value of Goods
Reason: The fatal error message occurs when the Value of Goods is reported as zero.
Resolution: Commercial documentation or other competent information should be examined to verify the Value of Goods reported is the selling price or cost if not sold, including inland freight, insurance, and other charges to U.S. Port of Exportation, but excluding unconditional discounts and commissions. The Value of Goods must be rounded to the nearest whole dollar, omit cents.


138 FATAL ERR - ZERO GROSS SHIP WGHT UNACCEPT

Data Elements: Gross Shipping Weight
Reason: The fatal error message occurs when the Gross Shipping Weight is reported as zero.
Resolution: Commercial documentation or other competent information should be examined to verify the Gross Shipping Weight is correctly reported in KILOGRAMS, including the weight of containers, but excluding carrier equipment. [Multiply Pounds (LBS) by .4536 to get Kilograms (KG)]. Gross Shipping Weight may be estimated, but must be rounded to whole numbers, omit decimals. A Shipping Weight less than 1-kilogram must be rounded up to 1 kg


139 FATAL ERR - MISS VEHICLE ID NUMBER (VIN)
140 FATAL ERR - INVAL VEHICLE ID NUMBER (VIN)
141 FATAL ERR - MISSING VEHICLE TITLE NUMBER
142 FATAL ERR - INVALID VEHICLE TITLE NUMBER
143 FATAL ERR - MISS VEHICLE STATE OF TITLE
144 FATAL ERR - INVAL VEHICLE STATE OF TITLE

Data Elements: Vehicle Identification Number (VIN), Vehicle Title Number, Vehicle State of Title, HS or Schedule B Number, Commodity Description
Reason: The fatal error message occurs when the shipment contains USED, self-propelled vehicles, and the VIN, Vehicle Title Number, and Vehicle State of Title are invalid or missing. The VIN must be in an acceptable format as given by the manufacturer.
Resolution: Commercial Documentation or competent information should be examined. When certain HS or Schedule B Numbers pertaining to USED vehicles are reported, requiring VINs, verify that the VIN(s), Vehicle Title Number(s), and Vehicle State of Title(s) are correctly reported and in the correct format.


145 FATAL ERR - MISSING PRODUCT ID NUMBER

Data Elements: Product Identification Number (PIN), HS/Schedule B Number, Commodity Description
Reason: The fatal error message occurs when the shipment contains USED, self-propelled vehicles not having a VIN, and the PIN is missing.
Resolution: Commercial Documentation or competent information should be examined to verify when certain HS or Schedule B Numbers pertain to USED vehicles not having VINs, that the PIN(s) are correctly reported.


146 FATAL ERR - USED VEHICLE NOT FOUND

Data Elements: Vehicle Identification Number (VIN), Product Identification Number (PIN), Vehicle ID Qualifier, Vehicle Correction Flag
Reason: The fatal error message occurs when the transmitter attempts to change or delete a VIN or PIN and the VIN or PIN is not on file in AES.
Resolution: Commercial Documentation or competent information should be examined to verify that the correct VIN or PIN has been reported when making the change or deletion. The Vehicle Correction Flags are ‘D’ for delete and ‘C’ for change.


148 FATAL ERR - MISS US STATE OF ORIGIN CODE
149 FATAL ERR - INVAL US STATE OF ORIGIN CODE

Data Elements: State of Origin Code
Reason: A fatal error message occurs when the U.S. State of Origin two-position code is invalid or missing.
Resolution: Commercial documentation or other competent information should be examined to verify that the two-position U.S. Postal Service abbreviation of the State or U.S. territory in which the merchandise actually starts its journey to the port of export is correctly reported.


155 FATAL ERR - MISSING COMMODITY LINES

Data Elements: Shipment Correction Flag, Line Correction Flag and Line Number.
Reason: A fatal error message occurs when no commodity lines are submitted with a new shipment.
Resolution: When adding a new shipment, submit at least one commodity line item.


160 FATAL ERR - EXPORTER PROFILE NOT SETUP

Data Elements:
Reason: A fatal error message occurs when the exporter profile has not been setup on the AES system.
Resolution: Contact your Client Representative.


162 FATAL ERR - FOR FUTURE USE

163 FATAL ERR - FOR FUTURE USE

164 FATAL ERR - OPTION 4 NOT YET ACTIVE

Data Elements: Exporter ID Number, Filing Option Indicator
Reason: A fatal error message occurs when the approved exporter's Option 4 privilege is not yet active. The Exporter cannot send Option 4 shipments prior to the start-up date scheduled by the Client Representative.
Resolution: Contact your AES Customs Client Representative.


165 FATAL ERR - OPT4 PRIVILEGE REVOKED

Data Elements: Exporter ID Number, Filing Option Indicator
Reason: A fatal error message occurs when the exporter's Option 4 privilege has been revoked.
Resolution: Contact your AES Customs Client Representative.


166 FATAL ERR-EXPRTER NOT OPT4 ELIGIBLE

Data Elements: Exporter ID Number, Filing Option Indicator
Reason: A fatal error message occurs when the exporter has not been approved for Option 4 filing privilege.
Resolution: Contact your AES Customs Client Representative.


169 FATAL ERR - INVALID FILING OPT. INDICATOR

Data Elements: Filing Option Indicator
Reason: A fatal error message occurs when the Filing Option Indicator contains an invalid value.
Resolution: The correct values are ‘Blank’ for Option 2, ‘3’ for Option 3, and ‘4’ for Option 4 shipments. One of these values must be reported in the Filing Option Indicator field.


170 FATAL ERR – MISSING BOOKING NUMBER

Data Elements: Transportation Reference Number, Method of Transportation
Reason: A fatal error message occurs when the Method of Transportation is sea (MOT 10, 11 or 12) and the transportation reference number, which is the Booking Number, is missing.
Resolution: Verify the Method of Transportation is sea and if so, verify that the booking number provided by the carrier or consolidator is reported.


171 FATAL ER - DEC NOT OPT4 ELIGIBLE

Data Elements: Filing Option Indicator, Party ID Type, Party Type
Reason: The fatal error message occurs when a Data Entry Center (DEC) attempts to file in AES using Option 4. The DEC can only report to AES using Filing Option 2 or Option 3 per signed agreement.
Resolution: Verify the Filing Option used to report the shipment to AES. If an approved Option 4 exporter request the DEC to file on their behalf, then the DEC must file as a freight forwarder.


178 FATAL ERR - PRE-DEPARTURE FILING INCOMPLET

Data Elements: Exporter ID, Forwarder ID, Carrier ID, Country of Ultimate Destination, Name of Ultimate Consignee, Commodity Description or Harmonized Number, Unique Identifying Number, Intended U.S. Port of Export, Estimated Date of Export, Transportation Reference Number, Mode of Transportation Code, HAZMAT, License Code, License Number
Reason: The fatal error message occurs when all the mandatory data elements for a particular commodity reported Pre-departure Option 3 were not included for the shipment.
Resolution: Verify that the filer has transmitted the mandatory (up to 14) data elements pre-departure. Note that while all commodities require a license code, not all commodities require a license number. The commodity description may be reported in lieu of the Harmonized Schedule Number. The Transportation Reference Number is only required when the MOT is 10, 11, or 12. If the Method of Transportation is 32,33,34,50,60, or 70, the Carrier ID (SCAC/IATA) is not required.


179 FATAL ERR - STATE DEPART. SHIPMENT INELIG

Data Elements: License Code
Reason: The fatal error message occurs when a commodity shipment that requires a State Department license is reported as a Pre-departure Option 3 filing.
Resolution: Commercial documentation or other competent information should be examined to verify that a State Department license is required. If the shipment requires a State Department license, the filer should revert to AES Option 2 filing (full pre-departure information). AES will capture this message and make it available for compliance reporting purposes.


180 FATAL ERR – PREDEPARTURE DATA NOT ACCEPTED

Data Elements: Filing Option Indicator
Reason: The error message occurs when a filer tries to transmit pre-departure data after the post-departure filing has been received and accepted.
Resolution: No action required.


181 FATAL ERR – INVALID COMMODITY DESCRIPTION

Data Elements: Commodity Description
Reason: Using Option 3, the pre-departure filing can contain a commodity description in lieu of reporting the Schedule B/HS number. However, the description must be complete enough to allow Customs Inspectors to verify the shipment if necessary. Therefore, AES has been programmed to reject descriptions that are too general, such as FAK or Freight of All Kinds or Other.
Resolution: Commercial documentation or other competent information should be examined to verify what commodity is being shipped. A more specific description of the commodity should be entered in the Commodity Description field.


185 FATAL ERR – FOR FUTURE USE

308 WARN ERR - MISSING FORWARDER INFORMATION

Data Elements: Party ID, Party ID Type, Party Type
Reason: The warning error occurs if the filer in the header (A) record is different than the exporter in the exporter (B) record and the forwarder has not been reported in the profile (N01, 2, 3) records.
Resolution: The filer of the information must submit the forwarder information in the profile records.


309 WARN ERR - OUTDATED LICENSE CODE

Data Elements: License Code, Estimated Date of Export
Reason: This warning message occurs when the three-position License Code is outdated. If the Estimated Time of Departure is not within the begin and end date range of the License code then it is outdated.
Resolution: Confirm that the Estimated Date of Export is within the range of the begin and end dates for the reported License Code. Refer to Appendix F for an update of the License Codes.


310 WARN ERR - MISSING LICENSE CODE
311 WARN ERR - INVALID LICENSE CODE

Data Elements: License Code
Reason: The warning message occurs when the three-position License Code is invalid or missing. The License Code designates the type of license, permit, license exception or no license required.
Resolution: Commercial documentation or other competent information should be examined to verify the correct three-position License Code is reported designating the type of License or Permit required for the commodity. Appendix F of this document contains a list of valid License Codes. For further clarification of the problem, the filer should contact the licensing agency.


312 WARN ERR - MISSING LICENSE NUMBER/CFR CIT
313 WARN ERR - INVALID LICENSE NUMBER

Data Elements: License Number/License CFR Citation, License Code
Reason: The warning message occurs when a License Code requires a License Number/CFR Citation and the License Number or License CFR Citation is missing or License Number is invalid.
Resolution: Approved licenses or competent information should be examined to verify when a License Code requires a License Number/CFR Citation be submitted that the License Number for this commodity OR CFR Citation is correctly reported. CFR Exemption Citations for State/ODTC should reflect why the merchandise is exempt from license application. CFR Citations for the Nuclear Regulatory Commission and the Office of Foreign Assets Control should reflect why the merchandise qualifies for export under a NRC or OFAC ‘general’ license. For further clarification of the problem, the filer should contact the licensing agency. The Dept. of State/Office of Defense Trade Controls, Licensing Division can be reached at 703-875-6637. The Dept. of Commerce/Bureau of Export Administration, Office of Enforcement Support can be reached at 202-482-4255. The Nuclear Regulatory Commission can be reached at 301-415-2342. The Department of the Treasury/Office of Foreign Assets Control can be reached at 202-622-2520.


314 WARN ERR - POST/PRE DEP LIC DOESN’T MATCH

Data Elements: Filing Option Indicator, License Number/CFR Citation
Reason: The warning message occurs when the license number on the post-departure filing does not match the license number reported on the pre-departure filing.
Resolution: Verify the license number is reported correctly on both the pre-departure and the post-departure Option 3 filing. It should be the same number on both. AES will capture this message and make it available for compliance reporting purposes.


315 WARN ERR - MISSING ECCN
316 WARN ERR - INVALID ECCN

Data Elements: Export Control Classification Number (ECCN), License Code
Reason: The warning message occurs when a License Code requiring an ECCN is reported, and the ECCN is invalid or missing. A four-digit or five-digit ECCN number is required. When a five-digit ECCN is reported, the fifth digit should be reported in the filler position.
Resolution: The Department of Commerce, BXA approved licenses or competent information should be examined to verify the four-position number corresponding to the COCOM export control structure format is the same as the ECCN submitted into AES. The correct four-position ECCN must be resubmitted. For further clarification of the problem, the filer should contact the licensing agency. The Department of Commerce/Bureau of Export Administration, Office of Enforcement Support can be reached at 202-482-4255. AES will capture the error message and make it available for compliance reporting.


317 WARN ERR - INVAL DEST CNTRY FOR LICENSE

Data Elements: Country of Destination, License Code, License Number/License Exemption Citation
Reason: The warning message occurs when a License Number is required and the Country of Destination reported in AES does not match the Country of Destination specified on the Department of State, ODTC approved License.
Resolution: The Department of State, ODTC approved License or competent information should be examined to verify the Country of Destination listed on the License is the same as the Country of Destination submitted to AES. The correct two-position Standard International Country Code (ISO) must be resubmitted. For further clarification of the problem, the filer should contact the licensing agency. The Department of State/Office of Defense Trade Controls, Licensing Division can be reached at 703-875-6637.


318 WARN ERR - DATE OF EXP EXCEEDS LICENSE

Data Elements: License Code, License Number/License Exemption Citation, Date of Exportation
Reason: The warning error message occurs when the License for this commodity has expired prior to the date of exportation.
Resolution: Approved licenses or competent information should be examined to verify that either the Date of Exportation or the License Number has been correctly reported. For further clarification of the problem, the filer should contact the licensing agency. The Department of State/Office of Defense Trade Controls, Licensing Division can be reached at 703-875-6637. The Department of Commerce/Bureau of Export Administration, Office of Enforcement Support can be reached at 202-482-4255.


319 WARN ERR - OUTDATED EXPORT INFO CODE

Data Elements: Export Information Code, Estimated Date of Export
Reason: This warning message occurs when the two-position Export Information Code is outdated. The code is outdated if the estimated date of export is not within the beginning and ending date range.
Resolution: Confirm that the Estimated Date of Export is within the range of the begin and end dates for the reported Export Information Code. Consult Appendix E of this document for an update of the Export Information Codes.


321 WARN ERR - USED VEHICLES INELIGIBLE

Data Elements: Filing Option Indicator, HS/Schedule B or Commodity Description, Country of Ultimate Destination
Reason: The warning message occurs when a used vehicle is reported under Filing Option 3 or Option 4 and the Country of Ultimate Destination is not the U.S. or Puerto Rico.
Resolution: Used vehicle exports, other than those traded between the U.S. and Puerto Rico, should not be transmitted under Option 3 or Option 4. The AES will accept the data; however, the above message is captured for monitoring purposes. It is the exporter’s responsibility to file using the appropriate filing option. Continued misuse puts the exporter at risk of losing their privilege to file using Option 4.


322 WARN ERR - LICENSE SHIPMENT INELIGIBLE

Data Elements: License Code, License Number, Filing Option Indicator
Reason: This warning message occurs when licensable shipments are reported using Filing Option 4.
Resolution: The AES accepts the data, however, this warning message is capture for monitoring purposes. Continued misuse puts the exporter at risk of losing Option 4 filing privileges. For further information, the filer may contact the licensing agency. The Department of Commerce/Bureau of Export Administration/Office of Enforcement Support may be reached on 202-482-4255. The Nuclear Regulatory Commission may be reached on 301-415-2342. The Department of the Treasury/Office of Foreign Assets Control may be reached on 202-622-2520. In the future, transmit licensable shipments using the appropriate filing option.


323 WARN ERR - STATE LICENSE INELIGIBLE

Data Elements: License Code, License Number, Filing Option Indicator
Reason: This warning message occurs when a shipment requiring a State Department license is reported using Filing Option 3 or Option 4.
Resolution: Contact your Customs or Census Client Representative.


324 WARN ERR - INVALID PRT OF EXP FOR MAIL SHP

Data Elements: Method of Transportation, Port
Reason:
Resolution:


325 WARN ERR - RELATED PARTY INDICATOR MISSING
326 WARN ERR - INVALID RELATED PARTY INDICATOR

Data Elements: Related Party Indicator
Reason: The warning message occurs when the Related Party Indicator is missing or invalid. A ‘Related Party Transaction’ is one in which either the U.S. Exporter or the foreign Consignee owned (directly or indirectly) at any time during the fiscal year, 10 percent or more of the voting securities of the incorporated business enterprise, or an equivalent interest of an unincorporated business enterprise, including a branch.
Resolution: The indicator should be reported to specify whether or not the Exporter and Consignee are related. The indicators are 1=Exporter/Consignee are RELATED; 2=Exporter/Consignee are NOT RELATED.


327 WARN ERR - SANCTION ON COUNTRY OF ULT DEST

Data Elements: Country of Destination
Reason: A warning message occurs when the Country of Ultimate Destination reported is on the list of countries under sanction.
Resolution: Commercial documentation or other competent information should be examined to verify the correct Country of Ultimate Destination. Resubmit with the correct ISO Country Code, as presented in the Harmonized Tariff Schedule or Appendix C of this document. The filer should check with local Customs to see what procedures should be followed in each individual case.


328 WARN ERR - OUTDATED COUNTRY CODE

Data Elements: Country Code, Estimated Date of Export
Reason: This warning message occurs when the two-character ISO Country Code is outdated. The code is outdated if the Estimated Date of Export is not within the begin and end date range.
Resolution: Confirm that the Estimated Date of Export is within the range of the begin and end dates for the reported Country Code. Consult Appendix C of this document for an update of the Country Codes.


329 WARN ERR - OUTDATED PORT OF UNLADNG

Data Elements: Port of Unlading, Estimated Date of Export
Reason: This warning message occurs when the five-digit Port of Unlading code is outdated. The code is outdated if the Estimated Date of Export is not within the begin and end date range.
Resolution: Confirm that the Estimated Date of Export is within the range of the begin and end dates for the reported Port of Unlading. Consult the updated version of the Schedule K in Appendix H for up to date Ports of Unlading.


330 WARN ERR - MISSING CONVEYANCE NAME
331 WARN ERR - INVALID CONVEYANCE NAME

Data Elements: Conveyance Name, Mode of Transportation
Reason: The warning message occurs when the MOT is ocean, air, rail or truck and the Conveyance Name is missing or invalid. It is invalid to report ‘vessel’, ‘airplane’, ‘train’, ‘truck’, or ‘international foot bridge’.
Resolution: Commercial Documentation or competent information should be examined to verify when the Mode of Transportation is Ocean, the Name of the Vessel transporting the merchandise is correctly reported. When the MOT is air, rail or truck, the carrier name must be reported.


333 WARN ERR - INVALID VESSEL FLAG

Data Elements: Vessel Flag, Conveyance Name, Mode of Transportation
Reason: A warning message occurs when the Mode of Transportation is Ocean and the Vessel Flag is invalid.
Resolution: Provide the ISO Country Code for the country under whose flag the vessel is registered. Resubmit with the correct ISO code (reference the Harmonized Tariff Schedule or Appendix C of this document).


334 WARN ERR-INVALID PORT OF EXP FOR VESSEL

Data Elements: Port of Exportation, Mode of Transportation
Reason: A warning message occurs when the Port of Exportation code submitted is impossible for shipments exported by vessel (MOT=10, 11 or 12). Customs ports that do not have water access are not considered vessel ports.
Resolution: Commercial documentation or other competent information should be examined to verify the U.S. Port of Exportation reported is an acceptable port of export for vessel shipments. The four-digit port codes can be found in Schedule D of the Harmonized Tariff Schedule or Schedule B, as an AES file, or in Appendix D of this document.


335 INFO ERR - SHIPMENT REPORTED LATE

Data Elements: Date of Exportation (or Date of Arrival for shipments between the U.S. and Puerto Rico), Correction Flag, Line Correction Flag, Filing Option Indicator
Reason: The information message occurs when the Header Correction Flag is missing and the Line Correction Flag is missing and the Date of Exportation [or Date of Arrival for exports between the U.S. and Puerto Rico] precedes the system date. This shows the transmission was not made pre-departure as required using Fling Option 2. Option 3 filers have five (5) working days past the date of exportation of the pre-departure shipment to send the complete post-departure data to AES. Approved Option 4 filers have ten (10) working days past the date of exportation to transmit post-departure data.
Resolution: Verify the Date of Exportation [or Date of Arrival for exports between the U.S. and Puerto Rico] is correctly reported. Please ensure that future shipments are reported prior to the carrier's departure or within the filing option time frames. AES will capture this error message and make it available for compliance reporting purposes.


336 WARN ERR - MISSING WAIVER INDICATOR
337 WARN ERR - INVALID WAIVER INDICATOR

Data Elements: Waiver of Prior Notice Indicator, Export Information Code
Reason: The warning occurs when the Export Information Code for Drawback is entered and the Waiver of Prior Notice is missing or not reported as Y for YES or N for NO.
Resolution: For Drawback Exports, Y for YES or N for NO must be reported to identify whether a drawback claimant has received a waiver of prior notice for the exported merchandise.


339 WARN ERR - MISSING COMMODITY DESCRIPTION

Data Elements: Commodity Description, HS or Schedule B Number, Filing Option Indicator
Reason: The warning message occurs when the Commodity Description is missing.
Resolution: Commercial documentation or other competent information should be examined to verify that a sufficient Commercial Description is reported in common trade terms to permit verification of the HS or Schedule B Number or the description as shown on a export license.


343 WARN ERR - MISS NET 1ST UNIT OF MEASURE
344 WARN ERR - INVAL NET 1ST UNIT OF MEASURE
345 WARN ERR - MISS NET 2ND UNIT OF MEASURE
346 WARN ERR - INVAL NET 2ND UNIT OF MEASURE
347 WARN ERR - QTY UNITS DO NOT MATCH HS REQ

Data Elements: Net First Unit of Measure, Net Second Unit of Measure, Net First Quantity, Net Second Quantity, HS or Schedule B Number
Reason: The warning message occurs when the Net Unit of Measure is missing or invalid or the Net Unit of Measure reported does not correlate to the Net Unit of Measure required for the HS or Schedule B Number reported.
Resolution: Commercial documentation or other competent information should be examined to verify the Unit of Measure is correctly reported. Consult the Harmonized Tariff Schedule or Schedule B to determine the appropriate Net Unit of Measure to be reported for the specific HS or Schedule B Number. For example, an invoice may read 84 gallons of crude petroleum, but in the HS/Schedule B; crude petroleum requires the Net First Unit of Measure in Barrels (of 42 gallons). Therefore the correct Net First Quantity reported should be 2.


348 WARN ERR - MISSING DOMESTIC/FOREIGN CODE
349 WARN ERR - INVALID DOMESTIC/FOREIGN CODE

Data Elements: Domestic/Foreign Code
Reason: The warning message occurs when the Domestic/Foreign Code reads other than ‘D’ or ‘F’.
Resolution: Commercial documentation or other competent information should be examined to verify whether the shipment is of domestic or foreign origin. Report ‘D’ for Domestic exports (defined as merchandise grown, produced, or manufactured (including imported merchandise that has been enhanced in value) in the United States). Report ‘F’ for Foreign exports (defined as merchandise that has entered the United States and is being re-exported in the same condition as when imported).


351 VERIFY - OUTDATED HS OR SCHED B NUMBER

Data Elements: HS or Schedule B Number
Reason: The Informational message occurs when the HS or Schedule B Number has expired. However, Census accepts the obsolete number for 30 days to give the filer time to update their classification.
Resolution: Commercial documentation or other competent information should be examined to verify that the HS or Schedule B Number is correctly reported. An up-to-date HS or Schedule B Number must be reported. Consult the Harmonized Tariff Schedule or the Schedule B - Classification of Exports or call the Foreign Trade Division, Bureau of the Census, Washington, DC (301) 457-2981 for classification assistance.


352 WARN ERR - INVALID PORT EXP FOR AIR

Data Elements: Port of Exportation, Mode of Transportation
Reason: A warning message occurs when the Port of Exportation code submitted is impossible for shipments exported by Air (MOT=40 or 41).
Resolution: Commercial documentation or other competent information should be examined to verify the U.S. Port of Exportation reported is an acceptable airport. The four-digit Schedule D Codes are presented in Schedule D of the Harmonized Tariff Schedule or Schedule B or in Appendix D of this document.


353 WARN ERR-INVALID PORT EXP FOR OVERLAND

Data Elements: Port of Exportation, Mode of Transportation
Reason: A warning message occurs when the Port of Exportation code submitted is impossible for overland shipments (MOT=20, 21, 30, 31).
Resolution: Commercial documentation or other competent information should be examined to verify the U.S. port of exportation reported is an acceptable land border port of export. The four-digit Schedule D Code are presented in Schedule D of the Harmonized Tariff Schedule or Schedule B or Appendix D of this document.


354 WARN ERR - UNLIKELY DATE OF EXPORT

Data Elements: Estimated Date of Export/Arrival
Reason: A warning message occurs when the Estimated Date of Export/Arrival exceeds 90 days from the current system date.
Resolution: Verify that the correct Estimated Date of Export/Arrival is reported. AES will accept estimated dates of export/arrival with-in 90 days of actual shipment.


355 WARN ERR - INVALID VIN FORMAT

Data Elements: Vehicle Identification Number, Vehicle ID Qualifier
Reason: A warning message occurs when the Vehicle Identification Number is not in the proper format as specified by the manufacturer of the vehicle.
Resolution: Commercial documentation or other competent information should be examined to verify that the Vehicle Identification Number was properly reported. The VIN reported in AES must be identical to the VIN on the used vehicle.


360 WARN ERR - TRANSPORTATION DATA REQUIRED

Data Elements: Conveyance Name, Vessel Flag, SCAC/IATA, MOT, Port of Export, Port of Unlading, Date of Departure, Equipment Number
Reason: A warning message occurs when one or more of the above data elements have not been received for the shipment.
Resolution: Transmit the transportation data.


361 WARN ERR - LICENSE IS EXHAUSTED

Data Elements: Value of Goods, License
Reason: The warning message occurs when the remaining license value is zero.
Resolution: License filed at Customs port, commercial documentation and/or other competent information should be examined to verify the remaining value of the license.


370 INFO ERR - FOR FUTURE USE

373 INFO ERR - POST-DEPATURE DATA OVERDUE

Data Elements: Filing Option Indicator, Date of Exportation (or Date of Arrival for shipments between the U.S. and Puerto Rico)
Reason: AES will automatically generate a reminder message every Tuesday to each filer whose post-departure submission is overdue. Filing Option 3 participants have up to five (5) working days to report complete SED information after the date of exportation on the Pre-departure filing before it is considered overdue.
Resolution: Transmit complete post-departure data within the required timeframe. Any post-departure data that has not been submitted should be sent to AES. It is the filer’s responsibility to ensure timely and complete reporting. AES will capture this reminder message and make it available for compliance reporting purposes.


374 INFO ERR - PRE-DEPARTURE DATA NOT FOUND
Date Elements: Filing Option Indicator, Correction Flag, Line Correction Flag, Shipment Reference Number
Reason: Upon receipt of a post-departure filing AES will match it with the corresponding pre-departure filing based on the Shipment Reference Number, i.e., the XTN. If a pre-departure record was not created prior to a post-departure filing, AES will generate this message and make it available for compliance reporting purposes.
Resolution: Pre-departure data will not be accepted after the post-departure record has been submitted to AES. It is the filer’s responsibility to understand and use the appropriate filing options. No further action is required on the part of the filer.


375 WARN ERR - NO PRE-DEPARTURE LICENSE INFO

Data Elements: Filing Option Indicator, License Code
Reason: AES verifies the error message and makes it available for compliance reporting purposes. No further action is required on the part of the filer.
Resolution: AES creates the error message and makes it available for compliance reporting purposes. No further action is required on the part of the filer.


8L1 VERIFY - VAL/QUANT 1 OUT OF RANGE LOW
8L2 VERIFY - VAL/QUANT 2 OUT OF RANGE LOW
8H1 VERIFY - VAL/QUANT 1 OUT OF RANGE HIGH
8H2 VERIFY - VAL/QUANT 2 OUT OF RANGE HIGH

Data Elements: HS or Schedule B, Quantity 1 and Unit of Measure 1, Quantity 2 and Unit of Measure 2, Value of Goods, Country of Ultimate Destination For example, VALUE/QUANTITY 1 OUT OF RANGE LOW means the ratio of the value to the first quantity is outside the normal range for that commodity. The ratio is too low.
Reason: The informational message occurs when the unit value of an item is not within expected parameters. The unit value is determined by dividing the value of goods by the reported quantity. For example, lawn-tennis balls, the number of tennis balls exported must be reported. If the HS number is shown with a value of $10,000 for 50 tennis balls, the value of each ball equals $200 ($10,000 / 50 each = $200 each). This is an unlikely price for a single tennis ball. Another example would be a guided missile with a unit value of $200.
Resolution: Commercial documentation or other competent information should be examined to verify the HS or Schedule B classification, reported quantities and value of goods is correct. Make certain the quantities are reported in metric units as required. Check any conversion, such as foreign currency to US dollars or unit conversions such as tons to kilograms. Retransmit with corrected information.


8PI VERIFY-IMPRB COMMODITY FOR FIXED TRNSPRT

Data Elements: HS or Schedule B, Mode of Transportation
Reason: The informational message occurs when the filer attempts to export certain commodities by fixed transport, i.e., pipeline or electrical energy. Only products classified for export under the following first two digits of the HS or Schedule B are acceptable: 22, 25, 27, 28, 29, 44, 47.
Resolution: Commercial documentation or other competent information should be examined to verify that the HS or Schedule B number is reported correctly. In addition, the MOT should be reviewed to ensure it is correctly reported.


8QR VERIFY - QUANT RELATION OUT OF RANGE

Data Elements: HS or Schedule B, Quantity 1 and Unit of Measure 1, Quantity 2 and Unit of Measure 2
Reason: The informational message occurs when the relationship between the two required quantities for the HS or Schedule B number is not within expected parameters. For example, sodium hydroxide in aqueous solution has ‘kg’ (kilograms) and ‘ckg’ (content kilograms) as the units of measure. The content kilograms should never be more that the net kilograms. Typewriter ribbons require net quantity in ‘doz’ (dozen) and ‘kg’ (kilograms) as the units of measure. One dozen ribbons are not going to weigh 100 kilograms.
Resolution: Commercial documentation or other competent information should be examined to verify the classification and quantities are correct. Check any unit conversions such as tons to kilograms or ounces to grams. Make certain the quantities are reported in metric units as required by the HS or Schedule B. Retransmit corrected information.


8Q1 WARN ERR - QUANTITY 1 EXCEEDS MAXIMUM
8Q2 WARN ERR - QUANTITY 2 EXCEEDS MAXIMUM

Data Elements: Quantity 1 and Unit of Measure 1, Quantity 2 and Unit of Measure 2
Reason: The warning message occurs when the quantities reported exceed the maximum allowed for the data element. Quantities this large are very unlikely.
Quantity 1 Maximum = 100,000,000
Quantity 2 Maximum = 100,000,000
The filer is expected to respond to these warning messages.
Resolution: Commercial documentation or other competent information should be examined to verify the correct quantity was entered in AES. Check for possible data input error. Note: Quantities should be reported in whole numbers only. Retransmit


8SO VERIFY - OTH MOT SWT TOO HIGH FOR COMMOD
8SR VERIFY - RAIL SWT TOO HIGH FOR COMMODITY
8ST VERIFY - TRCK SWT TOO HIGH FOR COMMODITY

Data Elements: HS or Schedule B, Shipping Weight (SWT), Mode of Transportation (MOT), SCAC/IATA
Reason: The informational message occurs for rail, truck and other modes of transportation shipments when the Gross Shipping Weight reported for the HS or Schedule B is too high based on normal gross shipping weight limitations for the reported method of transportation.
Resolution: Commercial documentation or other competent information should be examined to verify the HS or Schedule B, the MOT, and the Gross Shipping Weight is correct. Retransmit corrected information.


8SW WARN ERR - SHIP WEIGHT EXCEEDS MAXIMUM
Data Element: Shipping Weight
Reason: The warning message occurs when the Gross Shipping Weight reported exceeds the maximum allowed for the data element. A shipping weight this large is very unlikely.
Vessel Maximum = 135,000,000 kilograms
Air Maximum = 105,000 kilograms
Truck Maximum = 300,000,000 kilograms
Rail Maximum = 300,000,000 kilograms
Other Maximum = 300,000,000 kilograms
The transmitter is expected to respond to this warning message.
Resolution: Commercial documentation or other competent information should be reviewed to verify the Gross Shipping Weight is reported correctly. Check for possible data input error. Note: Shipping weight should be reported in kilograms, in whole numbers only. Retransmit corrected information.


8VL WARN ERR - VALUE OF GOODS EXCEEDS MAXIMUM
Data Element: Value of Goods
Reason: The warning message occurs when the Value of Goods reported exceeds the maximum allowed for the data element, normally $250,000,000. A value this large is very unlikely. The transmitter is expected to respond to this warning message.
Resolution: Commercial documentation or other competent information should be examined to verify the Value of Goods reported is correct. Check for possible data input error. Note: Value should be reported in whole dollars only, not dollars and cents. Retransmit corrected information.


8VW VERIFY - VALUE/SHIP WEIGHT OUT OF RANGE

Data Elements: HS or Schedule B, Value of Goods, Shipping Weight
Reason: The informational message occurs when the Value of Goods is divided by the Gross Shipping Weight and the price per kilogram is not within expected parameters for the HS or Schedule B classification.
Resolution: Commercial documentation and other competent information should be examined to verify the HS or Schedule B, Value of Goods and the Gross Shipping Weight are correct. Note: This edit is usually performed when the Unit of Measure 1 equals "X" (none required). Retransmit corrected information.


8W1 VERIFY - SHIP WGHT/QUANT 1 OUT OF RANGE
8W2 VERIFY - SHIP WGHT/QUANT 2 OUT OF RANGE

Data Elements: HS or Schedule B, Shipping Weight, Quantity 1 and Unit of Measure 1, Quantity 2 and Unit of Measure 2
Reason: The informational message occurs when the Gross Shipping Weight is divided by either Quantity 1 or Quantity 2 and the resulting ratio is not within expected parameters for that HS or Schedule B classification. Note: This edit is usually performed when the Unit of Measure is a net weight like kilograms or tons.
Resolution: Commercial documentation or other competent information should be examined to verify the gross shipping weight, quantities, and units of measure are correct.
Note: Shipping weight should always be reported as the gross weight, including packing. Quantity Units of Measure always require a net weight. Retransmit corrected information.


808 VERIFY - IMPROBABLE CTRY OF DESTINATION

Data Elements: Country of Ultimate Destination, Harmonized Tariff Schedule (HS) or Schedule B
Reason: The informational message occurs when certain commodities are unlikely to be exported to the specific country. For example, crude oil would not be exported to Saudi Arabia (SA), nor would snowmobiles be exported to Jamaica (JM).
Resolution: Commercial documentation or other competent information should be examined to verify that the country of ultimate destination and the HS/ Schedule B are correct. Retransmit corrected information.


809 WARN ERR - ZERO QUANTITY 1 UNACCEPTABLE
810 WARN ERR - ZERO QUANTITY 2 UNACCEPTABLE

Data Elements: HS or Schedule B, Quantity 1 and Unit of Measure 1, Quantity 2 and Unit of Measure 2
Reason: The warning message occurs when the reported Quantity 1 or Quantity 2 is zero and a quantity greater than zero is required by the HS/ Schedule B. The transmitter is expected to respond to these warning messages.
Resolution: Commercial documentation or other competent information should be examined to verify the HS/Schedule B classification, Quantity 1 and Unit of Measure 1, or Quantity 2 and Unit of Measure 2 are correct. Often the quantity is reported in the wrong units. Note: Occasionally the quantity may be reported as a fraction of a unit. In such cases, change the quantity to the next whole number. Retransmit corrected information.


821 VERIFY - VESS SWT TOO HIGH FOR COMMODITY
826 VERIFY - AIR SWT TOO HIGH FOR COMMODITY

Data Elements: HS or Schedule B, Shipping Weight, Mode of Transportation (MOT), SCAS/IATA
Reason: The informational message occurs for vessel and air shipments when the Gross Shipping Weight reported for the HS/Schedule B classification is too high based on normal gross vessel and air shipping weight limitations.
Resolution: Commercial documentation or other competent information should be examined to verify the HS/Schedule B classification, the Mode of Transportation, and the Gross Shipping Weight are correct. Retransmit corrected information.


835 VERIFY - VALUE TOO HIGH FOR COMMODITY
836 VERIFY - VALUE TOO LOW FOR COMMODITY

Data Elements: HS or Schedule B, Value of Goods
Reason: The informational message occurs when the Value of Goods reported for the HS/Schedule B classification is too high or too low based on normal expectations. For example, a value of $5,000 is too low for a passenger transport airplane. The value is too low for the commodity exported.
Resolution: Commercial documentation or other competent information should be examined to verify the HS/Schedule B and Value of Goods is correct. Retransmit corrected information.


837 VERIFY - QUANT 1 TOO HIGH FOR COMMODITY
838 VERIFY - QUANT 1 TOO LOW FOR COMMODITY
839 VERIFY - QUANT 2 TOO HIGH FOR COMMODITY
840 VERIFY - QUANT 2 TOO LOW FOR COMMODITY

Data Elements: HS or Schedule B, Quantity 1 and Unit of Measure 1, Quantity 2 and Unit of Measure 2
Reason: The informational message occurs when the quantities reported for the HS/Schedule B classification are either too high or too low based on normal expectations. For example, warships sailing under their own power are exported one at a time. A quantity greater than 1 would be too high for the commodity.
Resolution: Commercial documentation or other competent information should be examined to verify the HS/Schedule B classification, the reported Quantities and Units of Measure are correct. Retransmit corrected information.


850 VERIFY - IMPROB FOREIGN/DOMESTIC ORIGIN

Data Elements: HS or Schedule B, Foreign/Domestic Code
Reason: The informational message occurs when the commodity exported is unlikely to be of Domestic origin, Foreign origin, or in some cases, both Domestic and Foreign origin. For example, there are no Domestic exports of bananas; likewise there are no foreign exports of American pima cotton. Also, it is unlikely that live, fresh or chilled squid, regardless of origin, are exported because they spoil quickly.
Resolution: Commercial documentation or other competent information should be examined to verify that the HS/Schedule B classification and Foreign/Domestic Code are correct. Retransmit corrected information. Note that domestic exports represent merchandise grown, produced or manufactured in the United States (including imported merchandise which has been enhanced in value or changed from the form in which imported by further manufacture or processing in the United States). Foreign exports represent merchandise that has entered the United States and is being re-exported in the same condition as imported.

851 VERIFY - IMPROBABLE AIR/MAIL SHIPMENT

Data Elements: HS or Schedule B, Mode of Transportation, SCAC/IATA
Reason: The informational message occurs when the Mode of Transportation is air or mail, but the commodity is unlikely to be shipped by air or mail. For example, explosive substances, petroleum coke, coal of all classifications, rail locomotives, fire engines, yachts, and floating docks are unlikely to be shipped by air or mail.
Resolution: Commercial documentation or other competent information should be examined to verify that the HS/Schedule B classification and the Mode of Transportation are correct. Retransmit corrected information.


853 VERIFY - IMPROB CTRY FOR MILITARY GOODS

Data Elements: Country of Ultimate Destination, HS or Schedule B
Reason: The informational message occurs when military commodities are exported to the countries of Armenia (AM), Azerbaijan (AZ), Byelarus (BY), Cuba (CU), Georgia (GE), Iran (IR), Iraq (IQ), Kazakhstan (KZ), Kyrgyzstan (KG), Libya (LY), Moldova (MD), Mongolia (MN), North Korea (KP), Russia (RU), Syria, (SY), Tajikistan (TJ), Turkmenistan (TM), Ukraine (UK), Uzbekistan (UZ), Vietnam (VN), Burma (MM), China (CN), Haiti (HT), Liberia (LR), Rwanda (RW), Somalia (SO), Sudan (SD), Yugoslavia (YU), or Zaire (ZR) since trade in these commodities with these countries is unlikely. This list of countries was last updated September 1, 1997.
Resolution: Commercial documentation or other competent information should be examined to verify the country of ultimate destination and the HS/Schedule B classification are correct. Retransmit corrected information.


993 FATAL ERRORS - TRANSMISSION REJECTED

Reason: This message occurs due to the submission of inaccurate or incomplete data that results in fatal errors 001 - 020.
Resolution: Follow the instructions in the resolution of the specific fatal error message 001- 020. The entire transmission must be resent. Example: If you have a transmission with 50 shipment records and any one of the 50 shipments receives 993, all 50 shipments must be resent after the error is corrected.


994 FATAL ERRORS - MUST RETRANSMIT SHIPMENT

Reason: This message occurs due to the submission of inaccurate or incomplete data that results in fatal errors 021 - 299. The accompanying error message specifies the specific cause of the fatal error. Since it is a fatal error, no data was accepted and the shipment must be retransmitted.
Resolution: Follow the instructions in the resolution of the specific error message, 021 to 299. Retransmit shipment after correcting errors.


995 SHIPMENT ACCEPTED - MUST CORRECT WARNINGS

Reason: This message occurs due to invalid or missing data. The accompanying error message specifies the specific data item that is missing or invalid. The shipment was accepted, but the data element in question should be corrected and the shipment must be retransmitted.
Resolution: Follow the instructions in the resolution of the specific error message. Retransmit corrected information within four days of departure of the shipment.


996 SHIPMENT ACCEPTED - MUST VERIFY DATA

Reason: This message occurs because data is inconsistent. The accompanying error message specifies the specific data item that is unlikely to be valid. The shipment was accepted, but the data element in question must be verified and if found to be incorrect, the shipment must be retransmitted.
Resolution: Follow the instructions in the resolution of the specific error message. Retransmit corrected information if necessary.


997 AES DATA RECEIVED WITHOUT ERRORS

Reason: This message notifies the participant that the shipment was accepted as transmitted without errors.


R01 ALERT: REMINDER -- UNRESOLVED WARNINGS

Reason: This message alerts the participant that there are unresolved warnings that were not corrected prior to the fourth day after exportation.
Resolution: Send corrections to the errors specified in the reminder.


R02: ALERT: MUST VERIFY/CORRECT BY FRIDAY

Reason: This message accompanies R01. It alerts the participant that the unresolved warnings must be corrected by the upcoming Friday.
Resolution: Send corrections to the errors specified in the reminder by Friday.

U.S. Census Bureau Foreign Trade Logo U.S. Department of Commerce

[top of page]