Fund General Ledger Software for Private Funds

TL;DR. A fund general ledger has to keep a separate set of books per vehicle, answer entity, fund, deal and cost type on a single entry, hold both sides of every intercompany balance, and own its entity list rather than inherit one.

Four things are called a fund ledger

Guides on this topic answer four different questions. One set is construction accounting. One set is nonprofit restricted-fund accounting, and Blackbaud states that meaning plainly when it says "accounting software built for commercial businesses doesn't have the sub-fund capabilities nonprofits need to manage donor restrictions." A third set is general-business ledger roundups in which no fund term appears at all. Only the fourth is about private funds, where a fund is a legal vehicle with its own books rather than a restricted pot of donor money.

A fund general ledger holds one fund entity's own books, meaning its chart of accounts, its journal entries, its intercompany balances with the management company and the other vehicles, and the trial balance behind its financial statements. Each vehicle is a separate set of books, and shared costs are allocated across them under the rules in the partnership agreement.

Choosing a package for the fourth meaning is covered in fund accounting software. This page is the requirements list underneath it.

Why do funds run two ledgers?

Almost every private fund manager runs two ledgers, and the reason is structural rather than a failure of discipline. A consultant who implements both kinds of system for private funds explained it in one answer.

The fund-native ledgers do not have the functionality you need for management company accounting. No integration with the payroll system, no integration with the human resources system, no integration with the expense system. So for that reason the ERP is more suitable, and the way an ERP captures data in a multidimensional structure enables better reporting for the management company and budget-to-actual analysis.

So the management company buys a corporate ledger and the funds stay on a fund-native one. The corporate ledgers we connect to are QuickBooks Online, NetSuite and Sage Intacct. Of the 80 fund finance teams we spoke with in 2026, QuickBooks and NetSuite held 73% of that seat, QuickBooks at 51% and NetSuite at 23%, with Sage Intacct at 5% and a long tail carrying the rest. Behind it sits a separate fund-side system, and our tech stack data names Investran, Allvue, Carta and Geneva as the usual candidates.

Vendors on the fund-native side describe the seam accurately, because closing it is their pitch. FundCount opens with "stop reconciling QuickBooks to your investment record every month" and says its ledger "posts directly from partnership and portfolio accounting, no batch jobs, no broken bridges between your accounting system and your investment platform, no spreadsheets in between." A controller at a venture firm described the same seam from the buyer's side of it. To move general ledger information between her firm's two systems, somebody raises an invoice in the first one and sends it. There is no integration and no file transfer. Somebody keys the invoice into the receiving ledger at the other end.

Eight things a fund general ledger has to do

Every item here traces to something a fund finance team told us breaks. None of it is a feature list from a vendor page.

One, reconcile two charts of accounts. A head of finance at a mid-market private equity firm named this as the thing that drives her mad, because the management company runs a completely different chart of accounts from the funds, so every shared cost is mapped twice before it can be split. Mainstream ledgers have started answering this. Intuit's multi-entity guidance describes setting a primary company as the source and syncing its chart of accounts to the others, with the constraint that only the parent company can edit it.

Two, carry four real dimensions. A fund complex has to answer four questions about one entry at once. Which entity, which fund, which deal, which kind of cost. A ledger offering classes and customer names answers two of them, and teams then press unrelated fields into service to cover the rest. Concrete counts exist and are worth asking for. SoftLedger publishes its own, listing cost centers, products, jobs and up to three custom dimensions on top of entities and accounts, each taggable on "every document line and journal entry."

Three, carry adjustments as well as transactions. A ledger that books what happened and nothing else pushes every adjustment into a spreadsheet, and the spreadsheet quietly becomes the real record. Flexi is the general-purpose ledger that leans hardest into this, claiming unlimited allocation rules with visible history alongside unlimited companies, intercompany rules and automated eliminations.

Four, report along whatever line the business is actually run. A CFO at a large credit platform hired a head of financial planning specifically to get segments into the ledger, because the split was being done by hand outside it. At a multi-strategy venture firm the cut is not the fund at all, it is the subsector, and each one has different stakeholders. If that cut is not inside the ledger it gets rebuilt by hand every reporting cycle.

Five, keep both sides of every intercompany balance in agreement. Any allocation that crosses an entity boundary creates a due-to and a due-from, and the two have to match before consolidation can eliminate them. This is standard intercompany accounting and it is where multi-entity ledgers separate from single-entity ones.

Six, hold the entity list as its own truth. Every vehicle that exists has to sit in the ledger's own list rather than in a file that arrives from somewhere else.

Seven, survive being chosen by somebody else. Where an outsourced administrator runs the fund books, the manager inherits whatever ledger the administrator licenses. A controller at a wealth and alternatives platform put it as being at their mercy on the ledger they license, with no expectation of it changing.

Eight, get the split across the boundary without anyone typing it twice. Three firms, asked how their two ledgers talk to each other, gave three answers and not one was an integration. The first has no connection between them whatsoever. The second offered to take a file in whichever format its fund team can ingest. The third routes allocation output into a data layer its administrator runs, which enriches it before anything reaches the fund ledger. Put a write-back row on your requirements list by all means, and expect a file to be the honest answer to it.

Requirement six is the one whose failure is hardest to see, so it is worth walking through. An administrator sends a reference file each quarter carrying the entities and their commitments, and the allocation runs against it. One quarter the file omitted a newly formed vehicle. The team allocated a batch of shared costs without it, and because the omission changed the denominator, every other entity's share was wrong too.

Here is what that costs. A $180,000 batch of shared costs, allocated by committed capital, against a file listing five vehicles totaling $750M of commitments. The missing SPV had $150M committed, so the real base was $900M.

