The CBP filer code list is a reference that pairs filer codes with filer names and cites 19 CFR 142.3a(c). For import, logistics, and compliance teams, its practical value is straightforward: it can help connect a code appearing in an entry-related record with the name shown in the directory. But a code-name match is only one data point. Teams should treat the list as a lookup aid, preserve the exact identifier, and verify that the information is appropriate for the transaction and the current workflow.
What the CBP filer code list contains
The directory is organized into two fields: Filer-Code and Filer-Name. Each row associates a code with a named company or individual. Many entries use three digits, such as 101 for Kuehne & Nagel Inc. The directory also includes alphanumeric codes, such as 83R for Alltech Industrial, LLC and 8ED for Bosch Rexroth Corporation.
The names cover a broad range of organizations and people. Some entries identify customs brokers, freight forwarders, or logistics businesses; others are manufacturers, importers, and other companies or individuals. The list itself does not categorize entries by business type, explain a filer’s role in a particular shipment, or describe the scope of services an organization provides. A name in the directory should therefore not be treated as confirmation of any of those details.
Using the list for a filer code lookup
In operational settings, the directory can support basic identification and cross-checking. For example, a team reviewing a record with code 670 can look up the corresponding listed name, SICK, INC. That comparison may help staff investigate whether the code in a document or internal record matches the name they expected to see.
A simple lookup process can reduce avoidable transcription errors:
- Capture the code as recorded. Preserve every character, including letters and leading zeros where present. Do not assume that all codes are numeric or that similar-looking characters are interchangeable.
- Search the code field. Locate the exact code in the directory rather than relying on a partial name match.
- Compare the associated name. Check the listed name against the relevant shipment, broker, or internal reference record.
- Record the result and its source. If the lookup informs an operational decision, note which version of the reference was consulted and when.
- Escalate discrepancies. If the code and expected name do not align, resolve the difference through the appropriate internal or external verification process rather than guessing.
Why exact code handling matters
The directory’s mixed formats make consistent data handling important. A system that assumes codes contain digits only could reject or alter valid alphanumeric values. Similarly, treating a code as a number instead of text may strip a leading zero in systems that store numeric fields without preserving formatting. That can make an otherwise valid lookup fail.
For integration teams maintaining ERP, transportation, or customs-related data, filer codes should be stored and transmitted as identifiers, not values used for arithmetic. Validation rules should accommodate both numeric and alphanumeric formats where the applicable data source does. When importing a reference file, retain the original code and name fields and review any records that fail formatting or matching checks.
What the directory does not establish
A directory entry should not be mistaken for a complete compliance determination. The material provided is a code-and-name listing that cites 19 CFR 142.3a(c); it does not provide shipment-specific filing instructions, explain the responsibilities associated with a particular entry, or establish whether a listed name or code is suitable for a given transaction. Nor does the listing itself state when it was last updated.
These limits matter in procurement, onboarding, and day-to-day entry preparation. A successful lookup confirms only that the code and name appear together in the version being consulted. It does not, by itself, validate a business relationship, authorize a filing, or confirm that the directory reflects the latest information. When a decision depends on current status or legal requirements, consult the relevant authoritative source and your organization’s established customs procedures.
Practical controls for operations and compliance teams
Teams can make the directory more useful by incorporating it into controlled data practices rather than treating it as an informal list. Consider the following checks:
- Keep the code in a dedicated text field so letters and leading zeros are preserved.
- Maintain the associated filer name as a separate field and avoid replacing the code with a name-only reference.
- Document the source and date of any reference version used in a workflow.
- Use a defined review path for mismatches, unfamiliar codes, and changes to stored records.
- Separate directory matching from any broader legal, operational, or vendor approval review.
For plant managers and operations leaders, these controls can support cleaner handoffs between logistics, trade compliance, procurement, and finance. For system integrators, they provide clear data requirements for interfaces and master-data validation without assuming that a code alone carries all the information needed for a transaction.
Conclusion
The CBP filer code list is best used as a structured reference connecting listed codes with listed names. Its mixed numeric and alphanumeric formats make exact capture and text-based handling important, while the absence of update details and transaction-specific guidance makes verification essential. Used with those limits in mind, the directory can support record checks and smoother customs-related data workflows—but it should not replace current-source validation or established compliance review.