Stable

How Many Post Summary Corrections Are Too Many?

Reis Renneker

Written by Reis Renneker

No fixed cap applies to PSC filings, but repeated corrections can expose weak entry controls, raise reasonable care concerns, and invite CBP scrutiny.

How Many Post Summary Corrections Are Too Many?

Post summary corrections are essential for fixing entry errors before liquidation, but unrestricted filing does not mean filing volume is irrelevant. A recurring pattern of PSCs can reveal weaknesses in classification, valuation, origin, duty calculation, or broker instructions that warrant deeper scrutiny from U.S. Customs and Border Protection.

There Is No Fixed Limit on Post Summary Corrections

CBP generally does not impose a numeric limit on the number of post summary corrections that may be submitted for an eligible entry. An importer may file more than one PSC when additional information becomes available or when a later review identifies another issue, provided the entry remains eligible and all applicable filing conditions are satisfied.

The absence of a formal cap is important because import transactions can involve layered issues. A classification change may affect tariff treatment, special program eligibility, Section 301 duties, merchandise processing fees, or other calculations. Complex entries may therefore require more than one legitimate correction.

Volume Alone Does Not Determine Compliance

No specific number of PSCs automatically establishes a failure to exercise reasonable care. Ten corrections involving an isolated system migration may present less compliance risk than three corrections revealing a recurring valuation methodology error across a major product line.

CBP is more likely to evaluate the circumstances surrounding the filings, including:

  • The number and frequency of corrections
  • Whether errors involve the same data elements
  • The value of affected merchandise and duties
  • How long the problem continued before detection
  • Whether the importer implemented corrective action
  • Whether similar errors remain in uncorrected entries
  • Whether the original entry data was reasonably available before filing

A high PSC count can function as a risk indicator even when every correction is timely and accurate.

PSCs and Protests Serve Different Purposes

A PSC is generally a pre-liquidation mechanism for correcting entry summary data. A protest is generally used to challenge a qualifying CBP decision after liquidation or another protestable event. Protests should not be treated as substitutes for entry controls or timely pre-liquidation review.

Frequent use of either mechanism may be justified, particularly after a legal interpretation changes or a broad error is discovered. However, repeated filings without a documented root-cause response can suggest that the importer is relying on post-entry remedies as routine quality control.

Repeated PSCs Can Create Reasonable Care Concerns

Reasonable care generally requires importers to take appropriate steps to provide accurate classification, value, origin, duty, and admissibility information at entry. Filing a PSC can support reasonable care by showing that an importer identified an error and corrected it before liquidation. The risk arises when the same type of error continues after the importer knew, or reasonably should have known, that its process was defective.

A PSC is therefore both a corrective tool and a compliance signal. It documents the correction, but it can also reveal when the original entry process did not consistently produce reliable information.

Patterns Matter More Than Raw Counts

Certain filing patterns are more likely to attract attention than an isolated group of unrelated corrections. Examples include:

  • Repeated classification changes for the same products
  • Recurring additions to entered value
  • Persistent origin or marking corrections
  • Corrections that repeatedly increase duties
  • Multiple PSCs on the same entry
  • Corrections filed near the end of the eligibility period
  • Large refund claims unsupported by clear transactional records
  • Continued errors after a prior internal review or CBP inquiry

A pattern involving duty underpayments can be especially sensitive because it may indicate that the government repeatedly received less revenue than was due. Refund PSCs can also receive close examination when the claimed tariff treatment or exclusion is not adequately supported.

A Correction Does Not Erase the Underlying Control Failure

Timely correction generally places an importer in a better position than leaving a known error unresolved. It does not, however, eliminate questions about how the error occurred or why it was not prevented.

CBP may examine whether the importer maintained complete product data, obtained qualified classification guidance, communicated assists and royalties, validated origin claims, and provided accurate instructions to its customs broker. If PSC activity reveals a systemic problem, the inquiry may expand beyond the corrected entries to other transactions, business units, ports, or time periods.

Importers should be able to connect every material correction campaign to a documented investigation, defined population, remediation plan, and control improvement.

Managing PSC Volume Through Stronger Entry Controls

An effective post-entry program does not attempt to minimize PSC filings at all costs. Its objective is to identify errors promptly, correct the full affected population, and prevent recurrence. Avoiding a necessary correction merely to keep filing counts low can create greater exposure than submitting a well-supported group of PSCs.

Compliance teams should monitor PSC activity as a key performance indicator. Useful measures include corrections by error type, business unit, broker, product family, vendor, port, and financial impact. The analysis should distinguish one-time events from recurring control failures.

Build a Root-Cause Review Into Every Correction

Each significant PSC should answer more than what changed. The review should establish why the original entry was inaccurate, when the issue began, which entries are affected, and whether the problem extends beyond the entries already identified.

A structured process typically includes:

  1. Confirming the correct legal and factual treatment.
  2. Preserving supporting commercial and customs records.
  3. Identifying the complete entry population.
  4. Calculating duty, tax, and fee consequences.
  5. Filing eligible PSCs before the applicable deadline.
  6. Evaluating liquidated entries for potential protests or other action.
  7. Updating master data, broker instructions, and review controls.
  8. Testing later entries to confirm that remediation worked.

