Reminder: CBP Expects to Implement Rule Changes for Six ABI Application Identifiers on April 12th
U.S. Customs and Border Protection has issued a CSMS message reminding the trade of the projected date of April 12, 2009 for the implementation for two rules in the Batch & Block Control Chapter of the ACE ABI CATAIR1 that will need to be adhered to for all messages for six ABI application identifiers, or fatal errors will result.
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!
CBP states that it will notify the trade if there is a change to this date.
Two Chapter Rules Will Affect All ABI Filers
According to a previously issued CSMS message, the requirement to adhere to the two chapter rules will affect all automated ABI filers whether or not they will be participating and sending ACE entry summaries. The two rules will impact all ABI software packages capable of transmitting application identifiers TI and KI, even those not developing for ACE entry summary at this time. CBP notes that if the required changes are not in place by April 12, 2009, the KI and TI transactions will fail.
List of Affected ABI Application Identifiers
The six affected ABI application identifiers are:
| AE Entry Summary Create/Update | CJ Census Warning Query |
| CW Census Warning Override | JC Entry Summary Query |
| KI Importer/Bond Query | TI Importer/Consignee Create/Update |
(As additional ABI application identifiers become subject to the two rules, they will be added to the ACE ABI Batch & Block Control Chapter.)
Details of the Two Chapter Rules That Must be Adhered To
The two chapter rules that must be adhered to effective April 12, 2009 are:
- The addition of the Application identifier to positions 26-27 of the Batch Control Header (Input A-Record) as a mandatory field.
- The values in the Block Control Trailer (Input Y record) for Processing District/Port Code, Filer Code, Application Identifier Code, and Processing Filer Office Code must be identical to those same values in the previous Block Control Header (B-Record).
CBP states that this functionality is now available for testing in the ACE Certification Environment and questions should be directed to client representatives.
(CBP noted that in the fall of 2007 KI and TI messages were rerouted to ACE for processing with the deployment of ESAR A1. At that time ABI filers were not required to make any changes to the format of messages they were sending.
In November 2008, CBP issued a CSMS message advising ABI developers of the posting of the new ACE ABI Batch & Block Control Chapter to the CBP Web site and indicated that the rules therein would apply only to the above-listed ABI application identifiers specified in the chapter.)
1Automated Commercial Environment (ACE) Automated Broker Interface (ABI) Customs and Trade Automated Interface Requirements (CATAIR)
(See ITT's Online Archives or 03/18/09 news, 09031815, for BP summary announcing the upcoming changes.
See ITT's Online Archives or 04/03/09 news, 09040305, for BP summary announcing ESAR A2.2 will be deployed on April 12th.)
CSMS 09-000164 (dated 04/07/09) available at http://apps.cbp.gov/csms/viewmssg.asp?Recid=17553&page=&srch_argv=&srchtype=&btype=&sortby=&sby
ACE ABI Batch & Control chapter available at http://www.cbp.gov/linkhandler/cgov/trade/automated/modernization/ace_edi_messages/catair_main/abi_catair/catair_chapters/abi_bb_control.ctt/abi_bb_control.doc