How to Automate US Customs Filing

How to Automate US Customs Filing

To automate US customs filing you connect your software to CBP's Automated Commercial Environment (ACE) through EDI or ABI, register your identity with Form 5106, and feed clean, classified data upstream so filings clear on the first try.

TL;DR

• What it means: connecting your software to CBP's ACE so customs data transmits electronically instead of being re-keyed into portals.

• Know your scope: a forwarder automates the filings it owns, mainly ISF and AMS, plus the data prep; the import entry (ABI) is filed by a licensed customs broker, and exports go via AES/EEI.

• Core requirements: register identity (Form 5106), choose a transmission method (EDI or ABI software), extract data upstream with OCR, and automate HTS classification and validation.

• File clean the first time: pre-transmission validation catches missing data and bad values before they hit CBP.

• Imports vs exports: imports flow through ABI/entry; exports through AES/EEI.

• With CargoEZ: ISF and AMS file from the shipment record, and the same clean data hands off to your broker for the entry.

Why this matters

US customs runs on volume and deadlines: CBP processed roughly 36.7 million entries and 36.6 million cargo containers in FY2023. For a forwarder, every late or inaccurate filing (ISF at up to $5,000, a manifest violation at $5,000) is a penalty and a hold, and all of it starts from the same shipment data typed more than once.

Volume via CBP FY2023 Trade Fact Sheet. Confirm current figures with CBP.

"US customs filing" is not one filing. It is a stack: the Importer Security Filing (ISF), the Automated Manifest System (AMS), the import entry through the Automated Broker Interface (ABI), and the export declaration through the Automated Export System (AES). Automating it means your systems talk to CBP's ACE directly, with data pulled from the shipment instead of re-typed. This guide covers the requirements, the forwarder-versus-broker scope, imports versus exports, the tools, the benefits, and the manual cost.

US customs automation platforms at a glance

These are the platforms forwarders use to automate the customs filings they own and to connect to their broker. Confirm features and pricing with each vendor.

Directional comparison for US freight forwarders. Verify current capabilities and pricing with each vendor.

What a forwarder files, and what the broker files

Before you automate anything, be clear on which filings are yours. This is the step most "customs software" pages gloss over, and it decides what you can realistically automate in-house.

So for a forwarder, "automating US customs filing" mostly means automating ISF and AMS from your own system and feeding the broker clean data for the entry, not becoming a customs broker.

Core requirements to automate US customs filing

1. Establish importer identity: File CBP Form 5106 in ACE to register the tax ID (EIN or SSN). Physical street addresses are mandatory; P.O. boxes and virtual mail drops are rejected.

2. Choose a transmission method: Connect to CBP by EDI (Public Internet VPN, MPLS VPN, a service center, or a VAN, after testing and an Interconnection Security Agreement), or use ABI software and eManifest platforms that integrate with ACE.

3. Automate data flow upstream: Use AI/OCR to extract data from commercial invoices, packing lists, and bills of lading into your filing software before it reaches ACE.

4. Automate classification and validation: Apply automated HTS code assignment and pre-transmission validation to catch missing or rejected values before they hit CBP servers.

The flow, end to end:

Shipment docs → Extract + classify (HTS) → Validate → File ISF / AMS to ACE → Hand entry data to broker → Cleared

How CargoEZ does it: CargoEZ files ISF and AMS from the shipment record, classifies and validates the data once, and keeps it on the same file the booking and invoicing run on. For the import entry, the clean, classified data hands off to your customs broker, so nothing is re-keyed on the way to ACE.

Imports vs exports: ABI vs AES

The automation path forks by direction. Imports run through ABI and the entry process: the forwarder files ISF and (House) AMS, and a broker files the entry summary. Exports run through AES, where the electronic export information (EEI) is transmitted for shipments that require it. In both cases the win is the same: clean data extracted and classified once, then transmitted, rather than re-keyed per filing.

Self-file or work through a broker?

For the entry itself, most forwarders do not self-file; the import entry is a licensed customs broker's job, and the practical automation is to hand the broker clean, classified data through EDI or API. For the filings a forwarder owns (ISF, House AMS, and export EEI where applicable), automating transmission from your own system is both allowed and the bigger time saver. Decide filing by filing: what you own, you automate; what the broker owns, you feed.

Traditional vs automated customs filing

The benefits of automating customs filing

• Fewer penalties and holds. Validation and deadline tracking catch the errors that trigger ISF and manifest penalties.

• File once, reuse everywhere. The same shipment data feeds ISF, AMS, and the broker's entry, so it is not re-keyed three times.

• Faster clearance. Clean, classified, pre-validated filings clear on the first try more often.

• Audit trail. Every filing and CBP response logs against the shipment.

The cost of filing manually

• Penalties. Late or inaccurate ISF (up to $5,000) and manifest violations ($5,000) are billed back to you.

• Holds and delay. A rejected filing stops the cargo and adds demurrage.

• Triple data entry. The same shipment data gets typed into ISF, AMS, and the entry separately, multiplying errors.

• Classification drift. Manual HTS lookups are inconsistent and invite reclassification.

How CargoEZ automates US customs filing

CargoEZ automates the filings a forwarder owns from the same shipment record the rest of the operation runs on. ISF and AMS generate from the file, HTS and data are classified and validated once, deadlines track from the booking cut-off, and CBP responses log back onto the shipment. For the import entry, the clean data hands off to your broker, so the same shipment data is entered once and reused across the customs stack.

See the guides to automating ISF filing and automating AMS filing, the ISF and AMS modules, how it fits your wider freight forwarding workflow automation, or book a demo.