Audit Trails: Why Every Export and Download Should Be Logged
When a merchant disputes what they were sent or a broker leaves with your leads, the question is always the same: what actually happened? An audit trail answers it.
Three months after a deal funds, the merchant's attorney sends a letter claiming their client never received the final contract version and was quoted different terms on the phone. Your broker remembers it differently. The email thread is incomplete. Without a record of who changed the document, who downloaded it and when, you are left arguing memory against memory.
Now a different afternoon. A senior broker resigns. Two weeks later, merchants from your pipeline start mentioning calls from a competitor who knew their deposit numbers. Did the broker take data? Without logs, you are guessing.
An audit trail is a tamper-resistant record of who did what, and when, inside your systems. It is unglamorous, it rarely matters on any given day, and on the day it matters it can decide the outcome. Here is why every funding shop should log exports, downloads and changes, and how to use the log well.
Pre-flight summary
- Log exports, downloads, key field changes, sign-ins and permission changes, with user and time.
- Audit trails turn disputes into timelines and protect both merchants and your shop.
- Visible logging deters insider data theft as much as it detects it.
- A light, regular review habit beats occasional forensic hunts.
- Confirm record-keeping obligations with qualified counsel; the log supports them.
Leg 01What a useful audit trail records
Not every log is an audit trail. A useful one captures enough detail to reconstruct events without guesswork, and it cannot be quietly edited by the people whose actions it records.
- Exports of lists, reports or pipelines, including who ran them and how many records were included.
- Downloads of individual documents such as statements, applications and contracts.
- Changes to key fields, especially bank details, offer terms, deal stage and ownership.
- Sign-ins, failed sign-in attempts and second-factor resets.
- Permission and role changes, so you know when someone gained or lost access.
- Timestamps and user identity on every entry, stored where ordinary users cannot alter them.
Leg 02Settling disputes with facts instead of memory
Disputes in business funding often hinge on sequence. Was the disclosure sent before the contract was signed? Which version of the offer did the merchant open? Who changed the remittance amount, and was that before or after approval?
A deal-level history that shows every change and document event gives you a timeline you can hand to counsel. It will not make a weak position strong, and it should not be used to bend a story, but it replaces he-said-she-said with records. That protects merchants who were treated unfairly as much as it protects your shop from claims that are not accurate.
Leg 03Insider risk: the threat already inside the building
Most funding shops worry about outside hackers and overlook the more common problem: people with legitimate access using it for illegitimate reasons. A departing broker exporting a lead list is the classic case, but there are subtler ones, such as someone downloading statements from deals they are not assigned to, or editing bank details on a file just before funding.
Logging does two jobs here. It detects, because unusual activity stands out when you can see it. And it deters, because people behave differently when they know exports and downloads are recorded. Tell your team plainly that activity is logged. The goal is not to catch people; it is to make the wrong move unattractive.
An audit trail rarely matters on any given day. On the day it matters, it can decide everything.
Leg 04Answering funders, auditors and regulators
Funders increasingly ask brokers how they protect merchant data. Larger partners may want to know who can access files, whether access is reviewed and how you would detect misuse. Being able to say every export and download is logged by user and time is a stronger answer than describing a policy nobody can verify.
If a regulator, examiner or court ever asks about your handling of a specific file, an audit trail helps you respond accurately and quickly. What records you are required to keep, and for how long, depends on your situation and jurisdiction, so confirm the specifics with qualified counsel. The log supports your obligations; it does not define them.
Leg 05Making the log something you actually read
A log that no one ever opens is only half useful. The value comes from a light, regular review habit rather than forensic deep dives.
- Decide who reviews the log, usually an owner or operations lead, and how often.
- Look first at bulk exports, because they carry the most data in a single action.
- Check activity around departures, starting a few weeks before a resignation.
- Watch for changes to bank details or payoff instructions near funding time.
- Note anything odd, ask about it directly and record the explanation.
- Restrict exports to roles that need them, so the review list stays short.
Leg 06Where FundPilot fits
FundPilot keeps a full audit trail of exports, downloads and changes across each company's isolated workspace, alongside role-based access that controls who can export in the first place. Because calls, texts, documents and lender replies all live on the deal, the deal history doubles as a timeline you can review when a question comes up.
Think of it as the flight recorder for your floor. Nobody plans to need it, and everyone is glad it was running when they do. If you want to see how the history looks on a real deal, a walkthrough is the quickest way.
Questions from the floor
Should we tell brokers their activity is logged?
Yes. Transparency is part of the value. When people know exports and downloads are recorded, most risky behavior never happens. Mention it during onboarding and in your written policies, framed as protection for merchants and for the team. Hidden monitoring tends to damage trust and adds no deterrent effect, while open logging sets clear expectations from day one.
How long should audit logs be kept?
That depends on your business, your contracts and the rules that apply to you. Logs are most useful when they cover the life of a deal plus the period during which disputes are realistically possible, but the right answer for your shop should come from qualified counsel. Make sure whatever period you choose is applied consistently and documented in your retention policy.
Is an audit trail the same as call recording?
No. Call recordings capture conversations, while an audit trail captures actions in your systems, such as exports, downloads and edits. Both create records that can help in a dispute, and they complement each other. Call recording also raises consent questions that differ by jurisdiction, so it needs its own review with counsel before you rely on it.
Can an audit trail prove a broker took data?
An audit trail shows what happened inside your systems, such as which account exported a list and when. That is strong evidence of activity, but what it means legally, and what you can do about it, depends on your agreements and the circumstances. If you suspect misuse, preserve the records, avoid altering anything, and speak with qualified counsel before taking action against the person involved.
General information only — not legal, tax or financial advice. Rules for telemarketing, texting, recording, disclosures and data retention vary and change; confirm current requirements with qualified counsel.
Connecting flights