Amend or delete an accepted CSN from the JSON you filed

In this film

• Drop the CSN on SCMTR JSON upload, at the top of CSN filing. Without its ACK file, Check with ICEGATE asks customs whether the VCN is a listed call and whether it holds the CSN.
• Have the ACK file? Drop it instead — it proves the CSN was accepted. A CSN filed outside SCMTR is brought in under your organisation.
• Amend or delete this CSN. A deletion withdraws the whole CSN at customs, every bill on it — to correct a filing, amend it instead, the lighter route.
• The deletion opens read-only, and is only ever sent for the CSN it was opened for. Changed your mind? Discard it on the filing's page; the accepted CSN is untouched.
• Drop the CSN again — it is one of your filings now, so the ACK file is not needed — and amend it. Amend the day something is wrong: once another party's CSN on the same master B/L is accepted, customs allows no more changes (320).
• Correct what was wrong, and read the Changes list: here the notify party followed the consignee's address.
• Sign & upload sends it. Customs' answer comes back to your ICEGATE e-mail: drop that ACK file on the filing.

Chapters

1. 0:00Amend or delete an accepted CSN
2. 0:11Drop the CSN on SCMTR JSON upload
3. 0:23Add its ACK file
4. 0:39A deletion withdraws the CSN — read the warning
5. 1:11Changed your mind: discard it
6. 1:40Amend it, straight from the CSN
7. 2:13Correct it and read the Changes list
8. 2:33Sign & upload

Read it instead

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

• Amendments and deletionsChanging or withdrawing a filing customs has already accepted — what can be amended in place, what has to be deleted and re-filed, and when.
• SCMTR JSON uploadDrop a CSN, an ICEGATE acknowledgement or a SAM / SDM on the filing page and have it checked against the same rules the app files by.