An Equipment Dealership Group Runs a Finance-Owned Files.com Data Room for Lenders and Auditors

A US equipment dealership group operates construction and material-handling equipment dealerships across several states. Its dealerships sell, rent, and service heavy machinery.

The group is deliberately decentralized. Each division operates and manages itself under its own local brand, while a corporate center provides shared administrative services, including finance. That structure puts the corporate finance organization at the center of a constant exchange of sensitive documents. A dealership group that sells, rents, and finances heavy machinery lives on its lender relationships, and those relationships run on paper: bank statements, tax documents, borrowing-base reports, and audit materials moving between the corporate center and financial institutions across the country.

One Governed Path for the Documents That Go to Banks and Auditors

The group had one system built for moving files: an on-premises FTP server, and it stopped at the corporate firewall. Everyone the finance team needed to reach was outside it. Banks, investors, lenders, and auditors were never going to connect to a server behind the company’s network perimeter, so each document going out was a one-off send, and every send was a manual, per-message job for the finance staff.

The group wanted one governed path for that exchange. Lender reporting and audit collaboration call for differentiated access, so that each institution reaches exactly what it is entitled to and a view-only party stays view-only. They call for a record of what was delivered to whom. And they call for the document to stay under the group’s control after it goes out, rather than leaving as a copy.

What a Channel for Banks and Auditors Had to Do

A better server behind the firewall would not have met that requirement, because the firewall was the constraint. The group’s counterparties included many outside institutions, and a corporate finance department cannot put a bank on its network or dictate how an audit firm connects.

The replacement had to meet those institutions where they were. It had to be reachable over the web without requiring bankers or auditors to install anything, accommodate institutional security restrictions, give different parties different rights, and record every access. It also had to be simple enough for the finance department to configure and run itself.

The group selected Files.com to be that channel: a finance-run data room that its Director of Finance configured himself, without an IT project, and that carries several terabytes of files a month.

A Data Room the Director of Finance Built Himself

The group’s Director of Finance configured the Files.com site personally, and the design holds each institution apart from every other. Outside parties are assigned through Files.com Groups, so a lender’s users see exactly the folders that lender is entitled to and nothing else. Granular folder- and action-level permissions carry the differentiated rights: view, print, upload, and download are granted separately, so a view-only institution and a printing institution sit in the same data room under different rules.

The security controls were set to match the institutions on the other end. Accounts carry two-factor authentication. IP whitelisting was configured to line up with the access restrictions the group’s partner financial institutions apply on their own side, so the site accepts their connections on the terms their security teams already enforce. Every action lands in the audit history.

On the internal side, finance contributors post documents into the permissioned folders. When something has to go out one-off, they send a secure Files.com link in place of an attachment. The file stays on the platform under its permissions instead of leaving the company as a copy.

The rollout itself was treated as a trust problem. An unexpected invitation to a new document portal looks like phishing to exactly the kind of people banks employ, so onboarding of the outside institutions was staged behind a communications plan. By the time an invitation arrived, the recipient already knew it was coming and knew it was real.

Terabytes a Month Through a Channel Finance Controls

With the site in production, the group replaced a firewall-bound FTP server and one-off sends with one permissioned channel to its outside institutions.

The manual, per-message workflow changed with it. Finance contributors post documents once, and group notifications tell the appropriate party when new materials are waiting without an email carrying the file. When a question comes up about whether a lender received a document, the answer is a lookup in the Files.com audit history. Adding the next lender or auditor is routine: clone an existing user, assign the group, and the folder rights follow.

The site carries several terabytes of files a month. It became the standing channel for sensitive financial exchange and external audit collaboration, running inside the finance organization as a low-maintenance system without an IT project behind it.

A Finance Project, Not an IT Project

What changed at the group is who operates the connection between a multi-state dealership group and the institutions that finance it. A document going to a bank now means a folder on Files.com that one institution alone can reach, under rights the group chose, with a record of every access.

The portable lesson is in who did the work. Standing up a governed data room for banks and auditors did not take a managed-file-transfer program run by IT. The controls that made the channel acceptable to financial institutions, from differentiated rights and two-factor authentication to IP restrictions and the audit trail, were Files.com configuration, and the finance department that owns the documents configured them. The people accountable for the group’s lender relationships now run the channel those relationships travel on.