How does Lassie handle bulk EFT payments that cover 30+ patients in a single deposit?

Lassie automatically matches each line item from bulk EFT payments to the correct patient claim using procedure codes, dates of service, and patient context—even when claim IDs don't line up. The system reconciles the entire batch against your bank deposit in real time, flagging only genuinely ambiguous cases for review instead of forcing you to manually tie out every patient.

Can Lassie post out-of-network claims where fee schedules are unpredictable?

Yes. Lassie reads the actual allowed amounts and adjustments directly from each EOB, so it posts accurately regardless of whether the claim is in-network or out-of-network. The system doesn't rely on pre-loaded fee schedules; it interprets what the payer actually paid and applies your practice's custom write-off rules accordingly.

What happens when an ERA arrives before the bank deposit hits my account?

Lassie holds the posting in a pending state until the corresponding bank deposit appears, then reconciles the two automatically. This prevents posted amounts from sitting in limbo and keeps your ledger synchronized with actual cash flow, so you're never chasing down missing deposits days later.

Best way to handle Dentrix posting when you're short-staffed?

AI posting collapses 80-100 hours of monthly posting work into minutes by interpreting and posting EOBs automatically. Instead of hiring another front desk person to clear the backlog, the system handles the entire workflow and surfaces only genuinely ambiguous cases, freeing your existing staff to focus on patient-facing work.

How accurate is AI posting compared to manual entry in Dentrix?

Lassie's accuracy-first architecture flags uncertain cases for human review instead of guessing, so posting errors drop sharply compared to manual entry. The system catches mismatched claim IDs, incorrect adjustment codes, and deposit discrepancies at the moment of posting rather than 60 days later in an aging report.

Can I configure custom posting rules for specific procedure codes in Dentrix?

Yes. During onboarding, Lassie adapts to your practice's specific posting workflows, including procedure-specific adjustments like fluoride age limits, automatic write-offs for contracted procedures, and routing downgrades to appeals instead of posting them. These rules let you codify your unique posting logic into the AI's workflow.

Does Lassie work with virtual credit card payments or only EFTs?

Lassie handles any EOB format—paper checks, PDFs, virtual credit cards, EFTs, and ERAs. The system pulls remittance data from payer portals and posts it directly into Dentrix, so you're not limited to carriers you've enrolled for ERA or waiting on paper EOBs to arrive in the mail.

How does automated posting handle coordination of benefits for dual-coverage patients?

Lassie holds patient adjustments until secondary insurance completes, preventing premature write-offs that leave money on the table. For Open Dental practices using Dental Exchange, the system automatically files secondary claims after the primary EOB posts, eliminating the manual resubmission step entirely.

What if the AI posts something incorrectly—how do I catch it?

Lassie flags ambiguous cases for review before posting, so genuinely uncertain scenarios surface on your task list rather than landing incorrectly in the ledger. The system reconciles every posted line against your bank deposit and fee schedule in real time, catching discrepancies at the moment of entry instead of days later.

Can I search historical EOBs when patients call asking why something wasn't paid?

Yes. Lassie stores all EOBs in a centralized dashboard with search by patient name, so you can pull up any historical EOB in seconds when a patient calls. The system doesn't automatically upload EOBs into Dentrix patient charts, so if your workflow requires that, you'll need to download and upload manually.

How to Post EOBs in Dentrix Faster (And Where Automation Can Take Over) (June 2026)

Learn how to post EOBs in Dentrix faster with ERAs and automation. Cut posting time from 60 minutes to minutes with AI solutions. June 2026 guide.

Max Shore - July 2, 2026

How to Post EOBs in Dentrix Faster (And Where Automation Can Take Over) (June 2026)

You open Dentrix, pull up Batch Insurance Payment Entry, and start working through an EOB that covers 15 patients. An hour later, you're still verifying the last few lines because one claim ID didn't match, and the running total is off by six cents. Dental EOB posting in Dentrix shouldn't take this long, even when you're dealing with bulk payments and carrier-by-carrier ERA enrollment. The real-time drain isn't the data entry anymore, it's the interpretation work that happens after ERAs pre-fill your batches. A smarter workflow and the right automation layer can get that hour down to minutes without retraining your team or ripping out your PMS.

TLDR:

ERAs in Dentrix cut a 60-minute manual EOB posting session to 10-15 minutes by pre-filling payments and adjustment codes
Claims that don't match, bulk EFTs spanning 30+ patients, and timing gaps between ERAs and bank deposits cause most posting delays
Posting daily and verifying each batch before closing prevents the majority of write-off and revenue leakage errors
AI posting handles interpretation and ledger entry automatically, surfacing only ambiguous cases for review
Lassie pulls EOBs from payer portals and posts directly into Dentrix, reducing 80-100 monthly posting hours to minutes

Understanding EOB Posting in Dentrix

