A rejected PSC can create uncertainty about which version of an entry remains legally operative. In most cases, the answer is straightforward: if the Post-Summary Correction is not accepted, the original entry summary remains on file, and the proposed amended Form 7501 does not replace it.
What Happens When a Post-Summary Correction Is Rejected?
The Original Entry Summary Remains in Effect
A Post-Summary Correction, commonly called a PSC, is generally treated as a complete replacement of the entry summary data previously transmitted through the Automated Commercial Environment. It is not a separate entry layered on top of the original filing. The corrected transmission restates the entry summary with the filer’s proposed changes.
That replacement only becomes effective when the PSC is accepted through the applicable ACE processing and validation steps. If ACE rejects the correction, the replacement does not occur. The original uncorrected entry summary remains the operative filing in CBP’s system.
This distinction is important because a rejected PSC does not ordinarily require the filer to cancel the amended entry in favor of the original. From CBP’s perspective, the amended version never displaced the accepted entry summary. The filer should instead retain the rejected transmission, error messages, revised data, and supporting documentation as part of the entry record.
How the Amended Form 7501 Fits Into the Process
An amended Form 7501 may be generated to reflect the data included in the PSC or provided as supporting documentation when requested. Operationally, however, the controlling question is whether the corrected entry summary data was successfully accepted in ACE.
If the PSC is rejected, the amended Form 7501 does not independently revise the entry. It remains evidence of the correction the filer attempted to make. A broker may need to mark that version as rejected or superseded within its internal system, but it generally should not treat the original accepted entry as canceled.
The next action depends on the reason for rejection, the entry’s liquidation status, and whether sufficient time remains to submit another PSC.
Why CBP or ACE May Reject a PSC
Timing, Control, and Payment Conditions
A PSC may be rejected for procedural, technical, or substantive reasons. Timing is one of the most consequential. A correction generally must be filed no later than 300 days after the entry date and at least 15 days before the scheduled liquidation date. Once the entry has liquidated, the PSC process is generally no longer available.
An entry may also be temporarily or permanently ineligible for correction because it remains under CBP control or review. This can arise when CBP is examining the entry, reviewing admissibility, conducting an audit, considering enforcement issues, or otherwise restricting changes. Certain entries with suspended liquidation may be subject to separate processing rules, particularly when antidumping and countervailing duty matters, court injunctions, or enforcement proceedings are involved.
Payment status can also prevent acceptance. When a PSC produces an increase in duties, taxes, or fees, the additional amount generally must be paid in full through ACH. A subsequent PSC for the same entry may be blocked until the prior increase has been paid and processed.
Data Validation and Substantive Eligibility
ACE may reject a PSC because the corrected transmission fails an edit or validation requirement. Common issues can include inconsistent tariff data, invalid classification details, missing identifiers, incorrect line-level calculations, or conflicts between the corrected data and the entry’s current status.
The nature of the proposed correction also matters. A PSC is generally suited to correcting entry summary data, including factual errors involving classification, value, quantity, origin, duty calculation, or a qualifying duty exclusion. For example, an importer may typically request removal of eligible Section 301 duties through a PSC if the entry remains within the correction window.
A legal claim that depends on an interpretation of law, rather than a correctable factual or data error, may need to be raised through a protest after liquidation. Filing teams should therefore identify whether the issue is a transmission problem, a factual correction, or a legal disagreement before deciding how to proceed.
How to Respond to a Rejected PSC
Diagnose the Rejection Before Retransmitting
The first step is to determine whether the rejection came from an ACE validation, an eligibility restriction, a payment issue, or CBP review. The response should be based on the actual rejection condition rather than an assumption that the amended Form 7501 must simply be resubmitted.
If the problem is technical and the entry remains eligible, the filer can generally correct the transmission and submit another PSC. Before retransmission, the broker or importer should verify the complete entry summary because the PSC functions as a replacement filing. Every line, header field, duty calculation, and declaration should be reviewed, not only the data element that prompted the correction.
If the entry is under CBP control, the filer may need to communicate with the responsible port or wait until the restriction is resolved. If additional duties are due, payment processing should be confirmed before another correction is attempted. The filer should also monitor the scheduled liquidation date because a technically correct retransmission may still fail if the PSC window closes.
Determine Whether a Protest Is the Correct Remedy
When an entry has already liquidated, or when the correction concerns a legal decision that cannot properly be resolved through a PSC, a protest may be the appropriate mechanism. A protest challenges a qualifying CBP decision after liquidation, including certain decisions involving classification, valuation, duty rate, or denied refund treatment.
A protest is not simply a late PSC. It is a distinct legal and administrative procedure with its own deadlines, standing requirements, and documentation standards. The submission should clearly identify the protested decision, explain the basis for the claim, quantify the requested relief, and include supporting records.
Importers and brokers should preserve the rejected PSC, amended Form 7501, ACE messages, payment records, classification analysis, and correspondence. Those records can help establish what correction was attempted and why another remedy became necessary. When the issue involves a material refund, a disputed legal interpretation, or potential penalties, consultation with qualified customs counsel is generally appropriate.
- CBP issued CSMS #70261629 on October 22, 2026, providing updated guidance on Section 301 China product exclusion conforming amendments. Importers may file a PSC to request removal of previously paid duties if the entry remains within the PSC timeframe. Otherwise, a protest after liquidation is required.
- Thomson Reuters ABI documentation, updated October 15, 2026, confirms that CBP treats a PSC as a full replacement of Entry Summary (7501) data. If ACE rejects the PSC due to edits, validations, or other issues, the original uncorrected entry summary data on file remains unchanged.
- An industry guide published October 5, 2026, recaps operational rules from the July 6, 2026 Federal Register notice (effective August 5, 2026): duty, tax, or fee increases from a PSC must be paid in full via ACH (checks and cash no longer accepted). Subsequent PSCs on the same entry are blocked until the prior increase is fully paid and processed. Exceptions exist for certain suspended liquidations (AD/CVD, EAPA, court injunction).
- No new CBP Federal Register notices, CSMS messages, or major policy changes specifically amending PSC eligibility, timelines, or rejection procedures appeared in the past 30 days beyond the October 22 guidance. CBP's official PSC page (last modified August 6, 2026) continues to list core rejection criteria, including entries under CBP review, unpaid status, or outside the 300-day/15-day-before-liquidation window.
- Practitioner discussions on X in late October 2026 focused on 7501 forms in the context of IEEPA tariff refunds and DDP shipments, with no identified threads addressing PSC rejection outcomes, amended 7501 handling, or related ACE processing issues.
Frequently Asked Questions
Does a Rejected PSC Replace the Original Form 7501?
No. A rejected PSC generally does not modify the accepted entry summary data in ACE. The original Form 7501 information remains operative unless and until a corrected PSC is accepted or CBP changes the entry through another authorized process.
Must the Filer Cancel the Amended Form 7501?
The filer generally does not cancel the original CBP entry because the rejected amendment never replaced it. Internally, the broker may mark the amended Form 7501 as rejected, failed, or not filed successfully. The document and associated rejection messages should remain in the entry record.
Can a Rejected PSC Be Submitted Again?
Typically, yes, if the underlying problem can be corrected and the entry remains eligible for PSC processing. The filer should resolve validation errors, payment conditions, or data inconsistencies before retransmitting. Resubmission may not be available if the entry has liquidated or the applicable filing window has closed.
When Is a Protest Required Instead of a PSC?
A protest is generally considered after liquidation when the importer is challenging a qualifying CBP decision. It may also be more appropriate when the dispute is legal rather than factual. The availability of a protest depends on the decision involved, the importer’s standing, and the applicable filing deadline.
What If the PSC Would Increase Duties?
The additional duties, taxes, or fees generally must be paid in full through ACH. Processing of another PSC for the same entry may be blocked until the increased amount has been paid and posted. Payment status should therefore be confirmed before attempting a subsequent correction.
Can a PSC Be Used to Claim a Tariff Exclusion Refund?
A PSC can generally be used to claim an eligible tariff exclusion when the entry remains unliquidated and within the PSC timeframe. If the entry has already liquidated, the importer may need to pursue the refund through a timely protest, subject to the facts and legal basis of the claim.
How Stable Software Can Help
A Broker-Controlled Duty Drawback Model
Accurate entry records, correction histories, and supporting documentation also affect downstream refund programs such as duty drawback. Customs brokers need reliable data governance when determining which imported duties may support future claims.
Stable Software provides DrawbackAI, flat-license duty drawback software that U.S. customs brokers can white-label for importer clients. Brokers file claims under their own filer codes, retain control of the client relationship, and pay a flat software license. Stable Software never takes a percentage of the refund.
Customs brokers seeking to expand their refund services without adopting a contingency-fee technology model can learn more about Stable Software's approach for customs brokers.
Resources
| Type | Resource |
|---|---|
| Source | Primary source |
