CUSREP — EDIFACT Customs Conveyance Report Message (D.99B)
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.99B.
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.99B. The segments listed, their status (M / C), position and repetition factor are extracted from the official file cusrep_c.htm hosted on service.unece.org.
Segment structure
The CUSREP D.99B message has 53 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 | POC | Purpose of conveyance call | C | ×99 |
0060 | FTX | Free text | C | ×9 |
0070 | MEA | Measurements | C | ×9 |
0090 | SG1 | Group (×99) | C | ×99 |
0100 | RFF | Reference | M | 1 |
0110 | DTM | Date/time/period | C | 1 |
0120 | SG2 | Group (×99) | C | ×99 |
0130 | LOC | Place/location identification | M | 1 |
0140 | DTM | Date/time/period | C | ×9 |
0150 | SG3 | Group (×9) | C | ×9 |
0160 | DOC | Document/message details | M | 1 |
0170 | RFF | Reference | C | 1 |
0180 | DTM | Date/time/period | C | 1 |
0190 | LOC | Place/location identification | C | 1 |
0200 | SG4 | Group (×9) | C | ×9 |
0210 | TAX | Duty/tax/fee details | M | 1 |
0220 | MOA | Monetary amount | C | 1 |
0230 | FII | Financial institution information | C | 1 |
0240 | LOC | Place/location identification | C | 1 |
0250 | RFF | Reference | C | 1 |
0260 | DTM | Date/time/period | C | ×9 |
0280 | SG5 | Group (×9) | C | ×9 |
0290 | NAD | Name and address | M | 1 |
0300 | SG6 | Group (×9) | C | ×9 |
0310 | CTA | Contact information | M | 1 |
0320 | COM | Communication contact | C | ×5 |
0330 | SG7 | Group (×9) | C | ×9 |
0340 | RFF | Reference | M | 1 |
0350 | DTM | Date/time/period | C | 1 |
0360 | SG8 | Group (×99) | C | ×99 |
0370 | TDT | Details of transport | M | 1 |
0380 | TPL | Transport placement | C | 1 |
0390 | DTM | Date/time/period | C | 1 |
0400 | SG9 | Group (×99) | C | ×99 |
0410 | LOC | Place/location identification | M | 1 |
0420 | DTM | Date/time/period | C | ×9 |
0430 | QTY | Quantity | C | ×9 |
0440 | NAD | Name and address | C | ×99 |
0450 | MEA | Measurements | C | ×9 |
0460 | POC | Purpose of conveyance call | C | ×9 |
0470 | STS | Status | C | ×9 |
0480 | FTX | Free text | C | ×9 |
0490 | SG10 | Group (×999) | C | ×999 |
0500 | EQD | Equipment details | M | 1 |
0510 | EQN | Number of units | C | 1 |
0520 | SG11 | Group (×1) | C | 1 |
0530 | AUT | Authentication result | M | 1 |
0540 | DTM | Date/time/period | C | 1 |
0550 | UNT | Message trailer | M | 1 |
Detail
No segment in this section.
Summary
No segment in this section.
Changes vs D.96A
Top-level differences between D.96A and D.99B for the CUSREP message (segments directly inside header / detail / summary, ignoring nested groups). The comparison is indicative: a given tag may have evolved inside nested groups without showing up in this synthesis.
Segments added vs D.96A
POCin the header section (status C, repeat ×99) — not present at the top of the corresponding D.96A section.FIIin the header section (status C, repeat ×1) — not present at the top of the corresponding D.96A section.STSin the header section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.
Segments removed vs D.96A
GISin the header section — present in D.96A but missing in D.99B at the same level.
Structural example
Minimal example of an CUSREP D.99B message with mandatory segments only. The goal is to show the exact version declared in UNH (CUSREP:D:99B:UN) — not to replicate a full business case (see the CUSREP D.96A page for an annotated example).
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL099001'
UNH+1+CUSREP:D:99B: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+CTRL099001'Common errors
- Misaligned UNH tokens — The
UNH+...+CUSREP:D:99B: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.99B, 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.96A, CUSREP D.01B, CUSREP D.10A, CUSREP D.16B, CUSREP D.21B, CUSREP D.24A, CUSREP D.97A, 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.