Fund Accounting and NAV Oversight: Build Shadow, or Buy pControl?
Complexity decides this, not assets under management, and the test is a count rather than a number.
On this page
Complexity decides this, not assets under management, and the test is a count rather than a number. If none of these is true, buy: negotiated fee terms a vendor configuration cannot express, series accounting or equalisation where your oversight stops at fund level, more than one administrator, or oversight quality that visibly degrades on volatile days. If one is true, buy Milestone Group pControl and configure it. If two or more are true, build, and expect $80,000 to $180,000 for a first release in 12 to 18 weeks. Managers running one fund, one administrator, one share class and a liquid long only book should build nothing at all.
When is off the shelf genuinely the right call here?
If you run one fund, one administrator, one share class and a liquid long only book, buy nothing. A locked workbook with protected formulas and a signed checklist is honest oversight at that size, and a bespoke platform would be theatre. We say this to managers regularly and it costs us the engagement.
If your fund range is conventional, your fee terms are standard and your administrator relationship is stable, buy Milestone Group pControl. It is purpose built for net asset value (NAV) oversight and it is genuinely the closest packaged answer available. No first release build will match its depth for the same money, so buy it and put the difference into people.
If you already run SS&C Geneva or SimCorp Dimension as your investment book of record and your operating model matches theirs, extend that footprint before starting something new. BNY Eagle is a solid accounting and data management platform on the same logic. For private capital, FIS Investran is the standard and there is no reason to reinvent it.
None of these are poor products. They are built around their own model of a fund, a fee, a share class and a valuation policy, and where your operating model matches that model they will do the work faster and cheaper than anything you commission. The question is only whether your oversight rules are a fund model or your model.
When does a custom build actually pay off?
The build case is narrow and specific, and it starts with tolerance policy. Your rules are not a fund model. They are the tolerance you apply to a level two bond price against a level one equity, the five basis point difference you accept on the emerging market sleeve and the zero you accept on the money market fund, and the escalation path that sends a break over a threshold to the chief investment officer rather than to the analyst. Configuring that into a packaged platform is a long implementation with a consultant, and at the end you own a configuration you cannot read.
The second trigger is fee terms. Management fees on a tiered scale with a breakpoint, performance fees with a high water mark per series, an expense cap with a recoupment window, a distribution fee that differs by share class. Every one of these is arithmetic that any competent system can do and almost nobody independently checks daily, because checking it means reimplementing the fee schedule from the offering document. In our delivery experience that is the single feature that finds real money, because fee errors do not self correct. They compound quietly and surface during the audit.
The third is series accounting and equalisation. The administrator's number for the fund can be right while an individual investor's allocation is wrong, and if your offering documents promise a specific method, oversight that stops at fund level is not oversight of the promise you made.
The fourth is the honest one. If your review gets shallower on volatile days, the control fails on exactly the days it exists for.
How do they compare on the things that matter in this industry?
Reconciliation depth. Comparing two position files finds the easy breaks. It misses a position that agrees on quantity and disagrees on cost basis, a bond that agrees at security level and disagrees because a factor update was applied on one side only, a swap netting to the same exposure with a different sign convention, or a corporate action booked as cash on one side and stock on the other. A build normalises both sides into one instrument and event model first, then reconciles quantity, cost, accrued income and market value separately.
File reality. Every administrator sends a different package. Some send a clean daily extract, some send a workbook with merged cells and a tab per share class, some send a document. No packaged tool absorbs that gracefully, and an administrator change frequently turns into a second implementation project.
Price challenge. Under Rule 2a-5 the board or its designee owns fair value determination and the evidence has to exist. A challenge that lives in an email thread is not evidence. A build treats it as a first class object with source, timestamp, staleness measure, tolerance band, the alternative source, the administrator response and the applied price recorded together, and the valuation committee pack generates from that record.
Change cadence. If a change to your own escalation thresholds is a chargeable request with a queue position, your control function runs at somebody else's release cadence. That is the comparison line most managers underweight.
Where the products win. Depth, an operating history, and a support arrangement your auditor has seen before.
What does total cost of ownership look like at your scale?
A first release covering administrator file ingestion, an instrument and event model both sides normalise into, position and cash reconciliation, tolerance rules by security type with ageing, an exception queue and price challenge runs $80,000 to $180,000 in 12 to 18 weeks. Adding independent fee recomputation, capital activity checks against dealing deadlines and an evidence pack takes it to $200,000 to $350,000 over 6 to 9 months. Series accounting and equalisation at investor level, several administrators and derivative or structured credit event models push it to $350,000 to $500,000 over 9 to 12 months.
A worked manager with six funds across two administrators, a long only book with a modest over the counter sleeve and performance fees with a high water mark lands at $210,000, with the fee engine and evidence pack in scope from the start. Remove those two and it is $170,000. Add equalisation and a third administrator and it approaches $300,000.
Running costs are 15 to 20 per cent of build annually. Hosting is small, usually a few hundred dollars a month, because data volumes are modest even though the logic is dense. The recurring spend is people work: administrator format changes, new instrument types as the book evolves, fee schedules for new mandates. If you subscribe to an independent pricing source for the challenge workflow, that data contract can exceed the software support line, so price it before committing to the feature.
Get three numbers from your incumbent before you decide: the three year renewal, the per user cost of two more oversight staff, and the day rate plus lead time for a change request.
What does the hybrid look like, and when is it the honest answer?
The hybrid here is a boundary rather than two products. You are verifying an accounting record, not replacing one, so the general ledger stays where it is and every hour spent on ledger features is an hour not spent on tolerance and challenge logic. Managers who blur that line end up with an expensive second book of record and the same oversight gap.
The sequencing hybrid is the one worth planning. Start with your largest fund and your two noisiest break classes, which in our delivery experience account for most of the manual time, and prove the model there. Accept next day oversight in phase one if your dealing deadlines allow it, then tighten to same day once the reconciliation and tolerance logic has run against real files for a quarter. Same day verification before a forward priced cut off under Rule 22c-1 tightens every engineering choice about queueing, retries and partial data, and it is materially more expensive to build.
Encode only the fee terms you actually have. A configurable engine that could express any structure in the market costs several times what an engine expressing your eleven live schedules costs, and you extend it when the twelfth arrives.
One request costs nothing and removes weeks. Ask your administrator for their structured extract before you accept their workbook. Many will provide one and almost nobody thinks to ask.
Which should you choose, by operator size and stage?
One fund, one administrator, one share class, liquid book: build nothing. A locked workbook and a signed checklist is the control. Revisit when complexity arrives, not when assets do.
Conventional range, standard fee terms, stable administrator: buy pControl, or extend the Geneva or SimCorp footprint you already run. Resource the configuration properly and accept the operating model that comes with it.
Six to twenty funds, negotiated fee terms, one or two administrators: build the first release and add fee recomputation as a funded second phase. This is the population where the daily eighty minute scramble is real and the fee schedules are already outside what a vendor configuration will hold.
Series accounting or equalisation, or three or more administrators: build the platform. Oversight that stops at fund level is not oversight of what your offering documents promise, and multiple administrators means multiple ingestion problems with different failure modes rather than one problem at higher volume.
Any manager expecting an administrator change in the next two years: build the ingestion layer whatever else you decide. A custom mapping component isolates that change while your reconciliation rules, tolerances and evidence history stay intact, and that alone often justifies the phase.
If you would rather scope this before committing budget, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- APQC's Open Standards Benchmarking data on the monthly financial close found median performers take about 6.4 calendar days to close the books, while top performers (top 25%) do it in 4.8 days or fewer and bottom performers (bottom 25%) take 10 or more days. Source: APQC (2018) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
Frequently asked questions
What happens to our oversight system if we change fund administrator?
This is one of the strongest arguments for owning the layer. A new administrator means new file formats, new naming conventions and often a different level of detail, and a custom ingestion layer isolates that to one mapping component while your reconciliation rules, tolerances and evidence history stay intact.
Managers running oversight inside a packaged platform frequently find an administrator change turns into a second implementation project, with its own timeline and its own consultant. Ask any vendor what their last administrator migration took, in weeks, before you sign.
What happens if pControl or our incumbent raises prices or change request rates?
The renewal is rarely the number that decides it. Ask for the three year figure, the per user cost of two more oversight staff, and the day rate plus lead time for a change request, then compare that total against a build plus three years of support at 15 to 20 per cent.
The change request line is the one that matters. If altering your own escalation thresholds is chargeable and queued, your control function runs at somebody else's release cadence, and a price rise on top of that is a governance issue rather than a budget one.
How long does a NAV oversight build take, and when can we go live?
Twelve to eighteen weeks to a first release the oversight team runs daily, then a full reporting period of parallel running against your existing workbook before you retire it.
The schedule risk is almost never the reconciliation engine. It is normalising administrator packages, because some arrive as a clean daily extract and others as a workbook with merged cells. Managers who already receive a structured extract typically reach go live several weeks earlier, which is why asking for one is the first thing to do.
Is Milestone Group pControl good enough, or should we build?
For a conventional fund range with standard fee terms and a stable administrator, pControl is genuinely the closest packaged answer available and a first release build will not match its depth for the same money. Buy it.
The case for building appears when tolerance rules, escalation paths and fee terms are negotiated per mandate rather than standard, when you run series accounting or equalisation and need oversight below fund level, or when you use multiple administrators whose file realities differ. Configuring highly specific policy into a packaged platform tends to produce a long implementation and a configuration nobody can read afterwards.
Why does instrument complexity change the price so much?
Because each instrument class needs its own event model rather than an extra column. A swap can net to the same exposure with a different sign convention, a bond can agree at security level and disagree because a factor update was applied on one side only, and a private position needs capital call and distribution events a listed equity never has.
Reconciliation that compares two files will find none of those reliably. Building a model that does costs real weeks per class, which is why a long only book sits near the floor of the band and one with derivatives, structured credit and private positions sits near the ceiling.
Can custom software independently check management and performance fees?
Yes, and in our delivery experience it is the feature that finds real money. The approach is to encode the fee terms from your own offering documents as executable rules, including tiered scales with breakpoints, high water marks per series, expense caps with recoupment windows and class specific distribution fees, then recompute daily and compare against the administrator.
Fee errors do not self correct. They compound quietly through the period and surface during the audit, when fixing them is expensive and awkward to explain. Encode only the schedules you actually have and extend when a new mandate arrives.
What does Rule 2a-5 require a system to record?
Rule 2a-5 places fair value determination with the board or its designee, which means the evidence behind a valuation decision has to exist and be producible. A system supporting that treats price challenge as a first class workflow object rather than an email thread: source, timestamp, staleness measure, tolerance band, alternative source, administrator response and applied price all recorded together.
Insist on append only storage with independent verification, so no party including your developer can amend a past valuation decision. Your auditor will ask who can change the logic and who can edit history, and the answer needs to be clean.
What is the cheapest useful version we could build?
Ingestion, the instrument and event model, position and cash reconciliation with tolerance rules and ageing, an exception queue and price challenge. That is the $80,000 to $180,000 first release and it converts the daily scramble before the strike into a reviewed process.
Below $80,000 you are buying a reconciliation script. It will find the easy breaks and miss the ones that cost money, which is exactly the failure mode you are trying to remove, so a cheaper version is worse than no version.
Who owns the code when an agency builds my accounting software?
You should, outright, and the contract must say so with an explicit IP assignment clause rather than a usage license. Insist that the code lives in a repository you control from day one, so nothing, including the ledger schema and migration scripts, can be held back at the final invoice. Third-party libraries and any framework the agency reuses stay under their own licenses, and a clean contract lists exactly which those are.
When does it make sense to move off QuickBooks to custom accounting software?
Move when you are paying people to work around the tool, not when the subscription feels expensive. Common triggers are hitting the 25-user cap on QuickBooks Online Advanced, consolidating multiple entities in spreadsheets, or a billing model that forces manual journal entries every month. If your team spends several hours a week exporting to Excel just to answer basic questions, you are already paying for custom software in salaries.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
I'm outgrowing FreshBooks. Is custom software the logical next step?
Usually not directly, because FreshBooks is an invoicing tool more than a full accounting platform, and the natural next step is QuickBooks or Xero for proper double-entry books. Custom development makes sense when those do not fit either, typically because of a billing model none of them handle, like usage-based or milestone billing. In that case a custom billing engine that feeds a standard ledger is often smarter than replacing everything.
What can custom accounting software do that QuickBooks, Xero, and FreshBooks can't?
It encodes your actual business rules: progress billing tied to project milestones, revenue recognition for your specific contract types, landed cost tracking, or approval chains that match your org chart. Off-the-shelf tools handle generic bookkeeping well but force every business into the same chart of accounts and workflow. FreshBooks, for example, is built around freelancer-style invoicing, so inventory or multi-entity accounting means leaving the product entirely.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
How long until custom accounting software pays for itself?
Typical payback in Digital Heroes accounting projects is 18 to 36 months, driven by recovered labor hours and fewer billing errors rather than saved subscriptions. A business spending 30 hours a week on manual reconciliation and rebilling can justify a $75,000 build inside two years at ordinary bookkeeper rates. If your projected payback stretches past five years, extend your current tools instead.
What are the biggest mistakes companies make when building accounting software?
The three we see most across Digital Heroes rescue projects: replacing everything at once instead of automating the most painful workflow first, skipping the parallel run so errors surface in live books, and letting developers design the ledger without an accountant reviewing the data model. A fourth is quietly expensive: no assigned owner for tax rate and compliance updates after launch. Every one of these is cheap to prevent and costly to unwind.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other accounting software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from James.
Senior Copywriter · New-york · 14 posts on the site
Published · Last updated .
