EDIFACT message guide · Healthcare and social
JOBOFF Job order
The UN/EDIFACT message an employer uses to send an employment agency details of one or more vacancies.
- Sent by
- Employer
- Received by
- Employment agency
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT JOBOFF message?
JOBOFF is the UN/EDIFACT job order message. The directory defines it as a message specifying details of one or more vacancies, such as occupation, salaries, experience and work and contract conditions, sent by an employer to an employment agency.
Public employment services and private agencies receive vacancies from many employers. A structured job order lets the agency publish the vacancy and match it to job seekers automatically by occupation, location and requirements. The agency confirms receipt with JOBCON, and the employer can amend the order with JOBMOD.
How to read this diagram: the top row shows who sends JOBOFF, 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 JOBOFF 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
- Registering vacancies with a public employment service
- Sending job orders to staffing agencies
- Publishing several vacancies at once
Where it fits in the message flow
Structure
Mandatory segments in JOBOFF (directory D.21A)
In UN/EDIFACT directory D.21A, the JOBOFF 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
JOBOFF in practice
A logistics company needs 15 warehouse operatives for a new site. Its HR system sends the regional employment service a JOBOFF with the occupation code, location, shift patterns, pay range, required experience and start date. The service confirms the order and starts proposing candidates.
Implementation
Implementation considerations for JOBOFF
- Use the occupation classification the agency requires.
- Comply with anti-discrimination rules in the vacancy details.
- Send modifications when vacancies are filled or changed.
- Protect any personal data in contact details.
How ECOM helps
Automate JOBOFF with ECOM
Industry
Trucking and Transportation
Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.
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.
Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.
Related messages
Related healthcare and social messages
Need help with JOBOFF?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.