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 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.
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
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.
How ECOM helps
Automate the 429 with ECOM
Industry
Trucking and Transportation
Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.
Industry
Healthcare
Secure B2B integration and file transfer for providers, suppliers, distributors and healthcare partners.
Solution
Enterprise Integration
Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.
More general questions about EDI are answered in the EDI FAQ.
Related transactions
Related healthcare and insurance documents
- 111Individual Insurance Policy and Client Information
- 148Report of Injury, Illness or Incident
- 186Insurance Underwriting Requirements Reporting
- 255Underwriting Information Services
- 269Health Care Benefit Coordination Verification
- 270Eligibility, Coverage or Benefit Inquiry
- 271Eligibility, Coverage or Benefit Information
- 274Healthcare Provider Information
- 275Patient Information
- 276Health Care Claim Status Request
- 277Health Care Information Status Notification
- 278Health Care Services Review Information
Need help with the EDI 429?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.