How to audit the HTS codes on past entries, line by line

Why audit HTS codes from the entry export and not from the catalog?

A product catalog says how you would classify a part today. An entry says how it was classified on the day it crossed the border, and that is the claim CBP holds you to. 19 U.S.C. 1484 makes the importer of record responsible for using reasonable care to declare the classification and rate of duty, whoever typed the number.

The two often differ. A broker may map a part to a different number when the master record holds a retired statistical suffix. A new product may have been entered under a placeholder before anyone set up the master. A rush shipment may have been filed by a different broker with its own product file. None of that shows up when you review the catalog, and all of it shows up in the entry export.

The export also carries what the catalog cannot: the entry date, the Chapter 99 numbers stacked on the line, the entered value, the quantity in the tariff's unit and the duty paid. Those are what turn "this code looks wrong" into a finding with a dollar amount and a deadline.

So start from the broker's full entry export for the period you are auditing, every entry and every line, and treat the catalog as one piece of evidence about what the product is.

What do you pull from each line of the entry?

Each check compares a field on Form 7501 with the product facts. The field names below follow CBP's Form 7501 instructions (revision 02/26). For the full block-by-block reference, see Form 7501 field by field.

Pair each line with the commercial invoice description, the part number and the product facts that decide classification: what it is made of, what it does, how it is used, whether it is complete, and whether it is imported with other items as a set. Specification sheets, drawings and photos settle more classification questions than any description field.

How do you apply the General Rules of Interpretation to a past line?

The General Rules of Interpretation (GRI) at the front of the Harmonized Tariff Schedule are applied in order, and the order is the method. Skipping to "essential character" before reading the heading terms and notes is the most common way to reach the wrong number.

1. Read the heading terms and the section and chapter notes (GRI 1). Titles of sections and chapters are for reference only. Classification is decided by the terms of the headings and any relative section or chapter notes. Notes often exclude goods outright or send them elsewhere, so read them before you compare headings.
2. Check incomplete, unassembled and mixed goods (GRI 2). An unfinished article that already has the essential character of the finished one is classified as the finished article (GRI 2(a)), and so is a complete article entered unassembled. A heading for a material covers mixtures and goods made partly of it (GRI 2(b)), which sends goods of more than one material on to GRI 3.
3. Only when two headings both fit, use GRI 3. The most specific description wins (GRI 3(a)). If two headings each describe only part of a composite good or set, use the component that gives it its essential character (GRI 3(b)). If that cannot be decided, use the heading that comes last in numerical order (GRI 3(c)).
4. Use GRI 4 and 5 where they apply. Goods that fit nowhere go to the heading for the goods they are most like (GRI 4). Fitted cases and normal packing go with the goods they hold (GRI 5).
5. Repeat at subheading level (GRI 6). Compare only subheadings at the same level, with the subheading notes and, unless the context requires otherwise, the section and chapter notes.
6. Apply the Additional U.S. Rules where the heading depends on use or parts. A classification controlled by use (other than actual use) is decided by the principal use in the United States of goods of that class or kind at or just before import (Additional U.S. Rule 1(a)). A classification controlled by actual use needs the use intended at import, carried out, and proved within 3 years of entry (Additional U.S. Rule 1(b)). A provision for "parts" covers products used solely or principally as parts of the article, but does not prevail over a specific provision for that part (Additional U.S. Rule 1(c)).
7. Then pick the statistical suffix that matches the description, which completes the 10-digit HTS code.

Do this against the HTS revision in force on the entry date. 19 CFR 141.69 says the rates applicable to merchandise are the rates in effect at the time of entry, and headings, statistical suffixes and notes change between revisions. Write down the revision you used next to each conclusion. HS classification produces that kind of written record: every heading considered, the reasoning, and the detail that would change the answer.

Which lines should you check first?

A full export can hold thousands of lines. Rank them so the first hours go where errors are both likely and expensive.

• The same part number under two HTS codes. At least one set of entries is wrong. Sort the export by part number and HTS code and this list falls out in minutes.
• The highest duty paid per product, totalled across the period, including every Chapter 99 layer. A code error on a line with a stacked rate moves far more money than one on a line with a single low rate.
• Lines where the code decides a Chapter 99 measure. Section 232 and Section 301 apply by listed HTS numbers, so a code on one side of a list boundary is worth checking twice. The duty calculator shows the stack for a code, an origin and a date.
• Basket provisions ending in "other" where a more specific heading may name the goods.
• Parts entered under the heading of the finished article, or the reverse, and unassembled kits.
• Composite goods and sets classified under GRI 3, which turn on facts the description field rarely shows.
• New products in their first months of import, before anyone reviewed the master record.

