An incorrect HTS code, a misdeclared value, or a country-of-origin error can all flag an entry summary for correction. Before the current Trump administration’s tariff reporting changes, fixing those errors was usually straightforward. Not anymore. Today’s increased reporting requirements and the pace at which tariff rules keep changing mean you have to think about how a single correction fits into the bigger picture.
You have to consider:
1. The Liquidation Date for the Entry?
Check the liquidation date first. If you are within roughly 20 days of liquidation, CBP will reject a PSC (post-summary correction). At that point, your only option is to file a Protest within 180 days after liquidation. For one-off type-01 consumption entries, CBP has an online bulletin you can search by entry number. ACE Portal reports are also available to confirm past (ES-701) and upcoming (ES-010) liquidation dates for entries filed in bulk.
2. Duties Assessed Under the IEEPA (International Emergency Economic Powers Act)
CBP has rolled out a new CAPE (Consolidated Administration and Processing of Entries) Portal to handle IEEPA-related refund requests. No other duty refund updates can go through CAPE. And under Phase 1 of CAPE, entries must be less than 80 days past their liquidation date to qualify. That 80-day window matters. If your entry has both IEEPA and non-IEEPA errors, or non-optimized Section 232 classification, it behooves you to fix the non-IEEPA issues first. Then submit your CAPE Declaration for the IEEPA refund piece while the entry still falls within the allowable timeline.
3. The Primary HTS Code Subject to Section 232 Duties Based on When the Shipment Was Imported
CBP did not have validations built into ACE when many of these entries were originally filed. So if an import was subject to Section 232 and that was not declared properly, submitting a post-entry request such as through CAPE voluntarily asks CBP to review the full entry again. That kind of review could surface other problems, including the possibility of higher duties owed. How could it reject now and have been accepted before? Simply put, CBP has learned their prior validations were insufficient and improved them prior to launching CAPE.
4. Could There Be Other Errors Beyond the First One You Found
One error identified can be the tip of the iceberg without realizing it upfront. Before you file a correction, run a full post-entry audit on that entry to improve your odds that you caught everything CBP may flag for additional scrutiny when they review again. Then ask whether the same mistake might exist in other entries too. If the error is part of a pattern, and thus more systemic, those entries need their own audits before you submit anything to CBP as well. Thorough beats speed in this race to maximize your total refund potential.
Data Review Elements for a General Post-Entry Claim
There are generally 6 categories of data that need to be reviewed before filing a PSC or Protest. CAPE uploads only include the entry number, but if any of those entries get sent for compliance review, you will be grateful that you were prepared for this to be a possibility. We explain each on further below.
1. A Copy of the Original Entry Packet
You need the full original entry documentation. That means the Entry Summary (CBP Form 7501), Commercial Invoice/Packing List, Bill of Lading, Arrival Notice (if available), and any other supporting documents that defend your HTS classification, free trade agreement privileges, and punitive tariff exceptions. This is a regulatory requirement that you maintain these records regardless of post-entry and post-entry makes this control more urgent.
2. Declared Data Rationale
Even if your post-entry request does not involve an HTS classification change, the classification may still affect the outcome of what you are trying to correct. CBP might have enforcement priorities on your product category, or they may randomly select your filing for additional review before approving it.
Be ready with product specs and documented rationale. Know which General Rule of Interpretation (GRI) from the HTSUS was relied on to determine your classification. Beyond the primary HTS, CBP may also look closely at the additional CH99 classifications that were declared, including IEEPA programs, Section 232, Section 122, Section 301, and any exceptions or exclusions you claimed.
When Section 232 applies, a whole new layer of reporting comes under review:
- For Section 232 metals, you need to defend how you determined and split the metal content value versus the non-metal content value. You also need documentation of the steel country of melt/pour, the aluminum country of smelt/cast, and the copper country of origin where applicable. For aluminum specifically, if the country of smelt/cast is unknown, CBP may rate advance your imports into the 200% Russia classification due to your note being able to prove the metal is not Russian.
- For vehicles and parts (Section 232 Automobiles, Auto Parts, Medium- and Heavy-Duty Vehicles, Buses, and Parts (MHDV), as well as the recent Section 232 Metals exception for Motorcycle Parts used in Motorcycle Manufacturing), you must be able to defend the end-use following import. If your customs broker declares these duties and they do not apply to your products because you do not meet the specified end uses, you need documentation showing that as well.
- If you are in the Civil Aircraft industry and applied those corresponding punitive tariff exceptions, be prepared to show that your products meet the requirements.
3. SKU-Level Duty Data
Many duty calculations depend on material content value (Section 232 metals programs for steel, aluminum, and copper, for example) and/or the intended end-use of the imported article in the US such as auto parts vs MHDV vs agricultural/off-road or other purposes. Defending Section 232 calculations gets complicated when multiple invoice lines have been rolled into a single entry line. And even if the analysis is logical to you, if you have to explain it to CBP, the bar is set at whether it makes sense to them.
Some importers and customs brokers try to file one entry line per invoice line to keep the data clean when comparing the invoice/packing list with the 7501 later. ACE cannot report SKU-level detail, so that seems like a reasonable workaround and was arguably more helpful prior to metal derivatives. That approach breaks down when a line has to be split to separate metal content from non-metal content. The ability to run post-entry audits at the SKU level using only ACE reports without SKUs handicaps your ability ro reconcile these splits.
4. Entry Linkage Between Customs and Commercial Records
The odds of CBP selecting your post-entry submission for a full examination may be unpredictable, but they are not zero. Once you submit your request, CBP has the authority to ask for supporting records from the purchase order all the way through to payment to the foreign seller. Are you able to submit a defense and have it match with what was declared on your customs entry?
5. Liquidation Status and Timeline
From a process standpoint, checking liquidation status is an important early step. For larger post-entry projects, you can measure each entry’s urgency against the liquidation window and prioritize the order they get processed accordingly so you don’t inadvertently run down the clock.
If an entry has already liquidated, or is within 20 days of an upcoming liquidation, you have a 180-day window to submit a formal protest for non-IEEPA related refunds and an 80-day window to submit an IEEPA refund request. Future phases of the CAPE Portal may expand the IEEPA refund timeline, but CBP has not published those details yet. Because of that uncertainty, some importers have been including IEEPA in Protest filings for entries that don’t yet qualify for CAPE to try to protect future refund rights. These protests need to be withdrawn prior to uploading into CAPE or CAPE will reject both open and suspended protests.
6. Reason Code and Supporting Narrative
Every correction filed through ACE as part of a PSC requires a Reason Code. That code flags what type of data is being changed: HTS Code, Value, Country of Origin, Antidumping/Countervailing Duty, and so on. There is also a free-text PSC Filing Explanation submitted through ACE to provide more context and detail to support the Reason Code.
Writing that explanation is a balancing act. You want to give CBP enough information to understand and accept the changes without extra questions. But you do not want to include so much detail that the preparation time consumes resources for filing additional corrections without adding significant value to the overall process.
Where This Data Typically Lives and Why That’s a Problem
Assembling a complete PSC package means pulling data from multiple sources, often through multiple tools that don’t connect to each other. One correction is manageable. However, managing hundreds or thousands of corrections across different brokers, multiple suppliers, and/or types of corrections can become a full-time project. Every day spent chasing and normalizing data from these systems is a day closer to a liquidation deadline that won’t wait.
Building a Data Foundation for Clean PSC Filing With KlearNow
All six data categories above share the same challenge: the information exists, but it’s in different systems that were never built to work together. KlearNow’s KlearHub addresses that fragmentation at the source. The platform ingests trade documents from emails, PDFs, spreadsheets, and other formats from all of your brokers and supply chain partners and converts them into structured data in one place.
Your compliance team can gather everything from a single dashboard, rather than having to chase down a CBP Form 7501 from one broker, a commercial invoice from another system, and product details from a third.
KlearHub also provides SKU-level visibility and cross-broker reporting, so your team can confirm duty calculations, review HTS classifications, and compare declared amounts across entries without toggling between disparate systems. None of this substitutes for your customs broker although KlearNow’s ABI connection to CBP can also support your self-filing or third-party broker filings as well. KlearHub gives your compliance team the organized, centralized data they need to catch correction opportunities earlier, build better supporting documentation, and spend less time creating PSC packages from scratch.
Frequently Asked Questions
Q1. What happens if I file a PSC and CBP finds additional errors during their review?
Filing a PSC voluntarily requests CBP to review the entire entry. If they find Section 232 duties that you didn’t declare or other classification issues beyond what you flagged, those can get added to the review, too. So it’s worth the upfront time for the peace of mind a full post-entry audit brings before you file any corrections.
Q2. Can I submit both IEEPA and non-IEEPA corrections at the same time?
Not from the same channel currently. IEEPA refund requests are processed in the new CAPE Portal. All other corrections are filed as normal PSCs via ABI or as Protests via ACE. Filing the non-IEEPA corrections first, then submitting your CAPE Declaration for the IEEPA piece while the entry is still within the 80-day window, is the necessary approach if there are other entry changes in addition to IEEPA refunds.
Q3. How does CBP decide which post-entry submissions to examine more closely?
This is CBP’s secret sauce so we cannot know with certainty what could or won’t flag additional scrutiny. We understand that CBP uses pattern recognition and various enforcement tools including AI to find anomalies in an importer’s filing history and among importers of similar products. There can also be a random selection component. If you have your entry documentation, classification rationale, duty calculations, and rationale for any other changes ready before you file, you’ll be less prone to getting bogged down by additional questions during the approval process if you happen to be flagged for compliance review.
