ERA 835 processing is how a practice turns a payer's electronic remittance advice into posted payments. The 835 file lists each claim, each service line and every adjustment behind one payment. Software reads it, matches it to the deposit, posts the lines that balance, and leaves the odd ones, such as reversals and provider-level offsets, for a person.
What is an 835 remittance file?
An 835 remittance file is the electronic version of an explanation of benefits. A health plan sends it after it decides a batch of claims, and it explains one check or electronic funds transfer (EFT) line by line. The name comes from the X12 transaction number, 835, used for health care claim payment and advice.
The CMS page on health care payment and remittance advice says the electronic remittance advice (ERA) uses the X12 835 version 5010 format, which is the national HIPAA standard. It also says one ERA usually covers many claims and that one check or EFT is issued for the benefits it lists. A single file can therefore hold dozens of patients.
The file arrives electronically, either straight from the payer or through a clearinghouse or billing service that receives it for the practice. It is not meant to be read by eye. The CMS Medicare Claims Processing Manual, Chapter 22 calls the 835 a variable-length record designed for wire transmission that is not suitable for use in application programs, so receiving systems convert it before staff see it.
Medicare offers free viewers for that job. The CMS MLN booklet Remittance Advice Resources and FAQs names PC-Print for institutional providers and Medicare Remit Easy Print (MREP) for professional providers. Commercial practice management systems do the same work inside the posting screen.
The paper EOB and the ERA carry much of the same information but differ in delivery, codes and how they match a deposit. The comparison of EOB vs ERA 835 format, delivery, codes and matching covers those differences in a side-by-side table.
835 segments a payment poster should recognize
An 835 segment is one line of the file, starting with a short tag and holding data elements separated by asterisks. Six tags explain most posting questions: BPR for the payment, TRN for the trace number, CLP for each claim, SVC for each service line, CAS for adjustments and PLB for provider-level adjustments.
An annotated 835 excerpt
The excerpt below is fictional. The payer, clinic, patient, member ID, claim numbers and amounts are all made up for this example, and the envelope segments that wrap a real file are left out.
BPR*I*111*C*ACH*CCP*01*999999999*DA*123456*1512345678**01*888888888*DA*98765*20261012~
TRN*1*EFT20261012A*1512345678~
N1*PR*EXAMPLE HEALTH PLAN~
N1*PE*EXAMPLE FAMILY CLINIC*XX*1999999999~
LX*1~
CLP*PCN10045*1*300*136*34*12*EX7788123~
NM1*QC*1*SAMPLE*JANE****MI*XEM123456789~
SVC*HC:99214*200*112~
DTM*472*20260915~
CAS*CO*45*60~
CAS*PR*2*28~
SVC*HC:36415*100*24~
DTM*472*20260915~
CAS*CO*45*70~
CAS*PR*2*6~
CLP*PCN10046*4*150*0*0*12*EX7788124~
NM1*QC*1*EXAMPLE*SAM****MI*XEM987654321~
SVC*HC:97110*150*0~
DTM*472*20260918~
CAS*CO*197*150~
PLB*1999999999*20261231*WO:PCN09870EX6655001*25~
Read it segment by segment:
| Segment | Example value | What it tells the poster |
|---|---|---|
| BPR | 111, ACH, 20261012 | The payment: $111.00 sent by ACH transfer, dated October 12, 2026 |
| TRN | EFT20261012A | The trace number that ties this file to the bank deposit |
| N1PR / N1PE | Example Health Plan, Example Family Clinic | Who paid and who was paid |
| CLP | PCN10045, 300, 136, 34, EX7788123 | Claim one: your patient control number, $300 billed, $136 paid, $34 patient share, the payer's claim number |
| NM1*QC | Sample, Jane, XEM123456789 | The patient and member ID on that claim |
| SVC | HC:99214, 200, 112 | A service line: procedure code, billed amount, paid amount |
| DTM*472 | 20260915 | The date of service for the line |
| CAS | CO 45 60; PR 2 28 | Adjustments: group code, reason code, amount |
| PLB | WO, 25 | A provider-level deduction of $25.00 not tied to any claim in this file |
The lines balance. On the first service line, $200 billed minus $60 under CO-45 and $28 under PR-2 leaves $112 paid. The X12 Claim Adjustment Reason Codes list defines CO as contractual obligation, PR as patient responsibility, 45 as a charge that exceeds the fee schedule or contracted arrangement, 2 as a coinsurance amount, and 197 as precertification or authorization absent.
The payment balances too. The MLN booklet states that the check amount in BPR02 is the sum of all claim-level payments, less any provider-level adjustments in the PLB segment. Here, $136 plus $0 minus $25 equals the $111 in BPR.
Two more facts help when reading real files. CMS Chapter 22 says remark codes for a service line go in an LQ segment, and remark codes for a whole claim go in an MOA or MIA segment. The X12 sample file for multiple claims on a single check shows the same CLP, SVC and CAS pattern across nine claims, if you want a longer example to study.
ERA 835 processing steps: enrollment, receipt, auto-post, exceptions
ERA 835 processing runs in four stages. The practice enrolls with each payer to receive ERAs and EFTs, receives the file and the deposit, lets software post the lines that balance, and works the exceptions by hand. That sequence is the core of remittance processing in healthcare.
Enrollment
Enrollment is done payer by payer. The CMS fact sheet on EFT and ERA payment remittance reassociation basics says a provider must enroll with each health plan it bills to conduct EFT and ERA transactions. For Medicare, the MLN booklet points to each Medicare Administrative Contractor's website for directions, and notes that ERA becomes effective the day you sign up, with no access to remittances issued before that date.
Enrollment also decides who receives the file. A clearinghouse or billing service can receive ERAs on the practice's behalf. The MLN booklet warns that an entity receiving the 835 for you may not regularly pass along the remark codes that explain adjustments, so it is worth checking what your clearinghouse forwards.
Receipt
Receipt means two things arrive: the 835 file and the money. They travel separately and often on different days. The CMS reassociation fact sheet describes a CAQH CORE operating rule that requires health plans to release the ERA no sooner than three business days before the EFT's effective entry date and no later than three business days after it.
Auto-post
Auto-posting is the step where the practice management system reads each CLP and SVC line, finds the matching claim by patient control number, and records the payment, the adjustments and the patient share. The MLN booklet notes that ERA amounts can be posted automatically to accounting or billing applications, which removes the manual keying a paper remittance needs.
Exceptions
Exceptions are the lines the software cannot match or should not post on its own. A good exception queue shows the line, the reason it stopped and the claim it probably belongs to. The last section of this post lists the lines worth holding back.
The manual side of this work, line by line, is set out in the guide to EOB payment posting, step by step. The same entries apply whether the numbers come from paper or from an 835.
PLB provider level adjustments on an 835
PLB provider level adjustments on an 835 are amounts that change the payment without belonging to any one claim in the file. They sit in the PLB segment near the end of the remittance. Because the check equals claim payments minus PLB amounts, a PLB entry is the usual reason a deposit differs from the sum of the claims.
The MLN booklet gives three examples of provider-level adjustments: an increase for interest due on a late-paid clean claim, a deduction to recover a prior overpayment, and an increase for a provider incentive plan. CMS Chapter 22 says every provider-level adjustment must be reported in the provider-level adjustment section of the remittance.
The sign of a PLB amount matters. The MLN booklet states that positive adjustments reduce the payment and negative adjustments increase it. In the excerpt above, the PLB amount of 25 is positive, so it took $25.00 off the deposit. An interest payment would appear as a negative PLB amount and would add to the deposit.
Each PLB entry carries a reason code and a reference. The code says what kind of adjustment it is. The reference says what it relates to. An X12 interpretation on PLB reference IDs for overpayment recovery explains that code WO is used for overpayment recovery, and that the reference should carry the payer's claim number from CLP07. The same interpretation recommends adding your claim ID from CLP01 and the TRN02 trace number, in that order.
For a poster, the practical rule is short. Do not force a PLB amount onto a patient account just to make the batch balance. Post it to the account or ledger your practice uses for provider-level items, note the reference, and use that reference to find the claim it came from.
How PLB amounts affect matching a deposit to its remittance is covered in the guide to how to reconcile EFT payments with EOBs, which works through a mismatch on a reconciliation worksheet.
How do recoupments and takebacks appear on remittances?
Recoupments and takebacks on remittances are money a payer takes back from an earlier payment. They appear in one of two ways: as a reversal of the original claim with negative amounts, or as a PLB deduction that offsets the takeback against today's payment. Many takebacks use both, with the reversal explaining the claim and the PLB settling the cash.
Reversal claims
A reversal repeats the original claim with negative amounts. The MLN booklet describes claim status 22 as a reversal of previous payment, and says the reversed claim shows the negative amount that cancels the original. The payer then usually sends a corrected claim with the new amounts. Posting both entries leaves the account showing the net result.
CMS Chapter 22 adds a detail that trips up posters. Medicare does not issue a remittance for a voided or cancelled claim. It issues one for the adjusted claim, with the amount previously paid shown so the difference is clear.
Offsets in the PLB
An offset recovers money without a matching claim payment in the same file. Suppose the payer decides it overpaid an earlier claim by $25.00. It may report a PLB entry with code WO and a reference to that earlier claim, as in the fictional excerpt. The deposit shrinks by $25.00, and none of today's claims explains why.
Tying the takeback to the original claim
The reference in the PLB is the link back. Search your system for the payer claim number or the patient control number in the reference. Once found, post the recovery against the original claim so its balance reopens, then decide whether the takeback is correct. A takeback you disagree with is a follow-up item, not a write-off.
A denied line in a reversal and corrected claim needs the same care as any other denial. The guide on how to post a denied line from an EOB covers when to record a zero payment, adjust or transfer.
ERA 835 lines that auto-post wrong: exceptions to route to a person
ERA 835 lines that auto-post wrong share one trait: the numbers balance, but the meaning needs a judgment the posting rules cannot make. These lines should stop in an exception queue instead of posting. A short list covers most of them, and each one is cheap to hold and expensive to unwind after it posts.
| Exception | Why it posts wrong | What a person checks |
|---|---|---|
| Reversal (status 22) with no corrected claim in the file | The account goes negative until the correction arrives | Whether the correction is in a later file |
| PLB deduction with a reference to an unknown claim | The offset lands on no account | The original claim, by payer claim number |
| Claim that does not match a patient control number | Software guesses or skips it | Name, member ID and date of service |
| Line denied with a contractual group code | An automatic write-off can lose recoverable revenue | Whether the denial can be corrected and rebilled |
| Paid procedure code differs from the billed code | The line posts against the wrong charge | Both codes on the line |
| Patient responsibility on a claim already paid at the front desk | The patient may be billed twice | The patient ledger |
The procedure code case has a source behind it. The MLN booklet says that when the contractor pays on a procedure code different from the one submitted, both codes appear in the 835. Software that reads only the first one can post the payment to a charge that does not exist.
Denied lines deserve their own rule. A denial with a CO group code looks like a write-off to a posting engine, because CMS Chapter 22 describes CO adjustments as generally a write-off for the provider. Some of those denials, such as a missing authorization or a billing error, can be fixed and resubmitted. Holding them for review protects that revenue.
Not every practice receives an 835 from every payer. Paper EOBs still arrive for smaller plans, and someone keys them. Schema Care reads paper EOB service lines, allowed amounts, plan payments and remark codes into structured fields, and sends the ones it is unsure of to a reviewer who sees each field on the original page; the human review workflow shows how. It does not create 835 files.
For teams that want to look at an 835 outside the posting system, the guide to 835 spreadsheet columns with one row per service line shows a layout that keeps adjustments with their lines. Parsing X12 files in code, loop structure and file specifications belong to the developer integration category.