Archive for the ‘AES’ Category

Tips on How To Resolve AES Fatal Errors

Wednesday, October 12th, 2016 by Danielle McClellan

2016/10/12

(Source: census@subscriptions.census.gov, 22 Sep 2016)

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: 331

  • Narrative: Ultimate Consignee Country Unknown
  • Reason: The Ultimate Consignee Country code reported is not valid in AES.
  • Resolution: The Ultimate Consignee Country code must be a valid ISO Country code found in Appendix C – ISO Country Codes. Verify the Ultimate Consignee Country code, correct the shipment, and resubmit.

* Fatal Error Response Code: 628

  • Narrative: 1st Unit of Measure Code/Schedule B/HTS Mismatch
  • Reason: The Unit of Measure (1) reported does not match the Unit of Measure (1) required for the Schedule B/HTS Number reported.
  • Resolution: The Unit of Measure (1) must match exactly the Unit of Measure (1) prescribed by the Schedule B/HTS Number reported. See Appendix K – Units of Measure Codes.  Verify the Unit of Measure (1) required for the reported Schedule B/HTS Number, 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 pre departure and as soon as possible for shipments filed post departure, but not later than five calendar days after departure.

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

Say Good Bye to License Type C32…and Get to Know C33

Tuesday, July 12th, 2016 by Danielle McClellan

2016/07/12

By: Danielle McClellan

Effective October 1, 2016, the Bureau of Industry and Security (BIS) will remove license type C32, No License Required (NLR), from the list of License Types found in the Automated Export System (AES). Beginning October 1, 2016, C33 will be the only License Type in AES designating a NLR shipment. Changes to License Type C32 designated Electronic Export Information (EEI) will be accepted in AES for 6 months after the October 1, 2016 effective date.

United States Principal Parties in Interest (USPPIs) and their authorized filing agents (AES filers) must adhere to the Export Controls Classification Number (ECCN) reporting requirements for NLR designated shipments under C33 as per the EAR 758.1(g) (3).

Items that have a reason for control other than or in addition to Anti-Terrorism (AT), should report NLR (C33) as the license type in the EEI filing.

A complete list of AES License Type Codes is available at: https://www.cbp.gov/sites/default/files/assets/documents/2016-Jun/Appendix_F.pdf

For questions regarding these AES changes, please contact the Bureau of Industry and Security by email at ECR_AES@bis.doc.gov or at (202) 482-4933.

For general questions regarding AES, please contact the International Trade Management Division at the Bureau of the Census at 1-800-549-0595, option 1.

For classification questions about ECCNs, please contact the Bureau of Industry and Security at one of the numbers below:

  • Outreach and Educational Services Division (located in Washington, DC) (202) 482-4811
  • Western Regional Office (located in Irvine, CA) (949) 660-0144
  • Northern California branch (located in San Jose, CA) (408) 998-8806

AESDirect Accounts with Prefixes “60-79 and “80-99” Are Now Deactivated

Thursday, May 5th, 2016 by Danielle McClellan

2016/05/05

(Source: census@subscriptions.census.gov, 21 Apr 2016)

This message is not intended for filers using AESWebLink and AESDirect EDI Upload. It is strictly for the attention of filers using the legacy AESDirect portal at aesdirect.census.gov and the AESPcLink application.

On Monday April 11th at 12:01 AM ET Legacy AESDirect Accounts with prefixes “60-79” were deactivated.

On Monday April 25th at 12:01 AM ET Legacy AESDirect Accounts with prefixes “80-99” were deactivated.

The Refactored AESDirect system in the Automated Commercial Environment was launched on November 30, 2015. Since that time, filers have submitted over 950,000 accepted shipments using the new system.

As part of the transition of AESDirect to the ACE Portal, the ability to file Electronic Export Information via legacy AESDirect at aesdirect.census.gov and the AESPcLink application will be terminated in stages over the next month. All legacy AESDirect filers have been notified of their mandatory transition date to the Refactored AESDirect system upon login and have been provided a specific date their account will be closed off based upon their Filer ID.

As a reminder, your filing in the Refactored AESDirect system does not require vetting or Reports Authorization. Vetting is only required for those companies looking to obtain export reports access outside of the AESDirect Shipment Manager. For more information regarding the transition, please see our AESDirect Transition to ACE – Refactored AESDirect page.

Please make sure you have secured ACE Exporter access and have taken the necessary steps to begin filing in the Refactored AESDirect system in ACE prior to your mandatory transition date. For questions regarding your ACE Account access, please contact the CBP Accounts Service Desk at 1-866-530-4172 option 1, then option 2 or ACE.Support@cbp.dhs.gov.
Please expect 15 to 30 minute waiting times during this transition period.
Complete Transition Schedule:

  • Prefixes 00-19 on 02/29/2016
  • Prefixes 20-39 on 03/14/2016
  • Prefixes 40-59 on 03/28/2016
  • Prefixes 60-79 on 04/11/2016
  • Prefixes 80-99 on 04/25/2016

