Your SAA from your SAM, signed and sent to ICEGATE

In this film

• Open the SAM customs accepted. It is checked against customs' own record: three bills, no entry inward yet.
• Add the late bill from the forwarder's CSN and its ACK file. The bill, its date, the packages and the containers come from their CSN, and the line names the CSN, so the two agree.
• Type what their CSN does not hold from your bill of lading: shipper, consignee, notify party, goods.
• Fill the customs codes on the line itself.
• Build amendment writes the SAA: only the new line goes, and the bills customs already accepted are not sent again.
• Before entry inward there is no officer to ask.
• Sign & upload: the DSC Signer finds your token, you check the summary once, and it goes to ICEGATE.
• Customs' answer comes to your ICEGATE e-mail as an ACK file.

Chapters

1. 0:00Your SAA from your SAM
2. 0:15Open the SAM customs accepted
3. 0:32Add the late bill from the forwarder's CSN
4. 0:50What the CSN does not hold, from the bill of lading
5. 1:07The customs codes, on the line
6. 1:21Build amendment: only the new line goes
7. 1:40Sign with your DSC
8. 1:58Check it once, send it to ICEGATE
9. 2:15Uploaded, and when we prepare it for you

Read it instead

The SCMTR reference pages this film walks through — free to read, no sign-in.

• Amending a shipping line filing (SAA or SDA)What a minimal SAA or SDA carries — only the lines that changed, never the whole manifest again — what amdType means, and when to use each.
• Signing your filing with your DSCCustoms accepts nothing unsigned. How Sign & upload signs a filing with your DSC token, and the ICEGATE portal route if you cannot install it.