Archive for the ‘AES’ Category

Tips on How to Resolve AES Fatal Errors

Wednesday, November 15th, 2017 by Danielle McClellan

(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

Thursday, June 8th, 2017 by Danielle McClellan

(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

Thursday, June 8th, 2017 by Danielle McClellan

(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

Thursday, March 30th, 2017 by Danielle McClellan

(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

Thursday, March 2nd, 2017 by Danielle McClellan

(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.

Understanding Routed Export Transactions

Tuesday, January 31st, 2017 by Danielle McClellan

(Source: Global Reach Blog)

Routed export transactions are a much discussed topic.  Therefore, we are revisiting this blog topic to give some helpful tips on remaining compliant if you’re involved in a routed export transaction. We’ll also take a look at an example.  For those not familiar with routed export transactions, it is when the Foreign Principal Party in Interest (FPPI) directs the movement of the goods out of the U.S. and authorizes a U.S. agent to file the Electronic Export Information (EEI) on their behalf.

Below are some helpful tips to keep in mind: 

  • Communication is key!  Having conversations with all parties involved before the transaction occurs will make a difference in understanding roles and responsibilities to prevent filing errors in the Automated Export System (AES);
  • Refer to Sections 30.3(e), (e)(1) and (e)(2) of the Foreign Trade Regulations (FTR) for the definition and more information on the responsibilities of the parties involved in a routed transaction;
  • Utilize the Census Bureau resources; and
  • View sample templates for the power of attorney and written authorization on our website here or here.

Routed Export Transaction Example:

A U.S. Principal Party in Interest (USPPI) sells two paintings to a FPPI located in Italy.  Keep in mind, the USPPI is defined as the person or legal entity in the U.S. that receives the primary benefit, monetary or otherwise, from the transaction. The FPPI instructs the USPPI to send the paintings to an agent located in Florida.  The FPPI authorizes the agent to file the EEI in the AES on their behalf and ship the goods to Italy.  In this example, each party has important responsibilities that are outlined below.

FPPI

  • Provides the agent, who is authorized to file the EEI, with a power of attorney or written authorization, the authorization comes after the FPPI provides the POA or written authorization.

USPPI

  • Provides the agent with the data elements, such as Schedule B number, value, quantity, etc., specified in Section 30.3(e)(1) of the FTR.
  • Retains documentation to support the information provided to the authorized agent for five years from the date of export.
  • Requests a copy of the data elements that were filed in the AES and the power of attorney or written authorization.

Authorized Agent

  • Ensures that a power of attorney or written authorization is received from the FPPI.
  • Files the EEI in the AES.
  • Provides the Internal Transaction Number or exemption code if filing is not required to the carrier.
  • Retains documentation pertaining to the shipment for 5 years.
  • If requested, provides the USPPI with a copy of the USPPI data elements that were filed in the AES and the power of attorney or written authorization from the FPPI. For further questions, please contact the Trade Regulations Branch (TRB) at 1-800-549-0595, option 3 or email us at itmd.askregs@census.gov

Tips on Setting up an Account in the Automated Commercial Environment

Tuesday, December 20th, 2016 by Danielle McClellan

(Source: Global Reach Blog)

This blog provides a few tips to address some common questions and issues for those who set-up exporter accounts in ACE on behalf of a client, authorized agents and freight forwarder roles, as well as with existing ACE importer accounts. Exporter accounts and the AESDirect filing system now reside in the Automated Commercial Environment (ACE).

Exporter Roles

“Exporter” is an account type within the ACE account structure used for all export related roles including:

  • Authorized agent
  • Freight forwarder
  • Exporting company (U.S. Principal Party in Interest)

When you register in the ACE, you will also be registering for an ACE Exporter Account, regardless of your role in the export transaction.

 

Filing on Behalf of a Client

When filing on behalf of another company, the U.S. Principal Party in Interest (USPPI) section in ACE should be completed the same way it was for the legacy AESDirect system. An additional USPPI Employee Identification Number (EIN) should only be added to a top account for company subsidiaries. Authorized agents and freight forwarders should not add an USPPI EIN to their account.

 

Account Structure for Authorized Agents and Freight Forwarders

A USPPI will not be able to register in ACE if a forwarder or agent added the USPPI’s EIN to their ACE Top Account. The USPPI will not be able to get access to AESDirect or their ACE Export Reports.  If you notice this issue, the forwarder or agent must call the ACE Account Service Desk at 1-866-530-4172, option 1, then option 2 to submit a service ticket to solve this issue.

 

Existing ACE Importer Accounts

Any company with an existing ACE Importer Account needs to add the exporter role to their account to get instant access to their export reports. No vetting would be required in this case.

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

  • Telephone: (800) 549-0595; select option 1 for AES.
  • Email: askaes@census.gov
  • International Trade Management Division Website

Tips on How to Resolve AES Fatal Errors

Tuesday, November 15th, 2016 by Danielle McClellan

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

  • Narrative: State of Origin Unknown
  • Reason: The U.S. State of Origin indicated is not valid in AES.
  • Resolution: The U.S. State of Origin Code must be a valid two-character U.S. state, territory, or possession code (i.e., any USPS code). Verify the State of Origin, correct the shipment and resubmit.

Fatal Error Response Code: 572

  • Narrative: DDTC Registrant Expired
  • Reason: The DDTC Registration Number reported is not valid in the AES at the time of export.
  • Resolution: When the License Code/License Exemption Code indicates a Department of State – Directorate of Defense Trade Controls (DDTC) license (SAG, SCA, S00, S05, S61, S73, S85 or S94), the DDTC Registration Number must be reported. The DDTC Registration Number must be valid in the AES and cannot be expired at the time of export. Verify the DDTC Registration Number and the Estimated Date of Export, 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.

“Who is the USPPI? It could be YOU!”

Wednesday, October 12th, 2016 by Danielle McClellan

(Source: Global Reach Blog)

Questions about who the U.S. Principal Party in Interest (USPPI) is often come up when reporting exports. The USPPI is the person or legal entity in the United States that receives the primary benefit, monetary or otherwise, from an export transaction. The following parties can be the USPPI:

  • U.S. seller (wholesaler or distributor) of goods for export
  • U.S. manufacturer (if selling the goods for export)
  • U.S. order party (if directly negotiated between the U.S. seller and foreign buyer and received the order for the export of the goods)
  • U.S. customs broker (obtains clearance of goods through customs)
  • Foreign entity (if physically in the United States to purchase or obtain the goods)

Helpful tips to identify the USPPI 

  • The USPPI remains the same regardless of whether the transaction is standard or routed. For more information on the differences between standard and routed transactions, please see Clarification of Routed Transactions.
  • The exchange of funds does not need to occur for an entity to be the USPPI. For example, a U.S. company exporting goods at no cost (i.e., donations, replacement parts) to a subsidiary abroad would be the USPPI.

Identification scenarios ?

Scenario 1:

Company A in the United States manufactures lamps. Once assembled, the lamps are sold to Company B in the United States. Company C in Canada places an order with Company B and authorizes Company B to export the lamps to the ultimate consignee in France. Who is the USPPI and why?
Company B is the USPPI because it received the primary benefit from the foreign buyer. The transaction between Companies A and B is a domestic transaction.
Scenario 2:

A representative from Company A in Mexico is in the United States buying electronics from Company B. After making the purchase, Company A’s representative authorizes Company C in the United States to file Electronic Export Information in the Automated Export System and move the electronics on Company A’s behalf. Company A’s representative returns to Mexico. Who is the USPPI and why?

Company A’s representative is the USPPI because they were physically in the United States at the time the goods were purchased.

 

Scenario 3:

Company A in the United States stores bamboo stalks in a warehouse on behalf of a Foreign Principal Party in Interest. While in the warehouse, Company A converts the bamboo stalks into fishing rods. Who is the USPPI and why?

Company A is the USPPI because it was responsible for converting the bamboo stalks into fishing rods, changing the classification.

I hope this information provides more clarity on who the USPPI is in an export transaction. For assistance, please call 800-549-0595, Option 3 to contact the Trade Regulations Branch of the U.S. Census Bureau.

Tips on How To Resolve AES Fatal Errors

Wednesday, October 12th, 2016 by Danielle McClellan

(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.