Alternative Investment Vehicles — commonly known as AIVs — are a standard feature of sophisticated Cayman Islands private fund structures. They are used for deal-specific structuring, tax optimisation, and investor-specific arrangements. They are also one of the most frequently mishandled areas of FAR compliance.
Many fund managers assume that because an AIV is a subsidiary or satellite of the main fund, its regulatory reporting is handled automatically as part of the main fund's FAR filing. This assumption is often wrong — and the consequences of getting it wrong can result in the AIV (and its operator) being in breach of their own, independent CIMA obligations.
What Is an AIV?
An AIV (Alternative Investment Vehicle) is defined under the Private Funds Act as a company, unit trust, partnership, or similar entity that is:
- Formed in accordance with the constitutional documents of a private fund
- Established for the purposes of making, holding, and disposing of one or more investments wholly or mainly related to the business of that private fund
- Having as its only members, partners, or beneficiaries those who are also members, partners, or beneficiaries of the private fund
In plain terms: an AIV is a vehicle set up by a fund to hold specific investments, often for structural or tax reasons, where all the economic interest flows back to the main fund's investors.
When Must an AIV Register with CIMA?
This is where it gets nuanced. Not all AIVs must register as standalone private funds with CIMA. The key question is whether the AIV itself meets the definition of a "private fund" under the Private Funds Act.
If the AIV meets the full definition — pooling investor funds, with interests not redeemable at the investor's option — it must register as a standalone private fund and file its own FAR and audited financial statements annually.
However, a Cayman-domiciled AIV of a main private fund may instead be included within the main fund's registration if the main fund reports its financial statements on a consolidated or combined basis with the AIV. In this case, the AIV does not need to register separately — but this does not eliminate its FAR obligation. CIMA's rules are explicit: even where an AIV is covered by consolidated reporting and is not separately registered, it is still required to submit its own separate annual return to CIMA. The consolidated reporting option removes the registration requirement; it does not remove the filing requirement.
Where the main fund is non-Cayman domiciled, the AIV must register as a standalone private fund with CIMA — there is no consolidated reporting option available in this scenario.
How AIVs Are Reported in the FAR
Whether an AIV registers separately or is folded into the main fund's registration, it must be disclosed in the FAR. The private fund FAR form (PFR-049-77-02) includes a Related Fund Entity section specifically designed to capture AIVs, parallel funds, and co-investment vehicles.
For each AIV, the FAR requires disclosure of:
- The AIV's legal name and jurisdiction of establishment
- Its legal structure (company, limited partnership, unit trust, etc.)
- Its relationship to the main fund
- Financial information, where applicable
Omitting an AIV from the Related Fund Entity section — or failing to register a standalone AIV that should be registered — is a common source of CIMA queries and rejected FAR submissions.
The Sub-Fund Fee
AIVs that are disclosed in a main fund's FAR attract a sub-fund or AIV fee, payable at the time of the FAR filing. For financial year-ends on or before 31 December 2025, this fee is CI$150 (approximately US$183) per AIV, up to a combined maximum of 25 vehicles per fund. From 1 January 2026, this fee increased to CI$525 per sub-fund or AIV under the revised CIMA fee structure.
Managers with complex structures involving multiple AIVs across a portfolio of funds should account for this fee escalation in their 2026 compliance budgets.
The Most Common AIV Mistakes in FAR Filings
1. Treating a standalone AIV as automatically covered by the main fund's filing. Unless consolidated financial reporting has been adopted, a Cayman AIV that meets the private fund definition must register and file its own FAR.
2. Omitting the AIV from the Related Fund Entity section entirely. Even where the AIV is covered by consolidated reporting, it must still be disclosed in the main fund's FAR.
3. Misclassifying the entity. Not every deal vehicle is an AIV. An entity that has its own investors (i.e. persons who are not investors in the main fund) does not qualify as an AIV and may need to register separately as a distinct private fund.
4. Missing the AIV-level operator declaration. Where an AIV registers as a standalone private fund, the operator declaration (Sections 16, 17, and 18 of the Private Funds Act) must also be filed for that entity specifically.
A Note on Co-Investment Vehicles
Co-investment vehicles — formed to allow certain investors to co-invest alongside the main fund in specific deals — are related to AIVs but treated somewhat differently in the FAR. Co-investment vehicles may qualify as AIVs if their investor base is the same as the main fund, but often they have distinct investor sets (co-investors rather than fund LPs), which changes their regulatory classification. The distinction matters for whether they appear in the AIV section or the broader Related Fund Entity section of the FAR.
If you manage a fund with AIVs, validate your FAR structure before submission with our drag-and-drop FAR Validator →
All blog posts are for informational purposes only and do not constitute legal, regulatory, or compliance advice. Fund operators should always confirm current requirements with CIMA or their legal and regulatory advisors.