
Can You Use an HTS Code to Export? Schedule B vs HTS-10
Yes, you can use a ten-digit Harmonized Tariff Schedule (HTS) code for US export reporting, provided the code is eligible under the Foreign Trade Regulations (FTR). A valid import HTS code is not automatically accepted in the Automated Export System (AES), and some codes require a different Schedule B classification. An identical ten-digit match between HTS and Schedule B is not always necessary either.
Exporters need to verify whether their HTS code is permitted for export reporting, check for classification differences, and confirm that the code is valid for the shipment date to avoid AES rejections and reporting errors.
Quick answers
Can an HTS-10 replace a Schedule B number? For most commodities in chapters 1 through 97, yes. The permission is conditional and has published exceptions.
Do the same ten digits have to appear in both schedules? No. Substitution is permitted for eligible HTS numbers whether or not an identical export number exists.
Are all HTS numbers eligible? No. Census’s invalid-for-AES list bars specific numbers, import codes in HTS chapter 98 are excluded, and the permission covers chapters 1 through 97 only.
Does an ITN mean the classification was approved? No. An ITN confirms that AES accepted the shipment, not that the number describes the goods.
What does the FTR actually permit?
The FTR lets you report an HTS number instead of a Schedule B number, but the same sentence that gives the permission also limits it. Under 15 CFR 30.6(a)(12), your Electronic Export Information (EEI, the shipment data you file in AES) needs a ten-digit Schedule B number. You can report the ten-digit HTS number in its place “except as noted in the headnotes of the HTSUSA” (the official name of the import tariff schedule). Census says the same thing in its Schedule B introduction: for most goods classified in chapters 1 through 97, you can report either number.
In practice, that exception comes down to three published limits:
Chapters 1 through 97 only: The HTS Notice to Exporters limits the permission to statistical reporting numbers in chapters 1 through 97, with their descriptions and units of quantity, subject to the exceptions it lists.
The invalid-for-AES file: Census publishes a list of HTS numbers that cannot be reported in AES.
Chapter 98: The file also notes that all import codes in HTS chapter 98 are excluded, even though those codes are not itemized in it.
Does an HTS-10 need an identical Schedule B twin?
No, and here’s an example to show why. The HTS splits purebred breeding horses by sex at the statistical level, 0101.21.0010 for males and 0101.21.0020 for females. Schedule B has one combined number, 0101.21.0000, reported in units of number. Neither import suffix exists as an identical Schedule B number, and both remain usable because the rule permits substitution rather than requiring identity.
Before you report an HTS number on an export filing, check that it’s permitted for export reporting, current on the shipment date, and correct for the goods. You don’t need the same ten digits to appear in Schedule B.
Where do the two schedules diverge in practice?
At the national digits, not only the final two. Both schedules share the six-digit Harmonized System subheading, then extend it for different purposes: the HTS for tariff and import statistics, Schedule B for export statistics. Several import classifications can combine into one export classification, and the reverse happens too, which defeats suffix copying.
Goods | Import HTS-10 | Schedule B export numbers |
Purebred breeding horses | 0101.21.0010 males, 0101.21.0020 females | 0101.21.0000, combined |
Frozen bovine offal other than tongues and livers | 0206.29.0000, invalid in AES | .0010 hearts, .0020 kidneys, .0030 brains, .0040 sweetbreads, .0050 lips, .0090 other |
Switching and routing apparatus | 8517.62.0020, invalid in AES | .0030 Wi-Fi, .0040 Bluetooth, .0060 proprietary protocol, .0070 multiprotocol, .0080 other |
Other apparatus under 8517.62 | 8517.62.0090, invalid in AES | 8517.62.0085 |
Cotton seed other than seed for sowing | 1207.29.0000, invalid in AES | 1207.29.0010 animal feed, 1207.29.0090 other |
The last four rows share a pattern. The import number is perfectly valid on an entry and barred from AES, because the export schedule needs product information the import suffix never captured. A network equipment exporter cannot pick between .0030 and .0070 without knowing the transmission protocol, and nothing in 8517.62.0020 records it.
The cotton seed row also shows why timing matters. Effective January 1, 2026, Schedule B 1207.29.0000 was split into 1207.29.0010 and 1207.29.0090. The last digits of a code can change mid-cycle, without a new edition of the global Harmonized System.
Is there an official crosswalk that solves every mismatch?
No single file does. Census maintains an AES concordance resource with separate import and export files, layout documentation, change files and the list of HTS numbers that cannot be reported in AES. Those files establish code membership, descriptions, units, dates and export eligibility. They do not establish a one-to-one product crosswalk, because a one-to-many relationship cannot be resolved by digits.
When one import number splits into several export numbers, the most useful official guide is the Notice to Exporters itself. It lists the import numbers you can’t report in AES and names the Schedule B numbers to use instead. You’ll still need the product details (like the transmission protocol for networking equipment) to pick the right one.
What do the AES rejection messages mean?
Four responses cover the commodity number, and the current reference is AESTIR Appendix A, version 4.4 of October 2026.
Response | Severity | Resolution |
622: SCHED B/HTS NBR MISSING | Fatal, unless the household-goods exception applies | Supply the number, correct and retransmit |
623: SCHED B/HTS NBR UNKNOWN | Fatal where the number is not a known AES value | Verify a valid number, correct and retransmit |
624: SCHED B/HTS NBR OUTDATED, CANNOT BE USED | Fatal for an expired number outside the permitted period | Compare the estimated export date against the number’s begin and end dates |
625: SCHED B/HTS NBR OUTDATED, IN GRACE PERIOD | Verify response, covering a 30-day window in which an outdated number is still accepted | Update the classification file before the window closes |
Response 625 is the one that hides a problem. Census’s July 6, 2026 notice on the July 1 codes said AES would accept outdated codes for 30 days beyond the June 30, 2026 expiry date, which means through July 30. A filing that passes on a grace-period code will fail once the window closes.
What if AES accepts a number that is wrong for the goods?
Even after AES accepts your filing, you’re still responsible for getting the classification right. Section 30.6 requires the correct number plus an English description detailed enough to verify it. It also says that reporting the correct number doesn’t excuse an incomplete or inaccurate description. If you find an error later, Section 30.9 requires you to correct it as soon as you know about it.
Civil penalties are available for violations of Part 30, and knowingly submitting false or misleading AES information can trigger criminal provisions. A mistaken suffix is not in itself a knowing violation, but treating acceptance as approval is how classification errors survive in a filing history. The ITN is the response to an accepted shipment, nothing more.
When is no Schedule B number required?
Four situations arise, and only one of them is substitution:
An eligible HTS number is reported instead: That is substitution, not an exemption from reporting a commodity classification number at all.
Qualifying household goods: Section 30.38 provides limited reporting, and response 622 expressly excepts household goods reported with Export Information Code HH. The exception does not stretch to any shipment labeled personal effects.
An applicable EEI exemption: Section 30.37(a) exempts commodities valued at $2,500 or less per individual Schedule B or HTS classification, from one USPPI to one ultimate consignee on a single exporting conveyance. The total shipment value is not the test, and a mandatory-filing condition under 30.2(a)(1)(iv) overrides the exemption.
Qualifying Canada-destination shipments: Section 30.36 generally exempts US-originating shipments with Canada as the ultimate destination, subject to the mandatory-filing exceptions. Goods merely stored in or transiting Canada for a third country do not qualify.
Note what the third situation implies. The classification determines the exemption threshold, so “no EEI line is required” is not the same as “classification never mattered.”
Where do you get an answer you can rely on?
From the agency that owns the schedule in question, and the two agencies do not substitute for each other:
Census: It runs a commodity-classification assistance channel at eid.scheduleb@census.gov and 1-800-549-0595, option 2.
CBP: It issues binding advance rulings in connection with importation, and USITC directs anyone seeking a binding classification ruling on imported goods to CBP.
Managing import and export classifications for the same product requires keeping HTS and Schedule B codes accurate, current, and aligned with reporting requirements. Gaia Dynamics helps you manage both classifications within a single product record, without relying on one code to determine the other.
Try Gaia Dynamics to see how it can support classification management across your product catalog.
Frequently Asked Questions
Can I report the same HTS-10 I use on my import entry?
Often, but only if it is a chapter 1 through 97 number that is not on Census’s invalid-for-AES list and is current on the export date. Check the list and the shipment date for each product.
Does AES accepting a number mean the classification is right?
No. An ITN shows that AES accepted the filing. Section 30.6 still requires the correct number and a detailed English description, and section 30.9 requires correction as soon as an error is known.
Who can give a binding classification answer?
The agency that owns the schedule. Census answers Schedule B and AES questions, and CBP issues binding rulings on import classification. A CBP ruling does not override the FTR’s limits on using that number in an export filing.
Can an HTS number be valid on one date and invalid on another?
Yes. Numbers carry begin and end dates, and a number that is outdated on the estimated export date triggers response 624, or response 625 inside the 30-day grace window. Check the shipment date as well as the number.







