Attachments
The Attachments tab lists the supporting documents filed against a declaration: an invoice, a packing list, a certificate of origin. You can download each one, and the portal checks that the file you receive is exactly the one that was filed.
How ITS holds attachments
Each attached file is scanned for viruses when it is filed and then kept in ITS's document store. The signed declaration records each file's digest, a fingerprint computed from its exact contents. When you download a file, the portal fetches it and compares its fingerprint with the digest in the signed declaration before handing it to you.
The tab opens with the sentence Evidence filed against this declaration. ITS stores the digest and the reference; the bytes stay with the administration that filed them, so every download is checked against the digest before it is offered to you. Read it for the check it describes, which works as it says. The files themselves are kept in ITS's document store, as described above.
Before you start
- Your account must be able to read declarations, and the declaration must be in your scope. See What each role can do.
Open it
- Open the declaration. See Declaration details.
- Select the Attachments tab.

The screenshot shows what the tab looks like for a declaration with nothing attached. When files are attached, they are listed under Attached documents in its place.
| On the tab | What it shows |
|---|---|
| Attached documents | The list of files |
| 3 files · 3 carry a digest | How many files there are, and how many can be checked on download |
| One row per file | Its name, its document type if one was given, and a download button |
| This deployment did not return an id for this attachment, so it cannot be fetched individually. | ITS gave no id for this file, so the row has no working download |
| Nothing is attached to this declaration. | There are no files |
Download an attachment
- Select the download button at the right of the file's row.
The button shows a spinner while the file is fetched and checked. Then one of three things happens:
| You see | What it means |
|---|---|
| Digest verified, and the file is saved | The file is exactly the one that was filed |
| These bytes are not the ones signed for | The file that arrived is not the one recorded in the declaration. Do not rely on it; tell the administration that filed it |
| Nothing to check against | The declaration carries no digest for this file, so it cannot be checked. Treat it with care |
If the file cannot be fetched at all, a Download failed message appears; try again in a moment. If the list itself cannot be loaded, the tab says Attachments could not be listed. Reload the tab.
Attaching is done by your customs system
Attaching a document is an act on the declaration: it appends a new signed version and announces it to every country the declaration concerns. Like lodging and stamping, it is done by your administration's customs system. See Attachments and documents.
The Attach documents box appears under the list only for an account that is allowed to attach, which in the shipped roles means the Customs officer role. The Secretariat never is: it performs no customs act. Organisation administrators do not see the box either.
Your account holds the permission to attach. Anything you attach here is recorded, appends a new version and is announced along the corridor, exactly as if your customs system had sent it. Do not attach test files.