REQDOC — EDIFACT Request for Document Message (D.96A)
The REQDOC message is a formal request for a specific document between trade partners: duplicate invoice, proof of delivery, copy of a payment advice. It references the expected document by type, number or search criterion. This page summarises the segment structure as published by UN/CEFACT for directory D.96A.
Purpose
The REQDOC message is a formal request for a specific document between trade partners: duplicate invoice, proof of delivery, copy of a payment advice. It references the expected document by type, number or search criterion.
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 reqdoc_s.htm hosted on service.unece.org.
Segment structure
The REQDOC D.96A message has 30 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 | DOC | Document/message details | M | 1 |
0040 | DTM | Date/time/period | M | ×9 |
0050 | SG1 | Group (×9) | C | ×9 |
0060 | RFF | Reference | M | 1 |
0070 | DTM | Date/time/period | C | ×5 |
0080 | SG2 | Group (×9) | M | ×9 |
0090 | NAD | Name and address | M | 1 |
0100 | LOC | Place/location identification | C | ×9 |
0110 | SG3 | Group (×9) | C | ×9 |
0120 | CTA | Contact information | M | 1 |
0130 | COM | Communication contact | C | ×9 |
0140 | SG4 | Group (×999) | M | ×999 |
0150 | LIN | Line item | M | 1 |
0160 | GIS | General indicator | C | ×9 |
0170 | DTM | Date/time/period | C | ×9 |
0180 | PIA | Additional product id | C | ×9 |
0190 | IMD | Item description | C | ×9 |
0200 | MEA | Measurements | C | ×9 |
0210 | SG5 | Group (×9) | C | ×9 |
0220 | RFF | Reference | M | 1 |
0230 | DTM | Date/time/period | C | ×9 |
0240 | SG6 | Group (×9) | C | ×9 |
0250 | NAD | Name and address | M | 1 |
0260 | LOC | Place/location identification | C | ×9 |
0270 | SG7 | Group (×9) | C | ×9 |
0280 | CTA | Contact information | M | 1 |
0290 | COM | Communication contact | C | ×9 |
0300 | UNT | Message trailer | M | 1 |
Detail
No segment in this section.
Summary
No segment in this section.
Changes vs D.96A
Top-level differences between D.96A and D.96A for the REQDOC 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.96A for this message. Differences are then limited to nested groups and code lists.
Structural example
Minimal example of an REQDOC D.96A message with mandatory segments only. The goal is to show the exact version declared in UNH (REQDOC:D:96A:UN) — not to replicate a full business case (see the REQDOC D.96A page for an annotated example).
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL096001'
UNH+1+REQDOC:D:96A:UN'
BGM+700+REQDOC-2026-0044+9'
DTM+137:20260514:102'
NAD+MS+5410000000123::9'
NAD+MR+5410000000456::9'
DOC+380+INV-2026-7811'
DTM+171:20260512:102'
UNT+7+1'
UNZ+1+CTRL096001'Common errors
- Misaligned UNH tokens — The
UNH+...+REQDOC: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: REQDOC D.96A, REQDOC D.01B, REQDOC D.10A, REQDOC D.16B, REQDOC D.21B, REQDOC D.24A, REQDOC D.97A, REQDOC D.99B, REQDOC D.00B, REQDOC D.02B, REQDOC D.05A, REQDOC D.08A, REQDOC D.13B, REQDOC D.18B, REQDOC D.20B.
X12 functional equivalent: X12 627.