Allocations for SPVs and fund administration

Where Allocations fits

Allocations publishes products for SPVs, traditional funds, and migration of existing structures. Its positioning is especially relevant to solo GPs and emerging managers who expect to operate both deal-specific vehicles and a committed fund.

The platform's breadth should be broken into separate product scopes. A small standardized SPV, custom vehicle, traditional fund, and migration project carry different legal, accounting, tax, investor, and exception requirements.

Published products and pricing

As reviewed on September 5, 2026, Allocations publishes these starting prices:

The standard SPV tier describes up to 35 investors, one close, one venture asset, template documents, and a five-year term. The premium tier expands asset and closing flexibility. The price table separately lists charges for additional investors, calls, international assets, off-platform onboarding, distributions, and other events. A published migration price does not establish how historical records will be reconciled or which legal roles must change.

Treat the price as a starting point. Request a written calculation for the entity count, commitments, investors, closings, assets, jurisdictions, tax profile, reporting, audit, and holding period. Ask which legal, government, regulatory, banking, payment, tax, investor, migration, and dissolution costs are additional.

Compare total lifecycle cost with the SPV cost guide, not only the first invoice.

Operating model and authority

Identify the legal vehicle, manager or general partner, administrator, adviser if relevant, bank, counsel, tax preparer, auditor, and technology provider. Ask which are Allocations entities, affiliates, or outside partners. Confirm who signs each contract and who can bind the vehicle.

Map responsibility for offering work, investor eligibility, KYC, subscription acceptance, calls, cash approval, books, legal register, capital accounts, valuation, reporting, tax, filings, transfers, distributions, and wind-down. Request the contractual scope and exclusions for the exact product tier.

If the product includes a standardized manager or entity stack, ask how a manager preserves its own records and investor relationships. If the customer's entities supply those roles, ask what implementation data and controls the platform requires.

Migration deserves its own diligence

Allocations explicitly markets migration. A real migration must do more than import contact names. It should reconcile legal documents, investor admission, commitments, contributions, distributions, transfers, capital accounts, general ledger, bank activity, asset records, valuations, filings, and tax returns to a known cutover date.

Give the provider a migration pack with all entities, years, investors, assets, open obligations, file formats, missing records, and known discrepancies. Ask who validates opening balances, how exceptions are documented, what historical reports will remain available, and which data cannot be imported.

Run the first bank reconciliation, investor statement, tax package, call, or distribution under parallel review. Keep a migration issue log with source evidence and approvals.

Fund and SPV coexistence

Managers running a committed fund and SPVs need clean allocation and conflict controls. Follow-on SPVs, co-investments, warehouse positions, shared expenses, LP priority, and different carry terms can create questions that no product interface decides automatically.

Ask how Allocations records relationships between a fund, management company, general partner, SPVs, and portfolio assets. Confirm whether the system supports distinct investor rights, side letters, expense allocation, valuations, reporting, and tax records for every entity.

The fund operations guide provides the cross-entity responsibility model.

Data, controls, and service quality

Request sample commitment and capital-account ledgers, general-ledger exports, investor statements, calls, distributions, tax packages, filing calendars, and closing binders. Confirm bank ownership, user permissions, payment approval, and changed-instruction verification.

Ask which data can be exported without support and how identity data is returned or retained at termination. Review migration-out fees, read-only periods, partner contracts, transition support, and the process for replacing any affiliated manager or other legal role.

Test support with exceptions: late subscriptions, foreign investors, secondary transfers, side letters, follow-ons, tenders, corrected tax forms, and non-cash distributions. Obtain references that have completed more than formation.

Best fit and tradeoffs

Allocations is most plausible for managers who value one provider across SPVs, funds, and migrations, and whose structures fit the published product lanes. Clear public tiers can make initial budgeting easier.

The central diligence task is determining what each tier omits and how standardized processes respond to complex investors, assets, and historical records. A manager with bespoke institutional reporting, cross-border structuring, or a complex legacy portfolio should validate the exception team and migration method before buying.

Questions for an Allocations call

• Which product tier and legal-entity stack fits our fact pattern?
• What is included in the published price and what is separately charged?
• Who performs and approves each legal, cash, accounting, tax, and investor task?
• How do the fund and related SPVs remain separately controlled?
• What evidence validates a migration's opening balances?
• Which historical reports and documents remain available after migration?
• What can be exported without support?
• What does migration out cost, and which legal roles must change?

Test the migration claim with a concrete vehicle. Ask who validates investor balances, legal ownership, bank history, tax basis, prior filings, and outstanding exceptions before the replacement system becomes authoritative. A moved document folder is not yet a completed operational migration.

Use the comparison framework to preserve the written answers and open conditions.