CommonSpirit's Edgewise GPO Replaced Email and Weeks of IT Tickets for 150+ Vendors With Files.com

CommonSpirit Health is one of the largest nonprofit health systems in the United States, delivering more than 20 million patient encounters a year through over 2,300 clinics, care sites, and hospital-based locations across 24 states. It is the country's largest Catholic hospital chain and its second-largest nonprofit chain.

Inside it sits Edgewise, CommonSpirit's wholly owned group purchasing organization. Edgewise negotiates supply contracts with some of the largest medical-device and supply manufacturers in the country, on behalf of CommonSpirit facilities and member organizations outside the health system. Its revenue comes from administrative fees and rebates, calculated from sales each manufacturer reports against member spend.

That model has a consequence: every dollar Edgewise earns starts life as a file. Each vendor sends a monthly or quarterly report of what members bought, and those reports are the raw material of the GPO's revenue. In early 2025, the way those files arrived was an email inbox. Files.com would turn that process into an auditable intake operation the finance team could run itself.

The Revenue Stream Arrived as Email Attachments

Eighty-six manufacturers emailed Excel files to the Edgewise finance team. Staff opened each email, downloaded the attachment, and re-uploaded it into a Google Drive folder, where a nightly script picked it up for validation and loading into the data warehouse.

“It's pretty prehistoric how we're doing it.”

The cost was not just the hand-carrying. There was no record of who uploaded what and when. A vendor had no way to see whether its file had landed or why it had been rejected, so every problem became a back-and-forth over email. And the only sanctioned alternative was worse: an internally hosted SFTP server that the finance team could only touch through IT tickets.

“We have an internally hosted SFTP server, and it takes multiple IT tickets because we're not technically an IT team. One to create the user, and then one to whitelist their IP address.”

Onboarding a single vendor down that path ran into weeks. The structural problem was that the team that owned the revenue process was a finance and analytics team, not an IT team. Every step of connecting a new vendor belonged to someone else's queue, on both sides of the exchange.

Growth Was Outrunning the Inbox

The vendor base made the arrangement untenable. Eighty-six vendors in January 2025 became more than 100 by March, and the team projected 200 within a few years. Every new manufacturer meant either another inbox thread handled by hand or another weeks-long ticket cycle.

What the fix had to do was clear before any product was named. It had to be intake the finance team could provision and run itself, without tickets. It had to work for the people actually sending the files, who are financial analysts and sales managers at manufacturers, not IT staff. It had to keep each vendor's submissions separate from every other vendor's, and keep admin-fee and rebate streams structurally apart. And it had to feed the team's existing validation and warehouse pipeline.

“We're looking specifically for an endpoint that has a drag-and-drop web UI that we can send them to.”

Edgewise selected Files.com to be that intake layer.

One Branded Portal, a Write-Only Folder for Every Vendor

Files.com became the governed front door for Edgewise's vendor financial reporting: one branded portal the finance team administers itself, with the same warehouse pipeline running underneath it.

Every manufacturer logs into the portal, which runs on Edgewise's own branded Files.com subdomain, and sees exactly two things: a write-only folder for its own submissions, and a shared read-only resources folder holding the current reporting template, member roster, and FAQ. No vendor can see any other vendor. Intake folders accept only spreadsheet formats, and admin-fee and rebate submissions live in separate folder trees, preserving the financial separation the GPO is required to maintain between the two.

Provisioning is code, not tickets. Using the Files.com Python SDK, the team's data engineer wrote a script that takes a spreadsheet as input and creates every vendor user, upload folder, archive subfolder, and permission set in one run. More than 100 vendor structures were built that way at launch, with welcome emails suppressed so a single coordinated announcement could go out, and the same script re-runs for every vendor batch since.

The pipeline runs itself. A Files.com Agent on an on-premises server pulls each uploaded file into the team's flat-file checker before loading it to BigQuery. A file that fails validation generates an email to the vendor naming the specific column or format at fault. Files.com Automations rename and archive each file, while the audit log records every login and upload. The portal's two dedicated IP addresses also eased vendor-side security approval because a manufacturer's security team could allowlist two explicit addresses instead of a hostname.

The team treated the cutover like the revenue system it is. The Files.com path ran in parallel with the legacy Google Drive path until both produced identical warehouse output. The team then spent a month uploading real files while posing as its own vendors before the portal went live in January 2026.

Onboarding a Vendor Went From Weeks of Tickets to a Login

With the portal in production, Edgewise replaced an intake process built on email, a shared drive, and ticket queues with a repeatable pattern the finance team runs itself.

• Onboarding a manufacturer is now self-service: a login and a drag-and-drop upload, guided by a PDF and a screen recording. Edgewise no longer opens IT tickets to create accounts or allowlist each vendor's inbound IP, eliminating a path that used to run into weeks. Vendors can still allowlist the portal's fixed addresses when their own security policies require it.
• More than 150 vendor partners submit monthly and quarterly files through one portal, all consolidated into a single data warehouse. The base has grown from 86 at the start of the project to roughly 170, and each new batch of vendors is absorbed by re-running the provisioning script.
• Every submission is on the record: an audit history of who uploaded what and when, per-vendor archives, and a dashboard tracking the last file received from each vendor for delinquency follow-up.
• File problems no longer begin with a human conversation. A failed file comes back to the vendor with the exact column at fault, instead of an analyst reconstructing the error over email.

The Team That Owns the Revenue Owns the Intake

What is fundamentally different at Edgewise is who runs the machinery. A finance and analytics team now operates its own external file intake end to end on Files.com.

“It has delivered on everything we needed.”

Edgewise set out to build the intake operation of the larger GPO it intends to become, before the growth arrived. It did not wait to grow into a professional process. It built one on Files.com first, and has been growing the vendor base into it ever since.