July 18, 2019
Tips on How to Resolve AES Response Messages
 When a shipment is filed to the AES, a system response message is generated and indicates whether the shipment has been accepted or rejected. If the shipment is accepted, the AES filer receives an Internal Transaction Number (ITN) as confirmation. Though the shipment is accepted, the filer may still receive a Verify Message, Compliance Alert, Informational Message or Warning Message along with their ITN. However, if the shipment is rejected, a Fatal Error notification is received and must be corrected to receive a valid ITN.
To help you take the appropriate action for the different AES Response Messages, here are some tips on how to address the most frequent messages that were generated in AES for this month.
Response Code: 341
Narrative: Ultimate Consignee Must Be Reported Within 4 Days
Severity: Warning
Reason: The Ultimate Consignee was reported as “To Be Sold en Route”.
Resolution: Incomplete ultimate consignee information may be declared on an EEI when a “To Be Sold en Route” declaration has been made. However, the actual ultimate consignee must be declared within 4 days of the EEI transmission and approval by the AES.
Verify the ultimate consignee information, correct the shipment and resubmit.
Response Code: 835
Narrative: Value of Goods Too High for Commodity
Severity: Verify
Reason: For the reported Schedule B/HTS Number, the Value of Goods is too high for the commodity reported.
Resolution: For a particular Schedule B/HTS Number declared, the value of goods is higher than expected for the commodity based on historical statistical values for the particular goods. Value of Goods higher than this pre-determined parameter might indicate either a keying error or misclassification of the product.
Verify the Value of Goods and Schedule B/HTS Number, correct the shipment and resubmit (if necessary). If the line item is verified correct as reported, no action is necessary.
|
