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.
BMISRM D.21B

BMISRM — EDIFACT Bulk Marine Inspection Summary Report (D.21B)

The BMISRM message is the bulk-marine inspection summary report on a vessel cargo: volumes, qualities, temperatures, drafts, B/L difference calculations and damage findings. It is used by independent inspection bodies (SGS, Bureau Veritas…) to report on a crude oil, chemical, grain or ore cargo. This page summarises the segment structure as published by UN/CEFACT for directory D.21B.

Purpose

The BMISRM message is the bulk-marine inspection summary report on a vessel cargo: volumes, qualities, temperatures, drafts, B/L difference calculations and damage findings. It is used by independent inspection bodies (SGS, Bureau Veritas…) to report on a crude oil, chemical, grain or ore cargo.

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

Segment structure

The BMISRM D.21B message has 17 header entries, 28 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
00040RFFReferenceM×9
00050LOCPlace/location identificationM×9
00060FTXFree textC×99
00070  SG1Group (×9)M×9
00080  PNAParty identificationM1
00090  ADRAddressC1
00100  RFFReferenceC1
00110    SG2Group (×9)C×9
00120    CTAContact informationM1
00130    COMCommunication contactC×9
00140      SG3Group (×999)C×999
00150      DTMDate/time/periodM1
00160      STSStatusC1
00170      FTXFree textC×9

Detail

Pos.TagNameSRep.
00180  SG4Group (×999)M×999
00190  LINLine itemM1
00200  QTYQuantityC1
00210  FTXFree textC×99
00220    SG5Group (×9)C×9
00230    PNAParty identificationM1
00240    ADRAddressC1
00250    RFFReferenceC1
00260      SG6Group (×9)C×9
00270      CTAContact informationM1
00280      COMCommunication contactC×9
00290        SG7Group (×999)C×999
00300        TDTTransport informationM1
00310        EQDEquipment detailsC1
00320        RFFReferenceC×9
00330        QTYQuantityC1
00340        MEAMeasurementsC×99
00350        PCDPercentage detailsC×99
00360          SG8Group (×99)C×99
00370          PSDPhysical sample descriptionM1
00380          LOCPlace/location identificationC×99
00390            SG9Group (×999)C×999
00400            TEMTest methodM1
00410            MEAMeasurementsC×99
00420            PCDPercentage detailsC×99
00430            DTMDate/time/periodC×99
00440            FTXFree textC×99
00450UNTMessage trailerM1

Summary

No segment in this section.

Changes vs D.96A

The BMISRM message is not published in directory D.96A. No "D.96A → D.21B" comparison line can therefore be produced — see the block below for details.

This message is not published in directory D.96A: it was introduced into the standard after that release and therefore has no historical baseline for comparison. The first directory indexed on ediverse.io sets the reference; later changes are then documented from one release to the next in subsequent directories.

Structural example

Minimal example of an BMISRM D.21B message with mandatory segments only. The goal is to show the exact version declared in UNH (BMISRM:D:21B:UN) — not to replicate a full business case.

edifact bmisrm-d21b-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL021001'
UNH+1+BMISRM:D:21B:UN'
BGM+350+BMISRM-2026-OIL-099+9'
DTM+137:20260514:102'
TDT+20+TANKER42E+1++SHELL::ZZZ+++9301234:103:::SHELL VENTURE'
NAD+MS+5410000000123::9'
NAD+MR+5410000000456::9'
LOC+5+FRFOS::6'
LIN+1+++CRUDE-OIL:ZZZ'
QTY+58:215400:BBL'
MEA+AAE+T+CEL:18.4'
UNT+10+1'
UNZ+1+CTRL021001'

Common errors

  • Misaligned UNH tokens — The UNH+...+BMISRM:D:21B: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.21B, 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: BMISRM D.01B, BMISRM D.10A, BMISRM D.16B, BMISRM D.24A, BMISRM D.99B, BMISRM D.00B, BMISRM D.02B, BMISRM D.05A, BMISRM D.08A, BMISRM D.13B, BMISRM D.18B, BMISRM D.20B.

← All EDIFACT versions