How to automate dental insurance payment posting
By the ScoutIQ AI teamPublished
EOBs, ERAs, EFTs and virtual cards, posted to the ledger per procedure and matched to the bank without a person retyping them. The seven steps in the order that works, the hard cases that break most offices, the denial codes and what to do with each, a worked reconciliation, the numbers to expect, and a 30-day rollout.
Key takeaways
- 1Posting is three jobs, not one: read the remittance, post it per procedure to the ledger, and prove the money reached the bank. Most offices automate none of them.
- 2Route every remittance, paper EOB, ERA, portal PDF and virtual card notice, through one queue with a timestamp. The unposted backlog is the number that predicts everything else.
- 3Post per procedure with the right adjustment type every time. A lump sum against a claim is a plug, and it breaks the patient statement and the write-off report downstream.
- 4Match deposits to remittances with four keys: payer, amount, reference and timing. Expect 90 to 92% to match with no human review and plan for the 8 to 10% that need a person.
- 5Work denials from a queue with the reason code attached, inside the appeal window. Reconcile practice, bank and books daily and leave every difference named.
- 6Measure five numbers weekly: match rate, EOB-to-posted days, unposted dollars, denial rate by payer, and virtual card fee share.
What insurance payment posting is
Insurance payment posting is the work between a payer paying a claim and the practice knowing it: reading the explanation of benefits, recording the paid amount, the contractual write-off and the patient portion on each procedure line, marking the claim paid or denied, and proving the money reached the bank. Done by hand it is the single largest block of billing hours in a dental office. Done by software it is a queue that is empty by 8 am.
It is three jobs, and most offices only think of the first. Reading and posting puts the remittance in the ledger. Matching proves the deposit arrived and belongs to that remittance. Reconciling proves the practice system, the bank and the books agree. Automating one without the other two moves the manual work downstream instead of removing it.
Why posting by hand fails
The biller opens the mail at 8:15. Eleven envelopes: seven checks with EOBs, two denials, two virtual card notices. She logs into the clearinghouse for the ERAs, then two payer portals for the remittances that never come any other way. Each EOB is read, each line keyed into the PMS, each check listed on a deposit slip. By noon the stack is half done and a patient is at the desk asking why her statement shows a balance the insurance already paid.
Nothing in that morning is hard. All of it is slow, and every step is a place to mistype a number. The unposted stack is why the A/R report overstates what is owed, why the month never closes cleanly, and why the denial from three weeks ago is still unread. Industry estimates put 9 to 15% of dental practice revenue uncollected each year; a meaningful share of that starts as a remittance nobody posted in time.
The four doors a remittance comes through
Every practice receives insurance money four ways, and each way has its own failure mode. Automation starts by treating all four as one stream.
| Door | How it arrives | How it fails | Fix |
|---|---|---|---|
| Paper EOB with a check | Mail, days after adjudication | Sits in a pile; the check clears the bank before the EOB is read | Scan on arrival or route to a managed PO box; digitize and timestamp the day it lands |
| ERA (835) with an EFT | Clearinghouse, same day as the deposit | Auto-posts into the wrong procedure or auto-post is switched off for a payer | Pull every 835 into the queue; post per procedure; reassociate the EFT by trace number |
| Payer portal PDF | Only when someone logs in and looks | Payers that never mail or send 835s are simply missed for weeks | Schedule portal pulls per payer; treat a pulled PDF like a paper EOB |
| Virtual credit card notice | Fax or email, with a card number to key in | Card expires unprocessed; fee is never recorded; deposit lands under the processor name | Process on arrival, record the fee as its own line, match the processor deposit net of fee |
Anatomy of an EOB
An EOB or ERA carries eight things a ledger needs. A posting tool that cannot read all eight per line is a scanner, not a poster.
| Field | Why it matters when posting |
|---|---|
| Claim number and patient | Which ledger the money belongs to |
| Date of service | Which visit, and whether the claim is inside timely filing |
| Procedure code (CDT, or CPT for medical) | Which line on the ledger receives the payment |
| Billed and allowed amounts | The contractual write-off is the difference, per line |
| Paid amount | What posts as an insurance payment |
| Patient responsibility | Deductible, coinsurance and copay, which become the patient balance |
| Adjustment reason codes (CARC) and remark codes (RARC) | Why a line was reduced or denied, and what to do next |
| Check, EFT or card reference | The key that matches this remittance to a deposit |
The seven steps
- 1
Bring every remittance through one door
Route paper EOBs, electronic remittances (ERAs) from the clearinghouse, payer portal downloads and virtual card notices into a single queue with a timestamp, so nothing is posted from a pile on a desk and nothing waits in an inbox.
Insurance money arrives four ways, and most offices handle each one differently. That is why a payment can sit unposted for two weeks while the deposit already cleared the bank, and why the A/R report overstates what is owed.
The fix is boring and decisive: one intake queue. Paper goes to a scanner or a managed PO box and is digitized the day it arrives. ERAs flow in from the clearinghouse. Portal remittances are pulled on a schedule, per payer. Virtual card notices are processed on arrival. Every remittance lands in the same place with the date it arrived, so the backlog is a number you can read instead of a stack you can only estimate.
- 2
Read the EOB at the line level
Extract every field a ledger needs from each remittance: claim number, patient, date of service, procedure code, billed, allowed, paid, contractual write-off, patient responsibility, and the adjustment and remark codes.
A total posted against a claim is not posting; it is a plug. The ledger needs the paid amount, the adjustment and the patient portion on each procedure line, or the patient statement that follows will be wrong, the write-off report will be fiction, and the next audit will find it.
This is where AI changed the job. Template-based OCR broke on every payer layout it had not seen and read a remark code as noise. A model that reads an EOB the way a biller does handles a new payer format the first time, reads the CARC and RARC codes, keeps a confidence score per line, and flags the line it is not sure about instead of guessing.
- 3
Post to the practice management system automatically, per procedure
Apply the paid amount, the contractual adjustment and the patient responsibility to the correct procedure on the correct patient ledger in the PMS, mark the claim paid, partially paid or denied, and do it without retyping.
In our ROI model, a practice posts 30 to 40% of its insurance payments by hand at 1.5 to 3 minutes each; the rest auto-post from the clearinghouse. The hand-posted share is where the errors and the hours live, and it grows with paper-heavy payers, portal-only payers and virtual cards.
Automated posting should write into the system you already run. ScoutIQ AI posts into 58 practice management systems, from Dentrix, Eaglesoft and Open Dental to the specialty systems endodontists and oral surgeons use, such as TDO and WinOMS. Nothing is migrated, and the adjustment types are the ones your office already uses, so reports keep meaning what they meant.
- 4
Match every payment to its remittance
Tie each check, EFT and virtual card to the EOB it pays, using payer, amount, reference number and timing. Flag partials, splits and duplicates instead of posting them, and process virtual cards with their fees tracked.
Posting and matching are different jobs. Posting puts the EOB in the ledger; matching proves the money arrived. An office that posts every EOB but never matches deposits will still discover in March that a January check was never mailed.
Based on historical customer numbers, 90 to 92% of insurance payments match their EOB with no human review. The remaining 8 to 10% are flagged as partials, splits or ambiguous matches for a person to resolve, rather than posted wrong. That flag rate is the honest number to expect; a tool that claims 100% is hiding the exceptions somewhere.
- 5
Work denials and short payments from a queue, not a pile
Separate denied and underpaid lines into their own queue with the reason code attached, an owner and a due date, so appeals go out inside the timely-filing window.
The denial that costs the most is the one nobody saw. When EOBs are posted by hand, a denial is a line on page three of a stack; by the time someone works the aging report the appeal window has closed and the claim becomes a write-off with a story attached.
Automated reading pulls the adjustment and remark codes off the EOB at intake and routes the claim to a queue the same day, grouped by reason. The biller opens the queue, sees the CO-197 or the CO-16, and spends the morning on appeals instead of on retyping.
- 6
Reconcile three ways and book it
Compare what the PMS says was posted, what the bank says was deposited and what the general ledger says was booked, then post deposits and card fees to QuickBooks or Xero and leave every open item as a named exception with an owner.
Most month-end pain is not accounting; it is the practice system, the bank and the books each telling a slightly different story about the same week. A three-way reconciliation that runs daily turns that into a short list of named differences: one check in the mail, one virtual card fee not yet booked, one deposit posted to the wrong location.
The test of a good reconciliation is whether it ever needs a plug number. It should not. Every difference has a name, an amount, an owner and a date it is expected to clear, and the books close when that list is empty, not when someone gives up.
- 7
Measure weekly, with a handful of numbers
Track the match rate, days from EOB received to posted, the unposted backlog in dollars, the denial rate by payer and the virtual card fee share, weekly and per location.
Five numbers tell you whether posting is working: what share of payments matched without a person, how many days a remittance waits before it is posted, how many dollars are sitting unposted right now, which payers deny the most, and how much virtual card fees are costing you.
Based on historical customer numbers, ScoutIQ AI customers see about 20% fewer days in A/R. The number to watch is the unposted backlog: when it stays near zero every week, the rest follows.
The hard cases: secondaries, splits, recoupments, virtual cards
The routine EOB is easy to automate. Whether a tool is worth having is decided by what it does with the remittances that are not routine.
Secondary insurance and coordination of benefits
When a patient has two plans, the primary EOB sets what the secondary will consider. Post the primary per line first, then the secondary against the remaining balance, and never let the two adjustments exceed the billed amount. Automation should hold the secondary until the primary is posted, then apply it to the same lines.
One check, many patients
A bulk check from a payer covers a dozen claims. The ledger needs a dozen postings and the bank sees one deposit. Split the remittance per claim at intake, post each, and match the sum of the splits to the single deposit. A partial on one claim inside the bulk check is flagged as that claim, not as the whole check.
Recoupments and takebacks
A payer that overpaid last quarter will deduct it from this quarter’s check. The remittance shows a negative line against an old claim. Post the reversal to the original claim, not as a discount on the new one, so the old patient balance reopens correctly and the deposit still matches net of the takeback.
Virtual credit cards and their fees
A virtual card pays the allowed amount but the processor deposits it net of a fee. Post the full paid amount to the ledger, record the fee as a separate expense line, and match the deposit to paid minus fee. Track the fee share by payer; it is the evidence you need to push a payer back to EFT.
Overpayments and refunds
When a payer pays more than billed or pays twice, the overpayment is a liability, not income. Post it as a credit on the claim, queue the refund with the payer reference, and match the outgoing refund to the bank when it leaves. Nothing moves money without a person approving it.
Interest and penalty payments
Some payers add prompt-pay interest to a late remittance. It is not a payment on a procedure. Post it to an interest income line, not to the patient ledger, and match the deposit including it.
Denial codes and what to do with each
Payers explain a reduced or denied line with a claim adjustment reason code (CARC), often paired with a remark code (RARC) that says what was missing. These ten cover most of what a dental office sees. The group letters matter: CO is a contractual obligation the practice absorbs unless it appeals, PR is patient responsibility to bill, OA is other adjustment.
| Code | Meaning | What to do |
|---|---|---|
| CO-4 | Procedure code inconsistent with the modifier or missing a required modifier | Correct the code or modifier and resubmit |
| CO-16 | Claim lacks information or has a submission error; a RARC says what is missing | Supply the missing item (x-ray, narrative, tooth number) and resubmit |
| CO-18 | Duplicate claim | Confirm the original was paid; post nothing new |
| CO-29 | Timely filing limit expired | Appeal with proof of original submission if you have it; otherwise write off and fix the intake gap that caused it |
| CO-50 | Not deemed medically necessary | Appeal with clinical notes and imaging; common on endodontic retreatment and surgical extractions |
| CO-96 or PR-96 | Non-covered charge; the group code says who owes it | PR-96: bill the patient per the plan. CO-96: the practice absorbs it; check frequency limits and plan exclusions before appealing |
| CO-97 | Bundled: payment included in another service | Review the bundling edit; appeal if the procedures are separately billable |
| CO-197 | Precertification or authorization absent | Obtain retro-authorization where the plan allows; queue future cases for pre-auth |
| PR-1, PR-2, PR-3 | Deductible, coinsurance, copay | Not a denial: post as patient responsibility and start patient billing |
| OA-23 | Impact of prior payer adjudication | Secondary claim: post against the balance the primary left |
A worked three-way reconciliation
One day, four locations, the numbers from the morning band on our home page. The practice system says what was posted, the bank says what arrived, the general ledger says what was booked. The reconciliation is the list of differences, each with a name.
| Line | PMS | Bank | General ledger |
|---|---|---|---|
| Insurance payments posted | $12,430 | $12,430 | |
| Patient payments posted | $3,860 | $3,860 | |
| Deposits received | $15,250 | ||
| Check in transit (Tempe, expected Thursday) | $1,040 |
Sample data.
Posted: $16,290 in the PMS and $16,290 in the general ledger. In the bank: $15,250 received today. Difference: $1,040, and it has a name, one check for Tempe still in the mail, expected Thursday. A virtual card fee, when there is one, is booked as an expense on both sides so the deposit matches net. Nothing needs a plug, and nothing needs a person until Thursday. That is the standard: every difference is a named item with a date, or it is a mistake.
The five numbers to watch
Weekly, per location, on one page. Six lines below because days in A/R is the outcome the other five drive.
| Metric | How to compute it | Target |
|---|---|---|
| Match rate | Payments matched to a remittance with no human review ÷ all payments | Above 90%; historical customer numbers show 90 to 92% |
| EOB-to-posted days | Days from the remittance arriving to the ledger updated, median | Same day; anything over 3 days is a backlog forming |
| Unposted backlog | Dollars of remittances received and not yet posted, today | Near zero at every weekly review |
| Denial rate by payer | Denied lines ÷ adjudicated lines, per payer, trailing 90 days | Track the trend; a payer that doubles is a process change on their side |
| Virtual card fee share | Card fees ÷ payments received by virtual card | Know it per payer; it is the case for moving them to EFT |
| Days in A/R | (Total A/R ÷ average daily production), insurance and patient separately | Most practices start between 35 and 60; ScoutIQ AI customers see about 20% fewer |
Where specialty practices differ
An oral surgery office bills medical insurance as well as dental, so it receives two kinds of remittance with different claim forms (the CMS-1500 for medical, the ADA form for dental), different code sets (CPT and ICD-10 beside CDT) and different remark codes. Prior authorization denials (CO-197) are far more common on the medical side. An endodontic office sees fewer, larger claims, where one short payment is worth a phone call, and medical-necessity denials (CO-50) on retreatment. Both run practice management systems most billing tools were never built for: TDO, EndoVision, PBS Endo, WinOMS, OMSVision, DSN. The seven steps are the same; the intake has to read both payer types, and the posting has to write into those systems. How ScoutIQ AI handles endodontics and oral surgery.
What to ask a vendor
Ten questions. A vendor that answers all ten with specifics is selling posting automation. One that answers three is selling an 835 importer with a nicer screen.
- Does it read paper EOBs, ERAs, portal PDFs and virtual card notices, or only the 835?
- Does it post per procedure into my practice management system, by name, with the adjustment types I already use?
- What is the measured match rate on customer data, and what happens to the payments that do not match?
- How are partials, bulk checks, secondaries and recoupments handled?
- Are virtual cards processed, and is the fee tracked per payer?
- Is there a denial queue with the CARC and RARC codes attached, and who owns each item?
- Does it reconcile to the bank and to the general ledger, and does it ever post a plug?
- Does a person approve anything that moves money, including refunds?
- How long from signature to live, and is anything migrated?
- Does it support the systems my specialty runs, such as TDO or WinOMS?
A 30-day rollout
Four weeks, each releasing a little more of the routine to the software while a person keeps the exceptions. Run it on your own data and decide at the end on your own numbers.
Week 1
Connect and observe
Connect the PMS, the bank feed and the clearinghouse. Run intake only: every remittance lands in the queue and is read, nothing posts yet. Compare what the software read against what the biller would have posted for a week of EOBs. Fix the adjustment-type mapping.
Week 2
Post with review
Turn on posting with every line held for a person to approve. The biller approves in batches instead of keying. Measure EOB-to-posted days and the unposted backlog daily.
Week 3
Match and reconcile
Turn on deposit matching and the daily three-way reconciliation. Work the flagged 8 to 10% together with the vendor and name every open item. Book deposits and fees to the general ledger.
Week 4
Release the routine
Let the high-confidence lines post without review; keep denials, partials, recoupments and refunds on the queue with an owner. Set the weekly five-number review. Decide, on your own numbers, whether to continue.
Eight mistakes that undo the automation
| Mistake | What it costs |
|---|---|
| Posting claim totals instead of lines | The statement and the write-off report are wrong from that day on. |
| Leaving auto-post on for a payer nobody reviews | Clearinghouse auto-post is convenient until a payer changes its format and posts to the wrong line for a month. |
| Ignoring portal-only payers | The remittance that never arrives is the claim that ages past timely filing. |
| Treating a partial as paid in full | The short payment disappears into a write-off and the appeal window closes. |
| Keying virtual cards without recording the fee | The deposit never matches and the payer keeps sending cards. |
| Posting a recoupment as a discount on a new claim | The old balance stays wrong and the new one looks underpaid. |
| Closing the month with a plug | The difference is still there next month, with interest. |
| Automating posting and skipping reconciliation | Everything looks posted and the bank still does not agree. |
What good looks like
Based on historical customer numbers: 90 to 92% of insurance payments matched to their EOB with no human review, the remaining 8 to 10% flagged rather than posted wrong; 99.5% of patient payments reconciled with no human touch; about 20% fewer days in A/R; and 400 or more staff hours a year returned to the practice. Sources and methodology are on the platform data page.
How ScoutIQ AI does this
ScoutIQ AI insurance billing automation runs all seven steps as one system: one intake queue for paper, ERAs, portals and virtual cards; AI reading of every EOB line with a confidence score; posting into the practice management system you already run; matching of checks, EFTs and virtual cards to the bank; a denials queue with the codes attached; a daily three-way reconciliation booked to QuickBooks or Xero; and the weekly numbers through Atlas. A person on your team approves anything that moves money.
Glossary
- EOB
- Explanation of benefits: the paper or PDF statement a payer sends showing how a claim was adjudicated.
- ERA / 835
- Electronic remittance advice, the X12 835 transaction: the same information as an EOB in machine-readable form, usually delivered through a clearinghouse.
- EFT
- Electronic funds transfer: the deposit that accompanies an ERA, identified by a trace number.
- Virtual credit card (VCC)
- A single-use card number a payer issues instead of a check or EFT; the practice processes it and pays a processing fee.
- CARC / RARC
- Claim adjustment reason codes and remittance advice remark codes: the standard codes that explain why a line was reduced or denied.
- Contractual adjustment
- The difference between the billed fee and the payer’s allowed amount, written off under the network contract.
- Patient responsibility
- Deductible, coinsurance and copay left to the patient after the payer adjudicates.
- Timely filing
- The payer’s deadline for submitting a claim or an appeal, measured from the date of service or the denial.
- Recoupment
- A payer taking back a prior overpayment by deducting it from a later remittance.
- Three-way reconciliation
- Agreeing the practice management system, the bank and the general ledger to each other, with every difference named.