CONDPV — EDIFACT Conditions for Payment for Volume Sales Message (D.96A)
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.96A.
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.96A. 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.96A 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.
Header
| Pos. | Tag | Name | S | Rep. |
|---|---|---|---|---|
0010 | UNH | Message header | M | 1 |
0020 | BGM | Beginning of message | M | 1 |
0030 | DTM | Date/time/period | M | ×9 |
0040 | AUT | Authentication result | C | ×2 |
0050 | FTX | Free text | C | ×5 |
0060 | SG1 | Group (×9) | C | ×9 |
0070 | RFF | Reference | M | 1 |
0080 | DTM | Date/time/period | C | ×5 |
0090 | SG2 | Group (×9) | M | ×9 |
0100 | NAD | Name and address | M | 1 |
0110 | LOC | Place/location identification | C | ×25 |
0120 | FII | Financial institution information | C | ×5 |
0130 | SG3 | Group (×10) | C | ×10 |
0140 | RFF | Reference | M | 1 |
0150 | DTM | Date/time/period | C | ×5 |
0160 | SG4 | Group (×5) | C | ×5 |
0170 | DOC | Document/message details | M | 1 |
0180 | DTM | Date/time/period | C | ×5 |
0190 | SG5 | Group (×5) | C | ×5 |
0200 | CTA | Contact information | M | 1 |
0210 | COM | Communication contact | C | ×5 |
0220 | SG6 | Group (×5) | C | ×5 |
0230 | CUX | Currencies | M | 1 |
0240 | DTM | Date/time/period | C | ×5 |
0250 | SG7 | Group (×100) | C | ×100 |
0260 | IND | Index details | M | 1 |
0270 | RFF | Reference | M | 1 |
0280 | DTM | Date/time/period | C | 1 |
0290 | SG8 | Group (×1000) | C | ×1000 |
0300 | BII | Structure identification | M | 1 |
0310 | RCS | Requirements and conditions | C | 1 |
0320 | PAI | Payment instructions | C | 1 |
0330 | PAT | Payment terms basis | C | 1 |
0340 | SG9 | Group (×2) | C | ×2 |
0350 | APR | Additional price information | M | 1 |
0360 | DTM | Date/time/period | C | ×5 |
0370 | SG10 | Group (×100) | M | ×100 |
0380 | ARD | Amounts relationship details | M | 1 |
0390 | MOA | Monetary amount | M | ×6 |
0400 | FTX | Free text | C | ×10 |
0410 | SG11 | Group (×5) | C | ×5 |
0420 | TAX | Duty/tax/fee details | M | 1 |
0430 | MOA | Monetary amount | C | 1 |
0440 | LOC | Place/location identification | C | ×5 |
0450 | SG12 | Group (×20) | C | ×20 |
0460 | NAD | Name and address | M | 1 |
0470 | LOC | Place/location identification | C | ×25 |
0480 | FII | Financial institution information | C | ×5 |
0490 | SG13 | Group (×10) | C | ×10 |
0500 | RFF | Reference | M | 1 |
0510 | DTM | Date/time/period | C | ×5 |
0520 | SG14 | Group (×5) | C | ×5 |
0530 | DOC | Document/message details | M | 1 |
0540 | DTM | Date/time/period | C | ×5 |
0550 | SG15 | Group (×5) | C | ×5 |
0560 | CTA | Contact information | M | 1 |
0570 | COM | Communication contact | C | ×5 |
0580 | UNT | Message trailer | M | 1 |
Detail
No segment in this section.
Summary
No segment in this section.
Changes vs D.96A
This page documents directory D.96A itself: it serves as the reference for every other version of the message. The synthesis below describes the structural changes that later directories will introduce relative to it.
No top-level differences detected between D.96A and D.96A for this message. Differences are then limited to nested groups and code lists.
Structural example
Minimal example of an CONDPV D.96A message with mandatory segments only. The goal is to show the exact version declared in UNH (CONDPV:D:96A:UN) — not to replicate a full business case.
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL096001'
UNH+1+CONDPV:D:96A: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+CTRL096001'Common errors
- Misaligned UNH tokens — The
UNH+...+CONDPV:D:96A:UNtoken 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.96A, 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.
Related messages
Other versions of this message available on ediverse.io: CONDPV D.10A, CONDPV D.16B, CONDPV D.21B, CONDPV D.24A.