How to Automate AMS Filing (Ocean & Air)

How to Automate AMS Filing (Ocean & Air)

You automate AMS (Automated Manifest System) filing by connecting your ERP, freight, or warehouse software to CBP through EDI or API, or a certified AMS platform, so cargo manifests transmit automatically from the shipment instead of being re-typed into a portal.

TL;DR

• What it is: transmitting the CBP cargo manifest automatically from your shipment data over ACE/ABI, instead of keying it into a portal.

• The core steps: integrate via ABI/EDI → map mandatory data from the MBL/HBL → add error handling & status tracking → link to ISF for ocean.

• Ocean vs air: Ocean AMS is due 24 hours before loading; Air AMS at least 4 hours before arrival (or by takeoff for short flights), alongside ACAS.

• As a forwarder: you file the House AMS from your house bill; automation pulls it straight from the shipment file.

• Stay clean: block vague commodity descriptions, validate parties, reconcile AMS with ISF, and poll CBP status so people only touch exceptions.

• With CargoEZ: Air and Ocean AMS, ISF, and ACAS data all come from one shipment record, so you file once.

Why this matters

AMS is a hard deadline with a hard consequence. Miss the ocean 24-hour rule or the air pre-arrival window and CBP can issue a "Do Not Load," and late or inaccurate manifests draw penalties. For a forwarder filing House AMS across many shipments and two modes, that is a lot of countdowns to run by hand.

AMS requirements, U.S. Customs and Border Protection (ACE). Figures are directional; confirm current rules with CBP.

The Automated Manifest System is CBP's electronic cargo manifest: the record of who and what is on a vessel or flight bound for the United States. A forwarder files the House AMS from its house bill, against a strict clock, for both ocean and air. Automating it means your shipment system transmits to CBP for you and watches the responses, so your team only steps in on exceptions. This guide covers the core steps, the ocean-versus-air differences, the data and validation rules, how to track CBP status codes, a full checklist, the platforms that do it, and how AMS fits your wider freight forwarding workflow automation.

• 24 hrs Ocean AMS, before loading at the foreign port

• 4 hrs Air AMS, before US arrival (or by takeoff for short flights)

• Air + Ocean AMS applies to both modes (plus ACAS for air)

• House AMS the forwarder files, vs the carrier's Master AMS

Platforms that automate AMS for forwarders

If you file across ocean and air for many clients, these are the platforms that connect your workflow to CBP. We cover how automation works below; confirm features and pricing with each vendor, and see our best AMS filing software roundup for the full buyer's guide.

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

The core steps to automate AMS filing

Whether you build it in or buy it, automated AMS runs the same core steps from a closed booking to a CBP response.

The flow, end to end:

Booking closed → Map MBL / HBL → Validate data → Transmit to ACE → Poll CBP status → Released / exception

How CargoEZ does it: CargoEZ files Air and Ocean AMS from the same shipment record that holds the bills, parties, container, and commodity. Fields map automatically from the MBL/HBL, the deadline is tracked from the booking cut-off, and the same data reconciles with ISF and ACAS, so you file once across the whole customs stack.

Automating Ocean AMS vs Air AMS

Ocean and air run on different clocks and different matching logic, so your automation needs mode-specific rules.

For ocean, automation ties your booking or dock-receipt trigger to a strict countdown and blocks the load milestone until CBP returns a green status. For air, it extracts data from the flight booking and HAWB and transmits the moment the manifest locks, so the 4-hour threshold is met safely, with ACAS feeding preliminary screening before departure.

Key requirements to keep in mind

Two things decide whether an AMS filing clears: it is on time, and the data is complete and precise.

Timelines

• Ocean: submit at least 24 hours before loading at the foreign port (the 24-Hour Rule).

• Air: file before arrival, at least 4 hours out (or by takeoff for flights under 4 hours), alongside ACAS.

Mandatory data elements

• Full legal shipper and consignee (and notify party) names, physical addresses, and tax IDs.

• Standard Carrier Alpha Code (SCAC), and the vessel/voyage or flight number.

