> ## 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.

# Post payments from 835s

> Auto-posting setup for dental remittances, separate adjustment codes for write-offs versus downgrades versus limitations, the three-way triage, PLB takebacks, and balancing every remittance to its deposit.

**Posting** records what the payer paid, what the practice writes off, and what the patient owes. Dental benefit rules such as downgrades, frequency limits, and annual maximums often create patient balances. Correct posting moves those amounts to the patient ledger instead of losing them in a write-off.

## Prerequisites

* ERA enrollment complete and pointing at your current clearinghouse
* Auto-posting configured in the PMS
* Access to the bank account the EFTs land in
* Fee schedules loaded per payer, including leased-network variants, so underpayments are flagged

## Set up three separate adjustment codes

Before configuring auto-posting, create distinct adjustment types in the PMS. One generic "insurance adjustment" code destroys the information you need later:

| Adjustment type                    | What it records                                                                                                         | Where the money goes                                                                      |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| **Contractual write-off**          | The gap between your full fee and the PPO allowed amount                                                                | Written off because the participation agreement does not permit billing it to the patient |
| **Downgrade / LEAT difference**    | The plan paid the alternate benefit (composite priced at the amalgam allowance, porcelain crown at the metal allowance) | Patient ledger, when your contract and signed financial consent permit                    |
| **Frequency / maximum limitation** | Benefit exhausted, such as a third cleaning in the year or an annual maximum reached                                    | Patient ledger                                                                            |

Separate codes let statements explain why the patient owes a balance, keep benefit-design reductions out of the [denial queue](/guides/billing/work-the-denial-queue), and preserve accurate write-off reporting. PPO write-offs can run 30–45% of gross production at many practices. Mixing downgrades and limitations into that figure can distort contract analysis and [acquisition diligence](/guides/growth/acquire-a-dental-practice).

## Steps

<Steps>
  <Step title="Configure auto-posting properly">
    Most systems auto-post clean lines. Configure:

    * **Adjustment mapping** that assigns each CARC and group-code combination to one of the three adjustment types above
    * **Write-off rules** that write off CO adjustments and move PR adjustments to the patient ledger
    * **Denial routing** that sends \$\$0-paid lines with denial CARCs to the denial queue rather than a write-off
    * **Underpayment flagging** when the allowed amount is below the contracted rate
    * **Exception thresholds** that define what a person must review

    Test group-code mapping carefully. Posting a PR amount as CO can prevent a valid patient balance from reaching the ledger. Posting a CO amount as PR can result in billing a patient for a contractual write-off, contrary to the participation agreement. Test the mapping with a real 835 before going live. See [Group codes](/reference/edi/group-codes).
  </Step>

  <Step title="Triage every reduced line three ways">
    When the 835 pays less than billed, there are three situations, and each demands a different response:

    | Situation                                | How it reads on the 835                                                                                                    | Action                                                                                                                                     |
    | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
    | **True denial**                          | \$\$0 paid with a denial CARC, such as for a missing attachment, missing required preauthorization, or non-covered service | Route to the [denial queue](/guides/billing/work-the-denial-queue) and work it                                                             |
    | **Downgrade (alternate benefit / LEAT)** | Paid at the alternate procedure's allowance, with a remark code identifying the alternate benefit                          | Where the contract and consent permit, post the difference to the patient ledger with the downgrade code rather than appealing<sup>1</sup> |
    | **Frequency or maximum limitation**      | Reduced or unpaid with a benefit-maximum or frequency CARC, typically under group code PR                                  | Post an allowed patient balance to the ledger with the limitation code                                                                     |

    Read the group code before posting a downgrade difference. Some plans place it in PR, while others place it in CO. If the group code and the contract's LEAT clause appear to conflict, review the contract before billing the patient. See [Denials vs downgrades](/concepts/payments/denials-vs-downgrades) and the [CARC reference](/reference/edi/carc-codes).
  </Step>

  <Step title="Post daily, not weekly">
    Same-day posting keeps the patient ledger current, surfaces denials while the appeal window is long, and puts downgrade balances on a statement while the patient still remembers the visit.
  </Step>

  <Step title="Work the exception queue">
    What lands there and what to do:

    | Exception                      | Action                                                                           |
    | ------------------------------ | -------------------------------------------------------------------------------- |
    | **Unmatched claim**            | Find the claim; often a claim number or patient account mismatch                 |
    | **PLB takeback (WO)**          | Identify the original overpayment; verify it's legitimate; record the recoupment |
    | **PLB interest (L6)**          | Post as interest income, not as claim payment                                    |
    | **Forwarding balance (FB)**    | Note it; it will appear on a future remittance                                   |
    | **Reversal (CLP02 = 22)**      | A previously posted payment is being unwound; reverse the posting                |
    | **Secondary transfer (OA-23)** | Route to the secondary dental plan                                               |
    | **Unfamiliar CARC**            | Look it up before posting, do not guess                                          |
    | **Underpayment flag**          | Compare to the contracted rate; aggregate before disputing                       |

    One dental underpayment pattern is a discount applied by a payer you did not contract with. This may reflect **network leasing** rather than a posting error. Identify the contract and network behind the discount before accepting the rate. See [Network leasing](/concepts/payments/network-leasing).
  </Step>

  <Step title="Balance every remittance to its deposit">
    Sum of claim payments, plus or minus PLB, equals the EFT amount.

    **One 835 is not one bank deposit.** Deposits aggregate remittances; remittances split across deposits; PLB shifts totals. Match using the **TRN reassociation trace number**, not by hunting for matching dollar amounts. Amount-matching works until two payers send similar amounts on the same day, then it produces silently wrong postings.
  </Step>

  <Step title="Route patient balances into the statement cycle">
    Move allowed PR amounts, including coinsurance, downgrade differences, and exhausted-maximum balances, to the patient ledger. Send statements within days of adjudication rather than waiting until month-end. See [Run patient statements and balances](/guides/billing/manage-patient-statements).
  </Step>

  <Step title="Queue denials, don't write them off">
    Send each \$\$0-paid line with a true denial CARC to the denial queue with a root-cause tag. Keep downgrades and limitations out of that queue. See [Work the denial queue](/guides/billing/work-the-denial-queue).
  </Step>
