An SAA prepared for you, opened only with your DSC

Yes. For a shipping line or its agent, SCMTR.io can prepare an SAA (or an SDA, SEI or SDN) and hand it over sealed. You never receive the file. You open it with your authorised person's DSC, see what it does, and sign and send it to ICEGATE from SCMTR.io. To ask for one, write to support@scmtr.io with the bill and what has to change.

When is a prepared SAA worth asking for?

When working the change out yourself is the hard part:

A straight bill that has to become a consolidation, or a line that has to quote a forwarder's CSN, MCIN or PCIN instead of what it quotes now. ICES Advisory 38/2026 (Q1, Q2) says such a change is never an in-place update: the line is dropped and added back, in the SAA.A line removed whole. A removal sent with the line and nothing under it was refused on the line's route legs (242) and the declaration (300); the removal customs accepted on 3 October 2026 carried the line's containers and legs as well, each marked as removed.Numbering against what customs holds now. An SAA addresses lines and containers by customs' own numbers, and a new line takes the next number after the highest customs holds. A file built from an older copy of the manifest is refused (749, 394).

For a simple change — a late bill added from the forwarder's CSN, a figure corrected — you can build the SAA yourself in Shipping line filing: open the SAM customs accepted, make the change, press Build amendment, then Sign & upload the amendment.

How does a prepared SAA reach me?

SCMTR.io prepares and checks it. It is checked as any SAA is here, and pinned to the version of your manifest customs holds that day, read from customs' public record.It is sealed, and you get a link. Nothing else is sent to you: no file, no attachment.You open the link signed in to SCMTR.io. The first account to open it adds it to its organisation; for anyone else the link answers "not available".Only your authorised person's DSC opens it. The SAA names an authorised person by PAN, and the DSC Signer on your computer must hold a DSC carrying that PAN. Once opened, only that same DSC can sign it — a colleague's DSC, even one registered to another ICEGATE ID of yours, is refused before anything is sent. This is SCMTR.io's rule for a prepared filing, not customs'.You see what it does. The page shows the event, port and rotation, the job number and file name, each line it changes with what happens to it (removed, added, changed), and the voyage totals it declares. It never shows or offers the file itself.You sign and send it. Press Sign and send: your DSC signs the filing on your computer, you confirm what is going, and SCMTR.io uploads it to ICEGATE through the same checks and the same guard against sending twice as every upload from here.

What if customs' record has changed since it was prepared?

Then it is not sent. Just before the upload, customs' live record is read again. If your manifest has moved on — another SAA accepted, a bill gone from the record — or customs' record did not answer, the send stops and SCMTR.io is told, so the SAA can be prepared again against the manifest as it now stands. A filing prepared for one version of a manifest can carry the wrong totals for the next.

Where does customs' answer go?

To your ICEGATE ID, by e-mail, as for any SAA: an ACK file ending _ACK. Customs decides whether to accept the amendment; preparing it here does not promise that. An SAA after entry inward still needs the jurisdictional officer's approval (ICES Advisory 37/2026).

Can I keep a copy of the file?

Not from SCMTR.io. The prepared file stays with SCMTR.io until it is sent. After it is sent, customs' acknowledgement comes to your ICEGATE ID, and customs' public record shows the result once it is accepted.