American First National Bank Proves Delivery to Regulators with Files.com

American First National Bank is a US commercial bank with 20 branch locations across Texas, Nevada, and California, plus a Loan Production Office in California. Its core business spans consumer and commercial lending, supported by compliance, legal, enterprise risk, investments, and bookkeeping functions.

AFNB responds to information requests from government entities and works subpoenas with outside counsel. Each one ends the same way: the bank assembles a set of documents and delivers it to a counterparty it does not control. For a lender, those sets are large. Producing them is not an occasional event for a bank. It is a standing obligation.

Productions Split Into Zip Files, With No Record of Delivery

Those productions went out by email. Attachment limits forced staff to break each document set into multiple zip files and send them as a string of separate messages. That was manual work on every production. It was also, on the day it mattered, no record at all.

When a regulator asserted that a required delivery had not been made, the bank could not readily produce proof that it had. A sent-mail folder shows that messages left a mailbox. It does not show what a recipient received, or when, and it is not a record a bank wants to argue from. AFNB was making legally consequential deliveries over a channel that could not witness them, and every production carried the same exposure.

Onboarding the other side was not an option. The recipients are government agencies and examiners, and a bank cannot ask an investigator to create an account in its systems or install software to receive a file. Whatever replaced email had to work for a recipient who would do nothing more than click a link in a browser. That meant the proof had to attach to the send itself.

The Proof Had to Attach to the Send Itself

As requests continued to arrive, AFNB needed a standard outbound channel rather than a per-request workaround. It had to carry a complete production in a single delivery without email attachment limits forcing staff to split it. It had to record the send: which files, which recipient, what date, whether or not the link was ever opened. It had to demand nothing from the government side. And it had to stay under the bank's own governance, with expiration on every delivery and notification when a recipient acted.

AFNB selected Files.com to be that channel, in a rollout led by the bank's Chief Information Security Officer.

One Share Link Carries the Whole Production and Writes the Record

Staff working a request assemble the complete production in a Files.com folder and send it as a single email-delivered Share Link. Because the files are no longer being sent as attachments, there is no splitting: the whole set travels as one delivery, and the recipient downloads it from a page in the browser.

The record is written at the moment of sending. Files.com logs that the link went out, on what date, and to which recipient. That evidence exists whether or not the recipient ever opens the link, which is exactly the case a delivery dispute turns on. When the recipient does act, Share Link activity logging captures it, and email notifications tell the sending staff their files were downloaded. A production is not just sent. It is confirmed.

The government side does no work. A federal investigator receives a link, opens it, and downloads the files, with no account to create and nothing to install. Because the site runs on the bank's own domain, with outbound mail routed through the bank's own SMTP server, what an agency receives carries American First National Bank's name rather than a third-party tool's. Every link expires on a schedule the bank set, so a production cannot sit downloadable on the open internet after its purpose is served. Internally, staff sign in through the bank's Microsoft Entra ID single sign-on and work within restricted home folders, so access to a production is as scoped as the delivery.

The pattern turned out to be general. When bank staff worked a subpoena with an outside law firm, they used the same channel: documents uploaded to a folder, Share Links issued to the firm's attorneys, who are not employees and hold no accounts. A workflow built for regulator requests extended to the bank's other external legal counterparties.

Evidence the Bank Can Put in Front of a Regulator

With the Share Link workflow in production, AFNB replaced an email process it could not stand behind with a delivery channel that writes its own record.

• A complete production goes out as one link. The zip-splitting and multi-message sends are gone, and by the bank's own comparison, getting files out is easier than the email process it replaced.
• The bank can show a delivery was made: which link was sent, on what date, to which recipient, even when the recipient never opened it. The question that once had no answer is a log lookup.
• Staff know when an agency has actually retrieved a production, because download notifications close the loop that email left open.
• External counterparties require no recipient accounts or onboarding. Subpoena responses to outside counsel already run on the same pattern, and future requests can start from a channel that already exists rather than a workaround built for the occasion.

The change removed a standing risk and a standing chore at once: the exposure of unprovable deliveries, and the manual splitting that preceded every one of them.

Today, the Delivery and the Proof Are the Same Act

If a regulator asks whether a production was delivered, the person answering points at the record instead of reconstructing a chain of emails from a sent-mail folder. The transfer was never the hard part. Producing proof of the transfer was, and the bank's channel is now the thing that produces it.