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.
CONDPV D.97A

CONDPV — EDIFACT Conditions for Payment for Volume Sales Message (D.97A)

The CONDPV message conveys the pricing and payment conditions negotiated for a sales volume between an authority and a supplier (typically for alcohol, tobacco or state-monopoly contracts): unit prices, volume tiers, effective dates and rules over the contract period. This page summarises the segment structure as published by UN/CEFACT for directory D.97A.

Purpose

The CONDPV message conveys the pricing and payment conditions negotiated for a sales volume between an authority and a supplier (typically for alcohol, tobacco or state-monopoly contracts): unit prices, volume tiers, effective dates and rules over the contract period.

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

Segment structure

The CONDPV D.97A message has 58 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/periodM×9
0040AUTAuthentication resultC×2
0050FTXFree textC×5
0060  SG1Group (×9)C×9
0070  RFFReferenceM1
0080  DTMDate/time/periodC×5
0090    SG2Group (×9)M×9
0100    NADName and addressM1
0110    LOCPlace/location identificationC×25
0120    FIIFinancial institution informationC×5
0130      SG3Group (×10)C×10
0140      RFFReferenceM1
0150      DTMDate/time/periodC×5
0160        SG4Group (×5)C×5
0170        DOCDocument/message detailsM1
0180        DTMDate/time/periodC×5
0190          SG5Group (×5)C×5
0200          CTAContact informationM1
0210          COMCommunication contactC×5
0220            SG6Group (×5)C×5
0230            CUXCurrenciesM1
0240            DTMDate/time/periodC×5
0250              SG7Group (×100)C×100
0260              INDIndex detailsM1
0270              RFFReferenceM1
0280              DTMDate/time/periodC1
0290                SG8Group (×1000)C×1000
0300                BIIStructure identificationM1
0310                RCSRequirements and conditionsC1
0320                PAIPayment instructionsC1
0330                PATPayment terms basisC1
0340                  SG9Group (×2)C×2
0350                  APRAdditional price informationM1
0360                  DTMDate/time/periodC×5
0370                    SG10Group (×100)M×100
0380                    ARDAmounts relationship detailsM1
0390                    MOAMonetary amountM×6
0400                    FTXFree textC×10
0410                      SG11Group (×5)C×5
0420                      TAXDuty/tax/fee detailsM1
0430                      MOAMonetary amountC1
0440                      LOCPlace/location identificationC×5
0450                        SG12Group (×20)C×20
0460                        NADName and addressM1
0470                        LOCPlace/location identificationC×25
0480                        FIIFinancial institution informationC×5
0490                          SG13Group (×10)C×10
0500                          RFFReferenceM1
0510                          DTMDate/time/periodC×5
0520                            SG14Group (×5)C×5
0530                            DOCDocument/message detailsM1
0540                            DTMDate/time/periodC×5
0550                              SG15Group (×5)C×5
0560                              CTAContact informationM1
0570                              COMCommunication contactC×5
0580UNTMessage 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.97A for the CONDPV 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.97A for this message. Differences are then limited to nested groups and code lists.

Structural example

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

edifact condpv-d97a-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL097001'
UNH+1+CONDPV:D:97A:UN'
BGM+341+CONDPV-2026-0008+9'
DTM+137:20260514:102'
DTM+194:20260601:102'
DTM+206:20261231:102'
AUT+REF-MARCHE-2026-VOL-08'
FTX+AAI+++Conditions tarifaires marche annuel volume - alcools forts'
UNT+8+1'
UNZ+1+CTRL097001'

Common errors

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

← All EDIFACT versions