</Steps>

## Paper EOBs

Smaller payers, some Medicaid dental benefit administrators, and union or trust plans may still send paper explanations of benefits. Paper EOBs require manual posting, which increases the risk of group-code and downgrade errors.

Treat each paper-paying payer as an action item: complete their ERA enrollment. The labor saving is real and the error reduction is larger.

## Virtual credit cards

Payers that send single-use card numbers instead of EFT cost you 2–3% of the payment in processing fees.

* Key them **promptly** because VCCs expire
* Record the payment **gross**, with the processing fee as a separate expense, not netted
* **Convert the payer to EFT.** Complete their EFT enrollment and ask in writing to opt out of the card program. See [Paper checks and virtual credit cards](/concepts/payments/paper-checks-and-vcc).

## Multi-entity posting

In a multi-PC dental group:

* Each PC's 835s post to that PC's ledger
* Each PC's EFTs land in that PC's account
* Reconciliation is **per entity**

A misconfigured ERA receiver or EFT enrollment can route one entity's remittances or payments to another. That is a commingling problem, not just a posting error, and it is hard to detect if nobody reconciles per entity. See [Set up EDI, ERA, and EFT](/guides/enrollment/set-up-edi-era-eft).

## Verify it worked

* [ ] Three adjustment codes live: contractual write-off, downgrade, limitation
* [ ] Group code mapping tested with a real 835
* [ ] Denial routing sends \$\$0 lines to the queue, not to write-off
* [ ] Downgrades and limitations post to the patient ledger, never to the denial queue
* [ ] Underpayment flagging active against loaded fee schedules
* [ ] Posting happens daily
* [ ] Exception queue worked daily
* [ ] Every remittance balanced to its deposit via TRN
* [ ] PLB handled explicitly
* [ ] Patient balances routed to statements within days
* [ ] Paper EOB payers being converted to ERA
* [ ] VCC payers being converted to EFT
* [ ] Reconciliation performed per entity

## Common failure modes

| Failure                               | Consequence                                                                                        |
| ------------------------------------- | -------------------------------------------------------------------------------------------------- |
| PR posted as CO                       | Downgrade and maximum balances may never reach the patient ledger, creating recurring revenue loss |
| CO posted as PR                       | Balance-billing patients for contractual write-offs; contract breach                               |
| One generic adjustment code           | Write-off analysis meaningless; fee negotiation and acquisition models blind                       |
| Downgrades routed to the denial queue | Appeal capacity wasted on benefit design                                                           |
| Denials auto-written-off              | Recoverable revenue silently lost                                                                  |
| PLB ignored                           | Books overstate revenue; reconciliation never ties                                                 |
| Matching by amount instead of TRN     | Silently wrong postings                                                                            |
| Weekly posting                        | Stale ledger; late denial discovery; stale statements                                              |
| Accepting VCCs passively              | 2–3% lost permanently                                                                              |
| No per-entity reconciliation          | Cross-entity routing errors undetected                                                             |

## Sources

1. ADA, [Least expensive alternative treatment (LEAT) clause](https://www.ada.org/resources/practice/dental-insurance/least-expensive-alternative-treatment-clause). The ADA recommends informing patients before treatment when LEAT may apply.
