Set up your organisation once: ICEGATE ID, port, PAN

In this film

• A new organisation's getting-started list, and Settings saying exactly what is still missing before you can file.
• The filing profile: ICEGATE sender ID, the receiver port (search by name), the submitter type — ANC for forwarders, consol agents, NVOCCs and customs brokers; ASA for a shipping agent; ASC for a sea carrier.
• The submitter code is your bare PAN: typed with "PAN:" in front, it is caught before it is saved, not by customs.
• The authorised representative's PAN can stay blank when the submitter code is your PAN.
• The shipping line card, for lines and agents who file SAM / SDM: the line's code (BLK for a bulk or tramp operator without one) and the authorised sea carrier.
• No ICEGATE API key to apply for: filings go through ICEGATE's portal channel, signed with your own DSC.
• Inviting a colleague, the address book that fills itself, checking a file by e-mail, and where help lives.

Chapters

1. 0:00Set up your organisation, once
2. 0:13Settings: what is missing before you can file
3. 0:24The filing profile: sender ID, port, what you file as
4. 0:43Your submitter code — the bare PAN
5. 0:56The representative's PAN can stay blank
6. 1:09The shipping line card
7. 1:25Nothing left to set up — and no API key
8. 1:37Invite a colleague
9. 1:52The address book, and checking by e-mail
10. 2:05More settings, and where help lives

Read it instead

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

• Using SCMTRSigning in through to a filed declaration: organizations and roles, every route into a filing, and what each status on the list means.
• Registering for SCMTR on ICEGATEAn ICEGATE ID is not enough: filing needs a separate SCMTR registration that Customs approves. Which entity type to pick, and what to expect.
• 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.