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.
JINFDE D.99B

JINFDE — EDIFACT Job Information Demand Message (D.99B)

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.99B.

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.99B. 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.99B message has 16 header entries, 21 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×2
0040  SG1Group (×9)M×9
0050  PNAParty identificationM1
0060  ADRAddressC1
0070  LOCPlace/location identificationC×5
0080  DTMDate/time/periodC×5
0090    SG2Group (×5)C×5
0100    CTAContact informationM1
0110    COMCommunication contactC×5
0120      SG3Group (×5)C×5
0130      RFFReferenceM1
0140      DTMDate/time/periodC×5
0150        SG4Group (×5)C×5
0170        FTXFree textC1

Detail

Pos.TagNameSRep.
0180UNSSection controlM1
0190  SG5Group (×999)M×999
0200  RFFReferenceM1
0210    SG6Group (×999)M×999
0220    PNAParty identificationM1
0230    ADRAddressC1
0240    LOCPlace/location identificationC×2
0250    DTMDate/time/periodC×5
0260    NATNationalityC×9
0270    PDIPerson demographic informationC1
0280    DOCDocument/message detailsC×9
0290      SG7Group (×5)C×5
0300      CTAContact informationM1
0310      COMCommunication contactC×5
0320        SG8Group (×5)C×5
0330        RFFReferenceM1
0340        DTMDate/time/periodC×5
0350        FTXFree textM×30
0360          SG9Group (×30)C×30
0380          FTXFree textC1
0390UNTMessage trailerM1

Summary

No segment in this section.

Changes vs D.96A

Top-level differences between D.96A and D.99B 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

  • GIS in the header section — present in D.96A but missing in D.99B at the same level.
  • GIS in the detail section — present in D.96A but missing in D.99B at the same level.

Structural example

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

edifact jinfde-d99b-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL099001'
UNH+1+JINFDE:D:99B: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+CTRL099001'

Common errors

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

← All EDIFACT versions