Six entities to reclass because of one omission, and nothing in the ledger flagged it, since $180,000 was fully allocated either way and the entries balanced. The same firm gets its fund-side data file quarterly with a lag of roughly sixty days after quarter end, so the picture it allocates against is two months old before anyone touches it. Multi-entity allocation was named a core source of complexity by 77 of the same 80 teams, or 96%, and this is the shape it takes.

How do firms end up on the ledger they have?

Almost none of the fund finance teams we interviewed chose a fund general ledger by evaluating fund general ledgers. That single fact should change how this whole category is read.

One controller at a large middle-market private equity firm was direct about it. "We actually transferred over to NetSuite because we were using a really outdated system and it was going unsupported. So we kind of had to." At another firm the ledger came from the administrator's license. At a third, the firm does not own its own books of record, and the CFO drew the line carefully, calling what her team keeps internally shadow books held to reconcile against whatever the administrator publishes.

The long tail is stranger than a market-share chart suggests. A CFO with twenty-five years in private equity described his firm's ledger with a shrug, saying he had never heard of anyone else using it, and the allocations there are still done in Excel and pushed in. The system changes and the spreadsheet does not.

Can you configure a corporate ERP into a fund ledger?

Yes, and the cost is a permanent maintenance load. Two controllers described the same arc from opposite ends. The first implemented a major ERP about two years ago and thinks the firm over-engineered it, saying there are so many customizations that it is a load just to maintain it. The second, at a different firm, was blunter about capacity.

We're by no means NetSuite experts.

Put those together and you have the real trade behind "it is fully configurable." The configurability is real, the fund shape genuinely can be bolted on, and the resulting system has to be owned by somebody. On a lean finance team it is owned by whoever has time, which is how a firm ends up with seven or eight custom dropdown fields on every journal entry and nobody left who remembers why. What that configuration does and does not carry for allocations is set out in NetSuite fund expense allocation.

What lives on top of whichever ledger you run?

We sell an allocation layer that sits above the ledger, so we have a commercial stake in this section. That said, the reason the write path matters more than anything upstream of it is that the ledger is where a number stops being a draft. A spreadsheet, a methodology and an approval are all preparation for one entry, and an entry that lands without its reasoning has lost the reasoning for good.

That is why the allocation layer is a separate purchase from the ledger for most firms, and why the mechanics differ per ledger rather than being one integration built three times. The level above it, where several entities are rolled together rather than split apart, is multi-entity consolidation platforms. One shape recurs across every ledger. Either the split rewrites the original bill so a single unallocated line becomes ten, or the bill is left exactly as it arrived and a second entry balances it out, crediting the unallocated amount and debiting each entity. Whether the choice is yours usually turns on whether the bill has already been paid.

The limiting case makes the point better than any of this. One private equity manager runs the entire process over email. He has no expense platform and no bill-pay system, so there is nothing to write into any ledger. Reporting and exports were the whole of what he asked us for. A firm in that position still has an allocation problem, which means the allocation problem was never a property of the ledger. If the shortlist is what you came for, fund accounting software for private equity is the page that carries one.

Where does Ceviche fit?

Ceviche fits when the ledger is settled and the split that feeds it is still decided outside it, because the reasoning behind that split is the thing an auditor asks for and a spreadsheet does not keep. That is the layer Ceviche is. It applies the rules your team approved once, according to your LPA and expense policy, and every number it posts into the ledger you already run traces back to a human approval. Flybridge did that without changing systems, adding the allocation layer on top of the QuickBooks Online and Bill.com stack it was already running. It is not a fund administrator, a general ledger or a managed service, and it does not do the allocations for you. If a fund-side ledger is what you actually need, the requirements above are your specification and the shortlist is one page over.

Frequently asked questions

Do we need a fund general ledger, or a layer on the one we have? Ask what is actually failing. If your trial balance per entity is wrong or you cannot produce fund financials, that is a ledger problem. If the entries are fine and the quarter is consumed by deciding how to split shared costs, no ledger fixes it, because the decision happens before anything posts.

Can QuickBooks be used for fund accounting? It is the management-company ledger for 51% of the same 80 teams, so plainly it is workable, and Class tracking can stand in for entities in a small structure. Multi-entity allocation, a true fund-level balance sheet and the allocation audit trail are where teams tell us they hit the edge of it. Fund expense allocation in QuickBooks covers the workaround and where it stops holding.

What is the most popular general ledger software? For private fund management companies specifically, the two that dominate are QuickBooks at 51% and NetSuite at 23% of the same 80 teams, 73% between them. Sage Intacct was 5%. The remainder is a long tail including Xero, Dynamics, Workday and one ledger built on a customer relationship platform.

If our administrator runs the fund-side books, do we get any say in the fund general ledger? Usually very little. The administrator licenses the ledger and the manager inherits it, and switching means switching administrators. What you can negotiate is the data, which matters more day to day. Ask what format you receive, on what cadence, whether you get read access, and what happens to your history if the relationship ends.

What do we do about the chart of accounts differing between the management company and the funds? Map it once, deliberately, and keep the mapping somewhere both sides can see. Mainstream ledgers now support a shared chart across entities, with editing restricted to the parent. Where the fund books belong to an administrator, the mapping lives in your own documentation instead, and it needs an owner, because an unmapped new account silently breaks the next allocation run.

What are the risks of connecting third-party software to your general ledger? The two that bite are permissions and write shape. Something with write access can post entries, so scope it to the accounts it needs and require approval before posting where your ledger supports it. Then check whether it edits original transactions or adds balancing entries. The second is safer and easier to audit, because the charge as it arrived stays as it arrived.