Archive for the ‘AES’ Category

Tips on How to Resolve AES Fatal Errors

2018/05/30

(Source: census@subscriptions.census.gov)

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

  • Narrative: Quantity 2 Must Be Greater Than Zero
  • Reason: The Schedule B/HTS number reported requires a second Quantity to be reported and the Quantity 2 is missing or reported as zero.
  • Resolution: Quantity 2 must be greater than zero.

Verify the Quantity 2, 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 predeparture 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.


Tips on How to Resolve AES Fatal Errors

2018/04/04

(Source: census@subscriptions.census.gov)

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

  • Narrative: Port of Unlading Missing
  • Reason: The Port of Unlading Code is missing. All vessel shipments, and any air shipments between the United States and Puerto Rico must provide a Port of Unlading Code.
  • Resolution: The Port of Unlading Code is the foreign port where the exported merchandise is unloaded from the exporting carrier. Report a valid Port of Unlading Code for all vessel shipments, and any air shipments between the United States and Puerto Rico. Verify the Port of Unlading Code, 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


Tips on How to Resolve AES Fatal Errors

2018/02/08

Source: census@subscriptions.census.gov

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

  • Narrative: Country of Ultimate Destination Unknown
  • Reason: The Country of Ultimate Destination reported is not valid in AES.
  • Resolution: The Country of Ultimate Destination Code must be a valid ISO country code listed in the ‘Appendix C, ISO Country Codes’.  Verify the Country of Ultimate Destination, 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 predeparture 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.


Tips on How to Resolve AES Fatal Errors

2018/02/08

Source: census@subscriptions.census.gov

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

  • Narrative: Country of Ultimate Destination Unknown
  • Reason: The Country of Ultimate Destination reported is not valid in AES.
  • Resolution: The Country of Ultimate Destination Code must be a valid ISO country code listed in the ‘Appendix C, ISO Country Codes’.  Verify the Country of Ultimate Destination, 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 predeparture 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.


New Schedule B Numbers Have Arrived

2018/02/08

Source: Global Reach Blog

The Schedule B commodity classification codes for export have been updated for 2018. Codes are updated every January and July at the 10-digit level. In this blog, we will explore three resources available on our website to help you navigate these updates. All resources can be found online.

Schedule B Book

From our web site the new 2018 Schedule B book is available in the red box labeled “Browse” in HTML and PDF formats. Simply click on the link “Look through HTML or PDF versions of Schedule B book content” next to 2018 to browse section and chapter notes and Schedule B numbers by chapter.

All current and historic codes added or removed from the Schedule B going back to the last major revision, in January 2017, can be found in the “Add/Delete List” under “Browse chapters.”

 

Obsolete Codes List

Outdated Schedule B codes are available in the red box labeled “Obsolete Codes.” The “Obsolete to New” list is a quick way to see which codes are no longer valid, starting January 2018, and which new codes replaced them.

Notice that from 2016 forward, there were obsolete codes in both January and July. Before 2016, the Schedule B numbers were only updated annually.

 

Schedule B Search Engine

The third resource available is the Schedule B Search Engine.

Type a Schedule B number into the search engine, and if it appears, then the number is still valid. However, if the number is outdated, the search engine will show “No Results” for the code.

For more information on the new Schedule B numbers visit International Trade online; call the International Trade Help Line at 800-549-0595, Option 2 for Commodity Classification Assistance; or email eid.scheduleb@census.gov.


Tips on How to Resolve AES Fatal Errors

2017/11/15

