IFTIAG — EDIFACT Dangerous Goods List Message (D.96A)
The IFTIAG message conveys the list of dangerous goods carried on a given means of transport, sent by a shipper or forwarder to port/airport authorities or to the carrier for IMO/ADR/IATA-DGR compliance. Specific to historic directories (D.96A and earlier), it has progressively been superseded by IFTDGN in later directories. This page summarises the segment structure as published by UN/CEFACT for directory D.96A.
Purpose
The IFTIAG message conveys the list of dangerous goods carried on a given means of transport, sent by a shipper or forwarder to port/airport authorities or to the carrier for IMO/ADR/IATA-DGR compliance. Specific to historic directories (D.96A and earlier), it has progressively been superseded by IFTDGN in later directories.
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 iftiag_s.htm hosted on service.unece.org.
Segment structure
The IFTIAG D.96A message has 35 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 | CNT | Control total | M | 1 |
0040 | FTX | Free text | C | ×5 |
0050 | RFF | Reference | C | 1 |
0060 | SG1 | Group (×1) | M | 1 |
0070 | TDT | Details of transport | M | 1 |
0080 | DTM | Date/time/period | C | 1 |
0090 | CTA | Contact information | C | 1 |
0100 | SG2 | Group (×3) | M | ×3 |
0110 | LOC | Place/location identification | M | 1 |
0120 | NAD | Name and address | C | 1 |
0130 | RFF | Reference | C | 1 |
0140 | DTM | Date/time/period | C | 1 |
0150 | SG3 | Group (×9999) | M | ×9999 |
0160 | EQD | Equipment details | M | 1 |
0170 | SEL | Seal number | C | 1 |
0180 | SG4 | Group (×9999) | M | ×9999 |
0190 | CNI | Consignment information | M | 1 |
0200 | LOC | Place/location identification | C | ×2 |
0210 | RFF | Reference | C | ×2 |
0220 | NAD | Name and address | C | ×2 |
0230 | SG5 | Group (×9999) | M | ×9999 |
0240 | GID | Goods item details | M | 1 |
0250 | FTX | Free text | M | ×5 |
0260 | PCI | Package identification | C | 1 |
0270 | SG6 | Group (×1) | M | 1 |
0280 | DGS | Dangerous goods | M | 1 |
0290 | FTX | Free text | C | ×5 |
0300 | MEA | Measurements | C | ×2 |
0310 | SG7 | Group (×9999) | M | ×9999 |
0320 | SGP | Split goods placement | M | 1 |
0330 | LOC | Place/location identification | C | 1 |
0340 | MEA | Measurements | C | ×2 |
0350 | 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 IFTIAG D.96A message with mandatory segments only. The goal is to show the exact version declared in UNH (IFTIAG:D:96A:UN) — not to replicate a full business case.
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL096001'
UNH+1+IFTIAG:D:96A:UN'
BGM+268+IFTIAG-2026-DG-0007+9'
CNT+13:24'
FTX+AAI+++Dangerous goods manifest — IMDG voyage MSC1234W'
TDT+20+MSC1234W+1++MSC::ZZZ+++9301234:103:::MSC OSCAR'
LOC+9+FRLEH::6'
NAD+CA+5410000000123::9'
RFF+BM:BL-2026-MSC-7811'
LOC+11+NLRTM::6'
NAD+CN+5410000000456::9'
UNT+10+1'
UNZ+1+CTRL096001' Common errors
- Misaligned UNH tokens — The
UNH+...+IFTIAG: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
No other version of this message is currently indexed on ediverse.io.