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 · Healthcare and social

SSRECH Worker's insurance history

The UN/EDIFACT message a social security body sends to its counterpart in another state with a worker's insurance history, on request.

Sent by
Designated social security body
Received by
Equivalent body in another state
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT SSRECH message?

SSRECH is the UN/EDIFACT worker's insurance history. The directory defines it as a message sent by a designated body in one state to the equivalent body in another state, giving details of a worker's social security insurance history as requested by that state.

When a worker claims a pension or other benefit, periods of insurance in other countries may count toward entitlement. The insurance history lets the deciding body take those periods into account. Accurate histories avoid gaps in a worker's pension rights.

How the EDIFACT SSRECH message worksDiagram of the UN/EDIFACT SSRECH Worker's insurance history message. Designated social security body sends it to equivalent body in another state. It usually follows SSREGW. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and GEI (Processing information) and body and segment groups: the required SG2 loop with PNA (Party identification), the required SG3 loop with IND (Index details), DTM (Date/time/period) and COT (Contribution details), UNS (Section control) and the required SG5 loop with PNA (Party identification). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT SSRECH message worksWorker's insurance history: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSSSREGWNotification ofregistration of aworkerSSRECHSENDERDesignated socialsecurity bodyRECEIVEREquivalent body inanother stateCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage SSRECHUNH … UNTSTART OF MESSAGEBGMBeginning of messageGEIProcessing informationBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 2PNAParty identificationMandatory group SG3 · repeats up to 99INDIndex detailsDTMDate/time/periodCOTContribution detailsUNSSection controlMandatory group SG5 · repeats up to 6PNAParty identification+ 6 conditional groups, starting with:RFFEMPDTMPDICOTAUTBlue 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 SSRECH. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT SSRECH message worksDiagram of the UN/EDIFACT SSRECH Worker's insurance history message. Designated social security body sends it to equivalent body in another state. It usually follows SSREGW. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and GEI (Processing information) and body and segment groups: the required SG2 loop with PNA (Party identification), the required SG3 loop with IND (Index details), DTM (Date/time/period) and COT (Contribution details), UNS (Section control) and the required SG5 loop with PNA (Party identification). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT SSRECHmessage worksWorker's insurance history: who sends it, whereit fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSSSREGWNotification of registration of aworkerSSRECHSENDERDesignatedsocial securitybodyRECEIVEREquivalent bodyin another stateCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message SSRECH (UNH … UNT)START OF MESSAGEBGMBeginning of messageGEIProcessing informationBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 2PNAParty identificationMandatory group SG3 · repeats upto 99INDIndex detailsDTMDate/time/periodCOTContribution detailsUNSSection control+ required SG5 (PNA) and 6 conditionalgroups, starting with:RFFEMPDTMPDICOTAUTBlue 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 SSRECH.Your trading partner's implementation guide adds itsown requirements.

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

  • Supplying insurance periods for a pension claim
  • Answering requests from foreign social security bodies
  • Supporting coordination of benefits

Where it fits in the message flow

Usually follows SSREGW Notification of registration of a worker
This message SSRECH Worker's insurance history

Structure

Mandatory segments in SSRECH (directory D.21A)

In UN/EDIFACT directory D.21A, the SSRECH message has 31 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
  • GEI
  • SG2 (PNA)
  • SG3 (IND)
  • UNS
  • SG5 (PNA)
  • UNT

Practical example

SSRECH in practice

A retiree who worked in two countries claims a pension. The deciding body requests the insurance history from the other country's body, which sends an SSRECH listing the worker's insured periods and contribution types. The deciding body combines the periods to calculate entitlement.

Implementation

Implementation considerations for SSRECH

  • Follow coordination rules between the states involved.
  • Protect personal data under applicable law.
  • Use agreed codes for insurance period types.
  • Respond within the timescales agreements set.

How ECOM helps

Automate SSRECH with ECOM

Solution

Enterprise Integration

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

Solution

EDI Integration

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

Industry

Healthcare

Secure B2B integration and file transfer for providers, suppliers, distributors and healthcare partners.

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

Related messages

Related healthcare and social messages

All 20 healthcare and social messages

Need help with SSRECH?

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

Request a Demo Contact us