Getting Coupa Working at a Cancer Center Isn't For the Faint-Hearted
I spent about 18 months working with Memorial Sloan Kettering Cancer Center's procurement team as they migrated from a legacy SAP purchase order system into Coupa. Not that I was some vendor hero — I was just the person who had to clean up the mess when the cutover went sideways. The short version is that Coupa can absolutely transform how a cancer center manages spend, but only if you stop treating it like a software install and start treating it like a change management nightmare that occasionally has software attached to it. Before the Coupa deployment, MSKCC was running roughly 40,000 purchase orders a month. A lot of those were for things like imaging contrast media, surgical supplies, radiopharmaceuticals, and lab reagents. The rest were standard goods and services — IT equipment, facilities maintenance, janitorial contracts, consultants. Most of the POs came from department heads who had been given a blanket corporate card or a standing purchase limit and then told to figure it out themselves. There was no catalog discipline. There was no spend visibility until the monthly AP close, and even then the reports were 60 days old because finance was still waiting on invoice receipts to match three-way. The Coupa platform itself is actually decent for what it does. It's cloud-based, it has a decent procurement catalog engine, it integrates with most ERPs through prebuilt connectors, and its invoice matching logic is more flexible than what most people are running. The problem isn't the tool. The problem is that cancer centers have procurement needs that look nothing like a standard enterprise setup.
Here's what most people miss when they're evaluating Coupa for a hospital system: the item catalogs. In a typical enterprise, you set up a catalog with approved vendors and SKUs, you push it out, and everyone buys from it. At a cancer center, your catalog needs to account for clinical trial supplies, investigational drugs that can only come through specific channels, radiopharmaceuticals with short half-lives that require special ordering protocols, and surgical implants where the surgeon literally names the brand they want on the day of surgery. None of this fits neatly into a standard Coupa catalog. You end up building custom form fields, approval workflows, and exception codes that take months to configure correctly. I learned this the hard way. We were about two weeks into go-live when the radiation oncology department submitted a requisition for a specialized brachytherapy applicator through the new system. The Coupa workflow routed it to the procurement manager for approval, who approved it, and then it went to the ERP for PO generation. The PO went out. The supplier confirmed. The item arrived. And then the radiation safety officer flagged it because the requisition hadn't captured the NRC tracking number that's legally required for certain radioactive sources. The supplier couldn't ship without it. The whole order stalled for six weeks because nobody had built that field into the requisition form. The fix was straightforward in hindsight but expensive in practice. We had to add conditional logic to the requisition builder so that any line item tagged with the appropriate UNSPSC code — radiation therapy supplies, specifically the ones under the 32131400 category — would trigger a secondary data capture form requiring NRC license numbers, expiration dates, and the designated radiation safety officer's approval. That alone took us another four weeks of configuration and testing. And we weren't even done yet.
There are other areas where the system showed its limits. Clinical trial procurement is a mess. Every trial has its own sponsor, its own supply chain requirements, its own budget coding structure. Coupa doesn't natively support clinical trial budgets as a funding source. You have to build workarounds using custom cost centers and custom approval chains, and even then, the reporting side gets ugly because Finance wants to see trial spend rolled up by study number, not by cost center. We ended up writing a custom integration between Coupa and our clinical trial management system to pull that data together, which required about three months of API development work that wasn't in the original project timeline. Another thing nobody talks about is the supplier onboarding friction. Coupa's Supplier Network is meant to solve the problem of chasing down vendor W-9s, banking details, and compliance documentation. In practice, it works fine for large suppliers who already have Coupa accounts or are willing to create them. It does not work for the smaller specialty vendors that cancer centers rely on — the regional radiopharmacy, the company that specializes in cold-chain shipping for biologic samples, the local equipment repair firm that only invoices by email. For those vendors, you end up doing manual onboarding anyway, and the Coupa supplier portal becomes another place where someone has to click through forms that don't apply to their business model. Here's what the platform actually delivers, though, and it's significant. Once you get past the configuration headaches, spend visibility improves dramatically. We went from monthly AP close reports that came out 45 days late to near real-time dashboards where a department head could see their actual spend versus their budget by the end of the week. Invoice processing time dropped from an average of 12 days to about 3 days because three-way matching now happens automatically at the PO level instead of requiring AP staff to manually line up receipts with invoices in a spreadsheet. The corporate card integration eliminated roughly 15 percent of our low-value POs — purchases under $500 that were clogging up the approval queue anyway.
Get the Full Details
The budget control feature is probably the single most impactful piece. Before Coupa, department heads could spend past their budget without anyone knowing until the quarterly review. Now, the system enforces hard stops at the budget level. If you've committed 95 percent of your annual spend, the system either blocks new requisitions or routes them to a higher approval level depending on how you configure it. This sounds simple but it changed the conversation around budget planning entirely. Department heads started being more careful about how they estimated their annual needs because the system would literally reject their requisitions. For procurement staff, the contract management module is where you'll find the most quiet value. Coupa tracks contract terms, renewal dates, pricing agreements, and compliance deadlines in one place. At MSKCC, we had procurement managers who were managing supplier relationships based on a combination of email attachments, shared drives, and their own memory. The contract repository in Coupa isn't beautiful, but it centralized enough information that we could finally run compliance audits without pulling three people into a conference room for two days. There are downsides worth being honest about. The platform requires continuous maintenance. Catalog updates, workflow changes, user access reviews, integration monitoring — none of this is set-and-forget. You need at least one dedicated Coupa administrator on staff, preferably two if your organization is large or has complex procurement workflows. MSKCC ended up hiring a full-time Coupa product owner whose entire job was keeping the system tuned and training new users. Without that role, the system degrades within six months because someone always finds a workaround that breaks the process.
Another limitation is the learning curve for non-procurement users. Surgeons, principal investigators, lab directors — they don't want to fill out requisition forms. They want to click a button and have supplies appear. The first few months after go-live, help desk tickets from clinical staff spiked by about 300 percent compared to the previous system. A lot of those tickets were about users not understanding why they needed approval for something that used to be a phone call to purchasing. That's not a Coupa problem. That's a change management problem. But it still slows adoption and frustrates the people you need using the system the most. Integration costs also tend to be underestimated. The Coupa-SAP connector exists, but it doesn't cover everything out of the box. At MSKCC, we needed custom integrations for the clinical trial management system, the radiation safety tracking system, and our inventory management platform for high-value implants. Those custom integrations cost roughly twice what the base Coupa licensing did in the first year. If your organization has a lean IT budget, that's a real constraint. If you're evaluating Coupa for a cancer center or similar healthcare procurement environment, here's what I'd suggest based on the experience. Start with the catalogs before you touch anything else. Get the item classification right. Build in the conditional logic for regulated products early, because fixing it after go-live is exponentially harder. Map your approval workflows against your actual organizational structure, not the ideal one — I've seen too many implementations fail because the approval chain assumed a flattener org chart than actually existed. Budget your integration work separately from the licensing, and double the estimate. And hire a dedicated product owner on day one, not after you've already hit a configuration crisis.
The core platform is solid. The spend visibility, invoice automation, budget enforcement, and contract tracking capabilities are genuinely useful for an organization the size and complexity of a major cancer center. But the difference between a successful implementation and a painful one usually comes down to how well you anticipated the edge cases that standard enterprise deployments don't encounter. The radiation safety field incident I described isn't an anomaly. It's the norm for clinical procurement. Plan for it.