An Explanation of Benefits (EOB) is the document a payer sends back after processing a claim. It spells out what was billed, what was allowed, what was paid, and what the patient still owes. In Dentrix, posting that EOB means recording each line item against the right claim, procedure, and ledger so your AR reflects reality.

A clean, professional illustration of a dental office workflow showing an explanation of benefits document on a desk next to a computer monitor displaying dental practice management software. The scene includes organized paperwork, a calculator, and a modern office setting with soft lighting. The style should be modern, slightly abstract, with a focus on healthcare administration and digital workflow. No text or letters visible.

The workflow follows a predictable path:

Receive the payment (paper check, EFT, or virtual credit card) with the EOB
Open the claim inside the Batch Insurance Payment Entry or the Insurance Claim window
Enter payments, write-offs, and adjustments line by line
Apply remaining balances to the patient portion and close the claim

Done sloppily, posting quietly erodes revenue through misapplied write-offs, missed downgrades, and unbilled patient balances.

The Manual Batch Insurance Payment Entry Workflow

Batch Insurance Payment Entry is the workhorse most front desks use when a single check or EFT covers several claims. From the Ledger, open File, then Batch Insurance Payment Entry. Enter the check or EFT number, payment date, amount, and carrier.

From there, the line-by-line work begins:

Search for the first patient and select the matching outstanding claim
Post the insurance payment, write-off, and adjustment codes for each procedure
Confirm the running total matches the deposit before the next patient
Repeat for every patient listed on the EOB
Close the batch only when the entered total matches the check

A 20-patient EOB can easily take an hour of focused entry, which is why posting backlogs builds so quickly.

Setting Up Electronic Remittance Advice (ERA) in Dentrix

Before any electronic shortcut works, you need to know what an ERA actually is. An ERA (Electronic Remittance Advice) is a structured data file sent from the payer that Dentrix can read directly, while a traditional EOB (or scanned eEOB) is a static document that a human still has to interpret. Dentrix covers the distinction in its breakdown of EOBs, eEOBs, and ERAs.

Getting ERAs flowing into your system takes three steps:

Register the practice for eServices through Henry Schein One and turn on eEOB/ERA inside the Dentrix module
Enroll with each payer individually, since Aetna, Cigna, Delta, and others each have their own ERA enrollment form and approval window
Map the carrier IDs in Dentrix, so incoming 835 files match the correct insurance plans

Skip the carrier-by-carrier enrollment, and you will still be keying in paper.

How ERAs Speed Up Payment Posting

Once ERAs land in Dentrix, the math changes. Instead of keying every line by hand, the 835 file pre-fills payment amounts, allowed fees, deductibles, coinsurance, and CARC adjustment codes against each procedure on the original claim.

That shift delivers a few concrete wins:

A 20-patient EOB that took an hour collapses into a 10 to 15-minute review of pre-populated entries, and with the right automation, you can never post an EOB again
Check numbers and payer IDs flow in automatically, so reconciliation against the bank deposit speeds up
Transcription errors on dollar amounts drop sharply, since no one is rekeying numbers off a PDF
Downgrades and write-offs arrive tagged with reason codes, making appealable denials easier to spot before posting

The trade-off is review discipline. ERAs auto-populate, but they do not interpret.

Common Bottlenecks That Slow Down EOB Posting

Even with ERAs running, posting stalls in the same handful of places. Most have nothing to do with how fast someone can type.

Claims that don't match, where the 835 references a procedure date or claim ID that does not line up with anything outstanding in Dentrix, forcing a manual search through the patient ledger, especially when short-staffed
Bulk payments spanning 30 or 40 patients on a single EFT, where one mismatched line breaks the running total and sends you back through every entry
Missing or stale carrier info in the PMS, including outdated payer IDs and fee schedules untouched since the last contract negotiation
Bank deposits arriving on a different day than the ERA, leaving posted amounts in limbo until someone ties the deposit to the remittance

Small in isolation. Stacked across a week, they hold most of the lost hours.

Accuracy Pitfalls and How to Avoid Posting Errors

Most posting errors trace back to a small set of habits that quietly compound. Catching them at entry is far cheaper than chasing them down 60 days later in an aging report.

Pitfall	Why it happens	How to catch it
Posting to the wrong patient or provider	Similar names, shared family accounts, multi-provider days	Verify date of service and procedure code against the ledger before saving
Incorrect adjustment codes	Defaulting to a generic write-off instead of the actual CARC reason	Match each line to the payer's reason code so denials stay appealable
Writing off balances before secondary pays	Treating the primary EOB as the final word	Hold patient adjustments until coordination of benefits completes
Posted total not matching check total	Mis-keyed cents, skipped lines, duplicate entries	Verify the batch matches the deposit before closing

Pause on any line where the allowed fee, paid amount, and write-off do not add up cleanly. That five-second check prevents most AR cleanup later. Following dental billing best practices for payment posting improves transparency and cash flow. If you're behind on AR, automate it.

