> ## Documentation Index
> Fetch the complete documentation index at: https://dso.getlemma.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Clearinghouse vs RCM vs PMS (vs biller)

> Four things that get conflated constantly: where data lives, what carries it, who operates the workflow, and who you outsource it to, plus a 'who do I call when X breaks' table.

A **PMS** (practice management system) is where clinical and billing data lives. A **clearinghouse** is the pipe that carries claims to payers and remittances back. A **biller** is the person who operates the workflow. An **RCM company** is an outsourced team of billers, sometimes with its own software. These are four different things, and buying one to fix a problem in another is the most expensive mistake in dental operations.

## The layers

```mermaid theme={null}
graph TB
    subgraph "Layer 1, System of record"
    A[PMS<br/>charts, demographics, insurance,<br/>charges, patient ledger, claim status]
    end
    subgraph "Layer 2, Transport"
    B[Clearinghouse<br/>translate · scrub · route · attach ·<br/>acknowledge · aggregate 835s]
    end
    subgraph "Layer 3, Labor"
    C[Biller<br/>in-house employee]
    D[RCM company<br/>outsourced team]
    end
    A <--> B
    B <--> E[Payers]
    C -.operates.-> A
    C -.operates.-> B
    D -.operates.-> A
    D -.operates.-> B
```

|                   | What it is                                                                             | You buy it as                                       | Fails when                                                         |
| ----------------- | -------------------------------------------------------------------------------------- | --------------------------------------------------- | ------------------------------------------------------------------ |
| **PMS**           | Software system of record, such as Dentrix, Eaglesoft, Open Dental, Curve, or Denticon | Subscription or license, per office or per provider | Data is wrong, workflows are missing, or reporting is unusable     |
| **Clearinghouse** | Connectivity: the transport layer                                                      | Per transaction, or bundled into the PMS            | Claims don't reach payers; 835s don't come back; enrollment stalls |
| **Biller**        | A person doing the work                                                                | Salary                                              | Nobody works the denial queue                                      |
| **RCM company**   | Outsourced billers                                                                     | Percentage of collections                           | You lose visibility and control                                    |

## Where the confusion comes from

Vendor offerings often overlap:

**PMSs with embedded clearinghouses.** Most dental PMSs bundle an eClaims pathway and present it as a single product. Convenient, and it removes your choice, including your ability to leave.

**RCM companies that resell clearinghouses.** Your dental billing service may route through a clearinghouse you never chose and cannot see.

**Clearinghouses selling "RCM tools."** Denial analytics, worklists, and dashboards, which look like RCM but are software, not labor.

**PMS vendors selling "RCM services."** The software vendor also sells you the humans. One throat to choke, and also one vendor holding your data, your pipe, and your operations.

**"All-in-one" platforms.** PMS plus clearinghouse plus billing plus payments plus payroll. See [All-in-one platforms](/reference/vendors/all-in-one-platforms) and [When platforms bundle payroll and card processing](/concepts/banking/bundled-payroll-and-processing) for the tradeoffs.

## Who do I call when X breaks

The most practically useful table on this page.

| Symptom                                    | Layer                           | Call                                                                            |
| ------------------------------------------ | ------------------------------- | ------------------------------------------------------------------------------- |
| Claim never reached the payer              | Clearinghouse                   | Clearinghouse support                                                           |
| 999 rejection, malformed file              | Clearinghouse / PMS             | Clearinghouse first; PMS if the data is wrong at source                         |
| 277CA rejection, payer front-end           | Data                            | Whoever owns the data: PMS config or enrollment                                 |
| "Payer ID not found"                       | Clearinghouse                   | Clearinghouse, which maintains its payer-ID routing table                       |
| Claim pended for documentation             | Attachments                     | Attachment vendor or clearinghouse; confirm the reference number rode the claim |
| 835s not arriving                          | ERA enrollment                  | Clearinghouse, then the payer                                                   |
| Payment arrived, no 835                    | ERA enrollment or routing issue | Payer or enrollment vendor; ERA and EFT are separate processes                  |
| 835s arriving but not auto-posting         | PMS                             | PMS support; this is posting configuration                                      |
| Denials rising                             | Workflow                        | Biller or RCM; this is a process problem, not software                          |
| Days in AR rising                          | Workflow                        | Biller or RCM                                                                   |
| Can't produce a denial or write-off report | PMS reporting                   | PMS, or export and analyze elsewhere                                            |
| Dentist not recognized by payer            | Enrollment                      | Payer enrollment, not any vendor                                                |
| Eligibility check returns nothing          | Clearinghouse                   | Clearinghouse; confirm the payer supports real-time 270/271                     |

