Sign & upload your SAM once: the confirmation that names it, and the check against a resend

In this film

• Check the manifest first — against customs' record and the CSNs the forwarders filed
• Sign & upload: the scmtr DSC Signer signs with your token and uploads, with no signed file to carry around
• The fingerprint: a second send of the same file is stopped with the first one named, and going past that needs your own reason
• A file signed on another computer can be brought back instead
• The confirmation: filing, job and date, port, vessel and VCN, voyage, lines and containers — and a test (T) file says so. Nothing goes until you tick it; the server refuses an upload the screen never confirmed

Chapters

1. 0:00Sign & upload your SAM, once
2. 0:06Check it first
3. 0:14Sign & upload, and the fingerprint
4. 0:40The confirmation names what goes
5. 0:56Nothing goes until you tick it
6. 1:07Checked, confirmed, sent once

Read it instead

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

• Filing a SAM or SDM when you have no software for itBuild a SAM or SDM from nothing for a bulk, tanker, break-bulk or tramp call that no liner system files for — what you need, and what to expect.
• Working with a shipping line filing (SAM / SDM)Open a shipping line’s SACHM23 manifest — hundreds of bills, over a megabyte — as a searchable table, and correct a line without rebuilding it.
• Checking a manifest against ICEGATEAsk customs which of a manifest’s bills already carry an accepted CSN, and whether the cross-validated container fields agree with yours.