Payment Posting Services for ERA, EOB, and 835 Remittances
Payment posting matches the payer remittance to each claim line: paid amount, contractual write-off, patient responsibility, denial codes, and takebacks. If the books do not match the remittance, A/R is wrong. Vector Medical Billing posts inside your EHR from Jamaica, NY, for all 50 states.
What payment posting is in medical billing
Posting records what the payer paid, what was written off under the contract, and what the patient owes — line by line, with the reason codes that explain the gap.
Claims submission ends when the payer accepts the claim into adjudication. Posting starts when the remittance returns. Denials that land on the ERA route to denial management — they are not closed by writing them off as contractual. Short pays below the contracted allowed amount feed underpayment recovery.
Wrong posting corrupts the patient ledger, overstates revenue, and hides denials. Correct posting is mostly automatic on clean 835s; incorrect posting is what makes month-end A/R look invented.
Line-level posting vs claim-level posting
This distinction is the whole argument for doing the job carefully.
Claim-level posting
Collapses a whole claim into one payment figure. A denied line, a bundled line, and a short-paid line disappear into a single number. Denial management and patient billing cannot see what to work.
Line-level posting
Records payment, contractual adjustment, patient responsibility, and CARC/RARC for each service line. Denials stay visible. Underpayments stay measurable against the contract. That is how Vector posts.
ERA, EOB, and the 835 — three different things
Offices mix the words. The ledger cannot.
ERA (provider remittance)
The provider-facing remittance that explains how each claim and line was adjudicated — paid, adjusted, denied, or reversed.
EOB (patient notice)
The patient-facing explanation of benefits. Paper provider remittances are often called EOBs in the office — we post those too, at the same line detail.
835 (EDI transaction)
The HIPAA X12 file format that carries the ERA. Auto-posting ingests the 835; exceptions still need a human.
What payment posting puts on every line
Each field below is a wrong A/R balance or a missed denial when it is collapsed or skipped.
| Posted element | What it means | What fails if it is wrong |
|---|---|---|
| Paid amount | What the payer deposited for that line | Cash does not match the bank; A/R stays open incorrectly |
| Contractual (CO) | Write-off under the fee schedule or contract | PR posted as CO → patient never billed; CO as PR → patient billed wrongly |
| Patient responsibility (PR) | Deductible, coinsurance, copay, non-covered | Patient statements wrong; collections chase the wrong balance |
| Other adjustment (OA) | Adjustments that are neither pure CO nor PR under the remittance | Misclassified cash and unclear next action |
| CARC / RARC | Why the payment differs from billed | Denial reason lost; appeal has no starting code |
| Denied $0 lines | Adjudicated denial — not a write-off | Buried in bulk post; never reaches denial queue |
| Takebacks / PLB | Recoupments, interest, provider-level offsets | Deposit does not balance to posted claim payments |
| Secondary prep | Primary remittance data for the COB claim | Secondary billed late or with wrong primary payment |
Group-code mapping is the highest-stakes configuration in posting. Posting a PR amount as CO means you never bill a patient who owes you. Posting a CO amount as PR means you bill a patient for something the contract says they do not owe.
How Vector Medical Billing runs payment posting
Clean files same day. Exceptions named — not forced through.
Receive remittance
835 ERA via clearinghouse, or paper EOB / check. Unapplied deposits are logged — not guessed onto a claim.
Auto-post clean lines
Matched lines post with payment, CO/PR, and CARC. Denials route to the denial queue — not a silent write-off.
Work exceptions
Unmatched claims, splits, short pays vs contract, reversals, and paper EOBs get a human owner.
Balance to deposit
Posted totals reconcile to the EFT or check. PLB takebacks and interest are named on the remittance.
Exceptions, takebacks, and underpayments
These are the posting problems that inflate A/R or hide money the payer shorted.
Unmatched and split payments
Claim number or patient account does not match, or one payment covers multiple claims. Forced posting creates duplicate cash and ghost balances. The line stays in exception until it matches.
Takebacks and PLB offsets
Recoupments and provider-level balance segments can make the deposit differ from claim payments. They are posted as reversals or offsets against the original payment — not ignored so the bank “almost” balances.
Underpayment vs contractual
A short pay that matches the loaded contract is a contractual write-off. A short pay below the contracted allowed amount is flagged for underpayment work — not written off as CO by habit.
Unapplied cash and credit balances
A deposit without a remittance is not a guess — it is an open item.
Unapplied deposits
When an EFT lands without a matching 835, the cash is logged as unapplied and aged until the remittance arrives. It is never posted to a guessed patient or claim “to clear the bank.”
Credit balances
Overpayments and patient credits are identified during posting, not only at month-end. Disposition is research — refund, reallocation, or payer return — under the applicable contract and, for Medicare overpayments, the statutory return rules that apply to identified overpayments. Exact deadlines depend on the payer and situation; posting does not invent a one-size timeline on this page.
Turnaround and how posting is priced
Clean electronic remittances are posted the same business day they land. Exceptions and paper EOBs are worked next — not left until month-end close. Payment posting sits inside the full-cycle monthly fee. Standalone posting vendors sometimes quote per remittance or per FTE; Vector’s published model folds posting into the billing percentage.
Bands are on the medical billing page. Ask for a written rate.
Where the work sits
Submission sends the claim. Posting records the answer. Patient balances that remain after PR posts feed statements. Denial CARCs feed denial management — posting does not “close” a Denial by writing it off.
Line-level posting that balances to the bank
Send a sample remittance or describe your EHR and clearinghouse path. We reply with how posting, exceptions, and takebacks will be handled — written scope, no invented underpayment percentage.
Payment posting questions
Straight answers tied to the sections above.
What is payment posting in medical billing?
Matching the payer remittance to each claim line and recording paid amount, contractual adjustment, patient responsibility, and reason codes so the ledger matches the bank and denials stay visible.
What is the difference between ERA, EOB, and 835?
ERA is the provider remittance. EOB is the patient notice (paper provider remits are often called EOBs in the office). 835 is the EDI transaction that carries the ERA.
Do you post line by line or claim level?
Line by line. Claim-level posting hides denials and short pays inside one total.
Why does CO vs PR mapping matter?
CO is contractual obligation to the provider under the contract. PR is patient responsibility. Mixing them either never bills a patient who owes money or bills a patient who does not.
How do you handle takebacks?
Recoupments and PLB offsets are posted against the original payment or as named provider-level adjustments so the deposit still balances.
What happens to denied lines on an ERA?
They post as $0 with the CARC and route to denial management — not as a contractual write-off that closes the balance.
Is payment posting an extra fee?
No on the full-cycle monthly engagement. It is inside the billing percentage.
Do we change our EHR?
No. Posting runs in Athenahealth, eClinicalWorks, Tebra, AdvancedMD, DrChrono, NextGen, CareCloud, Practice Fusion, CureMD, Office Ally, or another system confirmed before start.