The Audit Trail: Building a Fund's System of Record

An audit trail is a chronological record that shows, for every transaction and every change in a fund's records, who made it, when, what changed, and what authorized it. In a private fund, the audit trail is what lets an auditor, regulator or investor trace any figure on a capital account statement back to its source. A fund whose records can be traced this way effectively has a system of record; a fund that relies on overwritten spreadsheets does not.

Why the audit trail matters in private funds#

Private funds rely heavily on judgment and calculation: valuations, allocations, fee offsets, waterfalls. Each of those numbers is produced by a chain of inputs and decisions. When someone asks "why is this LP's capital account $4.2M and not $4.3M?", the answer has to be reconstructable.

The audit trail serves four audiences:

What a complete audit trail captures#

For each event, a robust trail records:

1. What happened: the transaction or change, such as a journal entry posted, a valuation updated or an investor's bank details changed.
2. Before and after values for any modified field.
3. Who made the change, tied to an individual user account rather than a shared login.
4. When, with a reliable timestamp.
5. Why: a reason or reference, such as an approved valuation memo or invoice.
6. Approval: who reviewed or authorized it, if approval was required.
7. Supporting documents, linked rather than described.

The trail should cover both financial data (journal entries, capital activity, fees, valuations) and master data (investor records, commitments, side letter terms, bank instructions, user permissions). Master data changes are often where the real risk sits. A changed wire instruction or a modified fee rate can be more consequential than any single journal entry.

Regulatory context#

For SEC-registered investment advisers, Rule 204-2 under the Investment Advisers Act (the books and records rule) requires advisers to make and keep specified records, including journals, ledgers, and records supporting performance claims. Records generally must be kept for at least five years from the end of the fiscal year in which the last entry was made, the first two years in an appropriate office of the adviser. Electronic records must be maintained in a way that protects them from unauthorized alteration and allows them to be retrieved and produced promptly.

The custody rule, ILPA reporting expectations and LP side letter provisions add further pressure to produce consistent, verifiable records. Exempt reporting advisers are subject to fewer of these specific rules but face the same practical expectations from auditors and LPs. See private equity compliance for the broader framework.

How a good audit trail is designed#

Append, don't overwrite#

The most important principle is that history is never rewritten. If a journal entry was wrong, it is reversed and a corrected entry is posted, leaving both visible. Editing a posted entry in place destroys the evidence of what was reported before.

Lock closed periods#

Once a quarter is closed and statements are issued, the period should be locked. Any later adjustment goes through a controlled process, is posted in the current period or through an explicit reopen with approval, and is logged. This prevents silent changes to numbers LPs have already received.

Tie calculations to the ledger#

Calculations such as capital calls, management fees and waterfalls should post directly to the general ledger from the system that computed them, with the calculation inputs saved alongside. A ledger entry that says only "per spreadsheet" breaks the trail.

Individual accountability#

Every user needs a named account. Shared logins make the "who" meaningless. Role-based permissions should reflect segregation of duties, so the person who sets up a payment cannot also approve it.

Make it queryable#

A trail that exists but cannot be searched is little help during an audit. Teams should be able to filter by entity, period, user, record type and date range, and export the result.

Worked example (hypothetical)#

Assume an LP calls in March asking why its Q4 capital account statement shows $50,000 more in management fees than expected. With a complete audit trail, the controller can answer in minutes:

Without the trail, the team would have to compare spreadsheet versions and emails to reconstruct the same story, and the auditor would need to do it again at year-end.

Common gaps in fund audit trails#

• Spreadsheet calculations whose versions are saved over each quarter.
• Email approvals that are not linked to the transaction they approved.
• Shared credentials on bank portals or accounting systems.
• Unlogged master data changes, especially investor bank details and fee terms.
• Manual adjustments without a reason code or support.
• Data moved between systems without reconciliation, so the trail breaks at each handoff.

Steps to strengthen your audit trail#

1. Inventory the systems and spreadsheets that produce numbers LPs or auditors see.
2. Move recurring calculations into controlled systems that post to the ledger.
3. Require reason codes and attachments for manual journal entries and master data changes.
4. Implement period locking and a documented reopen process.
5. Review user access at least quarterly and remove shared accounts.
6. Test the trail: pick a number from a recent fund audit or LP statement and trace it end to end.

Audit trail versus backups and document storage#

Teams sometimes assume that backups or a shared drive amount to an audit trail. They do not. A backup tells you what the data looked like at a point in time; it does not tell you who changed a value between backups, or why. A document repository holds support, but unless each document is linked to the transaction it supports, a reviewer still has to guess which invoice belongs to which entry.

All three are needed. The audit trail is the one that answers questions about accountability.

How Privatis helps#

Privatis records an audit trail of every change across the fund general ledger, capital calls, distributions, management fees, valuations, investor records and side letter terms, with user, timestamp and before-and-after values. Period close locks prior periods, and calculations post directly to the double-entry ledger so balances on LP statements trace back to their source.