An audit-proof HS classification file is a record that lets anyone reviewing it trace how a code was reached: the product facts, the legal reasoning, and the check against the national tariff. It should answer an auditor’s question, “Why this code?”, from the file alone, by citing the General Rules for the Interpretation (GRIs) applied, the Section and Chapter Notes, the WCO Explanatory Notes and any rulings relied on.
Choosing the correct HS code is half the work. The other half is being able to show, from the file alone, how the code was reached. This article sets out what such a file should contain.
Why the file is needed
Customs control has moved largely from checks at the border to post-clearance verification and supply chain compliance reviews, often years after the goods were cleared. A well-built file makes the classification defensible because it follows the GRIs and cites the notes and Explanatory Notes. It keeps the classification consistent across the countries a company imports into and exports from. And it reduces penalties, shipment delays and disputes, because the reasoning is ready when it is asked for.
The three parts of the file
1. Technical product description
Start with the facts. A classification is only as good as the understanding of the product behind it. Include:
- Technical specifications: composition, function, use and design.
- Commercial documents: datasheets, drawings, safety data sheets (MSDS) and photos.
- Intended use and the end-user industry.
Example: for a portable lithium-ion power bank, record the capacity (mAh), voltage, housing material and ports. Those details are what the rules are applied to.
2. Legal classification reasoning
This part ties the product features to the legal text. It should show how you applied:
- The GRIs, in order: GRI 1 first, and the later rules only where GRI 1 cannot decide.
- The Section and Chapter Notes: any exclusions, inclusions or definitions that affect the product.
- The WCO Explanatory Notes that support the reading.
Example: “By application of GRI 1 (the terms of heading 85.07) and GRI 6, the item falls in subheading 8507.60 as a lithium-ion accumulator, supported by the WCO Explanatory Notes (2022).”
Correction: an earlier version of this example cited “GRI 1 and Note 2 to Section XVI” and called 8507.60 a heading. Note 2 to Section XVI sets the rules for classifying parts of machines, and a complete power bank is not a part, so the note has no role here. 8507.60 is a six-digit subheading of heading 85.07.
This is the core of the file. The legal status of each source it cites is explained in the legal anatomy of HS classification, and the rules themselves in the practical guide to the GRIs.
3. Jurisdictional validation
Countries extend HS subheadings in different ways and sometimes interpret them differently. Record how the classification maps to each national tariff you use, for example India’s 8-digit ITC(HS), the EU’s CN and TARIC, the US HTSUS or the ASEAN AHTN. The reasons these differ are covered in how country-specific tariff variations affect your supply chain.
Where relevant, include:
- Customs rulings or advance rulings on the same or similar goods.
- A comparison of how other jurisdictions classify the product.
- The duty rates that apply, with the date you checked them.
This step guards against disputes that arise from national differences.
A structure for the file
A standard, evidence-based layout makes files easy to review and compare. A workable format:
| Section | Contents | Purpose |
| 1. Product description | Commercial name, technical specifications, end use | Establish the facts |
| 2. Proposed HS code | 6-digit HS subheading and national extension (8–10 digits) | Show the national alignment |
| 3. Rule application | GRIs applied in order, starting with GRI 1 | Show the reasoning |
| 4. Legal references | Section Notes, Chapter Notes, Explanatory Note citations | Give the legal basis |
| 5. Supporting evidence | Photos, technical sheets, test reports | Substantiate the description |
| 6. Country-specific confirmation | Local tariff notes and rulings | Check consistency |
| 7. Decision summary | The classification and the reasons for it, including headings rejected | Make the decision transparent |
| 8. Approval record | Review and sign-off by the responsible classification specialist, with date | Assign accountability |
Following the method customs uses
Auditors look at the method as well as the result. A file is easier to accept when it uses the same interpretive structure customs authorities use. It should:
- Cite the HS 2022 Explanatory Notes wherever they apply.
- Name the GRIs applied explicitly, instead of leaving them implied.
- Show the reasoning specific to the product, not a generic template.
- Reach the code in the same order an officer would: headings and notes, then the later rules if needed, then subheadings and the national line.
Common audit red flags
Even experienced teams make documentation errors that weaken their position in an audit:
- No record of how the GRIs were applied, with the code taken from software or from earlier shipments.
- Chapter Notes ignored, a frequent cause of misclassification.
- Reasoning copied from an old file without checking it against the current HS 2022 text. The same check will be needed when HS 2028 enters into force on 1 January 2028.
- An incomplete product description that leaves out composition or function.
- No legal citations, which leaves nothing to point to during customs verification.
These errors also affect origin. Many preferential rules of origin in free trade agreements (FTAs) are written as changes in tariff classification, so a weak classification file can undermine an origin claim as well as the duty calculation.
Transparency across the team
The aim is that any reviewer can follow the logic from description to conclusion. Files written this way also keep the reasoning inside the company when people move on, and let teams in different countries, such as India, Singapore and Europe, classify and defend the same products in the same way.
Checklist: what auditors expect to see
- Product technical details and specifications.
- Step-by-step application of the GRIs.
- Section and Chapter Note citations.
- References to the WCO Explanatory Notes.
- A comparison of national tariff lines, where relevant.
- A written legal justification.
- Evidence of review and sign-off by the responsible classification professional.
Other uses of a good file
A properly documented file does more than get through audits. It shortens disputes, because the reasoning is already written. It supports consistent classification across a group, more accurate duty forecasts and valuation reviews, and simpler internal and external compliance reporting. It also helps the export control team, although the export control classification number (ECCN) is a separate determination under different rules and needs its own record.
Why this kind of written reasoning reduces penalty exposure is discussed in what GRI fluency actually buys you.