How to read an 835 ERA file

Start with what the file represents

An 835 is a payer-to-provider payment/advice transaction. An ERA is the electronic remittance advice that explains how claims were processed. It is different from the 837 used to submit a claim, and different from a bank deposit. One remittance can describe more than one claim.

Before you post anything, keep the original file and identify the payer, payee and payment reference. In a raw X12 file, short segment identifiers introduce groups of fields. A viewer makes those fields easier to scan; it does not replace the payer's explanation or your posting controls.

A practical order for reviewing an ERA

1. Identify the payment. Find BPR for payment information and TRN for the trace reference. Match the ERA to the corresponding check or EFT using the reassociation information available from your payer and bank.
2. Match the claim. Use the provider's claim reference and payer claim control number to find the correct account. Confirm service dates before attaching a payment to a balance.
3. Read the claim and its service lines. CLP gives claim-level information; SVC gives service payment information when present. Compare submitted charges with reported payment rather than assuming every claim in the batch was paid in full.
4. Read the adjustments in context. CAS carries adjustment groups, reasons and amounts. Read relevant remark codes too. A zero payment alone does not tell you whether a balance is patient responsibility, a denial, or another adjustment.
5. Check provider-level differences. A PLB adjustment can affect the payment total without belonging to one current claim. Keep it separate from a claim adjustment while you investigate.

CMS describes adjustments at service, claim and provider levels. Its remittance overview is a useful starting point for distinguishing them.

When totals do not look right

First check that you are comparing the same transaction and payment reference. Then look for claim reversals, provider-level adjustments and multiple transactions in the file. Do not force the bank deposit to match a sum of charges: charges and actual payments measure different things.

Build a follow-up note with the claim reference, service date, group/reason combination, remark code and disputed amount. That gives the next reviewer a specific question instead of an unexplained balance.

Practice without a real patient file

Open Visera's viewer and choose Try a sample file. Review its claims, payments and service lines first. The built-in examples are synthetic. If you need a signed agreement before using real remittance data, complete your organization's approval process before opening it in any tool.

For a reference to keep beside a raw file, see BPR, TRN, CLP, CAS, SVC and PLB explained.