Self-Filing a Post Summary Correction (U.S. Only)
A Post Summary Correction (PSC) is an amendment to an Entry Summary (excluding informal entry, type 11 or 12) prior to liquidation; yet after US Customs and Border Protection’s (CBP) acceptance of that Entry Summary, payment has been processed, and the entry is scheduled for liquidation.
A PSC can be filed up until the 300th day (11:59 PM Eastern time) after the entry date or up to midnight Eastern time on the 15th day prior to the scheduled liquidation date, whichever is earlier. Since CBP views a PSC as a full replacement of the Entry Summary data currently on file, the PSC will be accepted as the most up-to-date data available. However, it is important to remember that once CBP reviews the PSC, CBP may change the associated collection information to reflect any resulting monetary changes.
Most Entry Summary data elements can be updated using a PSC. However, elements affecting admissibility are not allowed to be changed in a PSC.
Just like with conventional summary filings, there are many edits and validations on the CBP side and several types of rejections can be encountered with a PSC filing. If the data is not accepted by ACE, then the Entry Summary data on file in ACE will remain unchanged.
There is no limit to the number of PSC filings ACE will accept for an Entry Summary. However, the filer must provide reasons for the data change on each PSC. It is also important to remember that once a PSC has been accepted by CBP, the filer can no longer submit conventional filings to CBP for that entry.
The option to self-file a Post Summary Correction (PSC) in the Entry Verification solution provides you the ability to push data to the ONESOURCE Automated Broker Interface (ABI) module to validate the entry and allow filing directly from ONESOURCE to US Customs and Border Protection (CBP).
Self-filing a Post Summary Correction within ONESOURCE allows you to:
- Leverage the ONESOURCE ABI module to complete the required entry validations necessary for PSC filing
- Transmit PSC data directly from ONESOURCE to CBP
- Maintain a history of all corrections made to an entry within ONESOURCE Entry Verification
- View replies from CBP for a PSC that has been filed through ONESOURCE
When the self-filing capability is enabled within Entry Verification, the
Declaration Correction
screen will show an additional Validations
column on the All Entries
tab. 
When an entry’s status changes to the configured
Requires Correction
status, the system will run the entry data against the preconfigured ABI validations. The validations being run are checking for entry completeness per CBP requirements should a PSC need to be filed.Any system configured for validations (even if it has not been configured to self-file PSCs), will run validations so that data may be provided in the report to third parties for subsequent filing.
ABI Validations
To review the data points that have been flagged by the validations, choose an entry from the grid and click its corresponding
ABI Validations
link. 
Clicking
ABI Validations
will open a pop-up containing the entry’s validation errors: 
If you choose to generate a report from the
Declaration Correction
screen, the ABI validation results will be included in that report as reference for the designated PSC Filer.Selecting an Entry
To select an entry, choose an entry from the
All Entries
tab and click its corresponding Select
link on the far left. 
Clicking
Select
will refresh the Declaration Correction
screen and open the Selected Entry
tab. This tab will contain an additional row of options, as defined in the table below:Options | Description |
|---|---|
Validate | Pushes corrections made on the Declaration Correction screen to ONESOURCE ABI for re-validation. |
View Validations | If the system has been configured for self-filing, the validations tab of the ABI Entry screen for the selected entry will open, allowing you to make any necessary corrections for self-filing purposes. If the system has not been configured for self-filing, the tab will open to show the ABI validation results. |
Correction History | Opens a correction history pop-up window for the selected entry. |
View Replies | Opens the ABI Replies screen for the selected entry, provided a PSC has previously been self-filed via ONESOURCE. Users will only be able to view replies from CBP if configured for self-filing. |
Validate
If the system has been configured for self-filing PSCs, clicking
Validate
will first prompt the user to choose what to do after validation:
Choosing
Self-File
will run the ABI validations and open a second browser tab containing the Validation Summary
tab of the Entry 7501
screen within ONESOURCE ABI. The currently selected entry will be pre-selected. From this screen, the user can make the appropriate corrections prior to submitting the PSC to CBP. This validation can be performed for both single-HS and multi-HS scenarios, depending on how the system was configured.Choosing
Report Only
will run the ABI validations, then open a pop-up containing the entry’s validation errors to review.
If the system has not been configured for self-filing PSCs, clicking
Validate
will run the ABI validations, then open a pop-up containing the entry’s validation errors to review.View Validations
To view all ABI validations for the selected entry, click
View Validations
. 
If the system has been configured for self-filing PSCs, clicking
View Validations
will open a second browser tab to the Validation Summary
tab of the Entry 7501
screen within the ABI module. The currently selected entry will be pre-selected. From the Entry 7501
screen, the user can make any additional corrections prior to submitting the PSC to CBP. 
Transmitting the Post Summary Correction
From the
Entry 7501
screen, the user can navigate to any of the tabs to view the existing data.To modify data for a tab, open the desired tab and click
Edit
. Add any additional changes that were not captured on the Declaration Correction
screen. 
After making additional changes, click
Validate
at the top of the screen to re-run validations. This will redirect the user to the “Validation Summary” tab so any outstanding validations can be reviewed. After all errors are corrected, the
Validation Summary
tab will be blank and the Entry Status will update to VALIDATED
.
Once the entry is in
VALIDATED
status, the Finalize
button will turn blue and allow the user to finalize the entry. Once clicked, the Entry Status will change to FINALIZING
. No changes can be made to the entry while it is in a FINALIZING
status. 
After the process is complete, the Entry Status will change to
FINALIZED
. Once the entry has finalized, a message will appear at the top of the screen: “Entry has been finalized”.After the entry has been finalized, review the
Header Post Summary
and/or Line Post Summary
tabs. On these tabs, the system will automatically calculate the PSC Reason Codes based on the changes made to the entry.In the event a code is incorrect or missing, these codes can be manually updated without having to Revalidate or Refinalize. Refinalizing will remove any changes made to the Reason Codes.
Changes to header information on the entry will trigger the
Header Post Summary
tab to be visible on the entry. The
Explanation
text box is used for providing details on why a change was made to the entry. The Reason Code
box is used for choosing the CBP Reason Code that best explains why the entry is being re-filed with a Post-Summary Correction.
ID | Description |
|---|---|
H01 | The Entry Type Code has been changed specifically from 01 to 03. |
H02 | The Entry Type Code has been changed (other than 01 to 03). |
H04 | The Mode of Transportation (MOT) Code has been changed. |
H05 | The basic and/or additional Surety Company Code has changed. |
H10 | The Continuous Superceded Bond Indicator has changed. |
H07 | Other basic and/or additional bond data has changed. Includes Bond Type Code, Single Transaction Bond Amount, Single Transaction Bond Producer Account Number, Bond Waiver Indicator, and/or Bond Waiver Reason Code. |
H08 | The Electronic Invoice Indicator has changed. |
H09 | The Shipment Usage Type Code has changed. |
H10 | The Consignee Number has changed. |
H11 | The Date of Importation has changed. |
H12 | The U.S. State of Destination Code has changed. |
H13 | One or more Entry Summary Header Fee (Header Fee Amount or Accounting Class Code) has changed. Includes 311 (Informal MPF), 500 (Manual Surcharge), and 496 (Mail). |
H99 | Another Entry Summary Header Grouping data element (not listed above) has changed. |
Changes to entry line information will trigger the
Line Post Summary
tab to be visible. In this tab, the filer will provide the CBP Reason Code that best explains the reason for filing the PSC as well as the tariff line number that is being corrected. 
ID | Description |
|---|---|
L01 | The Commercial Invoice has changed or items were missed in the original submission. This change may result in more or fewer Entry Summary Line Item Groupings. For an Electronic Invoice Processing (EIP) summary, the change may affect the EIP Invoice Grouping (i.e., the Invoice Line Reference Detail). |
L02 | The Trade Agreement/Special Program Claim Code has changed, but not the article classification. |
L03 | The classification of an article or an HTS Number has changed. This may affect the Article Set Indicator and/or the Trade Agreement/Special Program Claim Code. |
L04 | The value of the merchandise (Value of Goods Amount) has changed or the basis/determination for the value has changed (e.g. NAFTA Net Cost Indicator). This reason may be used if a currency conversion was a factor resulting in a change to the value. |
L05 | The Charges Amount has changed. |
L10 | The Duty Amount has changed. |
L07 | The Country of Origin Code has changed. |
L08 | The Country of Export Code has changed. |
L09 | The U.S. Department of Commerce has invoked “Critical Circumstances” regarding an Entry Type 01 Entry Summary filed 90 days prior to the Preliminary or Order period for an Antidumping/Countervailing Duty case. |
L10 | One or more Article Party Identifiers (API) has changed, thus changing the Antidumping/Countervailing Duty case suffix. |
L11 | The Case Deposit Rate and/or Case Rate Type Qualifier Code has changed. |
L12 | The “scope” of the Antidumping/Countervailing Duty case has changed. |
L13 | The Antidumping/Countervailing Duty Non-Reimbursement Statement and/or Antidumping/Countervailing Duty Non- Reimbursement Declaration Identifier changed. |
L14 | The Ruling Type Code or Ruling Number has changed. |
L15 | The 740 Header and/or 740 Continuation has changed (includes a change to an FCC PGA Invoice Description). |
L16 | The IR Tax Information (IR Tax Amount or Accounting Class Code) has changed. |
L17 | The formal Merchandise Processing Fee (499: User Fee Amount or Accounting Class Code) has changed. |
L18 | Another fee has changed (User Fee Amount or Accounting Class Code). Includes a change to 501-HMF or any agriculture commodity fee. |
L19 | The Manufacturer/Supplier Code has changed. |
L20 | The Foreign Exporter Code has changed. |
L21 | The Sold To Party Identifier has changed. |
L22 | The Delivered To Party Identifier has changed. |
L23 | The Category Code (for Textiles) has changed. |
L24 | The Standard Visa Number has changed. |
L25 | The Date of Exportation (for Textiles) has changed. |
L26 | The License/Certificate/Permit Type Code and/or the License/Certificate/Permit Number has changed. |
L27 | The Softwood Lumber Export Price amount has changed. |
L28 | The Softwood Lumber Export Charges amount has changed. |
L29 | Quantity (1,2, or 3) has changed on any HTS Number for the article. |
L30 | The Related Party Indicator has changed. |
L31 | The Gross Shipping Weight has changed. |
To send the entry data to CBP, click
Transmit
at the top of the screen. Clicking Transmit
will update the Entry Status to TRANSMITTING
. Once this process is complete, the Entry Status will change to TRANSMITTED
. No changes can be made to an entry in a TRANSMITTING
or TRANSMITTED
status. 
Once a response is received from CBP, the status of the entry will update to “
RESPONSE RECEIVED
”, at which point the user can click on the Entry Replies
tab on the Entry 7501
screen to view the disposition messages from CBP. The Summary Replies
sub-tab displays the responses on the CF7501 entry.To view more information on the reply, click the expansion arrow to the left. The Record Level, Message ID Code, Message, Reference Data and more detailed information from CBP (if provided) will appear here.
The Message Code definitions can be found on the CBP website under the ACE CATAIR Error Message section.
Correction History
To view a history of all corrections made to the selected entry, click
Correction History
. 
Some of the below columns options may or may not appear on the
Correction History
pop-up, depending on how the system was configured. 
View Replies
To view replies previously received on a Post Summary Correction, click
View Replies
. 
Clicking
View Replies
will open a second browser tab on the ABI Responses
page, with the current entry displayed. The PSC responses will be listed on the ACE Responses
tab.Clicking
View Details
will bring the user to the Entry 7501
page on the Entry Replies tab. 
Generate Report
To generate a Post Summary Correction Report, click
Generate Report
. 
Clicking
Generate Report
will open the Generate Report
pop-up window. Choose a document type for the report: Adobe PDF or Microsoft Excel XLS. Click Generate Report
to proceed. 
Once the report has been generated, the user will be asked to either open the report, or reset report selections, allowing the user to select a different file type to generate.
Selecting
Open Report
will open a second browser tab with the report loaded. The report will display the ABI Validations below the entry data. 
Related Content
-
Declaration Correction
Format:
Article