ISF 10+2 and AMS filing for freight forwarders

The Importer Security Filing has two separate deadlines, ten elements owed by three different parties, and liquidated damages of $5,000 for each violation. Most of the work is not filing — it is collecting. Here is the rule, and here is how the filing goes out of Linbis under your own CBP credential.

Reviewed: August 2026  ·  Scope: Ocean imports into the United States  ·  Not legal advice — confirm current requirements with your customs broker or CBP.

Two deadlines, not one

Nearly every guide treats ISF as a single cut-off. It is not. 19 CFR 149.2(b) splits the ten importer elements across two different clocks, and the second one catches people out because it is measured against a completely different event.

Eight elements are due no later than 24 hours before the cargo is laden aboard the vessel at the foreign port. The remaining two — container stuffing location and consolidator, the so-called flexible elements — are due “as early as possible, in no event later than 24 hours prior to arrival in a United States port.” That is weeks apart on a trans-Pacific sailing, and it means an ISF is rarely finished in one sitting.

Figure 1. The two ISF cut-offs and which elements fall under each. Original diagram, drawn from 19 CFR 149.2(b) linked in Sources below.

Who owes you each element

The operational problem is not knowing the rule. It is that ten data elements are held by three different parties, none of whom work for you, and you need all ten before a clock you do not control runs out.

Figure 2. The ten importer elements and the two carrier elements, with the party who normally holds each. Element names and timing from 19 CFR 149.2(b) and 149.3; the “who holds it” column reflects ordinary commercial practice, not a regulatory assignment.

Read that table as a chase list rather than a form. Nothing on it is difficult. All of it is late.

ISF-10, ISF-5, and the filing you may not realize you owe

Most forwarders meet ISF as the ten-element importer filing on cargo entering the United States. That is ISF-10. There is a second filing, ISF-5, for cargo that never enters US commerce — freight remaining on board, and Transportation & Exportation or Immediate Exportation moves under bond. It carries five elements instead of ten, and the party who owes it is not the goods’ importer: on freight remaining on board the ISF Importer is the carrier or the NVOCC, which is precisely why an NVOCC ends up owing it, and on an in-bond T&E or IE move it is whoever files that documentation.

The two also run on different clocks. On freight remaining on board the obligation attaches at the first foreign lading, so the deadline is measured against the first leg, not the leg that eventually reaches the United States. Getting that wrong is not a paperwork error; it files after lading, which is the $5,000 exposure.

Figure 3. How the cut-off is computed for each kind of move. The break-bulk row in particular can shift a deadline by weeks in either direction, so it is set from how the cargo really moves rather than from a default.

Where AMS actually fits

ISF and AMS are two different transmissions, and the relationship between them is where filings fail. AMS is the manifest: the ocean carrier transmits the master bill, and an NVOCC transmits its own house bills under its own SCAC. The ISF is a separate security filing that CBP has to be able to tie to a bill on that manifest.

So there are two shapes, and only one of them can fail a match.

The ordinary import. An ISF-10 is filed on its own and CBP matches it against the carrier’s AMS bill. The answer comes back as a bill-match verdict — awaiting bill, bill matched, or no bill match — and it is shown on the filing as its own chip, separate from the filing status. An unmatched filing is not a rejection: it stays on file and re-matches by itself once the carrier’s bill reaches AMS. What it does mean is that the bill number, the bill type and the issuing SCAC all have to be right, because that is the join.

The in-bill filing. For ISF-5 cargo — freight remaining on board, or moving in bond — the ISF data rides inside the AMS bill on the 309 manifest instead of pointing at it. There is no separate match to fail, by construction. This is the “manifest” half of filing from Linbis: the same preview and the same typed confirmation, sending a manifest bill rather than a standalone ISF.

One honest scoping note, because it is the sort of thing a vendor page usually blurs: there is no unified in-bill type for an ISF-10, and there is no standalone AMS manifest workflow for ordinary import cargo. The in-bill path exists for the ISF-5 bill types the 309 defines, and nowhere else.

Figure 4. The two filing shapes and where the AMS bill-match verdict applies. Original diagram; bill-match states and the in-bill ISF-5 path are as implemented in the product.

What it costs to get wrong

The ISF bond condition sets liquidated damages at $5,000 for each violation — late, inaccurate or missing alike — and the money is rarely the worst of it — a filing that is not on record invites a hold, and a hold invites an exam, and an exam invites demurrage on a container you are already paying for. Confirm the current figure and how it applies to your shipments with your customs broker or CBP.

