Investigating a Remittance Pattern With a Practice

A practice manager calls to say the remittance data does not add up, and the pressure lands on you to explain it right there on the phone. Resist that pull. This conversation goes better when you treat the complaint as something to investigate, not something to defend. Pull specific examples, name the actual owner of the answer, and give the practice a date they can hold you to.

Why This Conversation Goes Wrong

Remittance complaints sound like billing arguments, but they are usually data questions wearing a billing costume. A practice sees adjustment codes that do not match what they expected, or a payment that looks smaller than the contract implies, and they assume someone made a decision behind closed doors. Your instinct is to reassure them fast. You start explaining what the codes probably mean, or you defend the payer's system in general terms, and neither response is grounded in the actual records in front of the practice.

This is where trust breaks. A general explanation, even a correct one, does not answer a specific complaint. If Rae says three remittances used different labels for what looks like the same service, telling her that adjustment codes vary by claim type is true and useless. She needs to know what happened in those three cases, not how the system works in theory. Worse, if you start interpreting what a contract clause means on the spot, you have wandered into territory that belongs to the contracting team, and you may end up contradicting them later. The practice remembers that contradiction far longer than they remember your good intentions.

How to Prepare Before the Call

Before you sit down with the practice, get the raw material in hand. Ask for the specific remittances in question, the dates, the reference numbers, and the field that caused the confusion, whether that is an adjustment code, a payment amount, or a denial reason. Vague complaints turn into a useful review only once they are attached to real records.

Know your own boundaries going in. You can describe how a claim will be reviewed and who will review it. You cannot decide what a contract term means, and you should not guess at it out loud, even to be helpful. Identify ahead of time who owns claims operations and who owns contract language, so you are not searching for names while the practice is on the line.

It helps to have a simple template ready for logging the issue, one page with the practice's examples, the specific question each one raises, and a single name attached as the accountable owner. Provider relations managers run into this same structure in other conversations too. The approach in Creating a Reliable Roster Update Conversation works the same way, gather the specifics first, assign one owner, and commit to a date, rather than trying to resolve everything in the first exchange.

What to Say

Rae, the office manager, opens with the complaint. "Three of our remittances show different adjustment labels for what looks like the same procedure. My billing staff has spent hours trying to guess what changed between them."

Morgan, the provider relations manager, does not try to explain the codes on the spot. "Send me those three examples today, with the dates and reference numbers. I want to separate the label question from the payment question. Our claims operations lead can pull the actual records and tell us what happened in each case. If there turns out to be a contract language question buried in there, that goes to our contracting team, since that decision is not mine to make."

Rae is not fully satisfied yet. "I understand, but I need an answer this week. My staff cannot keep guessing on every remittance that comes in."

Morgan gives her something concrete instead of a promise. "I will send the three examples to claims operations today. I will update you by Thursday with the confirmed owner and the next step, even if the review is still open at that point. You will hear from me either way."

Notice what Morgan did not do. She did not guess at the labels, she did not promise a fix she could not control, and she did not let the deadline pass in silence. She gave Rae a process and a date, which is a different thing from an answer, but it is something Rae can actually rely on.

Mistakes to Avoid

A few habits undo this kind of review even when your intentions are good.

1. Guessing at what a contract clause or adjustment code means instead of routing the question to the team that actually owns it.
2. Promising a fixed outcome, like a corrected payment, before anyone has verified the record.
3. Logging the issue without naming a single accountable owner, which lets it drift between departments with no one responsible for the next step.
4. Waiting until the deadline to send any update, even when the review is still open. A short status update on time builds more trust than a complete answer that arrives late.
5. Treating every remittance complaint as the same complaint. Each example can raise a different question, and lumping them together slows the review down.

How to Practice and Score This Conversation

This conversation is hard to get right the first time you face it live, because the pressure to reassure the practice is strong and the boundary between your role and the contracting team is easy to blur under pressure. Rehearsing it first changes that. Have a colleague play the frustrated office manager and push back the way Rae does, asking for a firm answer before you have one. Notice whether you hold the line on routing the contract question elsewhere, or whether you start guessing to make the conversation feel resolved.

A manager scoring this practice run should check for specific things. Did you ask for dates and reference numbers in the first minute, rather than accepting a general complaint. Did you avoid making any contract determination yourself. Did you name one accountable owner instead of a department. Did you give a specific date for your next update, rather than a vague timeframe like soon or shortly.

DealSpeak's library of Healthcare practice conversations includes scenarios built around exactly this kind of dispute, so you can run the exchange several times with different pressure points before you face it with a real practice. The same discipline applies even when the complaint turns out to be about something else, as in Resolving a Practice's Missing Training Material Request, where the fix again starts with confirming the real question before answering it.

A practice that sees a disciplined review, with real examples, a named owner, and a date they can count on, tends to calm down even before the underlying issue is fixed. The relationship survives the wait because the process was visible. That visibility is the actual product of this conversation, not the final answer.

You can rehearse this exact conversation in the Healthcare practice conversations library before it happens for real. When you have this one down, read Creating a Reliable Roster Update Conversation next.