Post Summary Corrections Delayed Until Spring 2011 Due to Trade Concerns
U.S. Customs and Border Protection has issued a CSMS message regarding the delay in deployment of ACE Post Summary Correction (PSC) functionality.
Sign up for a free preview to unlock the rest of this article
If your job depends on informed compliance, you need International Trade Today. Delivered every business day and available any time online, only International Trade Today helps you stay current on the increasingly complex international trade regulatory environment.
CBP & Trade Both Identified Issues with PSC Functionality
During the technical review of upcoming ACE PSC functionality, CBP identified production issues within ACE that were problematic for PSC. The trade also identified a critical business processing capability that needed to be addressed for PSC functionality to be utilized.
Given the choice of utilizing the PSC functionality “as designed”, or waiting for the identified enhanced critical capabilities, the early trade adopters of ACE have chosen to wait until the necessary changes are made in the spring of 2011 to ensure successful deployment and use.
PSC Release Delayed Until Spring 2011
As a result, the PSC release will be delayed and the PSC functionality will not be implemented for use by CBP and the trade until spring 2011.
The rescheduling of the deployment of these new capabilities will be announced in a future CBP message.
(A PSC transaction will be a “full replace” of the existing ACE entry summary as a new version. It will replace the existing Post Entry Amendment (PEA) hardcopy process for ACE entry summaries.
PSCs will only be submitted for types 01 and 03 ACE entry summaries. PSCs will be processed through all existing validations including Census warnings. Liquidation will be automatically unset for PSCs so they can be processed.)
(See ITT’s Online Archives or 09/20/10 news, 10092014, for BP summary announcing that PSC functionality would not be part of the October 3, 2010 deployment of enhanced ACE capabilities due to trade concerns, etc.)
(CSMS #10-000232, dated 09/30/10)