Master-Feeder & Fund-of-Funds: US GAAP Insights

One of the first practical reporting questions in these structures is how individual Luxembourg vehicles should be characterized for US GAAP purposes, particularly when they operate as aggregators, intermediate holding entities, or capital-pooling vehicles.

Luxembourg structures are often used for aggregator-type or holding entities that pool investor commitments and channel capital into portfolio companies or other underlying funds. From a US GAAP perspective, a key consideration is whether such a Luxembourg vehicle would be viewed as an “investment company” under ASC 946, or rather as a more traditional holding or financing company.

This distinction can influence several areas, including the type and level of information that must be produced in Luxembourg-level financial statements and how that information can be used by US entities further up the chain. For example, it may affect:

• the extent and nature of portfolio information available to the US reporting entities;
• the degree to which look‑through analysis is feasible; and
• how valuation and concentration risks are described in group-level financial statements.

In simple terms, if a Luxembourg vehicle is treated as an investment company under ASC 946, its NAV and related disclosures may be used more directly by US reporting entities. If it is treated as a traditional holding company, US entities may need additional data or different analyses to meet their own US GAAP reporting requirements.

For Luxembourg funds acting in an aggregator-type capacity, it is therefore important to determine how they would be classified under US GAAP and to understand how their financial information will be used by US reporting entities above them in the structure. This assessment helps ensure that the Luxembourg reporting package is designed to support those upstream US GAAP reporting requirements.

This is particularly relevant where a Luxembourg master fund does not prepare US GAAP financial statements, but its financial information—for example, its NAV and underlying portfolio data—is relied upon by a US GAAP feeder or other upstream reporting entity. In such cases, the auditors of the upstream US GAAP reporting entity will typically assess how closely the Luxembourg vehicle resembles an ASC 946 investment company and what this implies for the extent to which they can rely on its NAV and disclosures.

Many Luxembourg fund platforms are set up as a master fund or core vehicle reporting under IFRS or Luxembourg GAAP, with separate feeder funds in the US or elsewhere that report under US GAAP. In such cases, the US feeder fund and its auditors will often consider:

• whether the Luxembourg master fund would meet the investment company definition if US GAAP were applied;
• whether the master fund’s NAV, prepared under IFRS or Luxembourg GAAP, is appropriate to use as a practical expedient for fair value;
• what differences in accounting policies—for example, valuation techniques, classification, recognition of income and expenses—may be relevant.

Put simply, the question is whether the US feeder can reasonably rely on the NAV produced under IFRS or LUX GAAP for US GAAP fair value purposes and, if not, what adjustments or additional information may be needed.

Because IFRS and Luxembourg GAAP do not necessarily require the same level of disclosure as ASC 946, additional disclosures may sometimes be requested to support the feeder fund’s financial statements. This can affect reporting processes, data flows, and timelines at the Luxembourg master fund level.

Aligning expectations early—for example, agreeing on what data the Luxembourg master fund can provide, in what format, and by when—often helps avoid last‑minute surprises and supports smoother US GAAP reporting at feeder fund level.

Beyond entity classification and accounting framework considerations, multi-layer fund structures can also create challenges around transparency and the availability of underlying portfolio information for US GAAP disclosure purposes.

ASC 946 may require funds, in some cases, to disclose significant indirect holdings held through investee entities, including where those holdings are assessed through a 5% look-through threshold. In multi-layer structures involving Luxembourg funds, US funds, and other vehicles, this raises practical questions about how far the look-through should extend and how it should be applied in practice.

On the one hand, investors and those charged with governance often expect visibility into major underlying exposures. On the other hand, it is difficult to obtain full bottom‑up detail at every level, particularly where:

• the Luxembourg fund does not control the next level;
• reports from the next level exist but are prepared under a different accounting framework; or
• certain information is commercially sensitive or not routinely shared.

As a result, Luxembourg funds positioned within the structure may receive requests for additional data, reconciliations, or aggregated information. Determining how such requests can be addressed efficiently and reliably is often an important operational consideration.

In practice, this may require agreeing on a reasonable level of look‑through that balances investor expectations, US GAAP disclosure requirements, and the operational reality of accessing underlying portfolio data across multiple jurisdictions and frameworks.

These timing and reporting dependencies often require close coordination across multiple entities, service providers, and reporting teams within the structure.

Cross‑border fund structures frequently combine entities with different year‑ends and different audit opinion dates. A Luxembourg fund may close its financial year on 31 December, while a US feeder fund or upper‑tier vehicle may have a different reporting date.

In a master‑feeder or FoF environment, this raises practical questions around:

• how a US reporting entity uses the most recent audited NAV from a Luxembourg fund when its own reporting date is later;
• what additional procedures or information may be needed to roll forward valuations to the US reporting date; and
• how timing gaps or subsequent events should be reflected in disclosures.

From a Luxembourg perspective, awareness of these interactions can support planning around closing timetables, coordination with service providers, and responses to information requests from investors or upstream reporting entities.

In some cases, it may be useful to align key reporting milestones where possible, or to establish specific reporting packages and cut‑off procedures for US GAAP purposes, so that upstream entities can rely on the Luxembourg NAVs with greater confidence.