The ERA cycle is the loop a dental claim payment travels after the payer finishes adjudication: the plan issues an electronic remittance advice, the 835 file, alongside an electronic funds transfer, your clearinghouse delivers both, the file posts line by line against the claim, the deposit is matched back to the file, and each account closes or moves on to a secondary claim or an appeal. It is the back half of the billing cycle, and it is where money you have already earned either lands in the ledger or quietly does not.
Worth separating two things that get run together. The claim cycle ends when the payer decides. The ERA cycle begins there. The front half, registration through submission, is covered in our step by step guide to the dental billing cycle, and the wider frame sits in what dental revenue cycle management is. This article is about what happens after the money is decided.
One note on the acronym, since it is used for other things in other industries. In dental billing, ERA means electronic remittance advice, specifically the ASC X12N 835 transaction adopted under HIPAA. It is the machine readable twin of the explanation of benefits, and it is what your practice management software actually posts from.
The ERA cycle, stage by stage
Elapsed times below are commonly quoted ranges for clean electronic dental claims, not guarantees. Your payer mix decides your real numbers, and state prompt payment deadlines vary, so confirm yours with your state insurance department.
| Stage | What has to happen | Typical elapsed |
|---|---|---|
| Claim accepted | The acceptance report shows accepted at the payer, not merely sent to the clearinghouse | Day 0 to 2 |
| Adjudication | Benefits applied, no attachment or narrative request left open | Day 1 to 20 |
| 835 generated, EFT released | Both ERA and EFT enrollment complete for that payer | Day 14 to 30 |
| File retrieved | Someone or something pulls the mailbox every business day | Same day the file lands |
| Posted line by line | Every service line has allowed, adjustment, and patient responsibility posted | Same or next business day |
| Reassociated | The trace number in the file matches the trace number on the deposit | Same day as posting |
| Line closed | Secondary billed, statement queued, or underpayment routed to appeal | Within one business day of posting |
Notice that only two of those stages belong to the payer. The other five belong to the practice, and they are where the cycle usually stalls.
The 835 is a file, not a picture
If your team only ever sees a PDF, they are reading a rendering of the file rather than the file itself, and renderings drop detail. Here is what lives inside, and what each piece is actually good for.
| Segment | Plain name | Read it for |
|---|---|---|
| BPR | Financial information | Total paid on this file and how it was sent |
| TRN | Reassociation trace number | The string that has to match your bank deposit |
| CLP | Claim level payment | Total charge, total paid, patient responsibility, claim status |
| SVC | Service line payment | The CDT code, submitted charge, allowed amount, amount paid |
| CAS | Adjustment | A group code, a reason code, and an amount for every dollar not paid |
| PLB | Provider level adjustment | Money added or removed outside any single claim, such as an overpayment recovery |
The CLP claim status code is the one most teams never look at, and it is the fastest way to sort a file. It distinguishes a processed primary payment from a denied claim, from a claim forwarded to another payer, from a reversal of a prior payment. Sorting by that field before posting turns a stack of remittances into three short queues instead of one long one.
Reassociation, or matching the deposit to the file
Reassociation is the unglamorous heart of the ERA cycle. The payer sends money through the banking system and sends the explanation through the clearinghouse. Those two arrive separately, sometimes days apart, and the only reliable thread between them is a trace number: the TRN in the 835 and the corresponding trace on the ACH deposit.
As of this writing, federal operating rules developed by CAQH CORE and adopted under HIPAA require health plans to carry that trace number and to deliver the ERA within a defined window of the payment date, commonly described as three business days. Rules change, so confirm the current requirement with CMS rather than taking a date from an article.
Three practical consequences:
- Enroll for both, separately. ERA enrollment and EFT enrollment are usually different applications with the same payer. Completing one and not the other produces the most common support question in dental billing, which is money in the bank that nobody can post. Enrollment also depends on your provider records being current, which is why credentialing delays ripple into the revenue cycle long after the credentialing itself is finished.
- Expect one deposit to cover several files. Bulk payments are normal. Match on trace numbers, not on dollar amounts, because two files summing to one deposit will never tie out line by line.
- Keep an unmatched queue with a name on it. Not a spreadsheet nobody owns. A queue, reviewed weekly, that should be empty at month end.
Adjustment codes decide who owes the rest
Every dollar of the submitted charge that the plan does not pay comes back with a group code plus a reason code. The group code is the part that decides who absorbs the money.
| Group code | Name | Who absorbs it |
|---|---|---|
| CO | Contractual obligation | The practice, written off under your participating agreement |
| PR | Patient responsibility | The patient, billed after the plan pays |
| PI | Payer initiated reduction | The practice, and worth questioning before you accept it |
| OA | Other adjustment | Neither cleanly, read the reason code before deciding |
An illustrative crown, D2740, makes the split concrete. Figures are made up for the arithmetic.
| Line on the 835 | Amount | Code |
|---|---|---|
| Submitted charge | 1,200 | |
| Allowed amount | 900 | |
| Charge above the allowed amount | 300 | CO-45 |
| Deductible applied | 50 | PR-1 |
| Coinsurance | 425 | PR-2 |
| Plan paid | 425 |
The write off is 300. The patient owes 475. Post that file as a 425 payment and a 775 adjustment, which is exactly what happens when a posting shortcut lumps every unpaid dollar into one write off bucket, and 475 of collectible balance disappears without a trace. It is the single most expensive mistake in the ERA cycle because nothing about it looks wrong. The ledger balances. The claim shows closed.
The related habit worth building is comparing PR amounts against what you quoted the patient at treatment presentation. A pattern of PR lines larger than your estimates points back at the verification step, not at posting. Our piece on patient verification in dental revenue cycle management covers what has to be captured up front to make the estimate hold.
Where the ERA cycle stalls
Four failure modes account for most of it.
The file lands and nobody fetches it. Clearinghouse mailboxes accumulate silently. If retrieval is a person's task rather than an automatic pull, it stops the week that person is out.
Zero dollar files get skipped. A file with no payment attached still carries denials, and denials carry deadlines. Appeal windows are commonly 90 to 180 days from the remittance date depending on the payer contract and state rules, and they run from the date on that file, not from the date somebody noticed it.
Provider level adjustments post as a mystery shortage. A PLB segment can recover an overpayment from an unrelated claim, forward a balance to a future payment, or add interest. If your deposit is short by an odd amount and no claim explains it, read the PLB before assuming a payer error. Each entry names a reason and, for recoveries, usually the original claim.
Reversals get posted as new payments. When a payer corrects a prior adjudication, the file may back out the original payment and reissue it. Posted as two positive payments, the patient ledger doubles a credit that never existed.
Three numbers that show whether your ERA cycle is healthy
Pull these for last month before you change anything.
| Measure | How to calculate it | What good looks like |
|---|---|---|
| Posting lag | Days between the payment date on the file and the posting date in your ledger | One business day or less |
| Unreassociated deposits | Dollars received with no matched remittance at month end | Zero, and no aged items |
| Electronic share | Remittance dollars arriving as an 835 divided by total remittance dollars | Rising quarter over quarter, driven by enrollment |
If posting lag is fine but patient balances are aging, the problem is the handoff after posting rather than posting itself. If the electronic share is low, the fix is enrollment paperwork, not software. A broader pass on where the leaks are sitting is laid out in how to audit your dental practice revenue cycle, and the cash flow arithmetic behind shortening these stages is in how revenue cycle software accelerates cash flow.
Curo posts 835 files against the original claim, compares each allowed amount to the contracted rate you actually signed, and flags the lines that came in short instead of writing them off, which is the part of EOB and ERA reconciliation that manual posting tends to skip.
Whatever you use to do it, the test of an ERA cycle is not how fast payments post. It is whether anyone can say, on any given Friday, which dollars arrived this week, which claim each one belongs to, and what is left on the line after the plan is done. If that question takes more than a few minutes to answer, the cycle is not closed. It is just quiet.