How to audit the HTS codes you already use

Short answer: An HTS code audit runs two different tests. The validity check asks whether each 10-digit number in your product master still exists in the current HTSUS (US Harmonized Tariff Schedule). The correctness check asks whether the legal basis (heading text, Section and Chapter notes, the General Rules of Interpretation (GRI) and any CBP rulings) still supports that number for the product as it is made today. Run the first on every code and the second on a risk-ranked sample, sort what you find by type and duty effect, fix the product master, and then decide separately what to do about past entries.

Most teams do only the validity check, because it can be scripted, and then treat “the code exists” as “the code is right.” This guide walks through six steps, with an example of each kind of finding and a decision path for entries already filed.

Why do HTS codes go stale?

HTS codes go stale because the schedule, the product and the interpretation all move. The USITC published the 2026 HTSUS Basic Edition on December 31, 2025 and had reached Revision 21 by October 9, 2026. Most revisions change Chapter 99 duties rather than classifications, but statistical suffixes are added and split during the year, and every HS edition deletes and creates six-digit subheadings. When HS 2022 took effect, subheading 8517.12 (telephones for cellular networks) was deleted and smartphones moved to the new 8517.13. HS 2028, which takes effect on January 1, 2028, brings 299 sets of amendments.

The product moves too. A supplier switches a fabric from woven to knit, adds a motor, or changes the alloy, and the code chosen at onboarding no longer fits. And CBP modifies or revokes rulings, so a classification that leaned on a ruling can lose its support without anyone in your company noticing.

Step 1: extract codes and entry history

Start with two extracts, because the code in your ERP and the code on your entries are often not the same. From the product master take SKU, description, current HTSUS number, country of origin, supplier, date the code was set, who set it, and any linked ruling or memo. From ACE or your broker take entry number, entry date, liquidation date, line HTSUS number, Chapter 99 numbers, entered value, quantity and duty paid, for at least the last five years (the general recordkeeping period in 19 CFR 163.4 and the limitations period in 19 USC 1621).

Join the two on SKU or part number. The first findings often come from the join itself: SKUs where the broker files a different code from the one in the master, usually because the broker corrected it at entry and nobody updated the ERP.

Step 2: validity check against the current HTS

The validity check confirms that every 10-digit number exists in the current schedule. The USITC posts each revision as CSV, Excel and JSON files on its HTS archive page, so download the current file, normalize both lists to ten digits without periods, and match. For each code that fails, find what replaced it: the archive lists the Federal Register notices and proclamations behind each revision, and for HS edition changes the correlation tables for that edition show where each old subheading went. Record the revision you tested against in the audit file.

While the file is open, compare units of quantity: if a line’s unit changed (number to kilograms, or a second unit added), entries will be wrong even with a valid code. And a code that passes Step 2 still has to face Step 3.

Step 3: re-test the legal basis on a sample

The correctness check re-classifies a sample of SKUs from current product facts and compares the result with the code on file. Pick the sample by risk, not at random: high-value lines, codes in “other” baskets, multi-material or multi-function goods, codes set more than a few years ago, and lines with Chapter 99 duties. Unit value outliers are a good way to find candidates, as shown in using USITC unit values to spot likely misclassification. If you need an error rate you can defend to management, use the sampling method in measuring the accuracy of your HTS codes.

For each sampled SKU, write down the answers to these questions:

What is the product today: materials by weight, function, how it is imported (complete, unassembled, in a set)? Get the current spec sheet, not the onboarding description.
Which headings describe it under GRI 1, and do any Section or Chapter notes include or exclude it?
If two headings still apply, which GRI 3 rule decides, and why?
Under GRI 6, which subheading, which 8-digit line (including any Additional U.S. Notes), and which statistical suffix?
Which CROSS rulings cover identical or close products, and has any ruling you rely on been modified or revoked?

A worked example (hypothetical): a 20-ounce stainless steel tumbler has been filed under 7323.93, household articles of stainless steel, since 2019. The 2026 spec sheet shows the supplier moved to a vacuum-sealed double wall in 2024. Heading 9617 covers “vacuum flasks and other vacuum vessels, complete,” and Section XV Note 1 excludes articles of Chapter 96 from the base metal chapters, so at GRI 1 the tumbler now belongs in heading 9617. The code passed the validity check, and the product master was still wrong for two years of entries.

Step 4: sort findings by type and duty impact

Sort each finding by what went wrong and how much duty it moved, because the type tells you the fix and the duty tells you the urgency.

