Check an ICEGATE CSN file before customs refuses it

In this film

• A curly apostrophe, found by line and column — ICEGATE fails a whole file saved in the wrong encoding, by e-mail, with no acknowledgement to read.
• Red is what customs refuses, and Sign & upload will not send a file with one: here a cargo type and cargo movement combination the MIG's trade-scenarios table does not list (IM with TC).
• Amber is worth a second look: it never blocks a filing, and it says what the evidence for it is.
• Click a finding to jump straight to the field, and open the ? help on any field.
• Pair customs' reply: drop the _ACK file and every error lands on the filing, with what it means and how to fix it — and the blocks customs marked good.
• Fix in the editor opens it as a draft on the first problem, with every other one listed beside it.

Chapters

1. 0:00Check any ICEGATE file
2. 0:14Drop the CSN: what the check finds
3. 0:41Red is refused, amber is a second look
4. 0:57Jump to the field
5. 1:14The ? help on every field
6. 1:28Pair customs' reply, and how to fix it
7. 2:17Fix in the editor

Read it instead

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

• 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.
• Reading an acknowledgement from customsYou filed and a JSON file came back. Which of the three files you have, what the verdict means, and why some refusals carry no code at all.
• Cargo type, movement and consolidationCargo type, cargo movement, the consolidation indicator and the prior-declaration flag are checked as one combination. Which ones are legal.