Run through this checklist first. It’s the fast version of everything below: what “automated AMS” actually looks like line by line.
Automated Manifest System filing is one of the biggest US-specific compliance clusters in freight forwarding, and most of the “automation” on the market only covers half of it, ocean, leaving air AMS as a manual gap.
AMS and ISF are not the same filing
They get confused constantly because they reference the same shipment and run on similar deadlines. ISF is the importer’s security filing, 10 data elements about the shipper, consignee, and cargo. AMS is the carrier’s or NVOCC’s manifest filing, advancing cargo manifest data to CBP ahead of arrival. A forwarder handling both sides of a shipment may be responsible for parts of each, and automating one without the other leaves a real compliance gap.
The deadline, and why it’s not optional
For ocean, AMS manifest data has to reach CBP 24 hours before the container loads at the foreign port, the same load-based deadline that governs ISF. For air, the requirement runs against wheels-up rather than a fixed 24-hour ocean rule. Either way, the filing has to happen before departure, not before US arrival, which is the detail most new forwarders get wrong on their first few shipments.
Why air AMS gets left out
Most AMS filing tools in the market were built for ocean NVOCCs first, and air AMS was added later or not at all. If your forwarding business handles meaningful air freight volume, check specifically whether a platform files air AMS, not just ocean, before assuming a tool covers your manifest filing end to end.
CargoEZ files AMS for both air and ocean from the same shipment record used for booking and documents, so manifest data doesn't need a separate entry pass per mode.
Pair this with the ISF filing checklist if you’re responsible for both filings on the same shipment, and see how to automate freight forwarding workflows for how AMS fits into the rest of the file.