Some fund administrators run their own technology. Most license someone else’s. A third group sells software and performs no administration at all. The three get described in almost identical language, and the difference surfaces at month end, in who is accountable when a number is wrong and how long it takes anyone to notice.
For a manager comparing providers, the useful question is not which platform has the better interface. It is which of these three things you are actually buying, and what remains your job after you sign.
Three models that share a vocabulary
Software vendors. Companies like Allvue and FundCount build fund accounting and reporting systems and sell them to administrators and to managers who keep their books in house. The products are capable and the firms are serious. The work still belongs to whoever bought the licence. A manager who buys a fund accounting platform has acquired a tool and still needs somebody to operate it, which in practice means hiring an operations person or an outsourced team to sit behind it.
Administrators running licensed technology. This is most of the market. The administrator delivers the service and runs it on software built by somebody else. Alter Domus publishes its stack openly, naming Yardi for real asset accounting, eFront, FIS Investran, and Allvue across different asset classes and strategies. There is nothing deficient about this arrangement. Firms in this category carry decades of operational depth and routinely handle structures that no platform can absorb. What defines the model is that the technology sits as a layer over an operating model designed around handoffs, between systems and between the teams that own them.
Administrators where the technology is the operating model. Here NAV production, investor onboarding, subscription processing, and reporting run through one system instead of being passed between several. The administrator built the software it runs on, so the system and the service were designed against each other.
One category is worth separating out before going further. Platforms built for venture capital and private equity, Carta being the most visible, serve closed-end vehicles with capital calls, cap tables, and multi-year lock-ups. They appear constantly in searches about fund administration software and they are solving a different problem for a different structure. A hedge fund with monthly subscriptions and redemptions, high water marks, and recurring NAV obligations was not the vehicle those systems were designed around. Managers who evaluate them anyway tend to spend several weeks confirming what the category description already implied.
The third model is not a recent invention. The largest administrators have operated this way for years. SS&C built and acquired its own technology stack and runs its service on it, which is a significant part of why it scaled the way it did. What has changed is the fund size at which the model is available, and the quality of the technology from new players. Integrated operations used to carry an institutional minimum, in both fee terms and in service complexity, and what was once cutting edge technology has grown stale and outdated. That minimum has come down, technology has improved, and the middle of the market now has access to an operating model that was previously reserved for the top of it.
Why the middle of the market had no integrated option
For most of the last two decades the choice available to a fund below institutional scale was constrained by economics on both sides.
Building an administration platform is expensive and the payback period is long. A firm doing that work needs enough funds on the system to amortise the build, which means either starting with institutional clients or absorbing years of loss. The administrators who made that investment did so from a position of existing scale, and they set fee and asset minimums that reflected what the investment cost them. A manager launching with twenty or forty million dollars was not a viable client for a firm carrying that overhead.
The firms that served the middle of the market therefore made the sensible decision. They bought capability instead of building it, licensing accounting and reporting software from specialist vendors and wrapping service around it. That produced a functioning market and it also fixed the operating model in place, because a service business assembled from licensed components has handoffs designed into it at the seams between the components. Nobody was going to redesign the workflow when the workflow was determined by which systems the firm had bought.
Two things shifted. Infrastructure costs fell far enough that building a platform stopped requiring institutional scale to justify, and the number of funds launching below the traditional minimums grew large enough to support a firm built for them. The result is that integrated operation is no longer coupled to fund size the way it was. A manager running fifty million dollars can now buy an operating model that a decade ago started at several hundred million, and a manager who grows past that point does not have to leave the model behind to keep growing.
What actually happens at month end
In the licensed-technology model, a close moves data across boundaries. Trade and position data arrives from prime brokers and custodians and is loaded into the accounting system. Accounting output feeds a reporting tool. Investor-level capital activity sits in a register that may be a separate application or, at smaller managers, a spreadsheet. Statements reach investors through a portal fed by an export, or by email.
Each of those boundaries is a reconciliation. Most months they are clean. When one is not, the manager usually finds out through a question from an investor or from the auditor, and answering it means tracing a number backward through several systems to establish which version is correct. The cost is rarely the error itself. It is the elapsed time between the error occurring and anybody being certain what the right number was.
In an integrated model there is one record. The subscription, the position data, the NAV calculation, and the statement the investor opens are drawn from the same source. Reconciliation between internal systems stops being a task because there are no internal systems to reconcile.
That is the entire operational argument. It is narrower than most marketing suggests and it is real.
Where the difference is material
Investor onboarding. Subscription documents that arrive as executed PDFs have to be read by a person and keyed into a register, and every key stroke is an opportunity for divergence between what the investor signed and what the fund’s books say. Digital subscription flows write directly to the record that the NAV calculation and the investor portal both read. Repool runs onboarding through its own subscription platform, Warp, and handles KYC and AML checks along with accreditation verification for all investor types, including verification for 506(c) funds.
NAV production and distribution. Repool produces monthly per-investor and fund-wide NAV prints and quarterly financial statements for the fund and its investors. In an integrated model, the figure an investor sees in the portal is the figure the administrator calculated, with no export sitting between the two.
Fee and expense calculation. Management and performance fee calculations depend on investor-level capital activity, including timing of subscriptions, redemptions, and any series or equalisation mechanics. When capital activity lives in the same system as the fund accounting, the fee run stops being a separate exercise assembled from two sources.
Ongoing filing obligations. Blue sky filing obligations and Form D deadlines turn on where investors are located and when they subscribed, which means the compliance calendar is a function of the subscription data. Repool monitors asset composition and Form D and blue sky filing obligations automatically, which is possible because both sets of information sit in one place.
The industry has spent years buying administration, compliance, external consultants, and technology separately and then having to coordinate all their disconnected vendors, in many cases overpaying for services they are unfamiliar with but which are actually trivial. Many fund services are far less complicated and worth far less than what people pay for them, and the administrative burden of managing all vendors is a distraction from a fund manager’s core mandate – generating returns. We built a unified platform to make operating a hedge fund simultaneously more transparent, more affordable, and less burdensome.
Kevin Fu, Chief Executive Officer, Repool
Where integration changes nothing
A piece like this is only useful if it marks the limits, so here are three.
Audit and tax. Repool publishes the boundary directly: its services do not include tax form preparation or annual audits. Those stay with external firms, and they should. An administrator producing the books and also auditing them is a governance problem that no amount of system design resolves. A published scope exclusion is worth more to a manager than a vague claim of end-to-end coverage.
Genuinely difficult valuation. A fund holding illiquid or hard-to-price positions needs a valuation policy with independent pricing sources, documented override authority, and a record of who exercised it. That is governance. Software can enforce a policy and cannot supply one. Managers with material Level 3 exposure should evaluate providers on valuation process first and platform second.
Multi-jurisdiction regulatory coverage. A manager running vehicles across several regulatory regimes may need a provider with specific jurisdictional presence and local filing capability. That is a function of the firm’s footprint, not of its architecture, and it is one of the areas where the large institutional administrators remain the correct answer for the funds that need them.
Independence and concentration are separate questions
Two objections circulate in this debate and they deserve to be handled separately, because they are usually collapsed into one.
The first is independence. Gresham Technologies has argued that managers should shadow their administrator by maintaining an independent set of books to check against, and AIMA has published on independent NAV validation and the transparency that allocators increasingly expect. Both positions are sound. Neither is an argument against integration. Independence in fund administration means the administrator is independent of the investment manager, which is what an allocator tests in operational due diligence. A single-system administrator is exactly as independent of the manager as a multi-system one. The architecture of the administrator’s software has no bearing on it.
The second objection is concentration, and this one is genuine. A provider holding formation, administration, investor servicing, and compliance is more concentrated than four providers holding one function each. That is a legitimate operational due diligence question and any platform should be able to answer it directly, covering what happens if the provider fails, what the exit path looks like, how long a migration takes, and who holds the records in the meantime. Managers should ask it, and a provider that treats the question as hostile has told you something useful.
Five questions that separate the models
A provider’s marketing will not reveal which category it occupies. These will.
- Did you build the system you run on, or do you license it? If you license it, from whom, and which functions sit outside that system?
- When an investor subscribes, how many systems does that subscription touch before it reaches the NAV calculation?
- Is the figure in the investor portal calculated in the portal, or exported into it from somewhere else?
- When a NAV is wrong, who do I call, and can that person see the trade data, the investor record, and the statement without asking a colleague?
- What do you not do, and who does it instead?
The last question carries the most weight. A provider that cannot state its boundaries in a sentence has not thought about them, and the manager will find them at the least convenient moment, usually during an audit or an allocator’s due diligence process.
None of the three models is the right answer for every fund. A manager running a straightforward long-short equity strategy with a growing investor base has different priorities from one running structured credit across three jurisdictions. The mistake is not choosing the wrong model. It is assuming that three things described in the same language will behave the same way once the money is live.
