CUSREP — EDIFACT Customs Conveyance Report Message (D.96A)
The CUSREP message is the conveyance report (vessel, aircraft, truck, train) sent to customs before or upon arrival: it carries vehicle identification, crew, route and references to the associated CUSCAR cargo reports. This page summarises the segment structure as published by UN/CEFACT for directory D.96A.
Purpose
The CUSREP message is the conveyance report (vessel, aircraft, truck, train) sent to customs before or upon arrival: it carries vehicle identification, crew, route and references to the associated CUSCAR cargo reports.
This page focuses on the structure published by UN/CEFACT for directory D.96A. The segments listed, their status (M / C), position and repetition factor are extracted from the official file cusrep_s.htm hosted on service.unece.org.
Segment structure
The CUSREP D.96A message has 45 header entries, 0 detail entries and 0 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.
Header
| Pos. | Tag | Name | S | Rep. |
|---|---|---|---|---|
0010 | UNH | Message header | M | 1 |
0020 | BGM | Beginning of message | M | 1 |
0030 | DTM | Date/time/period | C | ×9 |
0040 | QTY | Quantity | C | ×9 |
0050 | FTX | Free text | C | ×9 |
0060 | MEA | Measurements | C | ×9 |
0070 | GIS | General indicator | C | ×9 |
0080 | SG1 | Group (×99) | C | ×99 |
0090 | RFF | Reference | M | 1 |
0100 | DTM | Date/time/period | C | 1 |
0110 | SG2 | Group (×99) | C | ×99 |
0120 | LOC | Place/location identification | M | 1 |
0130 | DTM | Date/time/period | C | ×9 |
0140 | SG3 | Group (×9) | C | ×9 |
0150 | DOC | Document/message details | M | 1 |
0160 | RFF | Reference | C | 1 |
0170 | DTM | Date/time/period | C | 1 |
0180 | LOC | Place/location identification | C | 1 |
0190 | SG4 | Group (×9) | C | ×9 |
0200 | TAX | Duty/tax/fee details | M | 1 |
0210 | MOA | Monetary amount | C | 1 |
0220 | GIS | General indicator | C | 1 |
0230 | SG5 | Group (×9) | C | ×9 |
0240 | NAD | Name and address | M | 1 |
0250 | SG6 | Group (×9) | C | ×9 |
0260 | CTA | Contact information | M | 1 |
0270 | COM | Communication contact | C | ×5 |
0280 | SG7 | Group (×9) | C | ×9 |
0290 | RFF | Reference | M | 1 |
0300 | DTM | Date/time/period | C | 1 |
0310 | SG8 | Group (×99) | C | ×99 |
0320 | TDT | Details of transport | M | 1 |
0330 | TPL | Transport placement | C | 1 |
0340 | DTM | Date/time/period | C | 1 |
0350 | SG9 | Group (×99) | C | ×99 |
0360 | LOC | Place/location identification | M | 1 |
0370 | DTM | Date/time/period | C | ×9 |
0380 | QTY | Quantity | C | ×9 |
0390 | SG10 | Group (×999) | C | ×999 |
0400 | EQD | Equipment details | M | 1 |
0410 | EQN | Number of units | C | 1 |
0420 | SG11 | Group (×1) | C | 1 |
0430 | AUT | Authentication result | M | 1 |
0440 | DTM | Date/time/period | C | 1 |
0450 | UNT | Message trailer | M | 1 |
Detail
No segment in this section.
Summary
No segment in this section.
Changes vs D.96A
This page documents directory D.96A itself: it serves as the reference for every other version of the message. The synthesis below describes the structural changes that later directories will introduce relative to it.
No top-level differences detected between D.96A and D.96A for this message. Differences are then limited to nested groups and code lists.
Structural example
Minimal example of an CUSREP D.96A message with mandatory segments only. The goal is to show the exact version declared in UNH (CUSREP:D:96A:UN) — not to replicate a full business case.
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL096001'
UNH+1+CUSREP:D:96A:UN'
BGM+929+CUSREP-2026-0099+9'
DTM+137:202605141430:203'
NAD+CA+5410000000123::9'
NAD+CZ+5410000000456::9'
TDT+20+MSC1234W+1++MSC::ZZZ+++9301234:103:::MSC OSCAR'
LOC+5+FRLEH::6'
DTM+178:202605141200:203'
LOC+6+NLRTM::6'
DTM+178:20260516:102'
UNT+10+1'
UNZ+1+CTRL096001'Common errors
- Misaligned UNH tokens — The
UNH+...+CUSREP:D:96A:UNtoken must reflect exactly the directory in use — a mismatch between the UNH release and the release agreed with the partner is rejected by every strict validator. - Wrong UNT segment count — The value after
UNT+must include UNH and UNT themselves. By far the most common sender-side error, regardless of the directory in use. - Stale code lists — Between D.96A and D.96A, several code lists received new qualifiers (DTM status, RFF qualifier, NAD codes…). Reusing an older directory’s code tables triggers warnings or even rejections depending on the partner’s strict-conformance mode.
Related messages
Other versions of this message available on ediverse.io: CUSREP D.01B, CUSREP D.10A, CUSREP D.16B, CUSREP D.21B, CUSREP D.24A, CUSREP D.97A, CUSREP D.99B, CUSREP D.00B, CUSREP D.02B, CUSREP D.05A, CUSREP D.08A, CUSREP D.13B, CUSREP D.18B, CUSREP D.20B.
X12 functional equivalent: X12 309.