Every participation with its history Entry, transfer and exit recorded Distributions calculated per participation

Custom app for a fund's participant administration

Appfront builds participant administration systems for funds, limited partnerships (cv's) and partnerships: the register of participants and their participations, with every entry, additional contribution, transfer and exit recorded as a transaction with its supporting documents, the identification and screening that come with entry, distributions calculated per participation and sent to the bank as a payment batch, and the tax filings at year-end. So the fund's register isn't a spreadsheet of which three people each have their own version.

What is a fund participant administration app?

Participant administration is the register of who takes part in a fund, with how much, since when and on what terms, plus the administration of everything that changes: admissions, additional contributions, transfers between participants, withdrawals and inheritance. From it follow the distributions per holding, each participant's capital account and the tax returns. An app keeps that register with every change recorded as an event with documents and approval, calculates distributions per holding and produces the payment batch and the annual statements from the same data.

Without such an app, the register lives in a spreadsheet with a tab per fund, a transfer is processed by editing two rows, the identification file sits in a folder, and someone calculates each participant's distribution with a formula that no longer works when someone joins mid-period. At year-end reporting or an audit by your accountant, it turns out the register and the accounts disagree, and nobody knows since when.

We build custom because the register has to fit your fund structure and your obligations: how holdings are built up, which changes are possible and who approves them, what identification and screening you do on admission, how distributions are calculated and which accounting package you use. A generic CRM has no concept of a holding, a capital account or a transfer with approval.

Register and changes

Participants and holdings with their history; every admission, additional contribution, transfer, withdrawal or inheritance as a change with documents, approval and effective date, never as an overwritten row.

Admission with screening

On admission, the identification, the screening your framework requires and the participation agreement, recorded in the participant's file before the holding becomes active.

Distributions and statements

Distributions calculated per holding with the right period and proportion, approved and sent to the bank as a payment batch; annual statements and capital accounts from the same data.

How we build your fund participant administration app

We start with your last distribution and your last transfer: how they were calculated and processed, which documents went with them and where the register and the accounts diverged. The app follows from that.

1
Mapping the fund and your obligations

How holdings are built up, which changes occur and who approves them, what screening applies on admission, how distributions are calculated, which statements you produce and which accounting package you use.

2
Register and files

The participant register with holdings and history, and the file per participant with identification and agreements, linked to the fund.

3
Changes and approval

Admission, additional contribution, transfer and withdrawal as a change with documents, an approval flow and an effective date, and the capital account that moves with them.

4
Distributions, statements and taking over management

The distribution calculation with payment batch, the annual statements, the integration with the accounting system and the reporting portal, and then ongoing management.

What a fund participant administration app actually does

The components below come up in almost every fund with participants. Which ones you need depends on your fund structure and your supervisory framework.

Participant register

Per participant, the details, the file and the holdings per fund, with the history of each holding and the capital account.

Changes with approval

Admission, additional contribution, transfer, withdrawal and inheritance as an event with documents, approval and effective date, with an audit log.

Admission and screening

Identification, the screening your framework requires and the signed agreement in the file, with activation blocked while anything is missing.

Distribution calculation

Per distribution, the allocation across holdings by period and proportion, with approval and a payment batch to the bank.

Annual statements

For each participant, the annual tax statement and capital overview at year-end, generated from the register, as a PDF and as an export for the accountant.

Accounting integration

Mutations and distributions as entries in your accounting package, with the register and general ledger reconciled for each period.

Who we build a fund participant administration app for

The app is intended for administrators for whom the register is the basis of every distribution, statement and check, and where that register is currently a spreadsheet.

Real estate limited partnerships and partnerships

Participations in real estate funds with periodic distributions and transfers. The register with its history and the distribution calculation are the core.

Fund managers with multiple funds

Participants who are in several funds, each with its own terms. The register per fund and the mutations with approval matter most.

Crowdfunding platforms

Thousands of small participations with many new entrants. What you need is automated onboarding with screening, and payment batches.

Family funds and investment companies

A limited number of participants with complex participations and inheritance. The file per participant and the capital account are the core.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

This page covers the register and administration. For the quarterly reporting to participants, see our page on an app for quarterly reporting to participants; for real estate funds, our page on software for real estate investments; and for the accountant who audits the register, our page on accountant software. You can read about our approach at building software.

For the capital accounts and profit allocation behind the register, there is our fund administration software.

Participant register with participations and history Mutations as events with approval File with identification and agreements Activation blocked when screening is missing Distribution calculation per participation and period Payment batch to the bank Capital account per participant Annual tax statements Reconciliation of register and general ledger Integration with accounting and reporting portal

Why Appfront for your fund participant administration app?

A participant register is the fund's source of truth; if it's wrong, nothing after it is right. That's what we build on: every mutation an event, every distribution a calculation, every statement an export.

A mutation never overwrites

Entry, transfer and exit are events with a date, documents and approval. The register as it stood at any moment can be retrieved.

Distributions are calculated per participation

By period and proportion, including for mid-period entry. A formula that is right once is right every quarter.

Register and accounting reconcile

Every mutation and distribution is an accounting entry, and the reconciliation is checked for each period. The accountant gets an export, not a reconstruction.

Security and privacy in a fund participant administration app

The app works with participants' identification data, bank details, asset positions and documents, and with decisions that are subject to supervision. Access is set up per role and per fund: the administration team enters mutations, the manager and compliance approve, the accountant has read access to the fund, and the participant sees only their own participations via the reporting portal. Every change is logged with name and time; approved mutations and distributions are locked.

The app runs in a European data centre, with encrypted storage and daily backups, and keeps files for as long as your retention period runs. Integrations with accounting and the bank use their own keys, which can be revoked per integration.

Frequently asked questions about a fund participant administration app

Questions fund managers ask before they get started.

It maintains the register of participants and participations, records every entry, additional contribution, transfer, exit and inheritance as a mutation with documents and approval, keeps track of identification and screening at entry, calculates distributions per participation with a payment batch to the bank, and produces the annual statements and capital accounts from the same data.

As a transaction: the transferring and the receiving participant, the holding, the effective date, the agreement and the administrator's approval. The holding moves on the effective date, the capital accounts move with it and that quarter's distribution is apportioned by period. The register as it stood before the transfer can still be retrieved.

That depends on your fund structure and supervisory framework: identification of the participant, verification of the source of funds and suitability where required, and the signed participation agreement. The app records what you require, keeps the file up to date and blocks activation of a holding for as long as anything is missing.

For each distribution, the app divides the amount across the holdings in the proportion and by the period that your fund terms prescribe, including where a participant joins or leaves mid-period. The calculation is approved, then goes to the bank as a payment batch and to the accounts as a journal entry, and the participant sees it in their reporting.

Yes. The auditor gets read access to the fund, with the register at any reference date, the transactions with their documents and the reconciliation between register and general ledger per period. An audit starts with an export, not with a request for the spreadsheet.

Yes. Transactions and distributions go to your accounting package as journal entries, the payment batch goes to the bank, and the register feeds the quarterly reporting to participants if you also use that app. We connect to what you already have; the register does not become a second set of accounts.

Check that first. An external administrator keeps the register for you, and that may be enough if you don't need your own view of it. Custom software makes sense if you want to approve and track transactions yourself, if admission and screening are in your own hands, if distributions need to follow your own terms, or if the register is currently kept in your own spreadsheet alongside the administrator's.

A register that is right at every distribution, filing and audit?

Tell us how many funds and participants you manage, which accounting package you use and how your last distribution or transfer was processed. We'll show you what the register, the transactions and the distribution calculation would look like.

Edit content