EDI 820 Payment Order & Remittance Advice
What is the EDI 820 Transaction Set?
The EDI 820 transaction set specified under HIPAA 5010 establishes the format and data contents of the Payment Order/Remittance Advice for transmitting information electronically relating to payments. HIPAA 820 is used to pay by plan sponsors for insurance products, individual and group premiums, or to forward remittance advice, or both.
The 820 may be a payment order directing payment to a health plan. Payment reference information is communicated to enable the health plan’s system to match up the payment with coverages kept in force. Payments are frequently made in aggregate to cover several subscribers in a group policy. As electronic remittance advice, the 820 explains payment and partial payment.
In healthcare, the 820 is similar to the EDI 835 transaction set. The 820 is specifically for plan sponsors – that is, companies providing healthcare benefits to their employees – to transmit information on premium payments to the health plans. The 835 is used by health plans for transmitting information on payments to healthcare providers.
The EDI 820 A1 transaction set can be used to make a payment, send remittance advice, or make a payment and send remittance advice. The information provided in an 820 document is payer and payee identification, bank and account IDs, invoice number(s), adjustments from an invoice, billed and paid amounts. This information allows suppliers and health plans to reconcile payments they receive against invoices they have issued.
It can also be a remittance advice identifying the detail needed to perform cash application to the payee’s accounts receivable system. The remittance advice can go directly from payer to payee, through a financial institution, or through a third party agent.
EDI 820 Payment Order in Data Mapper
(Click to enlarge)
EDI 820 Frequently Asked Questions
While the EDI 820 is used by plan sponsors to transmit premium payments to health plans, the EDI 835 is used by health plans to communicate payment details to healthcare providers. PilotFish’s platform supports both transaction sets, optimizing financial data workflows across the healthcare ecosystem.
Yes, PilotFish’s integration engine is fully configurable, allowing it to map, transform and validate various EDI 820 formats and versions to meet the specific requirements of different health plans and financial institutions.
Yes, PilotFish’s platform can automate the reconciliation process by parsing EDI 820 remittance advice, identifying payment details, and automatically applying them to accounts receivable systems, improving payment accuracy and efficiency. Check out this Revenue Cycle Management solution case study.
Common challenges include handling diverse data formats, managing large volumes of transactions, and ensuring compliance with HIPAA. PilotFish’s integration platform simplifies these challenges by providing advanced mapping, error handling, and validation for smooth EDI 820 transaction processing.
PilotFish’s platform ensures secure and reliable transmission of EDI 820 data through financial institutions or third-party agents (TPAs) using industry-standard encryption protocols and secure FTP, ensuring that sensitive payment information is protected.
Check out our EDI FAQ pages for more.
EDI 820 A1 Format Example
Different Types of Payment Made by the HIX
ASC X12 Version: 005010 | Transaction Set: 820 | TR3 ID: 005010X306
This scenario demonstrates several different types of payments that will be made by the HIX. The total payment is for $220. The example demonstrates: advance payment of the premium tax credit (APTC), retroactive APTC reduction, and cost-sharing reduction payments. For this example, there is only one QHP for this transaction, therefore, we reported QHP identifiers in the header for simplicity and the example is for the Individual Market.
Transmission Explanation
Table 1
| ST*820*0001*005010X306~ | Beginning of an 820 transaction set, Control number = 0001 |
| BPR*I*220*C*ACH*CCP*******01* 199999999*DA*98765*20140604~ | Total Payment Amount is $220. The payee’s bank transit routing number is 199999999 and their bank account is 98765. The Check Issue or EFT effective date is June 4, 2014. |
| TRN*3*78905~ | Reassociation Key provides a sender unique Check or EFT trace number “78905”. |
| REF*38*123456~ | The Exchanged assigned QHP Identifier is 123456. |
| REF*TV*12565496~ | The Issuer assigned QHP identifier is 12565496. |
| N1*PE*BATA INSURANCE CO.*FI*012222222~ | The payee’s name (BATA INSURANCE CO.) and Federal Tax ID number (012222222). |
| N1*RM*GOVERNMENT AGENCY*58*123ABC~ | The payer’s name is Government Agency with an identifier of 123ABC. |
Table 2
| ENT*1~ | Start of detail loop for first detailed payment record. |
| NM1*IL*1*DOE*JOHN****C1*777222~ | The subscriber’s name (JOHN DOE) and Exchange Assigned Subscriber Number is 777222. |
| REF*POL*1232456~ | The Exchange Assigned Policy Identifier is 12565456. |
| REF*AZ*12565496~ | The Issuer Assigned Policy Identifier is 12565496. |
| REF*0F*555666~ | The issuer assigned identifier (555666) for subscriber JOHN DOE. |
| RMR*ZZ*APTC**35~ | Identification Qualifier ZZ = Exchange Payment Type RMR02 refers to a code list published and maintained by CMS representing the payment types. The July 8, 2014 draft version of the Payment Type Codes are used for the purposes of this exercise, APTC = Advance payment of the Premium Tax Credit (APTC) Payment. The APTC amount being paid for this individual is $35. |
| DTM*582****RD8*20120501-20140531~ | This DTM demonstrates the specified date range for which the APTC payment amount applies. |
| ENT*2~ | Start of detail loop for second detailed payment record. |
| NM1*IL*1*FIRSTONE*EMILY****C1*777333~ | The subscriber’s name (EMILY FIRSTONE) and exchange assigned identification number (777333). |
| REF*POL*1232457~ | The Exchange Assigned Policy Identifier is 12565457. |
| REF*AZ*12565497~ | The Issuer Assigned Policy Identifier is 12565497. |
| REF*0F*555777~ | The issuer assigned identifier (555666) for subscriber EMILY FIRSTONE. |
| RMR*ZZ*APTC**35~ | Identification Qualifier ZZ = Exchange Payment Type RMR02 refers to a code list published and maintained by CMS representing the payment types. The July 8, 2014 draft version of the Payment Type Codes are used for the purposes of this exercise, APTC = Advance payment of the Premium Tax Credit (APTC) Payment. The APTC amount being paid for this individual is $35. |
| DTM*582****RD8*20120501-20140531~ | This DTM demonstrates the specified date range for which the APTC payment amount applies. |
| ENT*3~ | Start of detail loop for the third detailed payment record. |
| NM1*IL*1*MIDDLEONE*JULIE****C1*777444~ | The subscriber’s name (Julie Middleone) and exchange assigned identification number (777444). |
| REF*POL*1232458~ | The Exchange Assigned Policy Identifier is 12565458. |
| REF*AZ*12565498~ | The Issuer Assigned Policy Identifier is 12565498. |
| REF*0F*544477~ | The issuer assigned identifier (544477) for subscriber JULIE MIDDLEONE. |
| RMR*ZZ*APTC**-350~ | RMR02 refers to a code list published and maintained by CMS representing the payment types. The July 8, 2014 draft version of the Payment Type Codes are used for the purposes of this exercise, APTC = Advance payment of the Premium Tax Credit (APTC) Payment. The APTC amount being paid for this individual is $-350. Because this is a negative amount, it reduces the overall BPR02 payment and represents a recovery or retroactive reduction in the individual’s APTC amount. |
| DTM*582****RD8*20140101-20140331~ | This DTM demonstrates the recovered APTC amounts apply to the time period ranging from 1/1/2014 thru 3/31/2014. This date supersedes the effective dates reported at the header level. |
| ENT*4~ | Start of detail loop for the fourth detailed payment record. |
| NM1*IL*1*NEWONE*KELLY****C1*777111~ | The individual’s name (KELLY NEWONE) and exchange assigned identification number (777111). NOTE: The REF containing the Issuer Assigned Identifier is not present because the payer does not have the identifier available. The exchange assigned identifier is the only identifier received in this instance. |
| REF*POL*1232459~ | The Exchange Assigned Policy Identifier is 12565459. |
| REF*AZ*12565499~ | The Issuer Assigned Policy Identifier is 12565499. |
| RMR*ZZ*APTC**450~ | RMR02 refers to a code list published and maintained by CMS representing the payment types. The July 8, 2014 draft version of the Payment Type Codes are used for the purposes of this exercise, APTC = Advance payment of the Premium Tax Credit (APTC) Payment. The APTC amount being paid for this individual is $450. |
| DTM*582****RD8*20140501-20140531~ | This DTM demonstrates the specified date range for which the APTC payment amount applies. |
| RMR*ZZ*CSR**50~ | RMR02 refers to a code list published and maintained by CMS representing the payment types. The July 8, 2014 draft version of the Payment Type Codes are used for the purposes of this exercise, CSR = Cost-Sharing Reduction (CSR) Payment. The amount being paid for this individual is $50. |
| DTM*582****RD8*20140501-20140531~ | This DTM demonstrates the specified date range for which the CSR payment amount applies. |
Table 3
| SE*37*0001~ | Transaction Set Trailer with segment count (37) and Control Number (0001). |
Source
Accredited Standards Committee X12. ASC X12 Standard [Table Data]. Data Interchange Standards Association, Inc., McLean, VA. ASC X12 Examples
X12, chartered by the American National Standards Institute for more than 35 years, develops and maintains EDI standards and XML schemas.