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

# Handle recoupments and takebacks

> Reading takebacks in 835 PLB segments, offset versus demand letters, dispute windows across dental payers and Medicaid dental administrators, negotiating repayment, and the accounting treatment that keeps revenue honest.

A **recoupment** is a payer recovering money it previously paid you. It arrives either as a **demand letter** or, more often, silently as an **offset**, money missing from a deposit with no corresponding claim-level entry. Dental groups that don't reconcile PLB segments don't notice until the books don't tie.

## Prerequisites

* 835 posting that surfaces PLB segments
* Daily reconciliation, see [Reconcile payments daily](/guides/payments/reconcile-daily-payments)
* Access to the original claim and remittance for the disputed payment

## How recoupments arrive

| Mechanism                | What you see                                                | Detection                                        |
| ------------------------ | ----------------------------------------------------------- | ------------------------------------------------ |
| **PLB offset in an 835** | A `WO` provider-level adjustment reducing the total payment | Only if you reconcile PLB                        |
| **ACH debit**            | Money withdrawn from the PC's account                       | Only if you scan for unexpected debits           |
| **Demand letter**        | A written request to repay                                  | Arrives by mail, to a monitored address, ideally |
| **Prepayment offset**    | Future claims paid at reduced amounts                       | Reconciliation variance                          |

<Warning>
  **The PLB segment is the one that hides.** `WO` in a PLB reduces the deposit with no claim-level entry. If your posting ignores PLB, your books overstate revenue, your reconciliation never ties, and the recoupment is invisible. See [The claim lifecycle](/concepts/payments/claim-lifecycle).
</Warning>

## Steps

<Steps>
  <Step title="Detect it">
    Three controls catch recoupments:

    1. **Reconcile PLB** on every 835. The sum of claim payments, adjusted for PLB entries, must equal the deposit.
    2. **Scan for unexpected ACH debits** on every PC account, daily
    3. **Monitor the correspondence address** where demand letters arrive for each payer and Medicaid dental benefit administrator
  </Step>

  <Step title="Identify what it relates to">
    A recoupment should be traceable to a specific prior claim. Find: the original claim, the original remittance, and the payer's stated reason.

    If you cannot identify what a takeback relates to, **ask the payer in writing.** An unexplained recoupment is not one you should accept.
  </Step>

  <Step title="Verify it's actually owed">
    Review the demand before assuming the payer's calculation is correct. Common errors include a COB determination based on stale dual-coverage information, two distinct services treated as duplicates, an annual-maximum recalculation that uses the wrong date, a recoupment already taken once, a reversed eligibility termination, or a necessity determination contradicted by the radiographs.

    Verify the demand against your records before paying. Also identify what the letter is actually asserting. A payer that reprocesses a crown under a lower-cost alternate benefit may be raising a downgrade issue rather than a recoupment issue. See [Denials vs downgrades](/concepts/payments/denials-vs-downgrades).
  </Step>

  <Step title="Dispute within the window if it's wrong">
    Recoupments have dispute or appeal windows, set by contract for Delta Dental and the other commercial dental payers, and by state regulation or the DBA's provider manual for Medicaid. They are frequently **shorter** than standard claim appeal windows.

    A dispute should include the claim reference, the payer's stated reason, the basis for disagreement, and supporting documentation. Include films and periodontal charting when medical necessity is at issue.

    Many states also have prompt-pay or takeback statutes limiting how far back a commercial payer may recoup; whether yours does is a contract-and-state question worth asking counsel once, then documenting.
  </Step>

  <Step title="Negotiate repayment terms if the amount is large">
    A large recoupment taken as a lump-sum offset can be a cash-flow event. Payers will often agree to an installment plan or a capped offset percentage against future payments. Ask before the offset starts, not after.
  </Step>

  <Step title="Account for it properly">
    **A recoupment reduces revenue in the period it is recognized; it is not an expense.**

    Booking recoupments as an expense, or omitting them, can overstate revenue. A quality-of-earnings review may reclassify the amounts, so reconcile the treatment before preparing investor reports. See [How investors read DSO financials](/concepts/finance/how-investors-read-dso-financials).

    Where a recoupment is disputed and material, discuss the accounting treatment with your CPA. A liability may be appropriate before the outcome is known.
  </Step>

  <Step title="Root-cause it">
    Recoupments cluster. A payer recouping one claim for a coding issue will find the others. Tag the cause, check whether it applies to other claims, and fix the process.

    If the root cause implies **other claims were also overpaid**, you have identified an overpayment, and for Medicaid that starts the **60-day report-and-return clock**. See [Report and return overpayments](/guides/compliance/report-and-return-overpayments).
  </Step>
</Steps>

## The double-jeopardy case

Apply this control to encounters with both payer and patient payments, which are common in dentistry.

If a patient wins a chargeback and the payer later recoups its portion, both payment sources disappear. Reconcile the **whole encounter**, including the patient payment, payer payment, chargeback, and recoupment. See [Respond to a chargeback](/guides/payments/fight-a-chargeback).

## Multi-entity considerations

Recoupments hit the **PC** that received the original payment. In a group with eleven accounts and no consolidated view, an unexplained debit in one PC can sit for weeks.

* Reconcile **per entity**, daily
* Route demand letters to a monitored address per entity
* A recoupment in one PC may affect that entity's ability to pay its management fee. Address the shortfall under the agreements rather than informally skipping or changing the fee. See [Move money between PC and DSO](/guides/banking/move-money-dso-pc).

## Verify it worked

* [ ] PLB reconciled on every 835
* [ ] Unexpected ACH debits scanned daily, per entity
* [ ] Every recoupment traced to a specific claim
* [ ] Unexplained takebacks queried in writing
* [ ] Validity verified before accepting
* [ ] Disputes filed within the window
* [ ] Large recoupments negotiated to installments where possible
* [ ] Recorded as a reduction of revenue, not an expense
* [ ] Root cause tagged; other affected claims assessed
* [ ] 60-day analysis triggered where a broader Medicaid overpayment is implied

## Common failure modes

| Failure                                  | Consequence                                   |
| ---------------------------------------- | --------------------------------------------- |
| Ignoring PLB                             | Overstated revenue; reconciliation never ties |
| Not scanning for ACH debits              | Weeks of unexplained cash movement            |
| Accepting a recoupment without verifying | Paying money you don't owe                    |
| Missing the dispute window               | Unrecoverable                                 |
| Booking as an expense                    | Overstated revenue                            |
| Not root-causing                         | The payer finds the rest of them              |
| Ignoring the 60-day implication          | False Claims Act exposure                     |