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.
TANSTA D.24A

TANSTA — EDIFACT Tank Status Report Message (D.24A)

The TANSTA message is the status report on bulk-liquid storage tanks (oil terminals, chemicals): level, temperature, pressure, quality, inbound/outbound movements. It feeds physical inventory and stock monitoring in the bulk-liquid sector. This page summarises the segment structure as published by UN/CEFACT for directory D.24A.

Purpose

The TANSTA message is the status report on bulk-liquid storage tanks (oil terminals, chemicals): level, temperature, pressure, quality, inbound/outbound movements. It feeds physical inventory and stock monitoring in the bulk-liquid sector.

This page focuses on the structure published by UN/CEFACT for directory D.24A. The segments listed, their status (M / C), position and repetition factor are extracted from the official file tansta_c.htm hosted on service.unece.org.

Segment structure

The TANSTA D.24A message has 19 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.
00010UNHMessage headerM1
00020BGMBeginning of messageM1
00030DTMDate/time/periodM1
00040NADName and addressC×9
00050  SG1Group (×9)C×9
00060  RFFReferenceM1
00070  DTMDate/time/periodC×9
00080    SG2Group (×9)M×9
00090    TDTTransport informationM1
00100    LOCPlace/location identificationM1
00110    DTMDate/time/periodM×9
00120    RFFReferenceC1
00130    FTXFree textC1
00140      SG3Group (×999)C×999
00150      LOCPlace/location identificationM1
00160      MEAMeasurementsM×9
00170      DIMDimensionsC×9
00180      FTXFree textC1
00190UNTMessage trailerM1

Detail

No segment in this section.

Summary

No segment in this section.

Changes vs D.96A

Top-level differences between D.96A and D.24A for the TANSTA 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.

No top-level differences detected between D.96A and D.24A for this message. Differences are then limited to nested groups and code lists.

Structural example

Minimal example of an TANSTA D.24A message with mandatory segments only. The goal is to show the exact version declared in UNH (TANSTA:D:24A:UN) — not to replicate a full business case (see the TANSTA D.96A page for an annotated example).

edifact tansta-d24a-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL024001'
UNH+1+TANSTA:D:24A:UN'
BGM+262+TANSTA-2026-TANK-04+9'
DTM+137:202605141430:203'
NAD+TR+5410000000123::9'
UNT+5+1'
UNZ+1+CTRL024001'

Common errors

  • Misaligned UNH tokens — The UNH+...+TANSTA:D:24A: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.24A, 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: TANSTA D.96A, TANSTA D.10A, TANSTA D.16B, TANSTA D.21B.

← All EDIFACT versions