Capital Call
Create capital calls from investor contribution files, track payment status, and reconcile incoming bank transactions with expected contributions
Introduction
The Capital Call feature enables fund managers, management companies (ManCos), and fund administrators to track investor capital contributions and reconcile incoming payments against expected amounts. Capital calls (also known as drawdowns or capital commitments) are the mechanism by which general partners (GPs) request investment capital from limited partners (LPs), and FinologeeBKO connects that process to the receiving bank accounts where the money actually arrives.
Major capital call scope — investor management, fund accounting, and notice preparation — typically resides in investment management systems such as eFront Invest or Investran, and those systems rarely connect directly to fund manager bank accounts. FinologeeBKO closes that gap: users import the expected contributions, the platform matches incoming credit transactions from bank statements against them, and each contribution carries a status showing whether the investor has paid, paid partially, or not paid at all.
The interface provides a capital call list with collection progress, a details page combining an overview card, a collection chart and the aggregated receiving-account balance, an expected contributions view that groups contributions by investor or by tranche, a list of non-reconciled related transactions, a document library, and a complete audit trail.
Prerequisites
Users need the Capital Call tenant flag enabled and the appropriate permissions. The interface displays only capital calls whose receiving accounts the user can access.
Permissions
| Permission | Description |
|---|---|
CAPITAL_CALL_READ | View the capital call list, details, contributions, investors, tranches, documents, and audit log |
CAPITAL_CALL_WRITE | Create capital calls, reconcile contributions, exclude transactions, upload and delete documents |
ORDERING_PARTY_ACCOUNT_READ | Select receiving accounts when creating a capital call |
ORDERING_PARTY_STATEMENT_READ | View and reconcile the statement transactions linked to a capital call |
ORDERING_PARTY_BALANCE_READ | View the aggregated D-1 balance of the receiving accounts |
Feature flag requiredThis feature requires the CAPITAL_CALL tenant flag. Without it, the Capital call entry does not appear in the navigation menu and the external API endpoints reject requests. Contact [email protected] to have the flag enabled for a tenant.
Account scopingUsers see only capital calls whose receiving accounts they have been granted access to. The non-reconciled related transactions list is scoped further: it shows transactions only from receiving accounts the user can read through
ORDERING_PARTY_STATEMENT_READ. Users without that permission still see contributions and reconciled amounts, but no transaction detail.
Capital call overview
A capital call groups the contributions expected from a set of investors, the bank accounts that receive them, and the reconciliations that link incoming transactions to those contributions.
Structure
| Component | Description |
|---|---|
| Capital call | The drawdown itself: name, unique reference, creation date, due date, currency, receiving accounts |
| Contribution | One expected payment: investor, optional tranche, expected amount, currency, reference, status |
| Investor | The limited partner owing the contribution, created from the investor names in the imported file |
| Tranche | Optional grouping of contributions, created from the tranche names in the imported file |
| Receiving account | An ordering party account on which incoming contributions are expected |
| Reconciliation | The link between a statement transaction and a contribution, carrying the reconciled amount |
Contributions sharing the same investor name are attached to the same investor, and contributions sharing the same tranche name are attached to the same tranche. Both comparisons ignore case and accents.
Lifecycle
A capital call progresses through the following stages:
- Creation — a user imports the expected contributions from a file, or an external system creates the capital call through the API
- Automatic reconciliation — each time a daily bank statement is processed, FinologeeBKO reconciles the credit transactions that match a contribution exactly
- Manual reconciliation — users reconcile the remaining contributions against candidate transactions, including partial and split payments
- Closure — the day after the due date, a scheduled job closes the capital call and sets every contribution still awaiting payment to Not paid or Partially paid
Currency handling
Each capital call is denominated in a single currency. When all imported contributions share the same currency, that currency becomes the capital call currency; when they differ, the capital call takes the tenant base currency.
Individual contributions keep their own currency. Aggregate amounts — total expected amount, total reconciled amount, tranche and investor subtotals — are converted to the capital call currency using the exchange rate of the due date, and the interface flags every converted amount so users know a conversion was applied.
Reconciliation is currency-strictA statement transaction can only be reconciled against a contribution in the same currency. The transaction-first reconciliation dialog lists only contributions matching the currency of the selected transaction, and transactions in a different currency never reach a match tier above Low.
Accessing capital calls
Capital calls are available from the main navigation menu, under the fund operations section.
Navigation
To open the capital call list:
- Locate the main navigation menu on the left side of the FinologeeBKO interface
- Expand the Fund management section
- Click Capital call
The list displays all capital calls for the receiving accounts the user can access.
Capital call list
The list view gives an overview of every capital call and its collection progress, so users can identify the drawdowns that need attention.
Information displayed
| Column | Description |
|---|---|
| Name | Capital call name |
| Collection progress | Reconciled amount against total expected amount, with the number of contributions fully paid |
| Status | Badge per contribution status showing how many contributions sit in each status |
| Due date | Payment deadline, highlighted when the due date has passed |
| Reference | Unique capital call reference used to match incoming payments |
Users can filter the list by Due date range and by Reference, and sort it by any displayed column. Clicking a row opens the capital call details page.
Creating a capital call
Users create a capital call by importing the expected contributions calculated in their investment management system. FinologeeBKO does not calculate contribution amounts; it records what the source system produced and tracks the incoming payments against it.
Import process
To create a capital call:
- Navigate to Fund management > Capital call
- Click Import
- Fill in the capital call details:
- Name — capital call name, unique per tenant, up to 255 characters
- Creation date — start of the period in which contributions are expected, defaults to today
- Due date — payment deadline, on or after the creation date
- Reference — unique reference, up to 135 characters, expected to appear in the remittance information of the incoming payments
- Receiving accounts — one or more active ordering party accounts on which the contributions arrive
- Download the XLSX template with Download template
- Fill in one row per expected contribution and upload the completed file as XLSX or CSV
- Click Import
FinologeeBKO validates the file, creates the capital call with its investors, tranches and contributions, attaches the uploaded file to the capital call as a document, and opens the details page.
Contribution file columns
| Column | Required | Description |
|---|---|---|
| Investor Name | Yes | Name of the limited partner owing the contribution |
| Tranche Name | No | Tranche the contribution belongs to; rows sharing a name form one tranche |
| Expected Amount | Yes | Capital contribution amount due, greater than zero |
| Currency | Yes | ISO 4217 currency code of the expected contribution |
| Reference | Yes | Contribution reference used to match incoming transactions |
File validationFinologeeBKO validates the file before creating anything. When the file carries no data rows, or when the mandatory column headers are absent, the upload field reports the problem and no capital call is created. When individual rows fail validation, the response lists the errors per row and provides the uploaded file annotated with an error column, so users can correct the rows and upload the file again.
Capital call details
The details page consolidates everything known about one capital call: its parameters, its collection progress, the expected contributions, the transactions that could still be reconciled, the attached documents, and the audit trail.
Overview
The overview card displays:
- Expected amount — total of all contributions, converted to the capital call currency
- Creation date — start of the expected contribution period
- Receiving accounts — accounts on which the contributions are expected
- Reference — capital call reference
- Due date — payment deadline, highlighted once passed
A doughnut chart next to the card splits the total expected amount into the reconciled amount and the amount still outstanding. Before the due date the outstanding part appears as Pending; once the due date has passed it appears as Not paid.
Collection chart
The collection chart plots the cumulative reconciled amount over time against the total expected amount, adds an expectation line between the creation date and the due date, and marks both today and the due date. The widget header shows the Total balance D-1 — the aggregated closing balance of the receiving accounts as of the previous day, converted to a single currency when the accounts differ.
Users without ORDERING_PARTY_BALANCE_READ on every receiving account see N/A instead of the aggregated balance; the chart itself remains available.
Expected contributions
The expected contributions section tracks each investor's payment status, which is the core question a capital call answers: who has paid, who has paid part of what they owe, and who has not paid at all.
View modes
Three view modes present the same contributions from different angles:
- Flat — one row per contribution
- By investor — contributions grouped per investor, each group showing the investor's expected and reconciled amounts
- By tranche — contributions grouped per tranche, each group showing the tranche's expected and reconciled amounts
The by-tranche view is available when every contribution of the capital call belongs to a tranche.
Information displayed
| Column | Description |
|---|---|
| Tranche | Tranche the contribution belongs to, in the flat and by-investor views |
| Investor | Limited partner owing the contribution, in the flat and by-tranche views |
| Status | Contribution status badge |
| Expected amount | Amount due, in the contribution currency |
| Reconciled amount | Amount matched with incoming transactions so far |
| Reference | Contribution reference |
| Transactions | Number of reconciled transactions, linking to those transactions in Transaction History |
Users can filter contributions by Investor, Tranche, Reference and Status, and search across them. Each row offers the Reconcile action for users with CAPITAL_CALL_WRITE.
Non-reconciled related transactions
Below the contributions, FinologeeBKO lists the incoming transactions that could still correspond to a contribution of this capital call. The list gives users the candidate payments without leaving the capital call, and disappears once every contribution is fully paid.
Candidate pool
The list contains credit transactions on the capital call's receiving accounts that are not yet fully reconciled and have not been excluded. By default it covers transactions with a value date between the capital call creation date and its due date. Users can widen the Value date filter up to one month before the creation date and one month after the due date; a range outside those bounds is rejected.
Information displayed
Each row shows the standard transaction history columns — value date, ordering party account, counterparty, amount, currency, remittance information, statement details — plus a Reconciliation match badge indicating the strongest match tier the transaction reaches against any contribution of the capital call.
Users can filter the list by Value date, My account, Counterparty, Amount, Currency, Transaction reference, Statement number, Statement date and Reconciliation match.
Actions
| Action | Description |
|---|---|
| Reconcile | Opens the transaction-first reconciliation dialog for this transaction |
| Exclude | Removes the transaction from this capital call's list of non-reconciled related transactions |
Excluding a transaction is recorded in the audit log. The transaction remains available in Transaction History and in other capital calls.
Reconciling contributions
Reconciliation links incoming bank transactions to expected contributions and drives the contribution status. FinologeeBKO scores every candidate pairing, reconciles the unambiguous ones on its own, and leaves the rest to the user.
Match tiers
Each transaction and contribution pairing receives one of four match tiers. Only same-currency pairings can reach a tier above Low.
| Tier | Criteria |
|---|---|
| Exact | The contribution reference appears in the transaction, the amount still available on the transaction equals the amount still due on the contribution, the transaction has never been used, and the contribution is Pending |
| High | The contribution reference appears in the transaction, but at least one other exact criterion is not met |
| Medium | The capital call reference or the investor name appears in the transaction counterparty name, remittance information, or information to account owner |
| Low | The transaction is an eligible candidate, but no reference or name signal matched |
References and names are compared without regard to case or accents.
Automatic reconciliation
Each time a daily bank statement is processed for a receiving account, FinologeeBKO reviews the credit transactions it contains and reconciles the pairings that reach the Exact tier. Only capital calls whose date window covers the transaction value date and whose receiving accounts include the statement account are considered, and only contributions still in Pending status are matched.
Every automatic reconciliation is recorded in the audit log and triggers the contribution reconciled webhook, exactly like a manual one.
Reconciling from a contribution
Use this flow when following up on a specific investor:
- Open the capital call details page
- Locate the contribution in the expected contributions list
- Click Reconcile on the row
- Review the contribution details and the remaining amount to be reconciled
- Filter or sort the candidate transactions; the strongest matches and any transactions already linked appear first
- Enter the amount to reconcile against one or more transactions, with an optional comment
- Confirm the reconciliation
Reconciling from a transaction
Use this flow when an incoming payment arrives and its allocation is unclear:
- Open the capital call details page
- Locate the transaction in the non-reconciled related transactions list
- Click Reconcile on the row
- Review the transaction details and the amount still available on it
- Filter or sort the candidate contributions; the dialog lists only contributions in the transaction currency, with pending contributions and the largest outstanding amounts first
- Enter the amount to allocate to one or more contributions, with an optional comment
- Confirm the reconciliation
Partial and split reconciliation
Both dialogs support amounts that do not match one to one:
- One transaction can be split across several contributions, for example an investor paying several tranches in a single transfer
- Several transactions can cover one contribution, for example an investor paying in instalments
- Setting a previously entered reconciled amount to zero removes that link
Reconciliation rules
FinologeeBKO rejects a reconciliation when:
- The reconciled amount is negative
- The total reconciled across all contributions would exceed the transaction amount
- The total reconciled across all transactions would exceed the contribution expected amount
- The transaction comes from an intermediate (intraday) bank statement, since such transactions can still be superseded by the final statement of the day
Closing capital calls
A capital call has no explicit close action. Once the due date has passed, a scheduled job runs at midnight and settles the contributions that never received a payment, so the collection outcome stops being open-ended.
For every capital call past its due date that still holds contributions in Pending status:
- Contributions with no reconciled amount become Not paid
- Contributions with a partial reconciled amount become Partially paid
- A capital call closed event is recorded in the audit log and the corresponding webhook is sent
Contributions already fully paid are left untouched. Users can still reconcile contributions after closure — a later payment moves the contribution back to Partially paid or to Paid once the expected amount is covered.
Status definitions
Contribution status is derived from the reconciled amount and from whether the capital call has been closed. The capital call itself has no separate status: the list and details views summarise the statuses of its contributions.
| Status | Definition | Trigger |
|---|---|---|
| Pending | Awaiting payment, or partially paid before the due date | Initial status after import; also set when all reconciled amounts are removed |
| Paid | Reconciled amount covers the expected amount | Reconciliation brings the reconciled amount to or above the expected amount |
| Partially paid | Part of the expected amount received, collection closed | Closure with a partial reconciled amount, or a later reconciliation on a closed contribution |
| Not paid | No payment received by the due date | Closure with no reconciled amount |
Documents
Fund managers keep the paperwork behind a drawdown next to its data. The details page provides a document library where users with CAPITAL_CALL_WRITE upload and delete files, such as capital call notices, investor correspondence, or bank confirmations.
The contribution file uploaded when the capital call was created is attached automatically and appears in the same library. Document uploads and deletions are recorded in the audit log.
Audit trail
Every action on a capital call is recorded, so users can reconstruct who reconciled what and when.
| Event | Description |
|---|---|
| Capital call created | Capital call imported, with the contributions it contains |
| Contribution reconciled | Contribution reconciled, with the investor, reference, reconciled amount, and comment |
| Transaction excluded | Transaction excluded from the non-reconciled related transactions list |
| Capital call closed | Scheduled closure after the due date, with the resulting contribution counts per status |
| Document uploaded | Document attached to the capital call |
| Document deleted | Document removed from the capital call |
The audit log appears at the bottom of the details page, and users can export it as a PDF report that also lists the receiving accounts.
API and webhook integration
Capital Call is designed to work alongside investment management systems: those systems calculate the drawdown, FinologeeBKO tracks the money. Beyond the file import, the platform exposes a REST API and webhook events so the exchange can run without manual steps.
API endpoints
The external API creates capital calls with inline contributions and reads them back:
| Operation | Endpoint |
|---|---|
| Create a capital call | POST /api-ext/v2/capital-calls |
| List capital calls | GET /api-ext/v2/capital-calls |
| Get a capital call | GET /api-ext/v2/capital-calls/{id} |
| List contributions | GET /api-ext/v2/capital-calls/{id}/contributions |
| Get a contribution | GET /api-ext/v2/capital-calls/{id}/contributions/{contributionId} |
| List investors | GET /api-ext/v2/capital-calls/{id}/investors |
| List tranches | GET /api-ext/v2/capital-calls/{id}/tranches |
A create request carries the capital call name, creation date, due date, reference, receiving account IDs, and at least one contribution with investor name, expected amount, currency, and optional tranche name and reference. The same uniqueness and date rules as the interface apply.
API referenceFor authentication, request and response schemas, and error codes, see the FinologeeBKO API documentation at https://docs.bko.finologee.com/reference/
Webhook events
| Event | Sent when |
|---|---|
CAPITAL_CALL_CONTRIBUTION_RECONCILED | A contribution is reconciled, manually or automatically, with its new status |
CAPITAL_CALL_CLOSED | A capital call is closed after its due date, with the contribution counts per status |
These events let the source system update investor records without polling the API.
Best practices
Follow these recommendations for effective capital call management:
- Use the contribution reference in the notice — the reference uploaded to FinologeeBKO must be the one investors quote in their payment, since it drives the Exact tier and therefore automatic reconciliation
- Give each capital call a distinct reference — a specific reference lets FinologeeBKO reach the Medium tier even when the contribution reference is missing from the payment
- Set the date window to the real collection period — automatic reconciliation only considers transactions with a value date between the creation date and the due date
- List every account that can receive contributions — a payment arriving on an account absent from the capital call is never proposed as a candidate
- Use tranche names consistently — matching names group contributions under one tranche and enable the by-tranche view and its subtotals
- Review non-reconciled related transactions regularly — payments quoting no usable reference need manual allocation before the due date
- Comment unusual reconciliations — comments on partial or split allocations are recorded in the audit log and explain the decision to the next reviewer
- Address currency mismatches early — a payment in a currency other than the contribution cannot be reconciled, so agree the settlement currency with the investor
- Exclude irrelevant transactions — excluding unrelated credits keeps the candidate list focused on genuine contributions
Related documentation
Explore related sections for more information:
- Bank Accounts - Account management, balance monitoring, and transaction history - Manage the accounts that receive contributions
- Transaction History - Review incoming payment details - Inspect the transactions reconciled with contributions
- Counterparties - Investor and beneficiary management - Investor and beneficiary management
- Transaction Currencies - Multi-currency handling and exchange rates - Exchange rates applied to aggregate amounts
- Permissions - Roles and access rights - Configure capital call access rights
- Tenant Flags - Feature availability per tenant - Feature flag configuration
- Webhooks - Event notifications - Subscribe to capital call events
- API - External API integration - Create and read capital calls programmatically
Support
For assistance with Capital Call features, file imports, reconciliation questions, or API integration, contact [email protected].
Updated 5 days ago

