Coalition Automates Workday Report Delivery With an In-House Files.com SFTP Model
Coalition is a cyber insurance provider that underwrites and services cyber policies and runs incident response work alongside its insurance business. With more than 700 employees, the company operates HR on Workday, finance on cloud platforms, and identity on Okta.
The structure of that business puts data on the wire every day. Coalition’s insurance partners depend on daily claims reports, while internal systems need scheduled data from platforms such as Workday. When those platforms cannot exchange data with each other on their own, the work of connecting them falls to people.
As Coalition’s operations grew, so did the number of these flows. The company needed a repeatable alternative to hand-carried files: a layer built around scheduled SFTP delivery that IT could stand up gap by gap without custom development, and that would not become its own maintenance burden. Coalition selected Files.com to be that layer.
Every Integration Gap Became Manual Work or a Vendor Invoice
Coalition had outgrown one-off workarounds for platforms that could not talk to each other. Scheduled reports out of Workday had to reach downstream systems, and the files moved by hand. Finance platforms offered no modern way to provision user data, so someone prepared and uploaded it. The daily claims reports Coalition’s insurance partners rely on were delivered manually, which put a recurring commitment to outside insurers on a person remembering to send files.
None of this was fixable at the source, because the gaps lived inside the vendors’ products. Coalition could not make Workday ship a connector to the systems its reports needed to reach, and it could not force a finance platform to add provisioning it did not have. Each gap was different, too: one system needed scheduled report delivery, another needed user data, and partners needed files pushed to servers they ran themselves. The vendors did offer a fix, and it was the expensive kind: professional-services engagements the team judged not worth the price.
SFTP In From Workday, SFTP Out to Partner Servers
Files.com became the neutral SFTP layer between systems that could not talk to each other. It accepts files from platforms that push, and it connects out to servers that expect delivery.
The Workday link was among the first workloads live. Coalition bound a Files.com folder to Workday’s own SFTP delivery settings. Workday pushes its scheduled HRIS reports into that folder, and from there they reach the downstream systems that need them. Nothing custom was built inside Workday; its existing SFTP settings simply point at Files.com.
For claims reporting, the connection runs the other way. Using Files.com Remote Server connections, Coalition delivers daily claims reports outbound to each insurance partner’s own SFTP server on schedule. Each partner keeps whatever server it already runs, and Files.com speaks to it. Finance platforms with no modern provisioning option exchange user data over the same route.
Access to all of it followed Coalition’s directory. Okta provisioned Files.com users and groups over SCIM with push groups, so who could reach which folder was decided in the identity system Coalition already managed, and nobody administered file users by hand.
The Reports Move Themselves Now
With those flows in production, Coalition replaced hand-carried files and manual delivery with a standing integration pattern.
- Workday report delivery runs end to end, with no one moving files between systems by hand.
- Daily claims reporting to insurance partners runs automatically over SFTP, instead of depending on a person to deliver it.
- Gaps in finance-system functionality are closed in-house, without the professional-services spend the vendors proposed.
- The layer requires almost no administration: Coalition’s IT team reports barely needing to touch it.
“A lot of them push us towards professional services or some giant actual spend where it’s not worth it at all.”
The larger result is that the pattern applies itself. The next platform that cannot exchange data on its own is a folder and an SFTP credential away from being connected. Adoption has spread exactly that way: the deployment started narrow in IT and HR and widened as more departments discovered the service. When a client asks Coalition for an SFTP endpoint, IT now provisions one from Files.com instead of standing up a server.
An Integration Gap Is Now an In-House Fix
Before Files.com, a gap in a SaaS platform’s functionality left Coalition with two options: absorb the manual work indefinitely, or pay the vendor’s rate for a fix the team judged not worth it. Now there is a third option, and it is the default. When an enterprise platform supports scheduled SFTP delivery even if it ships nothing else, Coalition connects its systems itself, over Files.com, without waiting on any vendor’s roadmap.
Related Customer Stories
Insurance
Old Republic Replaced Box with Files.com During Its PHI Backend Migration to Azure
A governed SFTP perimeter secured chain of custody immediately without forcing 15 hospital partners to follow the infrastructure behind it.
Read story →
Insurance
Ameriflex Replaced Its On-Premise SFTP Server With Files.com—Without Partners Reconfiguring a Setting
Preserving the existing hostname, host key, and access controls let a HIPAA-regulated partner estate move in one hard cutover without partner-side reconfiguration.
Read story →

Insurance
Trucordia Retired Its Own FTP Servers by Putting Files.com in Front of SharePoint
Files.com gave each external counterparty an isolated, branded route into the right SharePoint library while moving internet-facing transfer security off a small IT team.
Read story →