ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.
IFTDGN D.96A

IFTDGN — EDIFACT Dangerous Goods Notification (D.96A)

The IFTDGN message is the dangerous-goods notification sent to the carrier or port/airport authorities: UN code, ADR/IMDG/IATA class, packaging, net/gross masses, flash point, emergency instructions. It hardens the supply chain against IMO, ADR and IATA-DGR requirements. This page summarises the segment structure as published by UN/CEFACT for directory D.96A.

Purpose

The IFTDGN message is the dangerous-goods notification sent to the carrier or port/airport authorities: UN code, ADR/IMDG/IATA class, packaging, net/gross masses, flash point, emergency instructions. It hardens the supply chain against IMO, ADR and IATA-DGR requirements.

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 iftdgn_s.htm hosted on service.unece.org.

Segment structure

The IFTDGN D.96A 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.

Pos.TagNameSRep.
0010UNHMessage headerM1
0020BGMBeginning of messageM1
0030DTMDate/time/periodC×9
0040FTXFree textC×9
0050HANHandling instructionsC1
0060  SG1Group (×9)C×9
0070  RFFReferenceM1
0080  DTMDate/time/periodC×9
0090    SG2Group (×1)C1
0100    TDTDetails of transportM1
0110    RFFReferenceC×9
0120    LOCPlace/location identificationC×10
0130    DTMDate/time/periodC×2
0140      SG3Group (×9)C×9
0150      NADName and addressM1
0160        SG4Group (×9)C×9
0170        CTAContact informationM1
0180        COMCommunication contactC×9
0190          SG5Group (×999)C×999
0200          EQDEquipment detailsM1
0210          MEAMeasurementsC×9
0220            SG6Group (×999)M×999
0230            CNIConsignment informationM1
0240            HANHandling instructionsC1
0250            DTMDate/time/periodC×4
0260            LOCPlace/location identificationC×4
0270              SG7Group (×1)C1
0280              TDTDetails of transportM1
0290              RFFReferenceC×9
0300                SG8Group (×2)C×2
0310                NADName and addressM1
0320                  SG9Group (×1)C1
0330                  CTAContact informationM1
0340                  COMCommunication contactC1
0350                  RFFReferenceC1
0360                    SG10Group (×99)M×99
0370                    GIDGoods item detailsM1
0380                    FTXFree textC×2
0390                    PCIPackage identificationC1
0400                      SG11Group (×99)C×99
0410                      SGPSplit goods placementM1
0420                      MEAMeasurementsC×9
0430                        SG12Group (×1)M1
0440                        DGSDangerous goodsM1
0450                        FTXFree textM×2
0460                        MEAMeasurementsM×2
0470                        LOCPlace/location identificationC×99
0480                        RFFReferenceC×9
0490                          SG13Group (×99)C×99
0500                          SGPSplit goods placementM1
0510                          LOCPlace/location identificationC1
0520                          MEAMeasurementsC×2
0530UNTMessage trailerM1

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 IFTDGN D.96A message with mandatory segments only. The goal is to show the exact version declared in UNH (IFTDGN:D:96A:UN) — not to replicate a full business case.

edifact iftdgn-d96a-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL096001'
UNH+1+IFTDGN:D:96A:UN'
BGM+266+IFTDGN-2026-DG-0042+9'
DTM+137:20260514:102'
FTX+AAI+++Dangerous goods notification - IMDG class 3 - flammable liquids'
HAN+L'
RFF+BM:BL-2026-7811'
UNT+7+1'
UNZ+1+CTRL096001'

Common errors

  • Misaligned UNH tokens — The UNH+...+IFTDGN:D:96A:UN token 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.

Other versions of this message available on ediverse.io: IFTDGN D.10A, IFTDGN D.16B, IFTDGN D.21B, IFTDGN D.24A.

← All EDIFACT versions