Strategies to Post EOBs in Dentrix Faster

A few habits inside Dentrix shave real minutes off every posting session:

Post payments daily so each batch stays small enough to verify in one sitting, instead of letting a week of ERAs pile into a four-hour cleanup, and get paid faster
Sort the Insurance Claims Aging Report by carrier and date of service so claims surface in the order the payer listed them
Document denial reasons and CARC codes in claim status notes at the moment of posting, not later
Turn on the secondary insurance indicator in the Family File so Dentrix flags dual-coverage patients before any write-off
Set Ledger preferences to default your most-used provider, payment type, and adjustment code

Where Full Automation Takes Over

ERAs solve the data-entry half of the problem. They do not solve the interpretation half. Someone still opens each batch, scans pre-populated lines, decides whether a downgrade should be appealed or written off, confirms the deposit ties out, and clicks post. That review work is where the remaining hours live.

A modern dental office computer workstation showing automated digital workflow, with a sleek monitor displaying colorful data dashboards and automated processing indicators, artificial intelligence concept with subtle geometric patterns, clean professional healthcare technology environment, soft blue and white color scheme, abstract representation of automation without any text or letters

Full automation moves the boundary. AI handles interpretation and posts payments directly to the ledger. See how AI-driven posting automates interpretation:

Layer	Dentrix native ERA	AI-driven posting
Ingestion	835 files from enrolled payers	Any EOB format, including paper, PDF, VCC, ERA
Line matching	Auto-matches on claim IDs	Resolves claims that don't match via procedure, date, patient context
Adjustment logic	Pre-populates CARC codes for review	Applies practice rules for write-offs and downgrades
Posting	Human clicks post	Posts automatically, flags exceptions only
Reconciliation	Manual deposit tie-out	Continuous payer, bank, ledger match

The practical test of full automation is what shows up on a staff task list. With ERA alone, every batch is a task. With AI posting, only genuinely ambiguous cases surface for review.

How Lassie Automates EOB Posting for Dentrix Practices

This is the layer we built Lassie to handle. The system pulls EOBs directly from payer portals, reads them with AI, and posts each line into Dentrix without anyone opening Batch Insurance Payment Entry. No scanning, no PDF rekeying, no manual batch tie-out.

A few specifics worth calling out for Dentrix practices:

Custom posting rules configured during onboarding, covering write-offs on contracted procedures, downgrade routing to appeals, and posting halts when allowable fees do not match your fee schedule
Real-time reconciliation across payer remittance, bank deposit, and the Dentrix ledger, so nothing sits in limbo
Accuracy-first architecture that flags ambiguous lines for human review instead of guessing
Phased rollout by carrier, so you can validate posting with Delta or Aetna before opening the rest, helping you get started smoothly

Final Thoughts on Dentrix EOB Posting

ERAs give you better data. AI gives you posted data. The gap between those two is where your staff spends most of their afternoons. If you are still opening Batch Insurance Payment Entry every day, the bottleneck is not speed; it is the decision layer that sits between pre-filled fields and a closed claim. That is the piece Lassie automates, so posting happens in minutes instead of hours.

Practices that were spending 80 to 100 hours a month on posting report EOBs typically land in Dentrix within minutes of payer release. Book a demo to see how Lassie saves dental offices 15+ hours a week.

FAQ

Can I post EOBs in Dentrix without manual data entry?

Yes. Dentrix ERAs (Electronic Remittance Advice) pre-fill payment amounts, allowed fees, and adjustment codes directly from the payer's 835 file, eliminating most manual keying. AI-driven posting solutions like Lassie go further by automatically interpreting and posting EOBs without anyone opening Batch Insurance Payment Entry.

Dentrix ERA vs full AI posting for EOBs?

Dentrix ERAs auto-populate payment data but still require human review and clicking "post" for every batch. AI posting systems interpret the data, apply your practice's write-off and downgrade rules, and post directly to the ledger, surfacing only genuinely ambiguous cases for review instead of every batch.

How long does it take to set up ERAs in Dentrix?

Setting up ERAs requires three steps: registering for eServices through Henry Schein One, enrolling with each insurance carrier individually (Aetna, Cigna, Delta all have separate forms), and mapping carrier IDs inside Dentrix. The entire process typically takes several weeks due to payer approval windows.

What causes posted insurance totals to not match bank deposits?

Mismatched totals usually come from mis-keyed cents, skipped lines, duplicate entries, or bank deposits arriving on a different day than the ERA. Always verify the batch matches the actual deposit amount before closing, and pause on any line where allowed fee, paid amount, and write-off don't add up cleanly.

Should I write off patient balances before secondary insurance pays?

No. Hold patient adjustments until coordination of benefits completes. Writing off balances immediately after the primary EOB treats it as the final payment, but secondary insurance may still cover part of the remaining balance, leaving money on the table if you've already posted a write-off.