A Residential Mortgage Lender Replaces Citrix ShareFile and Lands Borrower Documents in SharePoint With Files.com

A US residential mortgage lender operates nationwide through a distributed branch network.

Every loan starts with documents. Borrowers hand their loan team some of the most sensitive financial paperwork a consumer ever produces: loan agreements, W2s, and similar PDFs, all of it time-sensitive, because a loan waiting on a document is a closing waiting on a document. And at the lender, that collection happens at the branch level, across distributed loan teams, at volume. A lender built this way was always going to need a serious answer for how borrower files come in from the outside and where they land once they do.

Isolated Intake That Lands in SharePoint

External file exchange with borrowers ran on Citrix ShareFile. The lender set a stricter requirement for sensitive borrower paperwork: every uploader isolated, so anyone using a shared upload path sees only their own submission.

The second half of the requirement was where the documents end up. The lender wanted every borrower document to land in SharePoint, the system of record for the branch team’s lending, without anyone moving it between systems.

The volume decided where to start. One branch team was moving gigabytes of PDF files per team member, every week, and had reached the limits of the provider it was on.

The fix could not be to simply use SharePoint, because borrowers needed a simple external upload path rather than access to the lender’s internal Microsoft environment. And it could not be another standalone sharing tool, which would leave the documents disconnected from the Microsoft estate where the branch team actually worked. For a pilot with that team, the lender needed an intake layer that was secure toward borrowers and outside vendors on one side, and wired into its own Azure tenant and SharePoint sites on the other. The lender selected Files.com to be that layer.

SharePoint Sites Mounted Behind a Borrower-Facing Front Door

For the pilot branch team, Files.com became the external face of SharePoint: governed intake toward borrowers and vendors, the lender’s own Microsoft estate behind it.

Using an Azure App Registration in the lender’s own tenant and Files.com Remote Server Mounts, the branch team’s SharePoint sites appeared as folders inside Files.com, targeted to the specific locations where borrower documents belonged.

On the intake side, borrowers could deliver documents through Files.com share links and inboxes. Each inbox session was isolated by design: an uploader could see only their own submission, never anyone else’s, meeting the lender’s uploader-isolation requirement. An outside video vendor used the same path as the branch team, while SSO and user and group permissions governed the internal side.

Between the two, Files.com synced everything through to SharePoint on a short interval, a cadence the lender tuned specifically for time-sensitive loan documentation. The lender’s own staff built the entire workflow, with Files.com sales engineering on call.

Minutes From Upload to the System of Record

With the workflow in production for the pilot team, the lender replaced the previous ShareFile intake with a single governed path from the borrower to the branch team’s system of record.

• Borrower documents land in the branch team’s SharePoint sites within minutes of upload, with no one shepherding files between systems.
• Gigabytes of PDFs per team member move through the path every week: the volume that had outgrown the previous provider now runs as routine.
• Inbox sessions isolate each uploader, so every borrower sees only their own submission, which is the requirement the lender set for the pilot.
• An outside vendor delivers through the same route as the branch team, under the same controls and into the same system of record.

The pilot also established a repeatable pattern for the lender’s intended wider rollout: another SharePoint site could join the path by being mounted and given a sync.

The Front Door SharePoint Never Had

For the pilot branch team, what changed was where the boundary of the lender’s Microsoft estate sat. External exchange used to happen outside it, on ShareFile. Now a borrower or vendor uploads through a governed Files.com page, and within minutes the document is sitting in the SharePoint site where the branch team does its work. A loan officer waiting on a W2 finds it there.

The lender did not abandon SharePoint to fix external file sharing for the pilot team, and it did not bend SharePoint into a borrower-facing job it was never built for. It put Files.com in front of it.