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

WKGRRE Work grant request

The UN/EDIFACT message an employer uses to request work grants or permits from a government authority for workers who need them.

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

What is the EDIFACT WKGRRE message?

WKGRRE is the UN/EDIFACT work grant request. The directory defines it as a message specifying details of requests from an employer to a governmental authority for workers who need a work grant or permit.

Employers hiring foreign workers often need authorization before they can employ them. The request carries the worker's details, the job and the employment conditions. The authority may ask for more information with JINFDE and decides with WKGRDC. Requests can cover several workers at once. Supporting documents, such as passport copies or qualifications, may be required separately by the authority.

How the EDIFACT WKGRRE message worksDiagram of the UN/EDIFACT WKGRRE Work grant request message. Employer sends it to government authority for work permits. It usually starts the exchange. It is usually followed by JINFDE and 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), DTM (Date/time/period), the required SG7 loop with GEI (Processing information), the required SG8 loop with RFF (Reference), the required SG9 loop with EMP (Employment details) and LOC (Place/location identification) and the required SG11 loop with SAL (Remuneration type identification), the required SG12 loop with ATT (Attribute) and the required SG14 loop with MOA (Monetary amount). 7 conditional segment groups are listed by their trigger segment.How the EDIFACT WKGRRE message worksWork grant request: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeWKGRRESENDEREmployerRECEIVERGovernment authorityfor work permitsCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYJINFDEJob informationdemandWKGRDCWork grant decision2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage WKGRREUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 3PNAParty identificationUNSSection control+ required SG5 (RFF) and 7 conditional groups, starting with:CTARFFGEIPNAATTBlue 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 WKGRRE. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT WKGRRE message worksDiagram of the UN/EDIFACT WKGRRE Work grant request message. Employer sends it to government authority for work permits. It usually starts the exchange. It is usually followed by JINFDE and 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), DTM (Date/time/period), the required SG7 loop with GEI (Processing information), the required SG8 loop with RFF (Reference), the required SG9 loop with EMP (Employment details) and LOC (Place/location identification) and the required SG11 loop with SAL (Remuneration type identification), the required SG12 loop with ATT (Attribute) and the required SG14 loop with MOA (Monetary amount). 7 conditional segment groups are listed by their trigger segment.How the EDIFACT WKGRREmessage worksWork grant request: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeWKGRRESENDEREmployerRECEIVERGovernmentauthority forwork permitsCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYJINFDEJob information demandWKGRDCWork grant decision2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message WKGRRE (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 3PNAParty identificationUNSSection control+ required SG5 (RFF) and 7 conditionalgroups, starting with:CTARFFGEIPNAATTBlue 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 WKGRRE.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends WKGRRE, 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 WKGRRE 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

  • Applying for work permits for foreign hires
  • Renewing work permits
  • Requesting permits for several workers

Where it fits in the message flow

This message WKGRRE Work grant request
Usually followed by JINFDE Job information demandWKGRDC Work grant decision

Structure

Mandatory segments in WKGRRE (directory D.21A)

In UN/EDIFACT directory D.21A, the WKGRRE message has 51 segment positions arranged in 16 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

WKGRRE in practice

An engineering firm recruits two specialists from abroad. Its HR system sends the labor authority a WKGRRE for each with the personal and passport details, the job title, salary, contract period and work location. The authority requests a visa reference with JINFDE and later grants the permits with WKGRDC.

Implementation

Implementation considerations for WKGRRE

  • Follow the authority's requirements and supporting documents.
  • Protect personal and identity data under applicable law.
  • Track requests through information demands to decisions.
  • Plan for processing times before the start date.

How ECOM helps

Automate WKGRRE 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 WKGRRE?

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

Request a Demo Contact us