A special purpose vehicle, or SPV, is a legal entity set up for a specific investment, often to bring several investors together in a single company. Funds and SPVs differ in purpose and structure, but their day-to-day operations follow a similar pattern. Investors are accepted, commitments are made, decisions are taken by those with the authority to take them, capital moves and ownership or participation records are updated.
Each step depends on the one before it. Yet the information that connects them is often spread across email threads, shared folders, spreadsheets, bank portals and the documents of external advisers.
What fragmentation hides
Fragmented records do not mean that the work is done badly. They mean that the state of the work is hard to see. Five questions become surprisingly difficult to answer:
When the answers depend on someone reconstructing events from an inbox, delays and errors become more likely, and explaining afterwards what happened becomes harder still.
An illustrative delay
Picture an SPV, invented for this example, raising capital from a small group of investors for a single investment. One investor has signed the subscription documents, but the transfer has not arrived by the agreed date. Meanwhile, the approval needed to admit a second investor is waiting for the signature of a director who is travelling.
Neither issue is dramatic on its own. But the administrator tracks them in a spreadsheet, the investor relations contact holds the latest email and the bank confirmation sits in a separate portal. When the sponsor asks whether the SPV can proceed, nobody can give a complete answer without first piecing the picture together. A traceable workflow would show in one place that one contribution is outstanding, that one approval is pending with a named person, and which register entries are waiting on those two events.
Recording is not deciding
An important distinction runs through this kind of workflow. Recording a confirmed decision is different from making it, and recording a payment that has been received is different from executing it. A system supporting fund and SPV operations can show what has been decided, by whom and on the basis of which evidence, and can record transactions once they are confirmed. The decision itself remains with the people and bodies authorised to take it, and the payment is executed through the bank.
The same applies to adjacent responsibilities. Legal structuring, KYC/AML checks (know-your-customer and anti-money-laundering procedures), accounting and tax remain the work of the authorised organisations and professionals involved. A workflow can make their input visible and connect it to the next step. It does not take their place.
Shared patterns, different rules
Funds and SPVs share operational patterns: onboarding, approvals, capital movements and register updates recur across many structures. Their mandates, legal arrangements, documents and approval rules differ. Who may approve an investor, which evidence is required and how holdings are recorded therefore have to be configured for each structure, rather than assumed from a generic template.
Where CrossVest fits
CrossVest, a venture in product development and market validation at Xablu Venture Studio, is being developed as an operational environment that connects participants, authority, evidence, decisions, capital movements and ownership or participation registers.
Building blocks are available for registering entities, fund terms and share classes; for parts of investor acceptance and decision recording; for recording subscriptions and holdings; and for recording and retrieving participation information. Complete end-to-end fund and SPV workflows are still being validated with pilot partners.
The scope is deliberately bounded. Full NAV (net asset value) calculation, complete investor reporting, support for every legal structure and comprehensive compliance coverage are not automatically part of the first release, and the approach is not built around tokenisation.
Is there a fund or SPV workflow in your organisation where handovers or exceptions keep recurring? Choose one, and we would be glad to examine with you where actions, evidence and approvals currently get lost.
Examine a workflow →