**Two rows deserve emphasis because they are misdiagnosed constantly.**

"Denials are rising" is almost never a software problem, and buying a new PMS will not fix it. It is a verification, attachment, documentation, or enrollment process problem.

"Dentist not recognized" is usually an enrollment or linkage problem, not a transaction-format fix. After an acquisition, new location, or hire, confirm the payer-recognized entity, TIN/NPI, contract, location, rendering provider, and effective date. See [Set up EDI, ERA, and EFT](/guides/enrollment/set-up-edi-era-eft).

## Who codes, and who bills

Many dental practices do not employ dedicated coders. The dentist documents the service and selects or confirms the applicable CDT code, while billing staff handle claim preparation and payer follow-up:

|                     | Coding                                                         | Billing                                                    |
| ------------------- | -------------------------------------------------------------- | ---------------------------------------------------------- |
| **Job**             | Record what was done as CDT, with tooth, surface, and quadrant | Get claims out, payments in, downgrades and denials worked |
| **Judgment**        | Clinical facts about what was done and why                     | Operational process and payer-rule application             |
| **In DSO-PC terms** | Coding is a **PC** responsibility                              | Billers are typically **DSO** employees                    |

The MSA and operating workflow should allocate coding responsibility in a way that preserves the authority required by state law. California's SB 351 expressly addresses coding and billing for covered dental practices. Oregon's SB 951 excludes dental practices from its management-services provisions, so it should not be cited as a dental coding rule.<sup>1</sup> A DSO may employ billers, maintain fee schedules, and operate queues where permitted, but it should not determine what a dentist diagnosed or performed. See [What a DSO can and can't do](/concepts/model/what-dsos-can-and-cant-do).

## Choosing at each layer

**PMS.** Evaluate multi-location architecture, data-export rights, ERA auto-posting quality, and support for your chosen clearinghouse. See [Choose a PMS](/guides/billing/choose-a-pms).

**Clearinghouse.** Evaluate coverage for your payer mix, attachment integration, enrollment support, rejection reporting, and API access if you plan to build internal tools. See [The clearinghouses, compared](/reference/vendors/clearinghouse-comparison).

**Labor.** A single office may use an outsourced service or share a biller because it cannot support a full-time specialist. A larger group may benefit from centralized in-house billing and the visibility it provides. Compare that value with the staffing burden and any percentage-of-collections pricing. See [In-house billing vs outsourced RCM](/guides/billing/in-house-vs-outsourced-billing).

## The bundling question

Buying all layers from one vendor is simpler. It also means:

* **You cannot swap a weak layer.** A great PMS with a poor clearinghouse is a package deal.
* **Pricing is opaque.** Bundled pricing hides which component costs what.
* **Switching costs compound.** Leaving means replacing everything at once.
* **Your data may not be portable.** Read the export terms before signing.

For a single-location practice, bundling is often the right call. For a multi-entity DSO group that will operate across states and wants its own analytics, unbundling the clearinghouse specifically tends to pay for itself.

## Sources

1. Cal. S.B. 351 (2025); Or. S.B. 951 (2025). See the [legislation tracker](/reference/legal/dental-legislation-tracker).