Reassociate a Remittance

A remittance is matched to a claim by what the payer reported. When the payer’s control number points at the wrong claim, or at none, reassociating moves it to the right one.

Before You Start

You need the User role, and you need to know which claim the payment actually belongs to. Reassociating moves ledger entries, so guessing is worse than leaving it.

Move It

1. Open the remittance.
2. On the Claim card, open the card’s menu.
3. Select Reassociate Claim. It is not offered on a superseded remittance or one returned to the payer.
4. In Target claim, search by claim number or patient name.
5. Select the correct claim from the results.
6. Select Continue. On a posted remittance, the confirmation shows the payment reversed on the current claim and re-posted on the new one. On a held or reversed remittance, only the record moves; a held one is checked again on the new claim.
7. Select Reassociate & Re-post, or Reassociate when only the record moves. Both claims’ balances are recalculated.

Result: the remittance and its entries move to the chosen claim. Both claims’ balances update.

What Reassociating Will Not Do

ClaimPod refuses to move a remittance onto the claim it is already on, and to move a posted payer takeback, whose entries offset an adjudication on the current claim. A refusal reads Couldn't reassociate the remittance - followed by the reason, and ends No entries moved. That is worth trusting literally: when a reassociation fails, the ledger is untouched rather than half-moved.

When the remittance moves off an import stub that no other remittance answers, the stub’s charge is reversed and the stub is voided. The confirmation says so.

Tip

A remittance that matched nothing at all arrives as an unmatched item rather than posting against a guess. Reassociating is how it finds its home, unless the money is not the practice’s at all: then resolve it as Not Ours - Return to Payer in its review item.

Related: Work a Remittance Review Item · Remittances