ICEGATE refused your file by e-mail? Forward it to find out why

In this film

• A refusal that arrives only as an e-mail, with no _ACK file attached.
• Forwarding it, as it is, to check@scmtr.io from the address you sign in with.
• The reply: the line it recognised, quoted back; the job number the refusal names; what it means; and whether any filing in SCMTR has that job number.
• What to do now: file again under a different job number, and have the corrected CSN checked before you do.
• The refusals it reads: the control number already processed, DSC validation failed, a file not UTF-8 encoded, User not Authorized, and "Something went wrong" when the e-mail is plainly from ICEGATE.

Chapters

1. 0:00A refusal with no file
2. 0:18Forward it to check@scmtr.io
3. 0:35What the reply says
4. 1:09What to do now
5. 1:22The refusals it reads

Read it instead

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

• Checking files by e-mailSend a CSN or an ICEGATE acknowledgement to the checking address and get the whole check back by reply — no sign-in and no upload.
• 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.