The DTM segment carries date and time information. The first sub-element is the qualifier that identifies what the date means, the second is the value, and the third is the format code. Common qualifiers: 137=document date, 2=delivery requested, 63=latest delivery, 35=delivery date, 131=tax point date, 36=expiry date, 11=despatch date. Common format codes: 102=YYYYMMDD, 203=YYYYMMDDHHmm.
DTMHover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.
DTM+137:20260823:102'Document date: 23 August 2026.
| 1.1 | Date: Qualifier | 137Document date |
| 1.2 | Date: Value | 20260823 |
| 1.3 | Date: Format | 102CCYYMMDD |
{
"documentDate": "2026-08-23"
}Example shape. In production the field names and structure follow your own API contract.
Elements are separated by + and their parts by :. Positions match the explainer, so 2.3 is the third part of the second element.
| Position | Element | Parts |
|---|---|---|
| 1 | Date | 1.1 Qualifier, 1.2 Value, 1.3 Format |
| Code | Meaning |
|---|---|
2 | Requested delivery date |
3 | Invoice date |
10 | Requested shipment date |
11 | Despatch date |
13 | Payment due date |
17 | Estimated delivery date |
35 | Actual delivery date |
50 | Goods receipt date |
63 | Latest delivery date |
64 | Earliest delivery date |
69 | Promised delivery date |
137 | Document date |
171 | Reference date |
194 | Start date |
200 | Pick-up date |
206 | End date |
361 | Best before date |
| Code | Meaning |
|---|---|
101 | YYMMDD |
102 | CCYYMMDD |
203 | CCYYMMDDHHMM |
204 | CCYYMMDDHHMMSS |
718 | Date range CCYYMMDD-CCYYMMDD |
Common EANCOM and UN/EDIFACT values. Your trading partner's implementation guide is the final word on which codes they send.
Have a real message with DTM in it? The explainer breaks down every segment and runs in your browser.
Explain my message