> ## Documentation Index
> Fetch the complete documentation index at: https://mso.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, 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. Practices 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 835](/concepts/payments/understanding-835s).
</Warning>

## Steps

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

    1. **Reconcile PLB** on every 835 — sum of claim payments plus or minus PLB must equal the deposit
    2. **Scan for unexpected ACH debits** on every PC account, daily
    3. **Monitor the correspondence address** where demand letters arrive
  </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">
    **Payers demand refunds they aren't owed.** Common wrong reasons: a "duplicate" that was actually two distinct services; a COB determination based on stale information; a recoupment already taken once; an eligibility termination that was later reversed; a medical necessity determination contradicted by the record.

    Verify against your own records before paying. Refunding money you don't owe is a real loss and hard to recover.
  </Step>

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

    A dispute should include: the claim reference, the payer's stated reason, why it's incorrect, and the supporting documentation.

    For Medicare, understand your rights around **when recoupment may begin** relative to an appeal — the rules govern whether the money is taken while the appeal is pending. Confirm current CMS policy.
  </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.

    Practices that book recoupments as an expense, or ignore them entirely, overstate revenue. In a group producing investor reporting, that overstatement is exactly what a quality-of-earnings review normalizes, and finding it yourself is much better than having a buyer find it. See [How investors read MSO-PC financials](/concepts/finance/how-investors-read-mso-pc-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 Medicare and 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

Specific to encounters with both a payer payment and a patient payment.

If a patient wins a chargeback on their portion **and** the payer later recoups its portion, you are out both. Reconcile the **whole encounter** — patient payment, payer payment, chargeback, recoupment — rather than treating each in isolation. 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 affects that PC's ability to pay its management fee — handle the shortfall properly rather than by skipping the fee. See [Move money between PC and MSO](/guides/banking/move-money-mso-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 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                     |


## Related topics

- [Respond to payer audits and record requests](/guides/compliance/respond-to-payer-audits.md)
- [Report and return overpayments (the 60-day rule)](/guides/compliance/report-and-return-overpayments.md)
- [Respond to NPI identity theft](/guides/compliance/respond-to-npi-identity-theft.md)
- [Post payments from 835s](/guides/billing/post-payments-from-835s.md)
- [Reconcile payments daily](/guides/payments/reconcile-daily-payments.md)
- [The 835: how payers answer](/concepts/payments/understanding-835s.md)
- [Payment rails 101 (ACH, checks, wires, RTP, cards)](/concepts/banking/payment-rails-101.md)
- [835 file anatomy](/reference/edi/835-anatomy.md)
- [Group codes (CO, PR, OA, PI)](/reference/edi/group-codes.md)