Cleaning Up Account Data Before a Health System Contract Review

A health system contract review turns into an argument about facts nobody agreed on ahead of time. The site list procurement has on file does not match yours. The service case history has gaps. Nobody can say with confidence which equipment is still installed and which got swapped out two years ago. As the strategic account manager, you are the person in the room who is supposed to own this record. When it does not hold up, the review stalls before anyone gets to the terms that actually matter.

Why this conversation goes wrong

Most account managers walk into a contract review treating the account record as settled. It is not. Health systems merge departments, open outpatient sites, retire equipment, and rotate procurement staff far faster than any vendor record gets updated. By the time renewal season arrives, your system of record and the customer's are usually telling two different stories.

The instinct when a customer flags a mismatch is to explain it away or fix it on the spot. Both reactions cause damage. Explaining it away signals that you are not taking their record seriously, and procurement will not send a contract to legal built on data they do not trust. Fixing it on the spot means you are guessing, often about things outside your authority, like whether a site is covered under the current agreement or whether an open service case affects renewal terms. A wrong guess repeated in a contract document is worse than an open question.

The result is a conversation that feels adversarial when it does not need to be. The customer is not attacking you. They are telling you their record does not match yours, and they need that resolved before they can move forward. Treat it as a data problem, not a conflict, and the tone of the whole review changes.

How to prepare

Do the reconciliation work before you sit down with the customer, not during the meeting. Pull four things ahead of time. Get your account record, the current signed agreement, the full list of open and recently closed service cases, and any written description the customer has given you of their own contracting process. Lay them side by side and look for disagreements in site addresses, contact names, equipment counts, and contract dates.

Do not try to resolve every disagreement yourself. Some of what you find belongs to other owners. Your service team should confirm equipment records, since they touch the machines and know what got installed or removed. Your contracts or legal team should confirm what the signed agreement actually covers. You should confirm the commercial history and the account relationship. Sort each discrepancy into a lane before you talk to the customer, so you are not promising answers you cannot deliver.

This same discipline shows up in Requesting Data for an Account Review With the Right Ownerswhich covers how to route a data request to the person who actually controls the answer instead of asking whoever is easiest to reach. The same logic applies here. A reconciliation list with the right owner attached to each line moves faster than one you try to close out alone.

What to say

Open by naming the mismatch yourself if you found it first, or by acknowledging it plainly if the customer raises it. Do not soften it into vague language. State what does not match and what you plan to do about it.

Procurement director Hannah opens the meeting by saying, "Your site list does not match ours, and I cannot send this to legal until it does." Account manager Victor responds, "Thank you for catching that before we went further. I do not want to guess which record is current, so let me build a reconciliation list instead. Could your team tell me which system you treat as the source for active locations? Our service lead will confirm the equipment records on our side, and I will bring back every difference with the source named next to it." Hannah agrees, then adds that a new outpatient site opened after the last amendment was signed, which explains part of the gap.

Notice what Victor does not do. He does not argue that his list is right. He does not promise a corrected list by the end of the call. He names a process, assigns ownership on both sides, and sets an expectation for what comes back. That is the entire move. When Hannah raises the new outpatient site, Victor treats it as new information to log, not a problem to solve in the room. "That is helpful. I will add it to the reconciliation list as a confirmed addition and get it into our record once we have the site details." The conversation stays productive because neither side is pretending to have authority they do not have.

Mistakes to avoid

The biggest mistake is guessing out loud. Saying "I believe that site is covered" in a room with procurement and legal turns a guess into something people will act on. If you do not know, say you do not know and name who will confirm it.

A second mistake is treating every discrepancy as equally worth arguing about. Some differences are trivial, like a contact name that changed after someone left. Others affect coverage and cost. Sort by what actually matters to the contract terms and spend your attention there.

A third mistake is closing the loop too slowly. A reconciliation list that sits for three weeks costs you the trust you just built by handling the meeting well. Set a date for when the customer will hear back, and hit it.

A fourth mistake is doing the reconciliation entirely in private and handing the customer a finished answer. That looks efficient, but it removes them from a process they need to trust. Involve them in confirming their own source data, the way Victor did by asking Hannah which system her team treats as authoritative.

If your account also touches training or education programs tied to the contract, the same ownership mapping applies to those relationships. Mapping Education Owners Across a Health System walks through identifying who actually controls those programs, which often turns out to be a different person than whoever signs the commercial contract.

How to practice and score it

Build a sample account record with three planted conflicts, something like a mismatched site address, an equipment count that is off by one, and a contact who no longer works there. Practice opening the conversation, naming the conflicts without guessing at the answers, and assigning an owner and a source to each one.

Write the follow up note you would actually send. It should name the specific field in question, the source you are treating as current, the owner responsible for confirming it, and exactly what you are asking the customer to do. A manager reviewing that note should check for three things. Does it state the conflict plainly instead of hedging around it. Does it give the customer something concrete to confirm rather than a vague request for input. Does it avoid stating an unconfirmed fact as if it were settled.

This is the kind of scenario where rehearsal actually changes the outcome, because the skill is not know your product, it is stay disciplined about what you do and do not know in front of a customer. Medical Devices practice conversations on DealSpeak let you run this exact exchange against an AI counterpart and get scored on whether you held that line.

Clean account data is not a formality before the real conversation starts. It is what makes the real conversation possible. Get the reconciliation right, and the contract review becomes a discussion about terms, not a dispute about facts.