Every field a transhipper or custodian files

Generated from ICEGATE's published Transhipper and CIM Custodian guides — do not edit by hand. Regenerate with pnpm kb:inland-fields.

Neither of these is yours to file. A forwarder, NVOCC or consolidator files a CSN and nothing else — these are the messages the inland leg produces, and they are here because their consequences reach you: a transhipper quotes a refusal that turns out to be about the cargo identification number your CSN earned, or a CFS sends you one of these files and asks what it says. Who else files against your cargo is the shorter answer to "why does this matter to me"; this page is the detail behind it.

Both guides name their blocks the same way — Declaration, Location, Cargo Container — so the two tables below are worth reading against each other where a movement involves both.

You do not have to read a file against this page by hand. Drop a TRCHE01 or CUCHE01 file on CSN filing → SCMTR JSON upload and it opens block by block with these same labels and descriptions attached to the values, its reporting event spelled out, and anything neither guide describes listed rather than dropped — see Reading a transhipper or custodian file. This page is the reference behind that screen; both come out of the same extraction, so they cannot disagree.

The transhipper — TRCHE01

Filed by the authorised transhipper (registration category ATP) who moves cargo between customs areas. Three reporting events: ASR allowed-for-shipment request, filed before departure from the port of call; DP inland departure and AR inland arrival, filed for every vehicle carrying the cargo. One transhipper is responsible for the whole movement and executes the bond, whatever the modes of transport.

Declaration

The envelope: what the message does, which customs station it is filed at, the job number and date, and which reporting event it is.

CIM

The Customs Inland Manifest number customs assigned, referenced by later messages in the same movement.

Location

Who is reporting and from where — the party type and code, the bond, the reporting location and the next destination.

Transport Means

The vehicle carrying the cargo on this leg — truck or train — and how many containers it holds.

Events

The expected and actual times of departure and arrival, which is what these messages exist to report.

Cargo Container

The containers on this movement: their identifiers, seals, sizes and load status.

Cargo Details

The cargo itself, tied back to the declaration it came from by its cargo identification number.

Cargo Itinerary

The route this cargo takes between customs stations.

Supporting Document

Documents referenced against the movement — type, number and date.

DigiSign

The digital signature block: the signature, the certificate and the signer version.

The custodian — CUCHE01

Filed by the custodian of a customs area or the terminal operator, reporting what physically happened to the cargo: SF stuffing, SFCN stuffing cancellation, ST stripping, DT departure time and AT arrival time. Customs answers the custodian with CC.

Declaration

The envelope: what the message does, which customs station it is filed at, the job number and date, and which reporting event it is.

CIM

The Customs Inland Manifest number customs assigned, referenced by later messages in the same movement.

Location

Who is reporting and from where — the party type and code, the bond, the reporting location and the next destination.

Transport Means

The vehicle carrying the cargo on this leg — truck or train — and how many containers it holds.

Events

The expected and actual times of departure and arrival, which is what these messages exist to report.

Cargo Container

The containers on this movement: their identifiers, seals, sizes and load status.

Cargo Details

The cargo itself, tied back to the declaration it came from by its cargo identification number.

Supporting Document

Documents referenced against the movement — type, number and date.

DigiSign

The digital signature block: the signature, the certificate and the signer version.

Where this comes from, and how far to trust it

ICEGATE's Transhipper Message Implementation Guide v1.5 (March 2026) and its CIM Custodian Message Implementation Guide v1.5 (January 2026), in each case the attribute table. Descriptions are quoted, including the guides' own spelling and their occasional missing letter. The sentence introducing each block is ours: neither guide describes what a block is for, only what its fields are.

One caveat particular to the transhipper table. That guide is published as a PDF whose table is hard-wrapped inside narrow columns, splitting words across lines — and splitting the header row and the data-type column too, so VARCHAR2 (11) prints as VARCHAR above 2 (11). It is reconstructed by column position here. Every field, key, type and label is recovered; three of the remarks still read with a word broken in two, and two of those also carry a fragment of the pattern column that overlapped them. Where one does, the published guide is the authority, not this page.

One key is quoted exactly as the guide prints it and looks wrong: the transhipper guide writes MCIN / PCIN as (MCIN/PCIN), where the custodian guide writes mcinPcin. A JSON key with a slash in it is implausible, and the custodian form is almost certainly the real one — but inventing a key ICEGATE has not published would be worse than showing the one it did.

Neither guide is a record of what customs accepts in practice, and this platform has never filed either message — nothing here is corroborated by a real filing the way the CSN pages are.

Related

Reading a transhipper or custodian file — what to do when one lands on youWho else files against your cargo — why these messages reach you at allWhich error list does my code come from? — the alphanumeric codes these messages are answered withTranshippers, CFSs and bond numbers — the fields on your filing that name themWhich SCMTR message do I file?Where the cargo goes after the gateway port