This approach allows a large filing volume to be explained as a controlled remediation project rather than an unmanaged series of recurring mistakes.

Account for Timing and Payment Constraints

A PSC generally must be filed within 300 days of entry and at least 15 days before scheduled liquidation. Operational timelines should therefore be monitored closely, especially when a correction affects a large entry population.

When a PSC increases duties, taxes, or fees, the additional amount generally must be paid in full through ACH. A later PSC for the same entry may be blocked until the prior increase has been paid. This makes sequencing, funding, internal approval, and broker coordination important parts of correction planning.

Importers should also avoid fragmenting a known issue into unnecessary successive filings. Where practical, a complete review before submission reduces rework and creates a clearer record of reasonable care.

Recent Developments
  • CBP maintains there is no numeric limit on PSC filings per entry (within the 300-day/15-day-before-liquidation window), but repeated or high-volume corrections without addressing root causes can indicate a failure of reasonable care at entry and invite scrutiny or audit.* This aligns with longstanding practitioner views; the July 6, 2026 Federal Register notice (91 FR 41053) and August 6, 2026 CBP page update reiterate the no-limit policy while listing failure to exercise reasonable care as grounds for test misconduct or suspension.
  • August 5, 2026 payment rule change (from July 6 FR notice and August 3 CSMS #69428352): Duty/tax/fee increases from a PSC must be paid in full via ACH (no checks/cash); a subsequent PSC on the same entry is blocked until the prior increase is paid. An October 5, 2026 industry guide notes this operational constraint and advises high-volume importers to treat PSCs as part of a structured review process rather than repeated fixes on the same entry.
  • October 4, 2026 CBP enforcement example: Chicago Field Office reported denying an improper PSC (attempted Section 232 duty deduction on copper products from Italy) and recovering $136,481.50, with plans to expand similar reviews. This shows active CBP examination of PSC filings.
  • Late September 2026 (CSMS around September 22-24): CBP encouraged importers to file PSCs (or protests) for refunds on certain Section 301 China exclusion conforming amendments after HTSUS changes, highlighting PSCs as a proactive correction tool in specific refund scenarios.
  • October 19, 2026 industry update: In a heightened enforcement climate (expanded CBP audits, DOJ False Claims Act use, and restricted penalty mitigation), experts recommend early identification of errors and use of PSCs (pre-liquidation) plus prior disclosures to demonstrate reasonable care, rather than waiting for CBP detection. No new hard cap on filings was announced.
  • No X discussions in the past 30 days specifically quantified “too many” PSCs/protests or reported new CBP guidance on a filing threshold; activity focused on using PSCs for targeted refunds or CBP denying improper ones. The core risk remains the same as in older practitioner forums: volume that suggests systematic entry errors can trigger reasonable-care questions.
1 2 3 4 5

Frequently Asked Questions

Is There a Maximum Number of PSCs per Entry?

CBP generally does not apply a fixed numeric maximum. Multiple PSCs may be filed for an eligible entry, but each filing must satisfy the applicable timing, payment, and technical requirements. Repeated amendments can increase scrutiny if they suggest that the importer submitted corrections before completing an adequate review.

Can Filing Too Many PSCs Trigger a Customs Audit?

High filing volume does not automatically trigger an audit, but it can contribute to an importer's risk profile. CBP may focus on recurring error types, significant revenue impact, unsupported refund claims, and the absence of corrective action. A documented remediation program can help explain why a concentrated group of filings was necessary.

Does Filing a PSC Demonstrate Reasonable Care?

A timely, accurate PSC can support a reasonable care position because it shows that the importer corrected a discovered error. It is not conclusive. CBP may still evaluate whether accurate information was available at entry, whether the importer ignored warning signs, and whether the underlying control weakness was corrected.

When Should an Importer Use a Protest Instead of a PSC?

A PSC is generally appropriate when an eligible entry has not liquidated and the correction window remains open. A protest is generally used after liquidation to challenge a qualifying CBP decision. The proper mechanism depends on entry status, timing, the nature of the issue, and the relief being requested.

Should Importers Delay PSCs Until Every Entry Is Reviewed?

Not necessarily. Waiting for a complete review may place earlier entries outside the filing window. A better approach is often to prioritize entries by deadline, confirm the correction methodology, and submit controlled filing groups while the broader review continues. The importer should document the scope and sequencing of the project.

How Stable Software Can Help

Support a More Controlled Post-Entry Process

Customs brokers can help importer clients manage correction risk by combining disciplined entry review with consistent documentation and filing workflows. Stable Software provides customs brokers with software that can support importer-facing trade compliance services under the broker's own filer code.

For duty recovery programs, DrawbackAI is white-label duty drawback software that brokers can offer to their importer clients. Stable Software charges a flat software license and never takes a percentage of the refund. This structure allows brokers to retain control of the client relationship and filing process while building a scalable duty drawback service. Brokers evaluating broader post-entry opportunities can consider how structured technology, documented review practices, and clear importer responsibilities fit into their compliance model.

Resources

TypeResource
SourcePrimary source

✉️

Sign up for our newsletter

A monthly post on trade, tariffs, and customs, delivered straight to your inbox.