Tips on How to Resolve AES Fatal Errors


(Source:, 18 May 2017.)

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. However, if the shipment is rejected, a Fatal Error notification is received.

To help you resolve AES Fatal Errors, here are some tips on how to correct the most frequent errors that were generated in AES for this month.

Fatal Error Response Code: 136

  • Narrative: PR to US Requires PR Port of Export
  • Reason: The Country of Destination is reported as the Unites States and the Port of Export Code is not a Puerto Rican port.
  • Resolution: A Port of Export Code must be reported on shipments from Puerto Rico to the United States and it must be a Puerto Rican port. See Appendix D, Export Port Codes for a list of acceptable Port of Export Codes. Verify the Country of Ultimate Destination and Port of Export Code, correct the shipment and resubmit.

Fatal Error Response Code: 538

  • Narrative: Shipping Weight Must Be Greater Than Zero For MOT
  • Reason: The Mode of Transportation Code reported was one that identifies a Vessel, Rail, Truck, or Air shipment and the Shipping Weight was not reported.
  • Resolution: When the Mode of Transportation is Vessel, Rail, Truck or Air, the Shipping Weight must be reported. Verify the Mode of Transportation and Shipping Weight, correct the shipment and resubmit.

For a complete list of Fatal Error Response Codes, their reasons, and resolutions, see Appendix A – Commodity Filing Response Messages.

It is important that AES filers correct Fatal Errors as soon as they are received in order to comply with the Foreign Trade Regulations. These errors must be corrected prior to export for shipments filed predeparture and as soon as possible for shipments filed postdeparture but not later than five calendar days after departure.

For further information or questions, contact the U.S. Census Bureau’s Data Collection Branch.

Comments are closed.