When does a CBP ruling settle the classification, and when does it not?

A ruling settles a line only when three things hold: the goods are identical to those the ruling describes (19 CFR 177.9(b)(2)), the facts in the request were accurate and complete (177.9(b)(1)), and the ruling was issued to you, since 19 CFR 177.9(c) says no one else should rely on it. The Form 7501 instructions also require the ruling number under the HTS number with the prefix "RLNG", with uncovered items on their own line, so a ruling the entry does not cite is not doing its job.

So the audit checks rulings in both directions. A line that cites a ruling for goods that no longer match it is a finding. A line with no ruling, where a published ruling on identical goods points to a different number, is a finding too. The full table of when a ruling controls, how to search CBP's rulings database for those, and what a new ruling can do for entries already filed are on binding rulings and CROSS for past entries.

What does a wrong HTS code cost on the line?

A code change rarely moves only the base rate. It can move the Chapter 99 stack, the unit of quantity, any AD/CVD exposure and the trade-agreement rate, all at once and sometimes in opposite directions. Work out the full stack for both codes on the entry date before you call a finding an overpayment or an underpayment. The arithmetic, with interest and penalty exposure, is on what a misclassification costs on past entries.

Origin interacts with classification here. The same code can carry different Chapter 99 duties for different origins, so a classification audit that finds a new code should also confirm the origin on the line. See country of origin on past entries.

What do you do with each finding?

A finding becomes actionable when it is tied to an entry, a line, a dollar amount and the entry's liquidation status. The route follows the status.

The windows come from these sources. CBP's post-summary correction page says a correction can be filed within 300 days of the entry date and up to 15 days before the scheduled liquidation date, whichever is earlier, and that the entry summary cannot be under CBP review. 19 U.S.C. 1514(a) makes the classification and rate of duty protestable, and 19 CFR 174.12(e) gives 180 days after liquidation for entries made on or after December 18, 2004. 19 CFR 162.74 defines a prior disclosure as telling CBP about a violation before, or without knowledge of, a formal investigation, with a tender of the duties lost.

The general order for any audit finding (confirm, list every entry with the same pattern, get each liquidation date, choose the route, fix the source) is on the post-entry audit pillar. Three points are specific to a classification finding:

1. Widen by product, not by HTS number. The same wrong reasoning usually sits behind several part numbers in one product family, some filed under other numbers. Search the export by part family and description as well as by the declared code, so one finding becomes the full list. Then get each entry's liquidation date; see how to check entry liquidation status.
2. File the GRI reasoning with the correction. A protest or prior disclosure on classification is argued from the heading terms, the notes and any rulings, so the written GRI steps from the audit become the core of the filing. For a protest built from the finding, see how to file a customs protest; for underpayments, see prior disclosure after you find an underpayment.
3. Decide whether the product needs a ruling for future entries. Rulings are requested only for prospective transactions (19 CFR 177.1(a)(1)), and a question about a liquidated entry may not be the subject of a ruling request (19 CFR 177.1(a)(2)(ii)).

Filing stays with your broker or your own filer. A protest or a prior disclosure is worth confirming with a licensed customs broker or trade counsel before it goes in.

What should the audit record leave behind?

Keep one row per line reviewed: entry number, line, entry date, declared HTS code, proposed HTS code or "confirmed", the HTS revision used, the GRI steps and notes relied on, the rulings checked, the reviewer, the route chosen and its deadline. Keep the product evidence with it.

That record does two jobs. It supports the correction or protest you file now. It is also evidence of reasonable care if CBP asks later, and 19 CFR 163.4 requires records relating to an entry to be kept for 5 years from the date of entry. A note that says "checked, correct, GRI 1 and note 2 to chapter 85" is worth more in a later review than an unexplained code.

How does TariffSense fit into an HTS code audit?

TariffSense reads Form 7501 lines from entry summaries and broker entry exports, checks each line's classification and Chapter 99 stack against the measures in force on that entry's date, and looks across your history for the same product classified differently from one entry to the next. Each finding states what was declared, what the rule says and the corrected value, in both directions, so the reviewer decides with the evidence in front of them. Classification decisions and filing stay with your team and your broker. The post-entry audit page describes what goes in and what comes back.

What should you do next on your own entries?

Ask your broker for the full entry export for the last twelve months, with every line, every Chapter 99 number and every liquidation date. Sort it by part number and HTS code and list every part filed under more than one code. Then take your five highest-duty products and walk one line of each through the GRI steps above, against the HTS revision for its entry date. Every confirmed error gets a row with its route and deadline before anyone touches the product master. The post-entry audit pillar covers the other checks to run on the same lines.