Once your account is deactivated, there will be no further access to legacy AESDirect to file or amend Electronic Export Information. You will only have access to the Shipment Manager application to view previously submitted shipments. The access to the Shipment Manager Application (for viewing submitted shipments) will be available for all users until May 20, 2016.

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

Legacy AESDirect Accounts with prefixes “20-39” Now Deactivated!

Wednesday, April 6th, 2016 by Danielle McClellan

2016/04/06

By: Danielle McClellan

On March 14, 2016, Legacy AESDirect Accounts with prefixes “20-39” will be deactivated. AESPcLink applications will be terminated in stages over the next two months. All legacy AESDirect filers have received notices about the mandatory transition date to the Refactored AESDirect system upon login and have provided a specific date their account will be closed off based upon their Filer ID.

Complete Transition Schedule:

  • Prefixes 00-19 on 02/29/2016
  • Prefixes 20-39 on 03/14/2016
  • Prefixes 40-59 on 03/28/2016
  • Prefixes 60-79 on 04/11/2016
  • Prefixes 80-99 on 04/25/2016

Once your account is deactivated, there will be no further access to legacy AESDirect to file or amend Electronic Export Information. You will only have access to the Shipment Manager application to view previously submitted shipments.

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

  • Telephone: (800) 549-0595, select option 1 for Data Collection Branch
  • Email: askaes@census.gov
  • Online: www.census.gov/trade.
  • Blog: globalreach.blogs.census.gov

Tips on How to Resolve AES Fatal Errors

Tuesday, March 29th, 2016 by Danielle McClellan

2016/03/29

(Source: census@subscriptions.census.gov, 18 Feb 2016)

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: 123

  • Narrative: Conveyance Name Missing
  • Reason: The Conveyance Name/ Carrier Name is missing when the Mode of Transportation reported is one that requires the Conveyance Name/ Carrier Name to be Reported.
  • Resolution: The Conveyance Name/ Carrier Name must be reported for Vessel, Air, Rail, and Truck shipments. For Vessel shipments, report the name of the vessel. For Air, Rail, and Truck shipments, report the name of the carrier. Verify the Mode of Transportation Code and Conveyance Name/ Carrier Name, correct the shipment and resubmit.

Fatal Error Response Code: 133

  • Narrative: Port of Export Must Be An Air Port
  • Reason: The Port of Export reported is not allowed for Air shipments.
  • Resolution: The Port of Exportation Code reported must accommodate the mode of transport reported in the shipment. See Appendix D, Export Port Codes for a list of acceptable Port of Exportation Codes and their corresponding modes of transportation. Verify the Port of Exportation code and Mode of Transportation Code combination, 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.

Transition to the Refactored AESDirect System in ACE

Wednesday, February 3rd, 2016 by Danielle McClellan

2016/02/03

(Source: census@subscriptions.census.gov, 14 Jan 2016)

This message is not intended for filers using AESWebLink and AESDirect EDI Upload. It is strictly for the attention of filers using the legacy AESDirect portal at aesdirect.census.gov and the AESPcLink application.

The Refactored AESDirect system in the Automated Commercial Environment was launched on November 30, 2015. Since that time, filers have submitted over 47,000 accepted shipments using the new system.

As part of the transition of AESDirect to the ACE Portal, the ability to file Electronic Export Information via legacy AESDirect at aesdirect.census.gov and the AESPcLink application will be terminated in stages over the next two months. All legacy AESDirect filers will be notified of their mandatory transition date to the Refactored AESDirect system upon login and be provided a specific date their account will be closed off based upon their Filer ID.

The dates for this transition are based upon the two-digit prefix of the Filer ID and accounts will be closed off from legacy AESDirect accordingly.

  • Prefixes 00-19 on 02/15/2016
  • Prefixes 20-39 on 02/22/2016
  • Prefixes 40-59 on 02/29/2016
  • Prefixes 60-79 on 03/07/2016
  • Prefixes 80-99 on 03/14/2016

Please make sure you have taken steps to begin filing in the Refactored AESDirect system in ACE prior to your mandatory transition date.

For more information regarding the transition, please see our AESDirect Transition to ACE – Refactored AESDirect page here.

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

Tips on How to Resolve AES Fatal Errors

Wednesday, February 3rd, 2016 by Danielle McClellan

2016/02/03

(Source: census@subscriptions.census.gov, 19 Jan 2016)

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: 515

