"RaftLabs elevated my ideas and brought them to life when everything seemed impossible."
Grady Lakshmono
CoFounder, Moka (acquired by Gojek) & Gula (acquired by Runchise)
Fund Administration Software Development Services
We build fund administration software when approved fund structures, accounting data, investor records, capital activity, allocations, reviews, reporting, and portal workflows cannot be supported by established products and integration. Start with one fund type and one controlled period close. Qualified fund, legal, tax, accounting, and compliance owners approve the rules and outputs.
Bring the problem, the current workflow, or the existing code. We reply with a practical next step within one business day.
Trusted by
The brief
Good software decisions begin with the constraint, not a list of features or a preferred technology.
Fund books, bank and custody records, investor allocations, capital activity, and reports require manual reconciliation across workbooks?
A released NAV or investor statement cannot be reproduced from the exact source versions, rules, exceptions, reviews, and approvals?
Plain answer
Fund administration software connects fund books, investor records, capital activity, allocations, valuations, fees, approvals, reports, and portal delivery through a controlled period close. Custom development fits when established products cannot support a material structure or workflow. The software executes rules defined by qualified owners and retains sources, rules, exceptions, and reviewer for each released result.
What to remember
One valuation arrived late, a fee calculation used an earlier period, and the investor statement came from a workbook that did not match the approved close.
Fund administration software earns trust when the released number and every allocation can be replayed.
The workflow may connect fund and entity books, holdings, valuation inputs, cash, fees, expenses, investors, commitments, subscriptions, calls, distributions, allocations, share or partnership interests, currency, approvals, reports, and portal delivery. The exact model depends on the fund and governing documents.
This buyer intent is distinct from generic accounting or workflow automation because the product must preserve the connection between fund-level results and investor-level positions through a controlled close. Established administration platforms remain the default. Custom ownership requires a material gap and qualified professional governance.
RaftLabs does not cite a named fund-administration result on this page. Buyers should assess fund and investor calculations, source lineage, period controls, parallel reconciliation, permissions, exception handling, document and report fidelity, security, and operating ownership. Adjacent fintech work is not evidence that a NAV or allocation is correct.
Custom software should solve a material structure or operating gap, not replace specialist review.
A fund, allocation, investor, portal, reporting, residency, or integration rule remains unsupported.
Fund accounting, operations, legal, tax, compliance, security, and technology owners can approve the workflow.
Representative periods, expected calculations, source records, and reports are available for a focused release.
An established platform supports the structures and only configuration, migration, or adoption is missing.
The team expects software engineers to determine valuation, accounting, tax, legal, or compliance treatment.
Governing terms, source authority, close controls, investor records, or professional owners are unresolved.
It is whether custom fund administration software is the right answer at all. We use four possible recommendations before discussing a development scope.
Choose a maintained product when it handles the core workflow and the remaining gaps can be solved with configuration, a connector, or a small process change. Paying for fund administration software you do not have to maintain is often the better trade.
Keep the existing product when users still get value from it and the code can be understood safely. Start with evidence: where the code lives, how the data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.
Own fund administration software when the workflow shapes margin, customer experience, speed, or a product customers pay for. Start with one complete path and the system connections that path cannot work without.
Do not turn a changing policy into permanent software. Stabilise the rules, name the workflow owner, and measure the cost of the current process before paying for a product.
Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.
Bounded scope
Ingest approved accounting, bank, custody, portfolio, expense, and valuation records with entity, account, instrument, currency, period, source, and version lineage. Reconcile balances and surface missing, late, duplicated, or conflicting records in an owned exception queue.
Execute client-approved fee, expense, valuation-input, currency, class, and investor-allocation rules. Preserve rule versions, assumptions, overrides, reviewer, and period state. Route preparation, review, approval, lock, correction, reopening, and rerelease without erasing the earlier close.
Track approved commitment, subscription, call, receipt, distribution, transfer, and balance events. Generate notices, statements, reports, and supporting schedules from the released period. Reconcile cash status without treating a portal update as authority to move funds.
Give authorised users access to approved documents, statements, capital activity, and requests by fund, entity, and role. Include strong identity, least privilege, access review, audit, retention, secure uploads, monitoring, support boundaries, incident response, release, and recovery.
| Approach | Use it when | |
|---|---|---|
| Administration platform | Use established fund, accounting, and investor functions | Its structures, rules, controls, integrations, and support fit. |
| Integration and reporting layer | Keep existing books and administration | Source reconciliation or approved report delivery is the main gap. |
| Custom workflow module | Own one material administration step | A calculation, review, exception, or portal need remains unsupported. |
| Custom platform | Own the controlled fund close | Distinct structures justify long-term professional, product, and security ownership. |
Prototype representative and difficult periods: late prices or valuations, amended transactions, stale exchange rates, fee boundaries, class differences, new and departing investors, calls, distributions, transfers, side terms where approved, rounding, corrections, and report regeneration. Expected results come from qualified client owners.
Run the new workflow beside the approved process. Reconcile fund books, cash, holdings, fees, expenses, NAV where applicable, allocations, investor balances, notices, statements, and reports. Every material difference needs a disposition. The client approves release; a passing software test does not replace fund accounting or assurance.
Delivery
Four phases make professional review and parallel close the gate to reliance.
Choose one fund type, entities, books, investors, capital activity, calculations, reviews, reports, advisers, and acceptance examples.
Run representative subscriptions, calls, distributions, valuations, fees, allocations, currency, corrections, exceptions, and reports through a prototype.
We define ingestion, books or subledgers, calculations, approvals, documents, portal access, integrations, audit, monitoring, and recovery.
Reconcile selected historical and current periods, resolve exceptions with qualified owners, validate reports, train operators, and transfer runbooks.
Risk
Scope and price
Start with one fund type, one controlled period close, and one investor-reporting path.
The estimate separates platforms, data, legal, tax, accounting and compliance review, banking, custody, hosting, security, support, and change ownership.
Starting investment
Starts at $10000
Several structures, currencies, classes, waterfalls, portals, or migrations add scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.
Parallel reconciliation before reliance
Representative periods are compared with approved expected results before cutover.
No fund-administration opinion
RaftLabs builds approved workflows; it does not provide valuation, fund accounting, legal, tax, compliance, or investment advice.
Financial Software Development
Build governed financial records, calculations, controls, reporting, and operating ownership.
Cap Table Software
Manage approved instruments, ownership events, vesting, scenarios, stakeholder access, and reconciliation.
Compliance Automation
Design control, evidence, review, exception, audit, and change-management workflows.
Data Engineering
Build governed ingestion, quality, lineage, storage, and operations across fund sources.
Proof
Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.
"RaftLabs elevated my ideas and brought them to life when everything seemed impossible."
Grady Lakshmono
CoFounder, Moka (acquired by Gojek) & Gula (acquired by Runchise)
Work with us
Bring one fund structure, representative periods, approved calculations, source and expected reports, exceptions, investor workflows, advisers, and control requirements.
Use an established fund-administration or accounting product when its structures, books, allocations, reporting, controls, and integrations fit. Custom development is credible when a material fund, investor, calculation, portal, residency, or operating workflow remains unsupported and the organisation can own professional review, security, reconciliation, and ongoing regulatory and product change.
It can execute calculation, valuation-input, fee, expense, allocation, currency, and approval rules defined by the client's qualified fund accounting and valuation owners. Each released result should retain sources, prices or values, rules, assumptions, exceptions, reviewer, and period version. RaftLabs does not determine fair value, accounting treatment, or reporting compliance.
Yes, using client-approved commitment, allocation, notice, due-date, receipt, default, distribution, recallable, fee, expense, waterfall, and reporting rules. Cash movement remains with approved banking, custody, payment, and control processes. The system reconciles requests, receipts, approvals, and investor records without presenting software workflow as legal or payment authority.
It can collect approved data and documents, integrate qualified providers, route review, track status, expiry, refresh, exceptions, and evidence, and restrict access. The client and its qualified compliance and legal teams define jurisdiction, investor eligibility, KYC, AML, sanctions, privacy, retention, escalation, and acceptance. Software does not approve an investor by itself.
Ask who performs NAV calculations, who reviews them, and who verifies they are correct. NAV should be calculated independently of the manager. Manual spreadsheet NAV creates key-person dependency and untraceable changes. Use a written valuation policy, independent pricing sources, and logged, reviewed overrides.
Ask who retains the fund's books and records, in what extraction format, and under what migration, termination, and transition provisions. Confirm you have independent data access without vendor consent, and that exit portability is stated in the contract.
Compare total operating effort, not invoice versus salary: personnel, software, accounting, compliance, reporting, controls, management time, and continuity. Admin work spikes at closings, capital calls, distributions, and tax season, so judge cost and staffing at the peaks, not the average. Complex performance fees and side-letter deals often live in spreadsheets; an independent shadow NAV and fee calculation is the verification answer.
Four questions. The independence question: who calculates, who reviews, who verifies? The portability question: what happens to our books if the provider fails? The spike question: how does the system handle closing week, capital-call week, tax season? The waterfall question: complex performance fees and side-letter deals, spreadsheet or calculated? Require dual authorization on all cash movements.
A focused administration workflow covers one fund type, one controlled period close, and one investor-reporting path. Several fund types, entities, currencies, classes, complex allocations or waterfalls, external providers, investor portals, large migrations, or formal validation add scope. Licences, specialist advice, data, hosting, security, support, and change ownership remain visible.