Set that against the cost of the work itself: the time spent re-keying data that already exists into a second system, plus chasing that happens from memory. Both of those are collection problems, and collection is the part a system can genuinely carry.

What you need before you can file anything

None of this can be automated away, because every line of it is a real-world step at a government agency, in your company’s name. It is also the list nobody tells you until a filing comes back rejected, so here it is up front.

Figure 5. The prerequisites, and the rejection each one produces when it is absent. Linbis generates and tracks the letter and walks the form, but items one through six are yours and stay yours.

How ISF and AMS filing work in Linbis

Everything above is dates and collection. It goes wrong because it lives in an inbox, a spreadsheet and somebody’s memory. Here is the actual sequence in the product, from a cold start to a filing CBP has accepted.

1. Connect your SCAC and your credential — onceSettings → Integrations → Customs walks four steps, and you act on the first two. You describe your company; every field says why CBP asks for it. Then you review a generated Letter of Intent to CBP and confirm it by typing SEND. The letter names Linbis as your transmission channel — it does not make Linbis your filer. Our customs team tracks the enablement with CBP, typically three to five business days, and the credential is issued and verified for you. You never handle a gateway key, and there is no filer code to invent: on this wire, the filer identity is your SCAC.
2. The filing starts filled in, not blankOpen an ocean import, expand Customs & Compliance, and choose Create ISF. The filing is linked to the shipment, and it is pre-populated from the record you already keep — parties, ports, containers, the HTSUS numbers on the commodities you already entered, the bill references. Every suggested value is badged with where it came from: the shipment, your connection, or the carrier’s profile. Suggestions, never inventions — you correct rather than transcribe, and nothing prefilled is enforced.
3. Completeness is a rail, not an opinionBeside the form, a rail lists every element that still blocks the filing, grouped by section, with a control that jumps to the first problem. It checks the things CBP will check: that the port of entry resolves to a CBP Schedule D code, that a house bill is carried as BM with its master as OB, that the bond block is complete, that the description is specific enough. When the rail reads “ready to preview and transmit”, the filing has passed every check we can run before CBP sees it.
4. The deadline is computed from how the cargo actually movesNot from a single template date. Freight remaining on board anchors to the first foreign lading; an in-bond T&E or IE move to lading; an ordinary ISF-10 to lading, transshipment-aware; a break-bulk shipment with a CBP-granted exemption and no containers to arrival. The file shows the time left, and alerts fire at 72, 48 and 24 hours before the cut-off, and again once it has passed.
5. Preview shows exactly what will be sent — and what will notPreview EDI opens a panel titled “what we are sending to CBP”. It is not a summary. Every element of the actual payload is listed with its value, where that value came from, and its CBP reference. A second block lists what is absent and why — deferred under flexible timing, optional and left empty, or not applicable to this filing type. CBP judges what arrives and what does not, so both halves are on the page. A manager can also read the raw X12, and that read is audited every time.
6. You type SUBMITThe confirmation asks for the whole word, and the word you typed, your name, the time, and a fingerprint of the exact payload you approved are all recorded on the submission. A filing cannot be transmitted before it has been previewed, and any edit after a preview invalidates it — you preview again and re-confirm. Two people cannot submit the same filing twice; the second attempt is refused, not duplicated.
7. CBP answers, in about five minutesA banner tracks the transmission live: queued and still cancellable, on the wire, received by CBP, answered. The outcome lands on the filing status — accepted, or rejected — and the AMS bill-match verdict lands on its own chip beside it. Both sit on the shipment record, next to the bill of lading, the charges and the documents, rather than in a portal nobody else can open.
8. A rejection is re-filed; an accepted filing is amendedCBP’s reason arrives in plain language rather than as a code you have to look up. If it was refused, you correct the data, preview again and file it as a new filing. If it was accepted and the facts then change, you file a replacement or delete the filing outright against the transaction number CBP issued — each behind its own typed word, REPLACE or DELETE.

Figure 6. The filing pipeline as it runs in the product. Original diagram; step 5 is the only point at which anything leaves for CBP, and a person performs it.

What CBP says back, and what it means

Rejections are a small, repeating set, and every one of them is a data problem you can see before you file. These are the ones you are most likely to meet.

Figure 7. The recurring CBP responses and their fixes, as they are surfaced in plain language on the filing.