IEEPA tariffs can create unexpected entry rejections when a tariff transition coincides with an earlier in-bond or entry-related date. Changing the estimated entry date alone may not resolve the issue because CBP systems generally evaluate a defined date hierarchy to determine which HTS provisions apply.
Why New Tariff Codes May Be Rejected
The Controlling Date May Precede the Filing Date
When tariff measures change, importers and customs brokers often focus on the entry summary date, transmission date, or preliminary statement date. Those dates matter, but they are not always the first dates considered when CBP determines whether a tariff provision is available for a shipment.
For non-quota entries involving an in-bond movement, the in-bond or in-transit date may take priority. A type 01 consumption entry with an Immediate Transportation movement can therefore be evaluated using an IT date that predates the effective date of new Section 122 HTS codes. If that earlier date controls, the Automated Commercial Environment may reject the newer codes and require tariff treatment associated with the earlier IEEPA regime.
This explains why changing the preliminary date or estimated entry date may have no effect. The updated date remains subordinate to a valid in-bond date already associated with the transaction. ACE validation generally compares the controlling date against the effective date range programmed for the declared HTS provision.
Effective-Date Validation Drives the Rejection
An ACE entry rejection in this situation is not necessarily evidence that the new tariff code is incorrect. The code may be valid for current transactions but unavailable for a shipment whose controlling date falls before the transition.
Brokers should distinguish between a classification error and an effective-date mismatch. Classification analysis determines which commodity provision and tariff measure apply, while date validation determines which version of that treatment is available for the specific entry. Resolving the rejection requires examining both elements rather than repeatedly changing lower-priority dates.
How CBP’s Date Hierarchy Affects Tariff Treatment
Date Order for Quota Entry Types
For quota entry types, CBP generally evaluates dates in a specific sequence. These entries include types 02, 07, 12, 32, and 38. The hierarchy typically begins with the CBP-determined entry date, followed by the 11-record estimated entry date when accepted without condition.
If neither date controls, the system may proceed through the following sequence:
- Release date as determined by CBP
- Preliminary statement print date, if accepted without condition
- 20-record estimated date of arrival, if accepted without condition and later than the EDI received date
- EDI received date when no other qualifying date is available
This hierarchy means the date entered by a filer does not automatically become determinative. System acceptance, transaction type, and the availability of higher-priority dates all influence tariff treatment.
Date Order for Other Entries
For entries outside the listed quota types, the 20-record in-bond or in-transit date generally appears first in the hierarchy when it is accepted without condition. The remaining dates are then considered in this order:
- Entry date as determined by CBP
- 11-record estimated entry date, if accepted without condition
- Release date as determined by CBP
- Preliminary statement print date, if accepted without condition
- 20-record estimated date of arrival, if accepted without condition and later than the EDI received date
- EDI received date when no other date is available
For type 01 entries with an IT movement, this ordering is especially important. An IT date on or before the tariff transition may cause CBP to apply the earlier IEEPA tariff logic, even when the entry summary is transmitted after new Section 122 HTS codes become available.
A Practical Workflow for Resolving Rejections
Diagnose the Transaction Before Editing Dates
A disciplined review should begin with the complete entry timeline rather than the rejection message alone. The broker should identify the entry type, determine whether an in-bond movement exists, and compare every relevant date against the effective periods for the old and new tariff provisions.
The review should include the in-bond date, CBP entry date, estimated entry date, release date, preliminary statement print date, estimated arrival date, and EDI received date. Teams should also confirm whether each transmitted date was accepted without condition. A populated field may not control if it failed a system condition or if a higher-priority date is available.
Once the controlling date is identified, the filer can test whether the selected IEEPA or Section 122 HTS code was valid on that date. This approach avoids repeated retransmissions based on assumptions about which date ACE is using.
File Correctly and Preserve Recovery Options
If the controlling date requires the earlier IEEPA tariff treatment, the entry may need to be filed with the HTS codes and duties accepted for that date. The transaction should then be documented for potential duty recovery if subsequent instructions, corrections, or legal developments support a refund.
A recovery file should generally capture the entry number, line-level HTS data, tariff code, duty amount, controlling date, in-bond number, rejection messages, and final acceptance response. Depending on entry status and timing, available mechanisms may include a post-summary correction, protest, reconciliation-related process, or another CBP-authorized procedure. Eligibility and deadlines vary, so trade compliance teams should evaluate each entry individually.
Strengthen Transition Controls
Leading operations create effective-date rules before a tariff change goes live. Automated validation can flag entries with pre-transition IT dates, incompatible tariff codes, or conflicting date fields before transmission. Exception queues should separate classification questions from date-hierarchy failures, allowing specialists to address the actual cause quickly.
These controls are particularly valuable when a high volume of in-bond shipments spans an implementation date. Without them, brokers may face avoidable rejections, delayed releases, inconsistent duty treatment, and incomplete refund populations.
Frequently Asked Questions
Why Does Changing the Preliminary Statement Date Not Fix the Rejection?
The preliminary statement print date may rank below the in-bond date, CBP entry date, estimated entry date, or release date. If a higher-priority date is valid and available, changing the preliminary statement date generally does not alter the tariff period applied by ACE.
Which Date Typically Controls a Type 01 Entry With an IT?
For a non-quota type 01 entry with an accepted in-bond movement, the 20-record in-bond or in-transit date will generally be evaluated first. The transaction’s complete data and CBP acceptance conditions should still be reviewed before determining the applicable date.
Can a Valid Section 122 HTS Code Still Be Rejected?
Yes. A Section 122 HTS code may be valid for shipments within its effective period but invalid for an entry assigned an earlier controlling date. In that case, the rejection reflects effective-date validation rather than an inherently invalid tariff code.
Should the Broker Use the Earlier IEEPA HTS Code?
If the controlling date falls within the earlier IEEPA tariff period, the corresponding code and duty treatment may be required to obtain acceptance. The filer should preserve supporting data and separately assess whether a correction or refund process becomes available.
How Should Potential Refund Entries Be Tracked?
Each entry should be recorded at the line level with its tariff code, duty amount, controlling date, in-bond details, liquidation status, and relevant deadlines. Centralized tracking helps prevent eligible transactions from being missed when correction or refund instructions are implemented.
What Is the Best Way to Prevent Similar Rejections?
Pre-transmission validation should compare tariff-code effective dates with CBP’s applicable date hierarchy. Rules should also flag in-bond movements that cross tariff implementation dates and route uncertain transactions to a compliance review queue.
How Stable Software Can Help
Automating Tariff and Date Validation
Stable Software helps importers and customs brokers convert complex tariff requirements into controlled, repeatable workflows. Automated validation can identify mismatches between IEEPA tariffs, Section 122 HTS codes, entry types, in-bond dates, and other transaction dates before files reach ACE.
Centralized exception management also gives compliance teams a clearer view of rejected entries, affected duty amounts, and potential refund populations. Instead of relying on spreadsheets and manual follow-up, organizations can maintain line-level audit trails and route exceptions to the appropriate specialist. Learn more about modernizing customs operations and tariff-change management at Stable Software.
