EDI Essentials: 10 Common Codes You’ll Use in HCM

CINTAP EDI Essentials Human Capital Management

Electronic Data Interchange (EDI)

What exactly is Electronic Data Interchange (EDI)

It’s how companies communicate and share documents with each other in the modern world (business-to-business). EDI automates communication and business workflows- resulting in streamlined processes for your company.  

Electronic Data Interchange allows for processing bulk amounts of transactions very quickly. In the digital age, nearly every company in any industry needs a reliable EDI platform. 

Ideally, Electronic Data Interchange 

  • saves companies man-hours and money 
  • practically eliminates the time it takes to share information, and  
  • results in greater security and fewer errors overall.  


EDI Essentials: 8 Common Codes for Warehouse Management   
EDI Essentials: 9 Common Codes You Need for Order-to-Cash 
EDI Essentials: 10 Common Codes 3PLs Need to Know
EDI Essentials: 6 Common Codes in Transportation 
EDI Essentials: 12 Codes Used in Procure-to-Pay 
EDI Essentials: 9 Common Financial EDI Codes
EDI Essentials: 12 Common Codes for Wholesale
EDI Essentials: 10 Common Manufacturing Codes 
Read CINTAP’s entire EDI Essentials series!

EDI codes for Human Capital Management

Human Capital Management (HCM) is all the organizational tools needed for managing a workforce. Whether these processes and applications are focused on hiring, managing, training, or providing other human resources benefits, HCM is a part of every successful enterprise. 

EDI makes it possible for these HCM processes to be more organized, more secure, and more efficient. 

11 of the most common Electric Data Interchange transaction codes for HCM are: 

  • 1. EDI 810 – Invoice  
  • 2. EDI 812 – Credit/Debit Advice  
  • 3. EDI 821 – Financial Information Reporting  
  • 4. EDI 832 – Price/Sales Catalog  
  • 5. EDI 834 – Benefit Enrollment and Maintenance  
  • 6. EDI 837 – Health Care Claim  
  • 7. EDI 850 – Purchase Order  
  • 8. EDI 855 – Purchase Order Acknowledgment  
  • 9. EDI 860 – Purchase Order Change Request  
  • 10 EDI 997 – Functional Acknowledgment 
  • Bonus Code! 

