Private equity software solutions: where LPA compliance fits

Private equity software solutions cover a manager's back office in pieces: fund accounting platforms keep the general ledger and calculate fees, administrators' portals show what the administrator booked, investor portals and CRMs handle communications, document systems hold the agreements, and separate tools run waterfalls and expense allocations. What none of them does on its own is read the LPA, with its amendments, side letters and consents, and check every booked fee and expense against it. That is the gap examiners keep finding. Botminds' LPA Compliance is built as a layer beside those systems rather than a replacement for them: it reads the documents and the books already held elsewhere, and writes back findings and approved corrections, never accounting entries of its own.

Examples come from a fictional sample manager, Quillfield Capital, with 40 vehicles and 612 governing documents in the solution.

What do private equity software solutions cover?

They cover the books, the investors and the documents, usually in separate systems. A typical stack has a fund accounting platform, often run by or alongside a fund administrator; an investor portal and CRM; a document management system for executed agreements; and specialised tools for waterfalls, management fees, expense allocation, portfolio monitoring and investor reporting. Private equity management software providers and private equity accounting software providers sell different parts of that list, and many managers run several.

Each system is accurate about what it holds. The fund accounting platform knows what was booked; the document system knows what was signed. The question "was this booking allowed by what was signed?" sits between them, and in most stacks it is answered by people reading email and spreadsheets.

Does LPA compliance replace our fund accounting system?

No. An LPA compliance layer reads the fund accounting platform and the administrator's figures; it does not keep books, calculate NAV, post journal entries or send capital calls. What it adds is the test those systems cannot run themselves: each booked expense and fee calculation compared with the governing terms in force, cited to the clause.

The design choice is deliberate. A fund's books have one owner, and a second system posting to them would create two versions of the truth. In the sample, when an expense is not chargeable to a fund, the agents propose a move to the manager; a fund accountant confirms it as maker, the CFO approves it, and the approved move goes to the expense allocation tool and to the administrator as a correction. The books are changed by the people and systems that own them.

The gap between the books and the LPA

The SEC's examiners have described the gap precisely. In 2020 they found advisers that promised investors management fee offsets but had no adequate way of tracking the portfolio company fees they or their operating professionals received, so investors may have overpaid (SEC risk alert, June 23, 2020). The fees were in some system; the offset clause was in another; nothing connected them.

The 2025 TZP order is the same gap in a single paragraph: the LPAs' exclusion list did not name interest on deferred fees, the adviser left that interest out of the offset, and $423,065 that should have reduced fees did not (SEC order IA-6908). In the sample, the Expense check agent finds the pattern in Fund V, $38,200 of interest on deferred monitoring fees left out of a 100% offset, by reading the fee data and the clause together. In the sample's words, the administrator books what it is sent; the layer's job is to check what it was sent.

What does private equity software need to connect to?

For LPA compliance, six connections: the document system, the fund accounting platform, the administrator, the tools that apply terms, the investor portal and the identity provider. The map below shows what the layer reads from each and what, if anything, it writes back.

Two details in the map matter for security reviews. Access follows the document system: the agents answer only from documents the person asking may open, and for confidential side letters they state the effect without showing the text. And platform administrators manage roles and connections but approve nothing, so the people who run the system cannot also clear its findings.

What it writes back: approved terms and corrections, never entries

The layer writes back two things. Approved terms, each with its version and clause, go to the tools that apply them, so the expense allocation, fee and waterfall calculations use the version counsel approved rather than the one someone typed at launch. Approved corrections go to the administrator and the expense allocation tool, carrying the clause, the amount, the maker and the approver.

Delaware law is relaxed about where those records live. A limited partnership "may maintain its books, records and other documents in other than paper form, including on, by means of, or in the form of any information storage device, method, or 1 or more electronic networks or databases," provided the form "is capable of conversion into paper form within a reasonable time" (6 Del. C. §17-305(c)). The adviser's own books and records under Rule 204-2 must be kept "for a period of not less than five years" (17 CFR 275.204-2(e)(1)). Exportable evidence is a requirement, not a feature.