• Bill of lading numbers, container numbers, and seal numbers.

• Itemized cargo weights, piece counts, and precise descriptions, avoiding generic terms like "FAK" or "general cargo."

Specific data validation rules

Build these guardrails into the workflow so a bad manifest is stopped before it transmits:

• Commodity description filters. Use regex or dictionary blocks that reject vague descriptions ("FAK," "general cargo," "chemicals," "car parts") and force itemized, precise text.

• Mandatory stakeholder validation. Require full legal names, complete physical addresses, and tax/ID numbers for shipper, US consignee, and notify party before submission.

• Single-source record mapping. Configure the TMS/ERP so booking data, house bills (HAWB/HBL), and master bills (MAWB/MBL) auto-populate the manifest fields with no re-entry.

• ISF reconciliation (ocean). Cross-check Ocean AMS data against the matching ISF (10+2) elements to prevent mismatch holds.

• Bill-format checks. Validate that bill numbers follow CBP styling so you don't trigger "Bill Not Found" errors.

Tracking CBP status codes

Automation earns its keep after transmission, by watching CBP's responses so your team only acts on exceptions. Poll the status continuously and route by message:

Route routine "Released" messages to close automatically, send "Hold," "Exam," and "Do Not Load" straight to an escalation queue, and keep a timestamped amendment log of every correction and resubmission so timeline compliance is traceable.

The AMS automation checklist (ocean & air)

1. Establish CBP-approved connectivity: Set up a direct EDI or API link to ACE through a certified network service provider.

2. Map a single source of record: Make booking data, house bills, and master bills auto-populate the manifest fields, no manual re-entry.

3. Enforce stakeholder validation: Require full names, addresses, and tax IDs for shipper, consignee, and notify party.

4. Block non-compliant commodity text: Auto-reject vague descriptions and force itemized, precise data.

5. Set the Ocean 24-hour countdown: Trigger a timer 24 hours before loading and hard-stop the load until CBP returns Accepted/Released; reconcile with ISF.

6. Set the Air pre-arrival trigger: Transmit on flight lock or eAWB completion to meet the 4-hour window, and feed ACAS for screening.

7. Automate status polling: Continuously poll CBP responses and clear routine releases without a human.

8. Route exceptions and log amendments: Escalate Holds and Do-Not-Loads, and keep a timestamped audit trail of every correction.

What getting AMS wrong costs

A missing, late, or inaccurate manifest draws CBP liquidated damages of $5,000 per violation, capped at $100,000 per conveyance arrival. For Air AMS, an aircraft arriving without a filing in place faces $5,000 for a first violation and $10,000 after. Miss the ocean 24-hour rule and CBP can issue a "Do Not Load," holding the container at origin.

The scale is why this has to run automatically: CBP processed 36.6 million cargo containers in FY2023, and the air rules keep tightening, with expanded ACAS data requirements phasing in and enforcement extended to 2027.

Automating the filing pays back fast. Vendors report around 50 minutes saved per entry and about $18 in labor per shipment (GoFreight, vendor-reported), and Descartes' customs and compliance suite holds a 4.4/5 on G2, with reviewers praising its automation and centralized documents but flagging slow performance during updates. Treat vendor figures as directional.

AMS vs ISF: how they fit together

Forwarders mix these up, so it helps to see them side by side. They share most of the same shipment data, which is exactly why filing them from one record removes the re-keying and the mismatch holds.

See the full guide to automating ISF filing for the import side of the stack.

How CargoEZ automates AMS filing

CargoEZ files US AMS, Air and Ocean, from the same shipment record the rest of your operation runs on. Manifest fields map automatically from the master and house bills, the deadline is tracked from the booking cut-off, validation rules block vague or incomplete data, and CBP status messages flow back onto the shipment so your team only works the exceptions. Because AMS, ISF, and the shipment share one record, the data is entered once and reconciled, not rebuilt per filing.

See the AMS filing software overview, read how it pairs with ISF filing and your wider freight forwarding workflow automation, or book a demo to file an AMS straight from a shipment.