- Global Reach Blog - http://globalreach.blogs.census.gov -
Clarification Of Routed Export Transactions
Posted By rosannatorres On April 1, 2010 @ 7:21 am In Foreign Trade Regulations | 40 Comments
By: Justin Jenkins
Understandably, this concept of a routed transaction is risky and generates many questions. Let’s try to answer those questions and mitigate the risk.
The Foreign Trade Regulations (FTR) defines a routed export transaction as, “an export transaction in which the foreign principal party in interest (FPPI) authorizes a U. S. agent to facilitate the export of a shipment from the U. S. and to prepare and file electronic export information (EEI).” Routed export transactions are a risk in that these transactions shift the control of the movement of the goods and the filing of the EEI from the U. S. Principal Party in Interest (USPPI) to the FPPI. The FPPI directs the movement of the goods out of the U. S. and authorizes the U. S. agent to file the Automated Export System record for the shipment. Though the FPPI is “controlling” the export transaction, the USPPI is still responsible for providing their name, address, and all the commodity information to the filing agent (see FTR section 30.3(e) for a detailed listing of the items).
To ensure that the EEI is filed accurately and to reduce your risk in this type of transaction, you should ask the FPPI to authorize you to file the EEI.
Key points about routed transactions:
Routed export transactions can be challenging, but if you adhere the key points discussed above, you will mitigate the risk involved in these transactions.
Article printed from Global Reach Blog: http://globalreach.blogs.census.gov
URL to article: http://globalreach.blogs.census.gov/2010/04/01/clarification-of-routed-export-tansactions/
URLs in this post:
 Image: http://globalreach.blogs.census.gov/files/2012/04/6a0120a61b56ed970c01311007aba8970c-500pi.jpg
 Tweet: https://twitter.com/share
 : http://globalreach.blogs.census.gov/2010/04/01/clarification-of-routed-export-tansactions/
 : mailto:firstname.lastname@example.org