– Narrative: ECCN Must be Formatted NANNN

– Reason: The Export Control Classification Number (ECCN) was not reported in the correct format.

– Resolution: The Export Control Classification Number (ECCN) must be reported in a NANNN format, where N is a numeric character and A is an alpha character. Verify the ECCN, correct the shipment and resubmit.

 

Fatal Error Response Code: 561

– Narrative: DDTC License Number Unknown

– Reason: The License Code/ License Exemption Code reported requires a Department of State/ Directorate of Defense Trade Controls (DDTC) license number, but the DDTC license number reported is unknown in AES.

– Resolution: The DDTC license number reported must be valid in AES. Verify the DDTC license number, correct the shipment and resubmit. For further assistance, contact the licensing agency. The Department of State/ Directorate of Defense Trade Controls / DDTC Help Desk can be reached on 202-663-2838.

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.

ACE Export Reports Access Tips

Wednesday, February 3rd, 2016 by Danielle McClellan

2016/02/03

The Census Bureau has released a few helpful tips to make the vetting process for obtaining authorization to access your export data in ACE a little easier.

Some helpful tips:

  • Vetting by the Census Bureau Team is NOT required to file Electronic Export Information (EEI) via AESDirect in ACE.
  • Only request “EIN Reports Authorization” if you want to access export reports in ACE.
  • Newly established export accounts without prior filing history at the EIN level will not be authorized to access export reports in ACE.
  • EINs associated with an established ACE Importer Account do not require further vetting by the Census team, therefore do not select the feature “Requests EIN Reports Authorization” when adding the exporter role to an existing account.
  • Submit the Certificate of Authority (COA) for subsidiaries that plan on retrieving export reports. Prior filing history for each requested EIN is required.
  • If you have multiple EINs associated with an account, request access for each EIN and submit a comprehensive COA listing the subsidiaries requesting access.
  • In addition, shipment information must be verified by the Census Team prior to obtaining approval for Reports Authorization.

The information provided in this broadcast will assist you in obtaining Export Reports Access. Please visit our website for additional information on obtaining Exports Reports authorization by the Census Bureau here.

For additional assistance, call the International Trade Helpline at 800-549-0595:

AESDirect Is Now Available in ACE!!!

Tuesday, January 19th, 2016 by Danielle McClellan

2016/01/19

(Source: census@subscriptions.census.gov)

Attention all export filers… the new AESDirect is available in ACE for export filing.

If you have ACE Exporter Account access, you can begin filing using the new system. If you have not yet obtained ACE Exporter Account access, please review the broadcast message covering ACE registration and exporter access.

Today marks the beginning of the transition from the legacy AESDirect application to the Refactored AESDirect in ACE. During this transition period, both the legacy and the ACE AESDirect application are available for export filing. Take advantage of this time and begin transitioning your users to the new system. Please ensure proper transition management to avoid duplicate filing.

For more information, including the new user guide, FAQs, archived broadcast messages, training materials, etc. please check out the ACE Transition page. The ACE One-Pager also has a wealth of contact information and resource links to assist you with this transition.

Note: If you have technical issues filing in the new system, please contact the AES Help Desk at askaes@census.gov or 800-549-0595, option 1.

If you have technical issues with your ACE Accounts Access, please contact the ACE Service Desk at ACE.Support@cbp.dhs.gov or 1-866-530-4172, option 1, then option 2.

Guidance on WebLink and EDI batch filing will be provided within the next 2 weeks. This deployment is for Portal and Bulk Upload filing through AESDirect only.

Tips on How to Resolve AES Fatal Errors

Tuesday, January 19th, 2016 by Danielle McClellan

2016/01/19

(Source: census@subscriptions.census.gov, 21 Dec 2015)

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: 256

  • Narrative: USPPI Postal Code Not Valid for State
  • Reason: The Postal Code and State Code reported in the USPPI Address do not match.
  • Resolution: The reported USPPI State Code must match the state associated to the Postal Code.

Verify the USPPI State Code and Postal Code combination, correct the shipment and resubmit.

* Fatal Error Response Code: 649

  • Narrative: Quantity 1 Cannot Exceed Shipping Weight
  • Reason: Shipping Weight is reported in kilograms. When the Unit of Measure 1 requires kilograms, the first net quantity (Quantity 1) cannot exceed the Shipping Weight. Ensure the Shipping Weight includes the weight of the packaging materials.
  • Resolution: The first net quantity (Quantity 1) in kilograms cannot exceed the Shipping Weight in kilograms. Verify the Quantity 1 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 pre departure and as soon as possible for shipments filed post departure, but not later than five calendar days after departure.
For further information or questions, contact the U.S. Census Bureau’s Data Collection Branch.