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

SLSRPT — EDIFACT Sales Data Report Message (D.21B)

The SLSRPT message is the periodic sales data report sent by a retailer or point of sale to a supplier or central organisation: it carries sales volumes per item reference, per outlet and per period, sometimes enriched with average prices and variances against forecasts. It drives production and replenishment decisions, particularly in mass retail. This page summarises the segment structure as published by UN/CEFACT for directory D.21B.

Purpose

The SLSRPT message is the periodic sales data report sent by a retailer or point of sale to a supplier or central organisation: it carries sales volumes per item reference, per outlet and per period, sometimes enriched with average prices and variances against forecasts. It drives production and replenishment decisions, particularly in mass retail.

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

Segment structure

The SLSRPT D.21B message has 19 header entries, 52 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/periodM×5
00040MKSMarket/sales channel informationC1
00050  SG1Group (×9)C×9
00060  RFFReferenceM1
00070  DTMDate/time/periodC×9
00080    SG2Group (×5)M×5
00090    NADName and addressM1
00100      SG3Group (×5)C×5
00110      CTAContact informationM1
00120      COMCommunication contactC×5
00130        SG4Group (×9)C×9
00140        RFFReferenceM1
00150        DTMDate/time/periodC×9
00160          SG5Group (×5)C×5
00170          CUXCurrenciesM1
00180          DTMDate/time/periodC×5
00190          STSStatusC×5

Detail

Pos.TagNameSRep.
00200  SG6Group (×200000)C×200000
00210  LOCPlace/location identificationM1
00220  DTMDate/time/periodC×5
00230  FTXFree textC×5
00240    SG7Group (×99)C×99
00250    RFFReferenceM1
00260    DTMDate/time/periodC×5
00270      SG8Group (×200000)C×200000
00280      LINLine itemM1
00290      PIAAdditional product idC×5
00300      IMDItem descriptionC×5
00310      DTMDate/time/periodC×9
00320      PACPackageC×5
00330      RFFReferenceC×5
00340      DOCDocument/message detailsC×5
00350      ALIAdditional informationC×5
00360      MOAMonetary amountC×5
00370      GINGoods identity numberC×9999
00380        SG9Group (×999)C×999
00390        PRIPrice detailsM1
00400        CUXCurrenciesC1
00410        PAIPayment instructionsC×9
00420          SG10Group (×999)C×999
00430          QTYQuantityM1
00440          MKSMarket/sales channel informationC1
00450          NADName and addressC1
00460          PRIPrice detailsC×9
00470          DTMDate/time/periodC×9
00480          RFFReferenceC×9
00490          STSStatusC×9
00500            SG11Group (×1)C1
00510            GEIProcessing informationM1
00520              SG12Group (×999999)C×999999
00530              LINLine itemM1
00540              PIAAdditional product idC×99
00550              IMDItem descriptionC×9
00560              PACPackageC×9
00570              MOAMonetary amountC×9
00580                SG13Group (×9999)C×9999
00590                LOCPlace/location identificationM1
00600                RFFReferenceC×9
00610                DTMDate/time/periodC×9
00620                MOAMonetary amountC×9
00630                  SG14Group (×99)C×99
00640                  QTYQuantityM1
00650                  PRIPrice detailsC×9
00660                  DTMDate/time/periodC×9
00670                  RFFReferenceC×9
00680                  STSStatusC×9
00690UNSSection controlM1
00700MOAMonetary amountC×9
00710UNTMessage trailerM1

Summary

No segment in this section.

Changes vs D.96A

Top-level differences between D.96A and D.21B for the SLSRPT 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

  • MKS in the header section (status C, repeat ×1) — not present at the top of the corresponding D.96A section.
  • STS in the header section (status C, repeat ×5) — not present at the top of the corresponding D.96A section.
  • FTX in the detail section (status C, repeat ×5) — not present at the top of the corresponding D.96A section.
  • CUX in the detail section (status C, repeat ×1) — not present at the top of the corresponding D.96A section.
  • PAI in the detail section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.
  • STS in the detail section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.
  • GEI in the detail section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.
  • UNS in the detail section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.

Status changes (M ↔ C)

  • PRI (detail): status C in D.96A → M in D.21B.

Max-repeat changes

  • PRI (detail): repeat ×5 in D.96A → ×1 in D.21B.

Structural example

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

edifact slsrpt-d21b-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL021001'
UNH+1+SLSRPT:D:21B:UN'
BGM+74+SLS-2026-W19+9'
DTM+137:20260514:102'
DTM+90:20260513:102'
NAD+SR+5410000000123::9'
CUX+2:EUR:4'
LOC+18+FRPAR01::ZZZ'
RFF+AAU:SLS-2026-W19-OUT01'
LIN+1++3520000001234:EN'
QTY+47:23'
MOA+203:966.00'
UNT+12+1'
UNZ+1+CTRL021001'

Common errors

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

X12 functional equivalent: X12 852.

← All EDIFACT versions