We Make EDI Integration Easy


Below you will essential information in regards to this EDI. If you have any specific questions about integrating your EDI with your ERP and eCommerce please reach out. Take advantage of our "start planning" feature to map out your integration needs. 

Let's Chat Start Planning
 
What is a 834 - Benefit Enrollment and Maintenance document?

The 834 EDI document type is an electronic version of a paper Benefit Enrollment and Maintenance. Standard EDI formats include X12, ANSI, EDIFACT and its subsets. The 834 EDI document type is used to establish communication between the sponsor of an insurance product and the payer. As well, to sign a member up with the payer. The sponsor is the party that pays for the coverage or benefit, and the payer is an entity that pays claims or administers the insurance product, such as an insurance company.

What makes up the 834 - Benefit Enrollment and Maintenance document?

An EDI 834 - Benefit Enrollment and Maintenance document is organized into segment and data elements. A segment can contain at least one data element. Each data element contains a data field. Data elements can include date of transaction, type of insuance plan, premium amount, and coverage details, identical to a paper benefit enrollment. There are an infinite number of possibilities available for a company to include data on an 834 Benefit Enrollment and Maintenance. There are an infinite number of possibilities available for a company to include data on an 834 - Benefit Enrollment and Maintenance.

How is a 834 - Benefit Enrollment and Maintenance used?

The 834 EDI document is sent to a payer by the insurance sponsor. After the 834 Benefit Enrolment and Maintenance is received, a 997 Functional Acknowledgement is sent back from the receiver indicating that the 834 Benefit Enrolment and Maintenance was successfully received.

How is a 834 - Benefit Enrollment and Maintenance processed?

An EDI solution is required to process the EDI documents received into an ERP or accounting system or into a readable format for manual entry. Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed.

eBridge Connections has pre-built maps for all EDI transaction documents including 850 purchase orders, 810 invoices, and 856 advance shipping notices.