X12 transaction guide · Healthcare and insurance

EDI 429 Railroad Retirement Activity

The X12 document used to transmit information on processing railroad employees' sickness and unemployment benefit claims against retirement funds.

Sent by
Railroad employer or benefits administrator
Received by
Railroad retirement benefits authority
Standard
ANSI ASC X12

What is an EDI 429?

The EDI 429 Railroad Retirement Activity is the ANSI X12 transaction set that lets the sender transmit information about the processing of railroad employees' sickness and unemployment benefit claims against retirement funds.

In the United States, railroad workers are covered by a separate federal system for retirement, unemployment and sickness benefits. Employers and the benefits authority exchange information about claims, such as employment and earnings details, so claims can be verified and paid. Exchanges follow the authority's own requirements and timescales.

How the EDI 429 worksDiagram of the EDI 429 Railroad Retirement Activity. Railroad employer or benefits administrator sends it to railroad retirement benefits authority. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the . 1 optional loops are listed by their first segment.How the EDI 429 worksRailroad Retirement Activity: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 429SENDERRailroad employer orbenefits administratorRECEIVERRailroad retirementbenefits authority997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code RUGS … GETransaction set 429ST … SEHEADING+ 1 optional loop, starting with:RU2Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 429. Your trading partner's implementation guide adds its own requirements.
How the EDI 429 worksDiagram of the EDI 429 Railroad Retirement Activity. Railroad employer or benefits administrator sends it to railroad retirement benefits authority. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the . 1 optional loops are listed by their first segment.How the EDI 429 worksRailroad Retirement Activity: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 429SENDERRailroademployer orbenefitsadministratorRECEIVERRailroadretirementbenefitsauthority997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code RU (GS … GE)Transaction set 429 (ST … SE)HEADING+ 1 optional loop, starting with:RU2Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 429. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 429, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 429 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Supplying employer information for benefit claims
  • Reporting claim processing activity
  • Verifying employment and earnings for claims

Where it fits in the document flow

This document 429 Railroad Retirement Activity
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 429 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • RU2
  • SE

Practical example

The 429 in practice

A railroad employee files a sickness benefit claim. The benefits authority needs to confirm the employee's last day worked and earnings. The railroad's HR system supplies the information in a 429, and the authority processes the claim without paper forms.

Implementation

Implementation considerations for the 429

  • Protect employees' personal and health data.
  • Follow the authority's implementation requirements.
  • Respond within the timescales the authority sets.
  • Reconcile reported data with payroll records.

Need help with the EDI 429?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.