Are insurance payments being posted correctly in eClinicalWorks? A payment can reach the practice successfully while the claim balance is still wrong if the remittance, adjustment, and patient responsibility are not posted correctly.
An ERA, or Electronic Remittance Advice, explains how a health plan adjudicated a claim and provides payment and adjustment information. An EOB, or Explanation of Benefits, communicates how the payer handled the claim, including amounts paid, adjusted, or assigned to patient responsibility. The X12 835 transaction supports the electronic exchange of health care claim payment and remittance information.
For eClinicalWorks users, payment posting should connect the payer’s remittance to the correct patient, claim, service line, payment, adjustment, and remaining balance. Practices that need additional support can also use specialized eClinicalWorks Medical Billing Services to manage billing and revenue cycle workflows within the platform.
How Does eClinicalWorks ERA and EOB Payment Posting Work?
The exact eClinicalWorks workflow can vary based on the practice’s configuration, payer connections, clearinghouse setup, and software version. The financial process, however, follows a consistent sequence:
Receive remittance → Match payment → Review claim → Post payment → Apply adjustments → Confirm patient responsibility → Reconcile → Work exceptions
1. Receive the ERA or EOB
The process begins when the practice receives payment and the corresponding remittance information.
An ERA provides electronic remittance information that can be processed by billing or accounting systems. CMS states that an ERA can contain adjudication information for multiple claims, with itemized information for each claim or service line.
An EOB provides similar payment information in a payer-generated explanation. Depending on the payer and workflow, staff may need to review and enter information manually.
Do not post a payment based only on the amount deposited. The remittance explains how the payer allocated that payment.
2. Match the Payment to the Remittance
The payment should be matched to the related remittance before it is allocated to individual claims. Review information such as:
- Payer
- Payment date
- Payment amount
- Check or EFT information
- Trace or reassociation information
- Claims included in the remittance
CMS explains that EFT and ERA information can use reassociation data to help connect an electronic payment with the related remittance.
3. Match the Remittance to the Correct Claim
Next, identify the patient and claim associated with the payment. Compare:
- Patient name or account
- Claim number
- Date of service
- Payer
- Provider
- Billed amount
- Allowed amount
- Paid amount
- Adjustment amount
- Patient responsibility
A payer payment should not be posted to a claim simply because the patient and payer appear to match. The remittance should support the allocation.
4. Review the Service Lines
A single claim can contain several services with different payment outcomes. For example, one line may be paid while another is adjusted or denied. Posting only the total payment without reviewing the service lines can leave the claim balance inaccurate. Check the relationship between:
Billed amount → Allowed amount → Insurance payment → Adjustments → Patient responsibility
CMS explains that ERA adjustment information can be reported at the claim, service-line, or provider level.
5. Post the Insurance Payment
Once the claim and remittance are matched, post the insurance payment to the appropriate claim and service lines. The amount posted should agree with the payer’s remittance. If the payment does not match what the system expected, stop and investigate the difference instead of forcing the payment onto the claim. Practices that need help managing these workflows can use Payment Posting Services to improve payment allocation, reconciliation, and account accuracy.
If the payment does not match what the system expected, stop and investigate the difference instead of forcing the payment onto the claim.
6. Apply the Correct Adjustments
Payment posting is not only about recording what the payer paid. The remittance can also explain why the payer did not pay the full billed amount. CMS identifies three code categories used for claim and line-level adjustments:
- Claim Adjustment Group Code
- Claim Adjustment Reason Code (CARC)
- Remittance Advice Remark Code (RARC)
Group codes help identify financial responsibility. For example, CO represents contractual obligation and PR represents patient responsibility in Medicare remittance reporting. CARCs provide the reason for an adjustment, while RARCs can provide additional explanation.
The adjustment should be posted according to the remittance rather than assumed from the remaining balance.
7. Confirm Patient Responsibility
After insurance payment and adjustments are posted, review the remaining balance. If the remittance assigns an amount to patient responsibility, make sure the patient account reflects the payer’s determination. Common patient responsibility categories include:
- Deductible
- Coinsurance
- Copayment
- Other amounts assigned by the payer
Do not automatically transfer every unpaid amount to the patient. The remittance determines how the remaining amount should be classified.
8. Reconcile the Payment
Payment posting should end with reconciliation. Compare the posted amount with the actual payment received and the corresponding remittance.
A simple control is: Payment received = Payment posted + applicable adjustments/reconciliation items
Any unexplained difference should be investigated before the batch is closed.
ERA vs. EOB: What Is the Difference?
ERA and EOB both communicate claim payment information, but they are not interchangeable terms.
| Feature | ERA | EOB |
| Full name | Electronic Remittance Advice | Explanation of Benefits |
| Main purpose | Communicates electronic claim payment/adjudication information | Explains how the payer handled a claim |
| Delivery | Electronic transaction | Payer-generated statement or electronic document |
| Standard transaction | X12 835 | May be delivered in different formats |
| Payment posting | Can support electronic processing | May require manual review depending on workflow |
| Adjustment information | Uses standardized remittance codes | Displays payment and adjustment information |
X12 defines the 835 as the Health Care Claim Payment/Advice transaction and states that it can be used to make a payment, send an EOB remittance advice, or do both.
That means it is more accurate to think of ERA as an electronic remittance transaction, while EOB describes the payer’s explanation of benefits/remittance information.
Common eClinicalWorks ERA and EOB Posting Errors
- Posting a Payment Without Reviewing the Remittance: The bank deposit tells you how much money arrived. It does not explain how the payer adjudicated every claim. Always review the remittance before allocating the payment.
- Posting to the Wrong Claim: Similar patient names, dates, or payment amounts can create matching errors. Verify the claim details before posting.
- Ignoring Service-Line Adjustments: A claim-level total may look correct while one or more service lines are posted incorrectly. Review line-level payment and adjustment information when available.
- Treating Every Remaining Balance as Patient Responsibility: An unpaid amount may result from a contractual adjustment, denial, payer correction, or another adjustment. Use the remittance to determine the correct balance category.
- Leaving Unapplied Payments Unresolved: Unapplied money makes account balances harder to interpret and can delay follow-up. Create a process for investigating unmatched payments instead of allowing them to remain open indefinitely.
- Failing to Review Denials During Payment Posting: Payment posting can reveal denials and recurring payer issues. A denied service should move into the appropriate denial or follow-up workflow rather than simply remaining as an unpaid balance.
- Not Reconciling the Batch: A payment batch should be compared with the actual deposit and remittance. Unexplained differences should be investigated before closing the posting cycle.
How to Handle ERA Exceptions in eClinicalWorks
Not every remittance will post cleanly. The goal is not to force every payment into the system. The goal is to identify exceptions and resolve them using the underlying remittance information.
Unmatched Payment
If the payment cannot be matched to a remittance or claim, review the payment reference, payer, date, amount, and available trace information. Do not apply the money to an unrelated claim simply to remove it from the unapplied balance.
Payment Amount Does Not Match
When the payment differs from the expected amount, compare:
- Billed amount
- Allowed amount
- Paid amount
- Adjustments
- Patient responsibility
- Previous payments or reversals
The remittance should explain the difference.
Missing Claim From the Remittance
If a payment is received but a related claim is not visible in the remittance, investigate the payment and remittance before allocating it elsewhere.
Denied Service Line
Denied Service Line
A claim may contain both paid and denied services. Post the paid portion correctly and route the denied portion for review based on the payer’s reason and the practice’s denial workflow. When denials require ongoing payer follow-up, Denial Management Services can help identify denial patterns, investigate root causes, and support timely resolution.
Reversal or Recoupment
A reversal, recoupment, or provider-level adjustment should not be treated like a routine claim payment. CMS notes that provider-level adjustments can include deductions for previous overpayments and other adjustments that are not tied to a specific claim.
Review the remittance details before deciding how the amount should be handled.
How to Improve eClinicalWorks Payment Posting Accuracy
A consistent payment posting process helps reduce incorrect allocations, unresolved balances, and reconciliation issues. Standardizing how staff reviews remittances also makes exceptions easier to identify and resolve.
Create a Standard Posting Workflow
Use the same basic sequence for every remittance:
- Receive the ERA or EOB.
- Match the payment.
- Identify the claims.
- Review service lines.
- Post payments.
- Apply adjustments.
- Confirm patient responsibility.
- Reconcile the batch.
- Route exceptions for follow-up.
A consistent workflow makes it easier to identify where an error occurred.
Separate Clean Payments From Exceptions
Not every payment needs the same level of manual investigation. Clean remittances can move through the normal posting workflow, while unmatched payments, unusual adjustments, denials, and reversals should move into an exception queue.
This keeps routine posting efficient without ignoring unusual transactions.
Track Recurring Posting Errors
If the same problem appears repeatedly, look beyond the individual claim. Track issues such as:
- Unmatched payments
- Incorrect adjustments
- Missing remittances
- Unapplied balances
- Incorrect patient responsibility
- Repeated payer discrepancies
- Reversals and recoupments
Recurring patterns can point to problems in payer setup, claim submission, payment posting, or staff workflow.
Connect Payment Posting With Denial Management
Payment posting and denial management should not operate as isolated processes. A remittance can reveal:
- Repeated payer denials
- Coding problems
- Authorization issues
- Contractual adjustments
- Patient responsibility
- Underpayments or unexpected payment differences
Sending these issues to the appropriate follow-up workflow can help the practice address problems earlier in the revenue cycle.
Can eClinicalWorks Automate ERA and EOB Posting?
eClinicalWorks offers revenue cycle management technology that includes receiving and posting electronic remittances. Its RCM materials also describe an EOB-to-ERA capability designed to create automation from paper EOB information when electronic payer options are unavailable.
Its financial integration materials also describe 835 files being used to facilitate payment auto-posting in eClinicalWorks.
However, automation does not mean every payment should be accepted without review.
Exceptions still require attention when the remittance does not match the claim, an adjustment is unexpected, a payment cannot be reconciled, or a denial needs follow-up.
The practical workflow is:
Automate routine posting → Review exceptions → Reconcile payments → Route denials and discrepancies
eClinicalWorks ERA Payment Posting Checklist
Use this checklist before closing a payment batch:
| Checkpoint | What to verify |
| Remittance | ERA or EOB is available |
| Payment | Payment amount matches the remittance |
| Claim | Correct patient and claim identified |
| Service lines | Paid and adjusted lines reviewed |
| Adjustments | Correct adjustment information applied |
| Patient responsibility | Matches the remittance |
| Denials | Denied services routed for follow-up |
| Unapplied payments | Unmatched amounts investigated |
| Reversals | Reversals or recoupments reviewed |
| Reconciliation | Posted payment agrees with the actual deposit |
Final Takeaway
Accurate eClinicalWorks ERA and EOB payment posting requires more than entering the amount received.
The payment poster needs to connect the remittance, claim, service lines, payment, adjustments, and patient responsibility before closing the transaction.
A reliable workflow is simple:
Match the payment → verify the claim → review adjustments → confirm patient responsibility → reconcile → work exceptions.
Automation can make routine posting faster, but exceptions still need human review. When payment posting, reconciliation, and denial follow-up work together, the billing record is more likely to reflect what the payer actually adjudicated.
