ediverse

Type to search across standards, messages, tools and glossary.

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.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools
JINFDE D.97A

JINFDE — EDIFACT Job Information Demand Message (D.97A)

The JINFDE message is the demand for information about a vacant job, exchanged between an employment agency, an employer and a job-seeker: it carries the job identifier, the required profile, training, remuneration and workplace. This page summarises the segment structure as published by UN/CEFACT for directory D.97A.

Purpose

The JINFDE message is the demand for information about a vacant job, exchanged between an employment agency, an employer and a job-seeker: it carries the job identifier, the required profile, training, remuneration and workplace.

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 jinfde_c.htm hosted on service.unece.org.

Segment structure

The JINFDE D.97A message has 0 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.

No segment in this section.

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 JINFDE 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 removed vs D.96A

  • UNH in the header section — present in D.96A but missing in D.97A at the same level.
  • BGM in the header section — present in D.96A but missing in D.97A at the same level.
  • DTM in the header section — present in D.96A but missing in D.97A at the same level.
  • PNA in the header section — present in D.96A but missing in D.97A at the same level.
  • ADR in the header section — present in D.96A but missing in D.97A at the same level.
  • LOC in the header section — present in D.96A but missing in D.97A at the same level.
  • CTA in the header section — present in D.96A but missing in D.97A at the same level.
  • COM in the header section — present in D.96A but missing in D.97A at the same level.
  • RFF in the header section — present in D.96A but missing in D.97A at the same level.
  • GIS in the header section — present in D.96A but missing in D.97A at the same level.
  • FTX in the header section — present in D.96A but missing in D.97A at the same level.
  • UNS in the detail section — present in D.96A but missing in D.97A at the same level.
  • RFF in the detail section — present in D.96A but missing in D.97A at the same level.
  • PNA in the detail section — present in D.96A but missing in D.97A at the same level.
  • ADR in the detail section — present in D.96A but missing in D.97A at the same level.
  • LOC in the detail section — present in D.96A but missing in D.97A at the same level.
  • DTM in the detail section — present in D.96A but missing in D.97A at the same level.
  • NAT in the detail section — present in D.96A but missing in D.97A at the same level.
  • PDI in the detail section — present in D.96A but missing in D.97A at the same level.
  • DOC in the detail section — present in D.96A but missing in D.97A at the same level.
  • CTA in the detail section — present in D.96A but missing in D.97A at the same level.
  • COM in the detail section — present in D.96A but missing in D.97A at the same level.
  • FTX in the detail section — present in D.96A but missing in D.97A at the same level.
  • GIS in the detail section — present in D.96A but missing in D.97A at the same level.
  • UNT in the detail section — present in D.96A but missing in D.97A at the same level.

Structural example

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

edifact jinfde-d97a-example.edi 
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL097001'
UNH+1+JINFDE:D:97A:UN'
BGM+315+JINFDE-2026-0011+9'
DTM+137:20260514:102'
NAD+MS+5410000000123::9'
NAD+EM+5410000000456::9'
EMP+1+SOFTWARE ENGINEER'
LOC+19+PARIS:::FR'
RFF+AHI:VAC-2026-7811'
UNT+8+1'
UNZ+1+CTRL097001'

Common errors

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

← All EDIFACT versions