CBP Info on In-Bond Access Controls for Use by M1 Ocean/Rail Carriers
U.S. Customs and Border Protection has posted a document on in-bond authorization for rail and sea carriers in ACE since the deployment of ACE e-Manifest: Rail and Sea (M1). The document provides instructions on how to create and maintain a carrier in-bond authorization, grant additional port access to an existing authorized partner, edit date parameters for authorized partners, remove ports from an authorized partner, and remove authorized partners from an account in ACE.
Sign up for a free preview to unlock the rest of this article
Communications Daily is required reading for senior executives at top telecom corporations, law firms, lobbying organizations, associations and government agencies (including the FCC). Join them today!
Carriers Can Control Who Can Obligate Their Type 2 Custodial Bonds (CBP Form 301)
With the deployment of M1, rail and sea carriers will have the ability to create a list of authorized Type 2 In-Bond users in their ACE Secure Data Portal Accounts. This functionality will allow the carrier to control who can obligate their Type 2 custodial bonds (CBP Form 301) for inbound cargo. Although carriers are not required to utilize this functionality, carriers who choose to control access to their bonds have the ability to indicate the specific ports and lengths of time a carrier or broker is authorized to obligate their bond.
In-Bond Authorization File Only Applicable for In-Bonds Submitted via EDI
CBP notes that the in-bond authorization file is only applicable for in-bonds submitted via EDI to the ACE rail and sea manifest functionality. Air AMS manifest will not utilize the in-bond authorization functionality at this time. Also, during the time period when ACE and AMS rail and sea manifests will be operating simultaneously, in-bonds created via AMS legacy rail and sea manifest will not utilize the ACE in-bond authorization functionality. QP filers submitting in-bonds into the legacy AMS application during this time frame will not utilize the ACE in-bond authorization functionality.
If Carrier Does Not Use In-Bond Functionality, ACE Will Not Restrict Use of Its Bond by Other Parties
If a rail or sea carrier elects not to utilize the In-Bond Authorization functionality, ACE will not restrict the use of their bond by other parties, i.e. any party will be allowed to use the carriers bond. If a carrier wants to limit bond usage to their own company they will need to add themselves as an “Authorized Partner.” This action will exclude all other parties from utilizing the carrier’s bond.
Carriers Can Limit Use of Their Bonds to Certain Identified Carriers
Rail and sea carriers with an activity Type 2 bond will be able to identify carriers by Standard Carrier Alphanumeric Codes (SCAC) and In-Bond filers by filer codes in their ACE Portal Account, for the purpose of limiting use of their bond to these entities. Once an entity is entered into the “In-Bond Authorization File”, no other carriers, brokers, or QP filers other than the ones identified, will be able to initiate an In-Bond request via manifest declarations, In-Bond submissions or subsequent In-Bond requests. ACE will not notify a carrier's business partner that their SCAC or filer code has been entered in your In-Bond authorization file.
(Note that the Trade Account Owner will need to grant full access to the Accounts tab to any Proxy Trade Account Owner or Account User who needs to add authorized partners.)
(See ITT's Online Archives or 08/16/11 news, 11081618, for BP summary the ACE Portal shared reports and in-bond improvements CBP stated would be included in the deployment of M1.)