How long does it take to go live with LPA compliance software?

It depends on the document set more than the software. No regulator or independent study publishes go-live times for this kind of tool, and a vendor's figure is only as good as the documents it assumed. The work is a document set and a data map: every governing document for the funds in scope, a quarter of booked expenses and fee calculations, and counsel's confirmation of the first term table before any check runs on it. In the sample, Fund III alone has 46 governing documents, and 138 of the manager's 612 are in French or German.

The practical way to judge a tool is to run it on a quarter you have already closed. Its findings can then be compared with what your team found by hand, line by line, and the differences explained. The LPA compliance checklist and its measures gives the counts to compare.

Who controls the layer: thresholds, access and approvals

Every setting that decides when the agents answer, when they stop and who approves is the manager's, versioned and approved by compliance before it takes effect. In the sample, the agents answer alone at or above 90% confidence, and only when a second, blind reading agrees; below 75% they give no verdict. Counsel rules on a conflict within three business days; moves above €250,000 need a second approver after the CFO.

Rules and thresholds in LPA Compliance: the manager's settings, versioned and approved

What should a private equity firm ask a software vendor?

Ask what it reads, what it writes, who approves, and what an examiner will see. The SEC's fiscal 2027 priorities say the Division "will also focus on advisers that use certain third-party service providers," and will weigh the risks of advisers' growing reliance on outside providers and shared technology, including how well those risks are managed (SEC, October 23, 2026). The questions below are the ones that diligence should be able to answer in writing.

Where LPA Compliance does not fit

LPA Compliance is not a general ledger, an administrator, an investor portal or a waterfall engine, and it does not calculate NAV. It does not manage side letter negotiation or capital calls; Botminds' Side Letter Management and Capital Call Processing do. It does not know who works where, so key person tests need that from the manager. If a manager's problem is that its books are wrong for reasons unrelated to its fund documents, the fix belongs in the accounting.

It fits where the question is whether what a fund paid, or was charged, follows what was signed. In the sample, an answer to that question for a €18,460 board dinner took 11.8 seconds, read 50 documents and cited 9, with a blind second reading agreeing; the move it proposed waited for the CFO. What obligation software must do with an undefined term and how legal review AI differs from LPA testing cover the neighbouring categories. To see it on the sample funds, start from LPA Compliance.

Ask the fund documents: a verdict with its clauses, its precedence chain and the terms used

Questions people ask

Which private equity accounting software providers does it work with?

It reads booked expenses, the general ledger and fee accruals from a fund accounting platform, and booked expenses, fee calculations and term sheets from an administrator's portal, through connections set up at go-live. The test is the data, not the brand: line-level expenses and fee calculations it can read, and a way to send approved corrections back.

Does it work if our administrator keeps the books?

Yes; that is the common case it is built for. It reads what the administrator booked and calculated, and sends back approved corrections and term versions, each with its clause, so the administrator's term sheet stays in line with what counsel approved.

Is there an SEC rule on using software providers?

There is no general outsourcing rule for advisers: the SEC proposed one in November 2022 and withdrew it on June 17, 2025. Oversight of a provider rests on the adviser's fiduciary duty, the compliance rule and any rule that reaches what the provider handles, and the fiscal 2027 priorities name third-party service providers as an examination focus.

Can we start with one fund?

Yes, and it is the sensible way to judge it: one fund family's documents and one closed quarter of booked expenses, with counsel confirming the first term table. The results can be compared line by line with what your team already found.

What records does the layer leave?

Every question, answer, source, ruling, term change, test and approval, with who, what, when and why, chained so that a later change shows. Advisers must keep most required books and records for not less than five years under Rule 204-2(e)(1); the trail should be exportable for that period.