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.05A

SLSRPT — EDIFACT Sales Data Report Message (D.05A)

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.05A.

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.05A. 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.05A 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.
0010UNHMessage headerM1
0020BGMBeginning of messageM1
0030DTMDate/time/periodM×5
0040MKSMarket/sales channel informationC1
0050  SG1Group (×9)C×9
0060  RFFReferenceM1
0070  DTMDate/time/periodC×9
0080    SG2Group (×5)M×5
0090    NADName and addressM1
0100      SG3Group (×5)C×5
0110      CTAContact informationM1
0120      COMCommunication contactC×5
0130        SG4Group (×9)C×9
0140        RFFReferenceM1
0150        DTMDate/time/periodC×9
0160          SG5Group (×5)C×5
0170          CUXCurrenciesM1
0180          DTMDate/time/periodC×5
0190          STSStatusC×5

Detail

Pos.TagNameSRep.
0200  SG6Group (×200000)C×200000
0210  LOCPlace/location identificationM1
0220  DTMDate/time/periodC×5
0230  FTXFree textC×5
0240    SG7Group (×99)C×99
0250    RFFReferenceM1
0260    DTMDate/time/periodC×5
0270      SG8Group (×200000)C×200000
0280      LINLine itemM1
0290      PIAAdditional product idC×5
0300      IMDItem descriptionC×5
0310      DTMDate/time/periodC×9
0320      PACPackageC×5
0330      RFFReferenceC×5
0340      DOCDocument/message detailsC×5
0350      ALIAdditional informationC×5
0360      MOAMonetary amountC×5
0370      GINGoods identity numberC×9999
0380        SG9Group (×999)C×999
0390        PRIPrice detailsM1
0400        CUXCurrenciesC1
0410        PAIPayment instructionsC×9
0420          SG10Group (×999)C×999
0430          QTYQuantityM1
0440          MKSMarket/sales channel informationC1
0450          NADName and addressC1
0460          PRIPrice detailsC×9
0470          DTMDate/time/periodC×9
0480          RFFReferenceC×9
0490          STSStatusC×9
0500            SG11Group (×1)C1
0510            GEIProcessing informationM1
0520              SG12Group (×999999)C×999999
0530              LINLine itemM1
0540              PIAAdditional product idC×99
0550              IMDItem descriptionC×9
0560              PACPackageC×9
0570              MOAMonetary amountC×9
0580                SG13Group (×9999)C×9999
0590                LOCPlace/location identificationM1
0600                RFFReferenceC×9
0610                DTMDate/time/periodC×9
0620                MOAMonetary amountC×9
0630                  SG14Group (×99)C×99
0640                  QTYQuantityM1
0650                  PRIPrice detailsC×9
0660                  DTMDate/time/periodC×9
0670                  RFFReferenceC×9
0680                  STSStatusC×9
0690UNSSection controlM1
0700MOAMonetary amountC×9
0710UNTMessage trailerM1

Summary

No segment in this section.

Changes vs D.96A

Top-level differences between D.96A and D.05A 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.05A.

Max-repeat changes

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

Structural example

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

edifact slsrpt-d05a-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL005001'
UNH+1+SLSRPT:D:05A: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+CTRL005001'

Common errors

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

X12 functional equivalent: X12 852.

← All EDIFACT versions