Why Vendor Portals Failed Healthcare AP (And What That Tells Us About Vendor Behavior)

The pitch is compelling. Build a portal where vendors can log in, check invoice status themselves, and stop emailing your AP team. You eliminate the inquiry volume at the source. Your team gets their time back. Everyone wins.

Healthcare AP departments have been sold this vision for the better part of a decade. The results — measured honestly, not through optimistic implementation reports — have been a consistent disappointment. Portal adoption in healthcare typically lands between 15% and 25% after twelve months, even after significant investment. That means 75 to 85 cents of every dollar spent on portal implementation delivers no reduction in inquiry volume whatsoever.

Understanding why portals fail in healthcare isn't just a retrospective exercise. It explains something fundamental about vendor behavior — and it should inform every vendor communication decision you make.

The Vendors Who Send the Most Inquiries Don't Use Portals#

Here's the core problem with the portal model: it asks vendors to change their behavior. And the vendors who generate the most inquiry volume are precisely the ones least likely to change.

McKesson, Cardinal Health, Medline, Owens & Minor — the large healthcare distributors that collectively represent a significant share of most hospital AP inquiry volume — each have dedicated accounts receivable teams. These are professional AR operations with established workflows, performance metrics, and their own systems. They're already managing collections across hundreds of hospital customers. They are not logging into 50 different hospital portals to check invoice status. They have their own ERP. They have their own AR aging reports. They contact you because their system flagged an unpaid invoice, and email is the fastest path to a response.

Large healthcare vendors will continue to email your AP inbox regardless of whether a portal exists. The portal doesn't change the math for them.

On the other end of the spectrum, small and mid-sized vendors — the solo-practice consultant, the regional medical equipment supplier, the local facilities contractor — often lack the bandwidth to manage yet another vendor portal login. They're already drowning in portals from customers across multiple industries. For the ones who try to adopt, the typical experience is: visit the portal, forget the password, request a reset, give up, send an email. Your inbox gets the email.

The Sunk Cost Trap#

One reason the portal failure doesn't get named openly is that significant investments have already been made. Admitting the portal hasn't worked means admitting to a CFO or CIO that $300,000 and eighteen months of implementation effort didn't solve the problem.

So instead, success gets defined down. The 20% adoption rate gets framed as "early traction." The vendors who do use the portal — which, as noted, tend to be the lower-volume ones who weren't causing much inquiry volume to begin with — become the success story. The fact that AP inquiry volume hasn't actually declined gets attributed to other factors.

Debra Richardson, an AP consultant with 20 years of experience at companies including GM and Aramark, wrote a three-part series on vendor self-registration portals that's worth reading if you're evaluating this decision. Her framework for measuring portal success is instructive: adoption rate alone is not a valid metric. What matters is whether inquiry volume — specifically inquiry type and frequency from the vendors who adopted — went down. In her experience, portal adoption by occasional vendors who were already low-touch doesn't move the needle on workload.

The honest metric for portal ROI is: did the vendors who were generating the most work adopt the portal and stop emailing? In healthcare, that answer is almost universally no.

What "Meeting Vendors Where They Are" Actually Means#

The lesson isn't that technology can't solve the inquiry problem. It's that the right technology meets vendors where they are, rather than asking vendors to come somewhere else.

Vendors email. That's their workflow. It works across every customer relationship they have. It requires no new logins, no new software, no behavior change at all. For a McKesson AR rep managing a book of 200+ hospital accounts, email is the lowest-friction communication channel available.

This is worth sitting with for a moment, because it reframes the entire problem. The AP inquiry burden isn't caused by vendor behavior that needs to be corrected. It's caused by a mismatch between how vendors communicate (email, at volume, expecting timely responses) and how AP teams are equipped to handle that communication (shared inboxes, manual ERP lookups, one email at a time).

The question isn't "how do we get vendors to stop emailing?" The question is "how do we handle the emails vendors are already sending faster and more systematically?"

That second question is the foundation of vendor communication automation — and it's a far more productive frame than waiting for vendor behavior to change. Auxtri's features are built around exactly this model: meeting vendors in email, where they already are.

Adoption Metrics That Hide Poor Outcomes#

One more dynamic worth naming: portal adoption metrics can be technically accurate while being practically meaningless.

Consider a health system with 2,000 active vendors. Of those, 150 vendors account for roughly 80% of invoice volume and 85% of inquiry volume — this kind of concentration is typical in healthcare, driven by the dominance of large distributors and GPO-contracted suppliers. The remaining 1,850 vendors are smaller, less frequent, and generate modest inquiry volume individually.

A portal that achieves 25% adoption — 500 vendors — may have achieved nearly all of that adoption in the low-volume tail. From a raw adoption percentage perspective, 25% sounds like progress. From an inquiry volume reduction perspective, it may represent a 3% to 5% reduction in actual workload.

This isn't hypothetical. It's the pattern that plays out repeatedly when portal adoption data is cross-referenced with inquiry volume data. The vendors who generate the work don't adopt. The vendors who adopt weren't generating much work.

A More Honest Evaluation Framework#

If your organization is considering a vendor portal investment, or evaluating whether an existing portal investment is delivering value, the questions to ask are:

Which vendors account for the top 50% of your inquiry volume? Pull 90 days of email data from your AP inbox. Which vendor domains are most represented? Which vendor names appear most frequently?

Have any of those high-volume vendors adopted your portal? Be specific. "Adoption" means they have logged in and used it to check invoice status at least once in the past 30 days.

Has your inquiry volume from those vendors declined since portal launch? Email count from key domains over time is the most honest measure of whether the portal is working.

If the high-volume vendors aren't using the portal, and your inquiry volume hasn't declined, the portal hasn't solved the problem — regardless of what the adoption percentage says in the vendor self-service report.

That's not a failure of your implementation team or your change management approach. It's a reflection of the structural reality that large, sophisticated vendors in healthcare operate their AR functions in ways that are fundamentally incompatible with the self-service portal model.

The inquiry backlog doesn't shrink because you built a door vendors won't walk through. It shrinks when you improve how you handle what's already coming in through the door they're using.

Vendor communication automation takes exactly this approach — automating the lookup-and-respond cycle for emails vendors are already sending, rather than trying to change behavior that has remained consistent for over a decade. For healthcare AP teams evaluating their options, the invisible backlog post provides the cost framework for making this argument to leadership.