An email arrives in the AP inbox from ar-midwest@mckesson.com asking about an unpaid surgical supply invoice. Another arrives the same afternoon from collections@mck-pharmaceutical.com asking about a different invoice — also unpaid, according to them. A third comes in later that week from a generic billing@mckesson.com address with a vendor statement attached covering 47 line items.
In your Enterprise Resource Planning (ERP) system, there are four separate McKesson vendor records: McKesson Medical-Surgical, McKesson Pharmaceutical, McKesson Patient Care Solutions, and a fourth legacy record from a distribution center consolidation that someone forgot to inactivate.
Each email is about a different vendor ID. Each requires a different lookup path in the ERP. And none of them are obviously connected to each other when they land in a shared inbox alongside 80 other messages from 40 other vendors.
This is the McKesson problem — and it's not unique to McKesson.
How Healthcare's Vendor Ecosystem Actually Works#
Healthcare distributes its purchasing across a relatively small set of very large distributors and an enormous tail of smaller, specialized suppliers. Companies like McKesson, Cardinal Health, Medline Industries, and Owens & Minor collectively handle a substantial portion of most hospitals' supply spending.
But "McKesson" isn't a single vendor in any operational sense. McKesson Corporation is a publicly traded company with dozens of operating subsidiaries, distribution divisions, and acquired entities. Each may have its own tax ID, its own contract terms, its own invoicing system, its own AR team, and its own preferred email address for collections.
When that complexity lands in a hospital's vendor master file, you typically end up with multiple vendor records for what is commercially one relationship. That's often a legitimate requirement — you may need to pay McKesson Medical-Surgical and McKesson Pharmaceutical on different terms because they're covered under different Group Purchasing Organization (GPO) contracts through Vizient or Premier. Split coding across different cost centers and contract compliance tracking requires those records to be separate.
The problem isn't having multiple vendor records. The problem is what happens when all of those entities email your AP inbox and your team has to figure out which vendor record each email belongs to — in real time, 50 to 150 times a day.
The Domain Disambiguation Problem#
Vendor email addresses in healthcare don't follow a simple rule. You cannot reliably determine which vendor ID an email belongs to just by looking at the sending domain.
Consider a few scenarios that aren't hypothetical:
A regional Cardinal Health distribution center in Texas uses a shared @cardinal.com domain but represents a different legal entity than the pharmaceutical division that uses the same domain. Your AP team sees @cardinal.com on both and needs to read the invoice numbers to figure out which vendor record applies.
A Medline subsidiary acquired three years ago still uses the acquired company's email domain while billing under the Medline entity's tax ID. The email says one thing; the invoice says another; the vendor master file record was created before the acquisition and may have outdated contact information.
A McKesson AR rep contacts you from a personal Microsoft account because their corporate email is down during a system migration.
Debra Richardson, whose work on vendor master file management is essential reading for AP teams, has written extensively about the challenge of validating vendor identity from email alone — noting that email addresses are neither unique to vendors nor reliably stable over time. In healthcare, this problem is amplified because the vendors with the most complex email patterns are also the vendors with the most invoice volume.
GPO pricing adds another layer: the same product purchased through a Vizient contract may arrive on an invoice from a different McKesson legal entity than the same product purchased off-contract. The contract ID, the vendor entity, and the email domain may all need to cross-reference each other for a single invoice to be matched correctly.
What This Looks Like Inside the ERP#
The complexity compounds once the AP rep is inside the ERP looking up the invoice. Here's a typical sequence:
The rep opens an email from remittance@mckesson.com asking about Invoice #45892-B. She searches her ERP — let's say Infor CloudSuite FSM — for that invoice number. Nothing comes up. She tries without the dash: 458928. Still nothing. She searches by vendor name, McKesson, and gets four results. She opens each record and looks for the invoice. It's in the third record — McKesson Medical-Surgical, which is mapped to a different vendor number than the one she initially searched.
The invoice is there, it's approved, it's scheduled for payment in five days. Responding to this email should take 90 seconds. Because of the vendor record disambiguation step, it took eight minutes — and that's a relatively clean scenario. The messier scenarios involve invoice numbers that don't match between the vendor's system and the hospital's, PO numbers referenced in the email that don't map to any PO in the ERP, or statements that mix invoices across multiple vendor entities on a single attachment.
The Monthly Statement: Where Complexity Peaks#
If individual inquiry emails expose this complexity one invoice at a time, monthly vendor statements reveal it in bulk. When a large distributor sends a statement of account, it may include invoices from multiple legal entities, different billing periods, invoices that have already been paid, invoices that are disputed, and invoices that legitimately aren't in the system because the goods haven't been received yet.
Reconciling a McKesson or Cardinal Health statement isn't a 30-minute exercise. For a health system with significant volume from these distributors, a thorough statement reconciliation can take half a day. And that's assuming the AP rep handling it has deep enough familiarity with the vendor's entity structure to recognize which line items belong to which vendor record.
For new AP team members — and given the turnover rates in healthcare AP customer service, there are always new team members — this kind of complex vendor reconciliation is a training challenge that rarely appears in formal onboarding documentation.
The Vendor Master File Is the Foundation#
The longer-term answer to this problem starts with vendor master file quality. Every legal entity that can send invoices and generate inquiries should have a distinct, accurate vendor record in the ERP, with correct tax IDs, correct remit-to addresses, and accurate email domains associated with each entity.
That's a project most AP teams know they need to do and haven't had time to finish. The inquiry volume consuming their days is, in part, a symptom of vendor master file gaps that were never closed — and closing those gaps requires time they don't have because they're handling inquiries.
In the short term, AP teams managing large, multi-entity vendor relationships benefit from building informal knowledge that doesn't live in any system: the cheat sheet of which Cardinal Health email domains map to which vendor IDs, the note in the vendor record flagging that Medline's pharmaceutical division uses a different billing entity than their surgical supply division, the institutional memory held by the senior rep who's worked with these vendors for eight years.
That institutional memory is fragile. When she leaves, it leaves with her.
Vendor Complexity Is a Feature of Healthcare, Not a Bug#
It would be convenient if the solution were simply "clean up the vendor master file and this problem goes away." It won't, entirely. The multi-entity, multi-domain complexity of large healthcare vendors is a structural feature of how these companies operate — and how healthcare supply chains work. GPO contracts, regional distribution, multiple lines of business: these aren't going away.
What AP teams can do is build systems — whether manual, procedural, or automated — that are designed for this complexity rather than surprised by it. Vendor communication automation that understands healthcare's multi-entity vendor landscape is one example — specifically designed to handle the domain disambiguation step that consumes minutes when done manually at scale. An AP operation built around the assumption that one email domain equals one vendor is going to struggle in an environment where that assumption is false 30% of the time.
The teams that handle large, complex vendor relationships most effectively tend to share one characteristic: they've stopped treating vendor disambiguation as an improvisation and started treating it as a documented, repeatable process. Whether that process runs on sticky notes, a spreadsheet, or something more sophisticated, having it at all is the starting point.
For a deeper look at the inquiry volume patterns that make multi-entity vendor management so demanding, see what your AP team isn't telling you — including how to estimate the cost of delayed responses from large distributors like McKesson and Cardinal Health.
Stop Relying on Institutional Memory
When your senior rep leaves, so does the mental map of which McKesson email domain maps to which vendor ID. Auxtri's vendor communication automation maintains that mapping systematically — across every entity and every email domain, for every vendor in your master file. Request a demo to see how it handles your most complex vendor relationships.