(Note: for a complete list of transaction codes, visit https://www.edistaffing.com/resources/edi-transaction-glossary/#supplychain)  

Woman in a work meeting turning and smiling

1. EDI 810- Invoice 

EDI 810 is a document sent to a buyer from a seller. Just like all invoices, sellers send EDI 810 to notify buyers of the balance due and ask for payment. This invoice can also be used for several order types across industries. 

As an invoice, EDI 810 includes the invoice number and date, order details, all charges and the total balance due. It may also include payment methods accepted, payment terms, and possibly tax details. 

Like other EDI documents, EDI 810 ensures data security, and nearly-instant communication without errors. As a bonus, sending an electronic invoice may result in sellers getting paid faster. 

2. EDI 812 – Credit/Debit Adjustment

EDI 812 is an EDI transaction buyers use to note payments adjustments. If there were any changes made, this transaction set securely reconciles invoices and payments. 

Since EDI 812 may accompany an EDI 810 Invoice, it needs to elaborate on the total adjustment amounts, item quantities and descriptions (such as SKUs and UPCs), any necessary chargeback codes, and of course the original invoice number. 

All parties benefit from using this EDI transaction set versus a paper or hard-copy memo with the same information. Changes can be made much more quickly, without risking clumsy typos. Additionally, using EDI provides extra security and peace of mind. By tracking adjustments in this way, the paper trail is much easier to follow. 

3. EDI 821 – Financial Information Reporting

EDI 821 is an EDI transaction set shares financial details and data about a person or business with a lender or banking institution. 

An EDI 821 is used to obtain loans, financial partnerships, or to make trade decisions regarding large financial assets. Data shared in this transaction could include a person or company’s income, expenses, assets, and liabilities. In response, you can expect to receive an EDI 997 (see below). 

EDI documents and transactions require specific data, and ensure high levels of encryption and data security. Financial documents arguably need even MORE specificity and security. By sharing this highly sensitive financial report via EDI, companies and banking institutions are protecting themselves against outside attacks, accidental leaks, and wasted time.

4. EDI 832 – Price/Sales Catalog

EDI 832 is sent by manufacturers or suppliers to their trading partners. This EDI transaction shares the most recent product details and prices. Because this essential EDI needs to be sent out a few times a year, it may not be part of the regular P2P process, but it is still an EDI.   

To give their customers as much information as possible, EDI 832 shares the catalog number/date, supplier data, product SKU or UPCs, product descriptions, per unit prices and minimum order amounts, and any ongoing promotions.  

As an electronic document, EDI 832 saves time and physical resources by being updated automatically, without re-publishing paper copies. Updating catalogs in this way also cuts down the amount of human error that would normally come with updating an entire catalog. And of course, like all EDI transactions, there is also the benefit of added encryption and security.

5. EDI 834 – Benefit Enrollment and Maintenance

EDI 834 is a transaction set used by employers to enroll or disenroll their employees in a healthcare plan. 

There are several instances where EDI 834 might be used, such as a new enrollment, changes to enrollment, and termination of enrollment. Information shared in this document may include employee name and identification, plan network ID, benefit information, and service details. 

The security and automation that comes from using EDI is a significant benefit for employers. Enrollment information can potentially be shared between employers and healthcare insurers via fax or directly inputting into an insurer’s system. However, as with other EDI transactions, all parties can be assured of data security. 

11 professional teammates standing in a tight circle with hands in, as seen from directly above

6. EDI 837 – Health Care Claim

EDI 837 is an EDI document used for HIPAA compliant healthcare claims, and is usually sent from a healthcare provider to an insurer.  

There are 3 subtypes of EDI 837 (outpatient, institutional, and dental), but required information remains standard. Data shared in this EDI document includes patient information and details, the reason for the visit, and overview of services rendered, and overall treatment cost. 

Processing claims submitted by mail or phone is extremely time consuming, while EDI speeds up the claims process with several added layers of security (a valuable benefit for HIPAA compliant documents). 

7. EDI 850 – Purchase Order  

EDI 850 contains all relevant details about a purchase order. In most cases, this transaction set (the first step in the ordering process) is usually sent to a vendor. 

Conveniently, EDI 850 can have details for a single order, recurring orders, or a changed order. As an electronic purchase order, EDI 850 outlines the Purchase Order number, order date, and vendor details. Also included are the shipping and delivery details, pricing and billing information, item descriptions and identifiers, and payment terms. 

When using an EDI, all communications are secure against outside threats. In addition to this added layer of security, EDI transactions streamline operations between partners, sharing and updating information almost instantly.  

8. EDI 855 – Acknowledgement

EDI 855 is a document typically sent in response to EDI 850 (perhaps in conjunction with EDI 997). A seller responds to a buyer’s purchase order to trigger the forward motion of the order processing workflow. 

The EDI 855 transaction set includes extremely detailed information for new orders. These details outline the EDI 850, seller’s vendor number, and any changes in the order or errors that need to be noted.   

Some key perks of EDI 855 are the security that comes from encrypted communication, real-time updates for all parties, and seamless transactions. All parties benefit from near-instant updates regarding order changes. 

9. EDI 860 – Purchase Order Change Request 

EDI 860 is an EDI document sent to a seller from a buyer regarding changes to EDI 850. 

Information included in EDI 860 outlines the PO number, buyer/seller details, and product descriptions. Additionally, EDI 860 includes changes in price, changes in product quantity or type, changes for an expected delivery date, and a brief explanation for all of these changes. 

By using EDI 860, communications between trading partners happen almost instantly. When all parties are aware of updates in shipments, trade is streamlined with less hiccups in the whole process. And as usual, all communication is more secure than with other communication methods.

10. EDI 997 – Functional Acknowledgement

EDI 997 is the EDI transaction set communicating to trading partners that another EDI document has been received. This document can be fully automated, and is sent back as a sort of sophisticated notification system. 

As a rather straightforward document, EDI 997 lists the received transaction code and a notification of whether the received transaction was accepted, rejected, or had errors. If there were errors, the transaction may still be accepted, but EDI 997 may elaborate on any errors made. When a company send out an EDI transaction, they will then automatically receive an EDI 997 to review. 

Acting as a kind of insurance, or audit, EDI 997 keeps all parties in the loop. By creating an electronic paper trail of sorts, any orders, invoices, payments, or changes made are easy to track. And if there are any errors, EDI 997 allows for corrections to be made before the final transaction is sent to the recipient. 

Four professional office employees wearing blue suits, standing with arms crossed while smiling

11. Bonus Code! 

If you didn’t see the transaction type your company needs for your 3PLs, good news! 

It’s possible for you to work with an integration platform to customize your own transaction type specific to your system, needs, and trading partners. 


An Integration Solution for HCM

CINTAP Cloud users don’t have to be limited to a rigid set of transaction types.  

No matter your industry, CINTAP is dedicated to walking each customer through solutions to every problem. And naturally, this includes creating customized transaction types for you, so you can get back the time and resources your company needs!  

As an integration platform, CINTAP streamlines EDI and business workflows. With CINTAP Cloud you can:   

  • accelerate your integration projects  
  • eliminate any redundancies 
  • simplify complex processes  
  • and provide real-time insights, so you (and your partners) have better tracking and visibility. 

All this while also offering huge savings compared to other providers in the iPaaS industry!

Start optimizing today: 

Get CINTAP Cloud as your solution for HCM!  

You can learn more about us or get in contact with us to start optimizing your 3PL transactions right away!

Optimize your HCM on CINTAP Cloud.

Author – Carissa Getscher

Related Posts

How onboarding can make or break your company CINTAP Cloud
How Onboarding Can Make Or Break Your Company
Onboarding is a top feature users look for.....
Could simplifying your order to cash really be this easy
Could Simplifying Your Order-to-Cash Really Be This Easy?
Yes: it's really that easy, thanks to CINTAP....
What was missing from iPaaS until now CINTAP Cloud
What Was Missing From iPaaS [Until Now]
What was integration lacking? And how did CINTAP....
Play Video