Schedule B vs. HTS classification,
what's actually the difference?
Companies that both import and export in the United States often run into two different 10-digit codes for what feels like the same product. They are not interchangeable, and using the wrong one causes real filing problems. This guide covers what Schedule B and HTS codes are, how they relate to each other, and which one applies depending on which direction your goods are moving.
8 min read · Trade compliance basics
What each system actually is
Both Schedule B and the Harmonized Tariff Schedule of the United States, or HTSUS, are built on the same foundation: the six-digit Harmonized System maintained by the World Customs Organization. From there, the United States extends that shared base into two separate 10-digit systems, one for goods leaving the country and one for goods entering it.
Schedule B is maintained by the US Census Bureau. It exists to track and report what the country exports, and it is the code that goes on Electronic Export Information filed through the Automated Export System, or AES, whenever a shipment requires that filing. It carries no duty rate, because exports out of the US generally are not taxed.
The HTSUS is maintained by the US International Trade Commission and used by Customs and Border Protection to process goods coming into the country. It determines the duty rate owed, whether a quota applies, and whether a shipment qualifies for a preferential rate under a trade agreement. Unlike Schedule B, it exists specifically because money changes hands at the border.
Why the distinction matters
The two systems look similar enough, sharing the same first six digits, that it is easy to assume one code works everywhere. It doesn't, and the two systems are checked by two different agencies for two different purposes.
| Mistake | What tends to happen |
|---|---|
| Filing AES with an HTSUS-only code | The code may not exist in Schedule B at all, and the filing gets rejected or flagged. |
| Filing a CBP entry with a Schedule B number | CBP requires an HTSUS code; Schedule B numbers are not valid for import entries. |
| Assuming duty rates apply to Schedule B | Schedule B carries no duty information, so any rate quoted against it is meaningless. |
| Using stale cross-reference data | The Census Bureau's Schedule B <-> HTS concordance is updated annually and can shift codes. |
| Reporting export statistics under the wrong code | Distorts government trade data and can trigger a correction request from Census. |
None of these mistakes are really about picking the wrong product description. They come from treating two systems that share a lookalike structure as though they were one and the same.
Where the two systems diverge
Both codes start out identical. The first six digits are the international Harmonized System heading, agreed on by every country that uses it, and they describe the same product the same way whether the code ends up feeding an export filing or an import entry.
The split happens at the seventh digit. From that point forward, Schedule B and the HTSUS are maintained by different agencies, updated on different schedules, and structured around different goals: one counts what leaves the country, the other taxes what arrives.
Because the two systems branch off separately, a code that is correct for an export filing on a given product is not automatically the code CBP expects on the same product coming back in for repair, or on a similar product being imported from a supplier. The last four digits have to be looked up in the right system for the direction the goods are actually moving.
Finding the right code, step by step
The process for landing on the correct code is short, but it depends entirely on getting the first step right. Everything downstream follows from which direction the shipment is going.
Step four catches more errors than any other. Because the two systems are maintained independently and updated on different cycles, the tenth-digit endings do not always line up one to one, even when the first six digits match perfectly. The concordance tool exists specifically to catch the cases where they drift apart.
Common mistakes companies make
Reusing an import HTSUS code on an export filing
The two schedules do not always end the same way past the sixth digit. Copying an HTSUS number straight onto an AES filing can produce a code that does not exist in Schedule B at all.
Treating Schedule B as a source for duty rates
Schedule B has no duty information attached to it. Anyone quoting a duty rate off a Schedule B number is quoting a rate that doesn't exist in that system.
Skipping the annual concordance update
Both schedules get revised periodically, and not always in sync. A code pair that matched correctly last year can drift out of alignment without anyone noticing until a filing gets rejected.
Assuming one system covers export licensing questions
Schedule B and HTSUS both describe what a product is, but neither one determines whether an export license is required. That depends on a separate classification, the Export Control Classification Number, which has to be checked on its own.
When to use which
The fastest way to avoid mixing the two up is to anchor the decision to a single question: which direction is the shipment moving? Everything else follows from that.
| Task | Use |
|---|---|
| Filing Electronic Export Information in AES | Schedule B |
| Reporting official US export statistics | Schedule B |
| Filing a CBP entry for imported goods | HTSUS |
| Calculating duty owed on an import | HTSUS |
| Checking eligibility for a trade agreement rate | HTSUS |
| Both directions for the same product line | Both, tracked separately |
Companies that both import and export the same products often end up maintaining two entries per SKU in their internal systems, one Schedule B number and one HTSUS number, precisely because the two are not the same code wearing two different labels.
Getting started
If your company ships in both directions, a few habits keep the two systems from getting tangled:
- Store Schedule B and HTSUS numbers as two separate fields per product, not one shared code.
- Re-run the Census Bureau concordance check whenever either schedule is updated, not just once at setup.
- Confirm which filing a code is headed for, AES or a CBP entry, before it goes on any document.
- Remember that neither code answers an export licensing question; check the ECCN separately when that applies.
The two systems exist for genuinely different reasons, one for counting exports and one for taxing imports, and once that distinction is built into how a company tracks its products, most of the filing errors that come from confusing the two disappear on their own.
Get both codes right,
for every product you move.
Enthron classifies against Schedule B and the HTSUS in parallel, so exports and imports on the same product line never fall out of sync.