(Source: census@subscriptions.census.gov, 19 Oct 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: 128

  • Narrative: Port of Export Unknown
  • Reason: The Port of Export Code reported is not valid in AES.
  • Resolution: The Port of Export Code must be valid in AES. Valid Port of Export Codes reportable in AES are contained in Appendix D – Export Port Codes. Verify the Port of Export Code, correct the shipment and resubmit.

Fatal Error Response Code: 147

  • Narrative: Routed Export Indicator Missing
  • Reason: The Routed Export Indicator is missing.
  • Resolution: A routed export transaction is a transaction in which the Foreign Principal Party in Interest (FPPI) authorizes a U.S. agent to facilitate the export of items from the United States and to prepare and file Electronic Export Information (EEI). You must report the Routed Export Indicator as Yes or No. Verify whether or not this is a routed export transaction, 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


Tips on How to Resolve AES Fatal Errors

2017/06/08

(Source: census@subscriptions.census.gov, 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.


The Automated Export System (AES) has a New Data Element

2017/06/08

(Source: Global Reach Blog)

The U.S. Census Bureau published the Final Rule entitled, “Foreign Trade Regulations (FTR): Clarification on Filing Requirements,” April 19.

This rule addresses new export reporting requirements related to the International Trade Data System and includes the addition of a new data element, the original Internal Transaction Number (ITN) that can be reported in the Automated Export System (AES). The original ITN field is an optional data element that can be used when a previously filed shipment is replaced, divided or cancelled.

The Census Bureau decided to add the original ITN data element to address situations when a party involved in an export transaction received penalties for shipments that were originally filed on time, but whose shipments were divided while in transit to the ultimate consignee. This data element makes it possible for U.S. Customs and Border Protection (CBP) to identify AES filings that are associated with previously filed shipments. Prior to the original ITN field, CBP was unable to determine if a shipment, identified as late, was associated with a shipment originally filed in accordance with the FTR. The inclusion of the original ITN field will enable parties in an export transaction to proactively provide CBP with additional information and will allow CBP to conduct a more thorough review of these types of shipments prior to assessing any penalties.

Let’s take a look at an example of how the original ITN field can be used. A foreign buyer in Italy purchases $20,000 worth of jewelry from a U.S. seller. The U.S. seller ships the jewelry to the buyer, but while in transit the seller is contacted by the buyer who now only wants $8,000 worth of jewelry. The seller then finds a new buyer in Sweden for the remaining $12,000 worth of jewelry. The originally filed AES record needs to be updated to reflect the value of $8,000 for the buyer in Italy. Additionally, a new AES record is created for the new buyer in Sweden. This new filing would generate a late filing compliance alert.  However, to ensure CBP is aware that the new shipment was filed prior to exportation in accordance with the FTR, the filer can include the previously filed ITN in the original ITN field.

For more information, contact the International Trade Management Division Call Center at 1-800-549-0595. Select option 3 for the Trade Regulations Branch.


AES Changes Impacted by Export Control Reform Implementation Rules

2017/03/30

(Source: census@subscriptions.census.gov, 22 February 2017.)

On July 28, 2016 and October 12, 2016, the Department of Commerce, Bureau of Industry and Security published final rules (available at here and here) that became effective December 31, 2016. As a result of these rules, the following changes were made to the Automated Export System (AES) in order for exporters and authorized agents to successfully report electronic export information in the AES.
(1) The Addition of “600 series” Export Control Classification Numbers (ECCN)

600-series ECCNs 1A607, 1B607, 1C607, 1D607, 1E607, 6B619, 6D619, 6E619, 7A611, 7B611, 7D611, and 7E611 were added to the AES ECCN reference table. See the following instructions to determine which “600 series” ECCNs are eligible for certain license types. By using any of the License Exceptions or “No License Required” (NLR), you are certifying that the terms, provisions, and conditions described in the EAR have been met.

  • C30 (BIS license), C40 (TMP), C41 (RPL), C42 (GOV), and C59 (STA) – All “600 series” ECCNs listed above are eligible to the extent permitted under part 740 of the EAR.
  • C33 (NLR) – All “600 series” ECCNs listed above are eligible only if exported to Canada. Some of these “600 series” items were previously authorized under an International Traffic in Arms Regulations (ITAR) Canadian exemption (SCA).
  • C35 (LVS) – The following “600 series” ECCNs are eligible: 1B607, 6B619, 7A611, and 7B611.
  • C44 (TSU) – The following “600 series” ECCNs are eligible: 1D607, 1E607, 6D619, 6E619,7D611, and 7E611.

 

If the “600 series” ECCNs are reported under any other license type, AES will generate a fatal error (FATAL ERR 666-ECCN MUST BE FROM APPROVED LIST) back to the filer. Please note that under 758.1 of the EAR, an AES filing is required for exports of items classified under “600 series” ECCNs, regardless of the value of the item or destination.
(2) Items subject to the EAR, including “600 series” ECCNs that are licensed by the State Department under the International Traffic in Arms Regulations (ITAR)

Under a delegation of authority, the State Department may license an item subject to the EAR on an ITAR license pursuant to new section 120.5(b) of the ITAR. If this occurs, the AES filer must report the ECCN (including “600 series” ECCNs) or the EAR99 designation in the ECCN field in AES, even if the license type is S05 (DSP-5). All other fields associated with license type S05 are required, such as registration number, significant military equipment indicator, DDTC eligible party certification indicator, USML category code, DDTC unit of measure and DDTC quantity.

A complete list of all of the AES License Type codes and reporting instructions for these types can be found at here.

For questions regarding these upcoming AES changes, please contact the Bureau of Industry and Security by email at ECR_AES@bis.doc.gov or at one of the phone numbers below.

  • Office of Technology Evaluation (located in Washington, DC): (202) 482-4933
  • 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

Tips on How to Resolve AES Fatal Errors

2017/03/02

2017/03/02

(Source: census@subscriptions.census.gov, 18 Jan 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: 336

  • Narrative: Ultimate Consignee State Cannot be Reported
  • Reason: The Country of Destination reported does not allow a State Code.
  • Resolution: Report a State Code only if the Country of Destination is the United States or Mexico. Verify the Ultimate Consignee Country Code and State Code, correct the shipment and resubmit.

 

Fatal Error Response Code: 503

  • Narrative: The Port of Unlading Code is missing. All vessel shipments, and any air shipments between the United States and Puerto Rico must provide a Port of Unlading Code.
  • Reason: The Port of Unlading Code is missing. All vessel shipments, and any air shipments between the United States and Puerto Rico must provide a Port of Unlading Code.
  • Resolution: The Port of Unlading Code is the foreign port where the exported merchandise is unloaded from the exporting carrier. Report a valid Port of Unlading Code for all vessel shipments, and any air shipments between the United States and Puerto Rico. Verify the Port of Unlading Code, 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.