Finding type	Example	Usual duty effect	Fix
Retired code	Master still holds an 8517.12 number for a phone; the broker has been filing 8517.13 since 2022	Usually none on entries; the master is wrong	Update master to the code actually filed, after confirming it
Wrong heading	Vacuum tumbler under 7323.93 instead of heading 9617	Can go either way; may change Chapter 99 exposure	Reclassify, then assess past entries
Wrong statistical suffix	Right 8-digit line, but the “other” suffix used where a specific suffix fits	Usually none on the base rate, which is set at 8 digits, but some Chapter 99 measures and exclusions are written at 10 digits; statistics are wrong	Correct going forward
Unsupported reasoning	Code is right, but the file cites only a supplier’s invoice, or a ruling on a different product	None today; weak reasonable care record	Write the GRI analysis and attach it

Then size the money. Example arithmetic with hypothetical rates: if a SKU entered at $400,000 a year was filed at 2% and the correct line is 6%, the underpayment is $400,000 x (6% – 2%) = $16,000 a year, before any Chapter 99 duty tied to the corrected line.

Step 5: fix the product master

Fix the product master with a dated change record, not by overwriting the field. For each corrected SKU keep the old code, the new code, the effective date, the reason, the reviewer and the analysis. Send the change to your broker in writing, update any ISF data that carries the six-digit code, and check whether the export side (Schedule B or HTS number used in AES) needs the same change. A corrected master changes future entries only; it does nothing to entries already filed.

For a catalog of thousands of SKUs, Steps 3 and 5 are where the hours go. TariffWolf’s bulk service can re-classify an existing product master at the 6-digit HS level and show, SKU by SKU, where its subheading and reasoning differ from the first six digits you file today, with the notes and rulings behind each code and the uncertain items sent to an in-house classifier. Your classifier then confirms or re-picks the last four digits from that documented starting point. The exported audit trail (reviewer, timestamps, sources, reasoning) can go straight into the change record.

Step 6: decide what to do about past entries

What you can do about past entries depends on whether the error cost you or the government money and on each entry’s liquidation status. An entry is deemed liquidated one year after entry unless CBP extends or suspends it (19 USC 1504). Work through the entries in this order:

Unliquidated, within 300 days of entry and at least 15 days before scheduled liquidation: file a post-summary correction (PSC), which can correct errors in either direction.
Liquidated, overpaid, and within 180 days of liquidation: file a protest under 19 USC 1514.
Underpaid on entries outside the PSC window: consider a prior disclosure under 19 USC 1592(c)(4) and 19 CFR 162.74, made before CBP begins a formal investigation. For negligence, the penalty is limited to interest on the unpaid duty, and the loss of revenue must be tendered.
Overpaid and past the protest deadline: usually no recovery route for classification errors; record the finding and fix the master.

Under 19 USC 1592(d), CBP collects lost duties even when no penalty is assessed, and the five-year limitations period runs from the violation. Scoping, timing and tender in a prior disclosure are legal decisions, so involve a licensed customs broker or trade attorney before filing anything; the details are in prior disclosure for HTS errors, and the choice among refund routes is in PSC, protest, 1520(d) or drawback.

Frequently asked questions

How do I check if an HTS code is still valid?

Download the current HTSUS revision from the USITC archive (CSV, Excel or JSON) and match your 10-digit numbers against it. A code that is missing has been deleted or split; the Federal Register notices listed for the revision, or the correlation tables for a new HS edition, show what replaced it. Record which revision you tested.

Does a valid HTS code mean the classification is correct?

No. Validity only shows the number exists. Correctness depends on whether the heading text, legal notes, GRIs and rulings support that number for the product as it is made today, which needs a re-classification from current product facts.

What should I do if my HTS code is wrong?

Correct the product master and tell your broker, then deal with past entries by liquidation status: a PSC for unliquidated entries within the PSC window, a protest within 180 days of liquidation for overpayments, and a prior disclosure for underpayments, with a licensed broker or trade attorney advising.

Does updating our ERP fix entries already filed?

No. The product master controls future entries only. Filed entries are corrected through a PSC, a protest or a prior disclosure, depending on their status and on whether duty was overpaid or underpaid.

How often should we audit our HTS codes?

Run the validity check against each new HTSUS Basic Edition and after any revision that touches your chapters. Re-test the legal basis whenever a product or supplier changes, and plan a full review of affected SKUs before HS 2028 takes effect on January 1, 2028.

Get the order right before worrying about tools. Validity on everything, legal basis on the risky sample, findings sorted by type and money, the master fixed with a record, and past entries handled one route at a time. Teams that skip to the last step without the first four tend to file corrections they later have to correct.

If your product master is large enough that Step 3 cannot be done by hand, TariffWolf’s bulk classification service can re-classify it to six digits with the legal notes and rulings attached to each code and flag every SKU whose current HTS number starts with a different subheading. Send a sample file and review the differences before deciding on the full catalog.

See TariffWolf in action — book a 1-hour walkthrough

Pick a time on the calendar that loads next — no email back-and-forth.