Straight-through processing (STP) in fund payments

Straight-through processing (STP) is the automated execution of a financial transaction from instruction to settlement without manual intervention at any stage. In fund payments, STP means that a validated capital call or distribution payment moves through instruction creation, authorisation, routing, and bank submission as a single automated workflow, with no human re-keying of data between systems.

STP matters in fund administration because manual data entry between systems is both the leading source of operational error and an attack surface for fraud: every point at which a human transcribes data is a point at which data can be altered, corrupted, or substituted.

How it works

A fully STP fund payment workflow begins when a capital call notice or distribution calculation is approved by the authorised GP or administrator. The approved instruction is passed directly to the payment processing system without manual re-entry, carrying the payee details (sourced from a verified counterparty registry, not from the notice itself), the payment amount, the value date, and the reference fields required for reconciliation.

The payment system validates the instruction against the registry, performs any required pre-payment checks (such as Confirmation of Payee or sanctions screening), and routes the validated instruction to the bank or payment provider for execution. Settlement confirmation returns automatically and updates the fund's accounting records without manual posting.

The contrast with a non-STP workflow is significant. In a non-STP environment, a capital call notice might be: calculated in a spreadsheet, emailed to a payment operations team, re-entered into a treasury management system, checked against a PDF of the notice, submitted to the bank via a web portal or SWIFT message, and then manually posted to the fund accounting system when the bank confirms settlement. Each of these handoffs introduces latency, error risk, and the possibility of data manipulation.

In practice, most fund administrators operate on a spectrum between fully manual and fully automated, with STP achieved for some payment types (such as recurring management fee payments) but not for others (such as irregular capital call drawdowns or distribution payments involving complex waterfall calculations). The fund administration sector as a whole has significantly lower STP rates than institutional asset management or banking treasury operations, largely because the volume of payments is lower, the amounts are larger, and the complexity of counterparty verification has historically made automation harder to achieve.

The critical dependency for STP in fund payments is a verified counterparty data foundation. STP cannot be safely achieved if the payment system draws on account details that have not been independently authenticated. An automated system that rapidly processes unverified instructions is not safer than a manual one; it is more dangerous, because fraud executes at machine speed.

Worked example

Beacon Road Fund Administrators manages distributions for a portfolio of fifteen private equity and private credit funds. Each quarter, it processes roughly 340 individual distribution payments across 28 GPs and approximately 600 LPs.

In its pre-STP workflow, the distribution processing cycle takes eleven working days from distribution approval to settlement confirmation. The process involves three handoffs between the fund accounting team, the payments team, and the bank portal, with data re-entered at each stage. Error rates require an average of 23 manual corrections per quarter. Two staff members are fully allocated to distribution processing during the peak window.

After implementing a payment system with direct integration between the fund accounting platform and the payment execution layer, drawing on a verified LP registry for all account details, the distribution processing cycle reduces to three working days. Manual corrections drop to four per quarter (all of which relate to GP-initiated instruction changes that arrive outside the standard verification window). Staff allocation during the peak processing window reduces by one FTE.

The payment trail for each transaction is complete from instruction to settlement, with every step timestamped and auditable.

Frequently asked questions

What is the STP rate in fund administration compared to other financial services sectors? Precise industry benchmarks are not publicly standardised, but fund administration is generally understood to have materially lower STP rates than corporate treasury, retail banking, or institutional asset management. This reflects the lower transaction volumes (which historically made bespoke manual processes economical), the complexity of LP-level waterfall calculations, and the lack of standardised payment instruction formats across the industry. ILPA's Capital Call and Distribution Template (2025 version) addresses the instruction standardisation gap.

Can STP be achieved without a verified counterparty registry? Technically yes, but prudently no. STP that draws on unverified payment instructions is operationally efficient but security-deficient. A fully automated system that processes account details provided by email without independent verification is a more attractive and more productive target for fraud than a manual system. STP and verified counterparty data are complementary requirements, not alternatives.

What is the difference between STP in fund payments and STP in securities settlement? In securities settlement, STP refers specifically to the automated matching and settlement of trades without manual intervention between trade execution and settlement (typically T+1 or T+2). In fund payments, STP refers to the automated processing of cash transfers associated with fund lifecycle events (capital calls, distributions, fees). The underlying principle is the same: eliminate manual data transcription between systems. The systems involved, the asset types, and the regulatory frameworks differ significantly.

What fund accounting systems support STP integration for capital call payments? The major fund accounting platforms used in European private markets administration (including eFront, Allvue, Investran, and Geneva) offer varying degrees of API integration capability for payment processing. The availability of STP depends on whether the payment system supports direct integration with the administrator's specific accounting platform and whether the integration has been configured to pull from a verified account registry rather than from open fields in the accounting system.

How does STP interact with maker-checker controls? STP and maker-checker are complementary, not contradictory. A fully STP workflow can still enforce maker-checker by requiring two authenticated users to approve an instruction before it enters the automated processing chain. The maker-checker step sits at the approval gate; STP governs everything downstream of approval. Combining both provides automation efficiency with four-eyes integrity.

Related terms

Maker-checker in fund administration, Confirmation of Payee, IBAN verification in private fund payments, Golden copy / ABOR, Capital call, Distribution

Related pages

How fund administrators can automate capital call payment processing, Swelv for fund administrators