Sep 23, 2026
Which HTS Revision Applied to Your Entry? Version Control for Classification Decisions
The HTS revision that applies to an entry is generally the version in effect at the regulatory time of entry. Identifying the correct revision is important when reviewing historical classifications, confirming the duty rates that applied, or preparing documentation for CBP. Because the HTS can be updated through multiple revisions during the year, the applicable version should be tied to the entry and the effective date of the relevant provisions.
A complete classification record should capture the applicable HTS release, the basis for its effective date, supporting source documents, and any Chapter 99 provisions that applied to the transaction.
What Decides Which HTS Version Governs Your Entry
The Harmonized Tariff Schedule is not a single document with an annual update. The US International Trade Commission compiles and maintains it, publishing a basic edition each year and then issuing numbered revisions whenever legal or statistical changes need incorporating. A revision reproduces the entire schedule even when only a few chapters change, which makes any given release a complete snapshot rather than a patch.
That structure creates the trap. Teams reach for the newest schedule, or the one that was current when they filed the entry summary, and treat it as authoritative. Neither is the legal test. For ordinary consumption entries, 19 C.F.R. § 141.69 sets the governing rule: the applicable duty rates are those in effect at the time of entry as determined under § 141.68, unless an executive action or an enumerated exception provides otherwise.
So the question is not which HTS PDF was newest. The defensible inquiry runs in four parts:
Establish the legally defined time of entry for the transaction.
Identify the provisions and rates effective at that moment.
Check whether a proclamation, executive order, Federal Register notice, Chapter 99 note, warehouse rule, quota rule, or in-transit exception altered the ordinary result.
Select the USITC release that best reproduces the governing text.
The fourth step is evidentiary. The archived release proves what the compiled schedule said; the operative instrument and its effective-date clause prove what the law required. Both belong in the file, and the foundations of tariff classification assume you can produce them.
Which Date Sets the Rate
Four dates attach to a single entry and only one of them ordinarily drives the tariff treatment. Confusing them is the most common source of version error.
Date | What it means | Role in version selection |
|---|---|---|
Date of importation | For non-vessel shipments, the date goods arrive within US customs territory; for vessel shipments, the date the vessel arrives at a US port intending to unlade | Usually not the duty-rate date. Matters for arrival-based rules and in-transit exceptions |
Time of entry | Determined under § 141.68; the result depends on the entry procedure used | Normally determines the applicable rates and provisions |
Entry-summary date | The date the entry summary is filed, recorded in Block 3 of Form 7501 | Ordinarily administrative, unless the procedure makes the entry summary the time of entry |
Liquidation date | The date CBP finalizes classification, value, and duty assessment | Determines whether a Post Summary Correction remains possible and starts the protest clock |
Time of entry is itself variable. Under 19 C.F.R. § 141.68, it can be the moment CBP authorizes release, the filing time the importer requested, the time of arrival within port limits, the time the entry summary is filed where it serves as both entry and entry summary, the presentation time for quota-class merchandise, or the time a warehouse withdrawal and estimated duties are filed. The procedure decides the rule.
One consequence matters for version control specifically. A separate entry summary may ordinarily be filed within 10 working days after the time of entry, so a revision published between release and entry-summary filing does not retroactively replace the provisions that applied at entry. Filing later than the change does not mean the change governs.
How to Establish the Governing Release for a Past Entry
Work the sequence below for each historical entry under review. It moves from procedure to law to evidence, in that order, because reversing the order produces a plausible answer that will not survive scrutiny.
Determine the entry type and procedure used: Consumption entry, warehouse withdrawal, immediate delivery, and quota-class merchandise each route to a different subsection of § 141.68.
Establish the regulatory time of entry under the subsection that matches that procedure. Record the reasoning, not just the resulting date.
Identify the HTS provisions effective at that moment, at both the 8-digit legal subheading and the 10-digit statistical level.
Check § 141.69 for exceptions covering warehouse goods, immediate delivery, overcarriage, and executive-action scenarios before accepting the ordinary result.
Read the operative proclamation, order, notice, or Chapter 99 note for transaction-specific timing. Effective clauses commonly refer to goods entered for consumption or withdrawn from warehouse at or after a stated time, and some carry in-transit carve-outs tied to loading date.
Reconcile the result against the archived USITC release and the transmitted entry summary, then save both.
Caution: Do not overwrite or delete the existing classification decision while working through this sequence. If the review turns up an error, the superseded decision and its effective period are part of the evidence trail. Freeze it, then supersede it.
A note on the shortcut most teams use. "Take the last revision published before the entry date" is a reasonable way to find a candidate release, and wrong often enough to be dangerous as a rule. A revision can incorporate changes effective on its publication date, changes effective earlier, provisions taking effect shortly after, and technical corrections made retroactive. Use it to locate the document, then verify against the source instrument.
What the USITC Archive Proves, and What It Does Not
The USITC HTS Archive holds editions from 1989 forward. It is the right starting point and an insufficient stopping point, because different artifacts within it carry different evidentiary weight.
Source | What it preserves | Limitation |
|---|---|---|
Complete archived release | The schedule as compiled for that edition or revision, including legal text, rates, and Chapter 99 as incorporated | A snapshot only; later instruments can carry earlier or transaction-specific effective dates |
Preface | Laws, proclamations, executive actions, and notices incorporated since the previous release | Summarizes sources without replacing their operative text |
Change Record | Provision changed, type of change, effective date, and source instrument | Generally incremental, not cumulative across a year |
CSV, XLS, or JSON export | Structured tariff lines, descriptions, units, and rate fields for database comparison | Excludes section and chapter notes, endnotes, and classification context |
Federal Register source | The legally operative amendment, annex, effective-date clause, and transition rules | May need reconciling against later amendments |
CBP CSMS or ACE message | Filing instructions and confirmation that records were implemented in ACE | Deployment timing is not the legal effective date |
Treat a change record as a delta. Establishing every change across a year means reviewing each intervening change record or comparing complete machine-readable releases, not reading one summary.
The archive itself carries a caveat worth recording: some early files lack graphics or header information because of format changes over the decades, though they retain what is needed to identify historical duty rates.
What a Versioned Classification Decision Should Record
The distinction that makes a file defensible is between a classification conclusion and a versioned classification decision. A conclusion says a SKU sits in heading 8504. A versioned decision says that based on product facts version 4, the SKU was classified in that subheading under a named HTSUS release, checked on a stated date, for entries occurring during a defined effective period, with specified Chapter 99 overlays.
No primary source prescribes a field-by-field revision record. The obligations that create the need are the importer's duty of reasonable care under 19 U.S.C. § 1484 and the five-year record retention rule at 19 C.F.R. § 163.4. Working back from those, a classification master should carry:
Decision identifier distinct from the tariff number, so the record survives a code change.
Product identity: SKU, model, supplier part number, composition, function, use, and the technical documents reviewed.
Classification at the full 10 digits, with the 8-digit legal subheading stored separately.
Analysis: The GRIs applied, section and chapter notes, Additional US Rules, rulings consulted, and material factual assumptions.
HTS release by exact title, such as HTSUS 2026 Revision 18, plus its publication date.
Effective-date basis: The time-of-entry rule used, the source instrument, its effective clause, and any transition or in-transit exception.
Chapter 99 stack: Every additional number, relevant US note, rate, exclusion, and expiration date.
Source evidence: Saved cover page, relevant chapter and notes, change record, preface, and CBP implementation guidance.
Approval and review evidence: Analyst, reviewer, decision date, last-checked date, release checked, and next trigger.
Supersession link: Prior decision ID, replacement ID, effective date, and affected entries.
The Chapter 99 line deserves particular attention. Products stay classified in their ordinary Chapters 1 to 97 provision while the Chapter 99 number supplies the additional duty, exclusion, or temporary treatment. A product database can look entirely stable while the entry's total tariff treatment has moved underneath it, which is why the Section 301 list structure belongs in the review record rather than in someone's memory.
Where Version Control Breaks
Version control breaks in six distinct ways.
Stale suffix: The 8-digit legal classification is still valid, but the 10-digit statistical reporting number was discontinued or divided. The product master keeps sending the old suffix until ACE rejects it, at which point a filer substitutes a current one without updating the underlying decision record.
Split subheading: One provision becomes two or more based on a factual distinction such as composition, dimensions, or intended use. Blind code mapping cannot pick the successor; the amended legal text has to be reapplied to each affected SKU.
Deleted provision: A number disappears through renumbering, merger, or termination. Treating the nearest numeric neighbor as an automatic crosswalk produces a legal misclassification that looks tidy in the database.
Chapter 99 omission: The ordinary classification stays correct while an additional duty, exclusion, or temporary provision changes. Nothing in the product record signals the problem.
Effective-date mismatch: A new code gets assigned to all open shipments based on publication date, even though some goods entered before the effective time or qualify for an in-transit exception. The mirror image happens when a revision posts after the provision's effective date.
Revision drift: The file stores "HTS checked" or a URL to the live USITC search page. Eighteen months later that URL displays current text, not the text actually relied on. The check happened; the evidence of what was checked did not survive.
That last one is the quiet failure. It usually surfaces when CBP issues a Form 28 requesting information for a classification review, and the response file shows a current classification that can be defended alongside no record of what governed the historical entry.
What to Do When a Code Turns Out to Be Superseded
Finding a superseded number does not establish a violation. Determine first whether the change was statistical only, whether the original provision was valid at the legally defined time of entry, and whether the replacement alters duty, admissibility, quota, trade-remedy treatment, or reporting. A discontinued 10-digit suffix does not necessarily mean the 8-digit rationale changed.
Route the correction by entry status:
Entry status | Route | Timing |
|---|---|---|
Entry summary not yet filed | Correct classification and Chapter 99 treatment before transmission | Entry summary ordinarily due within 10 working days after entry |
Unliquidated, PSC-eligible | File a Post Summary Correction through ACE | Generally within 300 days after entry and no later than 15 days before scheduled liquidation, whichever comes first |
Liquidated, protest period open | Consider a protest where the disputed classification is a protestable liquidation decision | Within 180 days after liquidation or reliquidation |
Possible material false statement across entries | Assess prior disclosure with customs counsel | Before, or without knowledge of, the start of a formal investigation |
Protest period closed | Determine whether any statutory correction, reliquidation, or refund mechanism remains | Highly fact-specific |
Warning: Where the review suggests a pattern of material misstatement across multiple entries, take advice before filing corrective submissions. A prior disclosure must satisfy 19 C.F.R. § 162.74 and must precede knowledge of a formal investigation, so the sequence in which you correct and disclose has consequences that a routine PSC does not carry.
Two operational points. Increases in estimated duties resulting from a PSC must now be paid electronically through ACH under the modified NCAP test. And the PSC framework itself is maintained through Federal Register notices rather than one consolidated CFR provision, so eligibility and payment rules should be checked against current CBP business rules each time a correction is prepared rather than assumed from the last one.
The Difference Between a Classification and a Versioned Decision
Most classification files answer the question "what is this product?" The files that survive a CBP review answer a harder one: "what governed this transaction, when, and how do you know?" The gap between those two is where version control lives, and closing it costs almost nothing at the point of decision while costing a great deal to reconstruct afterwards.
Practically, that means three habits:
Record the exact HTS release: Save the release title instead of relying on a live search-page link.
Capture the effective-date rule: Record the operative clause, not just the date itself.
Keep superseded decisions: Preserve older classifications with their effective periods instead of overwriting them.
Treating classification as a versioned record makes historical reviews easier to trace and support. Gaia keeps the rationale and source evidence together, but the process matters more than the tool. It starts with understanding what each digit of the code represents and which release supported the decision.
Gaia’s Tariff Audit platform helps importers review historical entries, identify classification discrepancies, and prioritize corrective action. Get your free trial to see how Gaia can simplify historical entry reviews.
FAQ
Does a new HTS revision automatically change my existing classifications?
No, a revision is a compiled snapshot, not an instruction to reclassify. Whether a classification changes depends on the source instrument behind the revision and its effective-date clause. A revision may affect none of your products, carry statistical-only changes at the 10-digit level, or carry legal changes at the 8-digit level requiring the amended text to be reapplied.
Is a discontinued 10-digit suffix a compliance problem?
Not necessarily. The final two digits generally form a nonlegal statistical reporting number, and the 484(f) Committee can modify them without touching the legal 8-digit subheading. Establish whether the change was statistical only before treating it as a misclassification. Changes at the 8-digit level can alter both classification and duty treatment.
How long do I need to keep the version evidence?
Entry-related records are generally subject to a five-year retention requirement under 19 C.F.R. § 163.4, measured from the date of entry. Because a defensible response depends on reproducing what governed at the time, retention should cover the archived release and the source instrument, not only the entry paperwork.
What if the archived file for my entry period is incomplete?
The USITC archive notes that some early files omit graphics or header information because of format changes, while retaining what is needed to identify historical duty rates. Where a release is incomplete, fall back to the Federal Register source for the operative amendment, which carries the effective-date clause.
