A Physician Association Replaced Manual FileZilla Transfers With a Files.com Payer and Clearinghouse Exchange in Six Months

An independent physician association is two businesses at once. The first is the association itself: staff-model clinics, a network of thousands of in-network physicians, and hundreds of thousands of managed lives across several counties. The second is a management services organization that runs the administrative machinery of managed care for those clinics and physicians, including eligibility, capitation, credentialing, and the review and adjudication of medical claims.

That second business runs on files. Every payer, clearinghouse, and hospital relationship in managed care is a stream of them: 837 claim files going out, 835 remittance files coming back, eligibility and capitation data moving on their own schedules, all of it carrying protected health information. And in early 2026, when the management services arm set out to run claims adjudication on a new claims platform of its own, the payer and clearinghouse exchange behind it had to be built from the ground up.

A Claims Platform That Needed Its Exchange First

Until then, every exchange was hand work. Partner connections ran through FileZilla sessions, each configured by hand on both sides. Staff logged in to pull claims files by hand. The organization wanted one governed repository for the patient data its hospital administrators exchange with outside physicians and other hospitals. The operating model everyone knew was in-house, on-premises FTP, where every partner meant another bespoke connection to build and babysit.

The specification came into focus the day a major payer sent its security questionnaire. The form asked for a hostname, a connecting IP address, preferred authentication methods, and an outbound directory, and the new exchange had to supply every one of them before the payer relationship could move forward.

And the payer was one of many. The counterparties the organization needed, spanning payers, clearinghouses, and hospital partners, each arrived with their own protocols, their own IP whitelisting demands, and their own preferred way of contributing files. Some pushed over SFTP. One transmitted machine-to-machine over HTTPS on its own schedule. One returned files several times a day and needed to be pulled from. The systems team could not build and operate a bespoke FTP connection per partner and route claim files by hand while the same people were building and testing the claims platform itself. That platform had a production go-live in August 2026, and every route to every clearinghouse had to exist before it.

What the organization needed was one exchange layer every counterparty could reach in whatever way it already worked: fixed IP addresses a payer's security team could whitelist, a walled-off space per partner, a BAA covering the PHI passing through, and automated pickup from the claims system that would not disturb anything already depending on its output. The organization selected Files.com to be that layer.

The Router Between the Claims System and Every Clearinghouse

Files.com became the hub for the organization's claims file exchange.

The pickup runs inside the organization's own network. A Files.com Agent installed on an on-premises server makes an outbound-only connection to the platform, so no inbound firewall changes were needed and the claims server was never exposed to the internet. The Agent copies 837 and 835 files out of the claims platform's output directory rather than moving them. That distinction mattered: several downstream programs read that same directory for reconciliation and other reports, so the exchange had to take its copy without breaking anything that already depended on the folder.

From there, Files.com routes each file by type. 835 remittance files go to the clearinghouse that processes remittances; 837 claim files go to the clearinghouses that carry claims. For the clearinghouse that returns files several times a day, a timed sync pulls them in and delivers them to the right directory, with no one logging in to fetch anything. The organization's managed IT provider ran the build alongside Files.com's onboarding team, standing up the counterparties one at a time from February through August 2026.

One Front Door for Every Counterparty

On the inbound side, every partner gets the same structure: a dedicated folder tree with separated incoming and outgoing directories, and a partner account scoped to exactly that space. The site runs on the organization's own branded domain with fixed IP addresses, which gave payer security teams a hostname and an IP to whitelist. Those are the answers the first payer questionnaire asked for.

Partners connect however they already work. Some push over standard SFTP. One trading partner transmits machine-to-machine over HTTPS on its own cadence. A hospital administrator with a one-off file uses the web interface.

Internally, staff sign in through Microsoft Entra ID over SAML SSO, with accounts provisioned automatically on first login. Inbound partner files sync on a schedule into a SharePoint library set aside for this traffic, so Microsoft 365 remains the organization's system of record while Files.com is the governed perimeter in front of it. Arrival notifications fire when a payer drops a file. The account carries a BAA, covering the PHI in every exchange.

Ready Before the Claims System Turned On

By August 2026, the organization had replaced manual FileZilla transfers with a standing, governed platform, in place ahead of the claims system's go-live.

• File exchange with every payer, clearinghouse, and hospital counterparty runs through one Files.com platform, built in roughly six months by the systems team.
• Manual retrieval is gone from the claims path. Files leave the adjudication system and reach the right clearinghouse automatically, where staff used to log in and pull them by hand.
• The payer connection that set the specification is live, with automated notification the moment its files arrive.
• Claims import files received through the platform follow the retention schedule that governs claims data.

Today, the claims administration behind hundreds of thousands of managed lives runs its file traffic through Files.com without anyone touching it, and when a new health plan arrives with its own set of transfer requirements, the exchange it needs already exists. The organization never built file transfer infrastructure of its own. It stood up its entire payer and clearinghouse exchange on Files.com, and it was there before the claims system it serves ever went live.