Every few months I get on a call with someone who spent the last decade in medical revenue cycle management and recently landed at a dental DSO. They want to bring best practices with them. Run everything through a clearinghouse. Lean on X12 271 responses for eligibility. Let the ERA handle posting. And every time, someone on their new team has to explain something that sounds like an excuse: "it doesn't work the same way in dental."

This is not because dental RCM is primitive. It is because dental insurance carriers are primitive, and the tooling that works for medical billing makes a specific assumption about the data infrastructure underneath it that dental carriers have never built.

I want to make that case directly, because the framing matters. Every year I hear some version of "dental RCM is where medical RCM was fifteen years ago." That framing puts the gap on dental practices, or on dental software vendors, or on billing teams that have not yet modernized. The actual gap is on the carrier side, and it is structural, not generational. Dental practices are not behind. The carriers are.

Why medical billing got standardized and dental didn't

Medical insurance was fundamentally shaped by CMS. Medicare and Medicaid set the rules: ICD-10 codes for diagnoses, CPT codes for procedures, ANSI X12 837P formats for electronic claims, ERA timelines, 270/271 eligibility specifications. The standardization was messy and slow, but it happened because a very large payer had the leverage to require it of everyone else.

Dental insurance is privately structured. Delta Dental, MetLife Dental, Cigna Dental, Aetna Dental, UnitedHealthcare Dental: these are separate entities, many operating as subsidiaries of larger medical insurers but running entirely separate claims systems, separate portal architectures, separate EDI infrastructure. The American Dental Association publishes CDT codes, the dental equivalent of CPT. But the ADA is a professional association, not a regulatory authority, and there is no dental equivalent of CMS to require carriers to accept and process those codes in a standardized format, or to require them to build out complete eligibility responses, or to mandate ERA adoption timelines.

The result is a carrier ecosystem that has been able to set its own rules for decades, with no external pressure to converge.

What the 271 response actually tells you, and what it doesn't

When a billing team runs an eligibility check through a clearinghouse, they get back an X12 271 response. In medical billing, that response usually confirms active coverage, deductible status, and in-network benefit levels with enough completeness to do real treatment planning.

In dental, the 271 response tells you whether the patient is covered. That's about it.

It doesn't tell you the patient's remaining annual maximum. It doesn't tell you whether they've had a cleaning this benefit year. It doesn't tell you the coordination-of-benefits order if they carry two plans. It doesn't tell you whether D4341, scaling and root planing for one to three teeth, requires prior authorization with this carrier for this patient's specific plan. It doesn't tell you whether a restorative code has hit a frequency limitation. It doesn't tell you whether the patient's last eligible exam is inside or outside the waiting period for a new plan.

None of that is in the clearinghouse response, because dental carriers were never required to put it there.

A billing team that has built workflow assumptions around medical eligibility data is going to run into a wall on every one of those items. The front desk starts calling the carrier. Or logging into the portal manually. Or estimating, because that is what clearinghouse data licenses you to do. Those estimates sometimes become collection problems at the end of the appointment, when the patient's actual responsibility turns out to be different from what was quoted.

Where the data actually lives

The information that medical billing routes through clearinghouses, dental RCM has to go get from the source. It lives in the carrier portals.

I work with a billing coordinator at an eight-location group in North Carolina who runs eligibility on all of next week's hygiene appointments every Wednesday afternoon. She pulls the 271 feed from her clearinghouse as a first pass, which flags obvious inactives quickly. Then she opens the portals. Delta Dental's portal. Cigna Dental's portal. Aetna's portal. MetLife's portal. Not because her clearinghouse vendor failed her, but because the clearinghouse gets exactly what the carriers give them, and the carriers gave them the minimum.

The carrier portal has the remaining maximum. It has the plan history. It has the frequency limitations, the waiting-period rules, the embedded prior-authorization requirements by CDT code. The clearinghouse has a coverage flag. These are not the same thing, and the gap between them is not a technology failure. It is the data infrastructure the carriers built, which is the data infrastructure dental practices are stuck working with.

This is also why the "AI voice calling for eligibility" pitch does not work in dental the way vendors selling it would like. AI calling services can get what a human on the phone can get, and what a human on the phone can get from a carrier is a basic active-coverage confirm. The data that actually matters for dental treatment planning (annual remaining benefit, D-code frequency limitations, COB priority order) lives in a system that only the carrier portal exposes. The voice agent cannot get it because the carrier's phone agent cannot get it either.

The ERA gap is the same problem

Electronic remittance advice in dental is a visible version of the same structural issue. Medical billing teams have largely moved to auto-posting against ERA files. The ERA arrives via clearinghouse, the practice management system catches the payment, the biller reviews exceptions. The workflow is not perfect but it is built and it works.

In dental, a meaningful portion of remittances still arrive as paper EOBs. At practices I work with, this is not exceptional. Delta Dental of California, to name a specific carrier, has ERA availability that varies by plan type and by clearinghouse relationship. A single group can receive ERAs for most Delta claims on the same week they receive paper EOBs for certain plan codes from the same carrier. I have seen this with my own customers, and I hear about it from every billing team I talk to at groups with significant Delta volume.

This is not because dental practices have not asked for ERA. It is because the carriers have not built consistent ERA infrastructure, and in many cases have no contractual obligation to do so. There is no CMS equivalent requiring dental carriers to standardize ERA format and timelines the way CMS required medical carriers to. Large DSOs negotiating carrier contracts have asked for this. They have sometimes gotten it and sometimes not, depending on the carrier and on the negotiating leverage the group has.

What this means for tooling decisions

Any tool built to solve dental RCM by routing primarily through clearinghouse data is solving for the data that exists in that feed, not the data that matters for accurate dental billing. The clearinghouse vendors in dental are not failing. They are delivering exactly what the carriers give them. The problem is what the carriers give them, which is less than the portal holds.

Unify was built around the carrier portal as the primary data source because that is where the complete dental eligibility picture lives. We have built workflows for over 350 dental carrier portals. Not because portal-native architecture was the easiest path, but because it is the only architecture that works with the data landscape that actually exists in dental insurance. The 271 response filters obvious inactives, and then the portal check fills in everything the clearinghouse could not deliver.

The reason I can say with confidence that carrier portals have the most complete dental insurance data at the most reasonable cost is that I have spent years watching what happens when practices try to get that data somewhere else. The clearinghouse is incomplete. The AI voice vendors are capped by what the carrier's phone agent can read. The portal is the source of truth.

The framing matters because the fix is different

If you accept the "dental RCM is behind" narrative, the implied fix is that dental practices need to catch up: adopt more clearinghouse integrations, push for better clearinghouse data feeds, wait for the industry to mature. That framing has no practical endpoint, because the gap is not dental practices falling short of a standard. The gap is dental carriers not building the infrastructure medical carriers built under regulatory pressure.

The correct framing, the one that leads to a workable fix, is: dental insurance operates on a structurally different data infrastructure than medical insurance, and dental RCM tooling that works has to be built for the infrastructure that exists, not the infrastructure medical has.

If you're evaluating eligibility workflows or tooling at your organization, ask one specific question: where does your actual plan-maximum data come from? If the answer is the clearinghouse, you are working with an estimate. If the answer is the carrier portal, you have the real number.

Book a demo with me at https://calendly.com/tanner-unify/unify-demo if you want to walk through how Unify handles this across your specific carrier mix and portal workflows.