972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Government and legal

JINFDE Job information demand

The UN/EDIFACT message a government agency sends an employer to request additional information on a work grant request.

Sent by
Government authority for work permits
Received by
Employer
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT JINFDE message?

JINFDE is the UN/EDIFACT job information demand. The directory defines it as a message sent by a governmental agency to an employer in response to a work grant request, asking for specific additional information, such as a visa, needed to process the request further.

An information demand pauses the application until the employer responds. Handling it quickly avoids delays to a worker's start date, so employers route these demands to the person managing the application. Several demands can be issued during one application.

How the EDIFACT JINFDE message worksDiagram of the UN/EDIFACT JINFDE Job information demand message. Government authority for work permits sends it to employer. It usually follows WKGRRE. It is usually followed by WKGRDC. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG1 loop with PNA (Party identification), UNS (Section control) and the required SG5 loop with RFF (Reference), the required SG6 loop with PNA (Party identification) and FTX (Free text). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT JINFDE message worksJob information demand: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSWKGRREWork grant requestJINFDESENDERGovernment authorityfor work permitsRECEIVEREmployerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYWKGRDCWork grant decision2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage JINFDEUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 9PNAParty identificationUNSSection controlMandatory group SG5 · repeats up to 999RFFReferenceMandatory group SG6 · repeats up to 999PNAParty identificationFTXFree text+ 6 conditional groups, starting with:CTARFFGEIBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for JINFDE. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT JINFDE message worksDiagram of the UN/EDIFACT JINFDE Job information demand message. Government authority for work permits sends it to employer. It usually follows WKGRRE. It is usually followed by WKGRDC. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG1 loop with PNA (Party identification), UNS (Section control) and the required SG5 loop with RFF (Reference), the required SG6 loop with PNA (Party identification) and FTX (Free text). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT JINFDEmessage worksJob information demand: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSWKGRREWork grant requestJINFDESENDERGovernmentauthority forwork permitsRECEIVEREmployerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYWKGRDCWork grant decision2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message JINFDE (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 9PNAParty identificationUNSSection control+ required SG5 (RFF) and 6 conditionalgroups, starting with:CTARFFGEIBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for JINFDE.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends JINFDE, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around JINFDE and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Requesting missing details for a work permit application
  • Requesting visa or document references
  • Clarifying employment conditions

Where it fits in the message flow

Usually follows WKGRRE Work grant request
This message JINFDE Job information demand
Usually followed by WKGRDC Work grant decision

Structure

Mandatory segments in JINFDE (directory D.21A)

In UN/EDIFACT directory D.21A, the JINFDE message has 30 segment positions arranged in 9 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • SG1 (PNA)
  • UNS
  • SG5 (RFF)
  • UNT

Practical example

JINFDE in practice

The labor authority reviewing a work grant request needs the applicant's visa reference. It sends the employer a JINFDE identifying the request and the missing item. The employer supplies the reference, and the authority completes its review.

Implementation

Implementation considerations for JINFDE

  • Route demands to the person managing the application.
  • Respond within the deadline the authority sets.
  • Reference the original work grant request exactly.
  • Keep a record of the information supplied and when.

How ECOM helps

Automate JINFDE with ECOM

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related government and legal messages

All 5 government and legal messages

Need help with JINFDE?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us