EDIFACT message guide · Healthcare and social
JOBCON Job order confirmation
The UN/EDIFACT message an employment agency sends an employer to confirm receipt of a job order.
- Sent by
- Employment agency
- Received by
- Employer
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT JOBCON message?
JOBCON is the UN/EDIFACT job order confirmation. The directory defines its intent as confirming receipt of a job order message for one or more vacancies, transmitted from an employment agency to an employer, with the information related to the vacancy.
The confirmation gives the employer the agency's reference for each vacancy and shows how the agency recorded it, so the employer can correct misunderstandings before candidates are proposed and refer to the vacancy in later messages. It is the first reply in the job order exchange, before any candidates are proposed with JOBAPP.
How to read this diagram: the top row shows who sends JOBCON, 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 JOBCON 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.
When it is used
- Confirming receipt of a job order
- Returning the agency's vacancy references
- Showing how a vacancy was recorded
Where it fits in the message flow
Structure
Mandatory segments in JOBCON (directory D.21A)
In UN/EDIFACT directory D.21A, the JOBCON message has 59 segment positions arranged in 19 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
JOBCON in practice
After receiving a job order for 15 warehouse operatives, the employment service sends the logistics company a JOBCON with its vacancy number and the recorded details. The HR team notices that the shift pattern was recorded incorrectly and corrects it with a JOBMOD.
Implementation
Implementation considerations for JOBCON
- Store the agency's vacancy references for later messages.
- Check the recorded details against the original order.
- Correct differences quickly, before matching starts.
- Track job orders that have not been confirmed.
How ECOM helps
Automate JOBCON 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.
Industry
Trucking and Transportation
Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.
Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.
Related messages
Related healthcare and social messages
Need help with JOBCON?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.