ACE: Recon “blanket flagging” to be discontinued on Jan 14


Calendar Icon with long shadow. Flat style. Date,day and


Attention recon filers!  Effective January 14, US Customs will no longer apply ‘Blanket Reconciliation Flagging’ to entry summaries.  CBP has left it up to the importers and their brokers.  As a result, all reconciliation flagging must be done on an entry-by-entry basis.

Failure to do so will require importers to submit 520(d)s, post-summary corrections or prior disclosures to correct issues that are otherwise handled by reconciliation.

By way of background, CBP announced in the December 12, 2016, Federal Register that:


  • CBP is streamlining the process for blanket flagging underlying entries for reconciliation.
  • Under the existing process, importers provided CBP a request asking that CBP input and apply a blanket flag to all underlying entries filed by the importer for a specific time period. Importers also identified the specific issue(s) for which they requested that CBP input and apply the requested blanket flag.
  • This document announces that effective January 14, 2017, importers no longer will submit requests asking that CBP apply a blanket flag on their behalf. Instead, importers may input and apply a blanket flag themselves. Importers who use blanket flagging must continue to identify the issue(s) they are flagging.

Importers that currently benefit from blanket flagging on their recon entries should work with their customs brokers to ensure entries are flagged in accordance with the importer’s requirements.  If self-filing*, importers should ensure that their ABI software providers’ systems are programmed accordingly.

Please note that reconciliation flags are applicable ONLY to entry summary types 01, 02 and 06

 * CustomsNow self-filing clients have the ability to manage their recon flags at either the “blanket” level, or even at the Part/SKU level, a fantastic option. Learn more.

ACE: Update on PGA integration for exports

While much of the fanfare around ACE has been on the import side, US Customs continues to work with the PGAs to complete full integration in ACE for exports. Below is a table listing all the agencies that have export data requirements, methods used to receive data in ACE, pilot availability and the required export data:

Screen Shot 2017-01-09 at 8.54.11 AM (1)Screen Shot 2017-01-09 at 8.52.18 AM


For additional information on the integration of the PGAs for exports, please navigate to the “ACE Features” page of and click on the “PGA Integration” tab to review the ACE PGA Forms List – Export document.


AAEI: Jan 10th deadline to take 2017 e-Commerce Benchmark Study

Screen Shot 2017-01-06 at 7.54.27 AM


From our friends at AAEI

Dear Trade Compliance Professional,

The upsurge of online shopping grew to historic proportions in 2016, having positive and negative effects on retailers, manufacturers and shippers.

AAEI and Amber Road are launching a survey to measure the trade community’s current international e-commerce activities and capabilities, in addition to risk factors and compliance concerns. Click here for further details on this initiative.

A report of the findings will be released in January 2017 and presented at the 2017 FTA and AAEI Western Regional Conference in Torrance, CA on January 30-31, 2017.

This brief survey should take 4-5 minutes to complete and will remain open through January 10, 2017. Your responses are confidential and will be analyzed in aggregate.

As a thank you for participating, all survey participants will receive a $10 Starbucks gift card from Amber Road as well as a complimentary copy of the full report when released.


Be ready for Jan 14! Updated ACE documentation posted on




With the deployment of complete ACE core processing on January 14, you should check out US Customs’ recently posted new and updated information concerning ACE and PGAs on, including:


ACE: Full core trade processing, including post-entry, deploys January 14!


Calendar Icon with long shadow. Flat style. Date,day and


US Customs is preparing to deploy capabilities that will complete the delivery of core trade processing in ACE. The date for the deployment and mandatory transition of these capabilities will be January 14, 2017.

The capabilities in the deployment include: drawback, duty deferral, liquidation, collection, statements, and reconciliation. Please note: Importer Security Filing (ISF) is transitioning on January 14 as well. Beginning January 14, 2017 transactions supporting these capabilities must be filed in and processed through ACE. Submissions to CBP’s legacy system, the Automated Commercial System (ACS), will no longer be supported.

Full details on the transition of each of the capabilities, reference materials, and technical documentation are available on CBP’s website through the following links:


For details on what specific applications are transitioning from ACS to ACE and what transactions and queries will no longer be available, please reference CBP’s ACS to ACE Application Transition Plan. Any items on the spreadsheet marked January 2017 will no longer be available beginning January 14 2017, including items under ‘Scheduled to Transition’, ‘Available in ACS and ACE’, and ‘Will Not Transition’.

Please note:
  • The January 14, 2017 deployment does not include Manufacturer ID Add (MID), as this capability must be deployed at the same time as Foreign Trade Zone (FTZ) Admissions (e214s). Details on these capabilities will be made available through future communications.
  • The ACE Product Code query will be removed from and no longer supported in ACE.
  • For further details on CBP’s transition to ACE, visit the ACE Mandatory Use Dates page, or reference the ACE Entry Summary Business Process Document for policy and business process flows.
  • For technical support during the transition, contact your company’s assigned Client Representative. During the deployment period Client Representatives will have access to additional headquarters policy, operations and technical personnel to expedite any transition issues. More details on this additional support will be made available in early January.
  •  Reports in support of the capabilities being deployed will be made available after January 14, 2017. After deployment of capabilities into production, additional time is needed to migrate and synchronize legacy data to ensure accuracy of data prior to reports being made available. More details will follow as various reports become available.