How to post insurance payments in Eaglesoft
To post an insurance payment in Eaglesoft, open the claim the EOB or ERA pays, enter the paid amount on each procedure, post the write-off the payer allowed, leave the patient’s share as a balance, close the claim and tie the payment to its deposit. Here is each step, and the cases that go wrong.
Book a demoBy Dr. Mark Haddad, endodontist and DSO co-founderPublished 7 min read
Key takeaways
- Post every payment per procedure, from the EOB or ERA, never as one total against the claim.
- The write-off comes from the remittance, not from the estimate Eaglesoft made when the claim went out.
- One check that pays many claims is posted claim by claim and tied back to the single deposit.
- Denials and short pays leave the posting desk with their reason code and an appeal date.
- Posting is finished when the deposit is matched at the bank and booked, not when the claim is closed.
What you need before you post
Eaglesoft, Patterson Dental’s desktop practice management system, holds the claims and the ledger. Posting is the step that brings what the payer decided into that ledger, procedure by procedure. Have these in front of you first:
- The EOB or ERA, with every line, the adjustment codes and the check, EFT or card reference.
- The claim in Eaglesoft that the remittance pays, found by patient, date of service and claim number.
- The payer’s fee schedule for that plan, so you can tell a contractual write-off from a short pay.
- The adjustment types your office already uses for write-offs, so reports keep meaning what they meant.
- The deposit it belongs to: the check in hand, the EFT on the bank statement or the card payout.
About screens and menus
How to post an insurance payment in Eaglesoft
Open the claim the remittance pays
Find the claim by patient, date of service and the payer’s claim number, and confirm the procedures on the EOB are the procedures on the claim.
If the payer paid a different code from the one billed, or split one procedure into two, stop and note it before you post: the payment has to land on the procedure that was actually done.
Enter what the payer paid on each procedure
Apply the paid amount line by line, matching each line of the EOB to its procedure in Eaglesoft.
A total entered against the claim leaves the patient portion and the write-off report wrong from that day on. Per-line posting takes longer by hand, which is the reason most offices look at automating it.
Post the write-off from the remittance
The contractual write-off is the billed amount minus the allowed amount on each line, usually shown with the code CO-45.
If Eaglesoft estimated a PPO write-off when the claim was sent, check the posted write-off against the remittance and correct it to what the payer actually allowed. Use the adjustment type your office reserves for contractual write-offs.
If the allowed amount is lower than your contracted fee and no code explains it, do not write the difference off. That is an underpayment to dispute.
Leave the patient’s share as a balance
Deductible, coinsurance and copay (PR-1, PR-2, PR-3) stay on the ledger as what the patient owes.
Check that the remaining balance on each procedure equals the patient responsibility on the EOB. If it does not, something above was posted wrong.
Close the claim, and send the secondary if there is one
Mark the claim paid, partially paid or denied, and create the secondary claim with the primary EOB attached when the patient has a second plan.
Denied or short-paid lines go to a work list with the reason code, an owner and the date the appeal window closes. Check each payer contract for that window.
Tie the payment to its deposit
Record the check number, EFT trace number or card reference, add the payment to the day’s deposit, and confirm the deposit matches the bank.
A card payout arrives net of the processing fee. Post the full amount the payer paid, and book the fee as a cost in your accounts, not as a patient adjustment.
Posting from an ERA instead of a paper EOB
An ERA carries the same information as a paper EOB in a standard electronic file, the 835, usually delivered through your clearinghouse. When Eaglesoft is set up to receive ERAs, the payment detail can be applied from the file instead of typed, which removes most keying errors.
Two things stay the same. Someone still has to review what the file applied, especially write-offs, partial payments and denied lines, and someone still has to match the EFT to the bank deposit. ERAs also only arrive from payers you are enrolled with, so paper EOBs, portal PDFs and virtual card notices keep coming from the rest. See EFT and ERA enrollment for how to move more payers onto electronic payments.
Bulk checks, secondaries and takebacks
Most posting time goes into a handful of cases that do not fit the simple path. Here is how to handle each one, and the shortcut that causes trouble later.
| Case | How to post it | What to avoid |
|---|---|---|
| One check pays many claims | Post each claim on its own from the EOB, then confirm the sum of the claims equals the check. | Posting the check as one lump against one patient |
| Secondary insurance | Post the primary first, then the secondary against what the primary left on the same lines. | Two write-offs that together exceed the billed fee |
| Recoupment or takeback | Reverse the payment on the original claim; the new check is posted net of the takeback. | Recording the takeback as a discount on a new claim |
| Overpayment | Leave it as a credit on the claim and refund the payer, with the payer’s reference. | Moving the credit to another patient balance |
| Virtual card | Post the full paid amount; book the card fee separately; match the net payout. | Writing the fee off on the patient account |
For the codes on each line, see CARC and RARC codes, and for secondaries, coordination of benefits.
Common Eaglesoft posting mistakes
Posting the claim total instead of the lines
The patient statement and the write-off report are wrong from that day on, and nobody sees it until a patient calls.
Trusting the estimated write-off
The estimate was made when the claim went out. The remittance says what the payer actually allowed.
Writing off an underpayment
A short pay posted as a contractual write-off disappears, and the appeal window closes on it.
Closing the claim without a deposit reference
Without the check or trace number, nobody can prove later that the money reached the bank.
Letting the paper pile wait for a quiet day
The check clears before the EOB is posted, and the A/R report overstates what is owed until it is.
How ScoutIQ handles it
ScoutIQ works on top of Eaglesoft and 59 practice management systems in all. Remittances come in four ways: staff uploads, a ScoutIQ PO Box where paper EOBs and checks are opened and scanned, your clearinghouse, and the payer portals ScoutIQ checks. Each ERA and paper EOB is read line by line and applied to its claim in Eaglesoft with the write-off.
95% of insurance payments are matched to their EOB with no human review (see the data page). The rest, along with short pays and denials, go to a queue with the payer’s reason and the days left to appeal; your team files the appeal. Every payment is matched to the bank deposit and booked to QuickBooks or Xero, which is the reconciliation step most offices do by hand at month end. ScoutIQ does not submit claims, and most practices are live in 48 hours.
ScoutIQ product
Insurance Billing Automation
Insurance Billing Automation
ERAs and EOBs read; EFT, check and card payments reconciled.
See Insurance Billing Automation