DomicileISINFundamentals

Ireland vs Luxembourg: fund domicile explained, and what the ISIN prefix tells you

Why most UCITS are Irish or Luxembourg funds, what IE/LU/FR/DE/GB/US prefixes mean, ICAV vs SICAV, UK OEICs, US 40-Act funds and how to route by prefix in code.Published 10 September 2026 · 6 min read · by FundFacts API

The first two letters of a fund's ISIN are the cheapest piece of metadata you will ever get. They tell you the fund's domicile — the country whose law the fund is set up under and whose regulator supervises it — and from that you can infer which documents exist, which disclosure regime applies and what the legal wrapper looks like. This article explains why two small countries dominate European fund domiciles, what each common prefix implies, and how to route by prefix in code.

What domicile means

A fund's domicile is where the legal entity is established, not where it is managed or sold. An ETF managed from London, listed in Frankfurt and bought by an investor in Milan can be — and often is — an Irish fund. The domicile decides the regulator (Central Bank of Ireland, CSSF in Luxembourg, AMF in France, BaFin in Germany, FCA in the UK, SEC in the US), the fund law it is constituted under, the tax treatment at fund level and the documentation it must publish. The glossary entry for fund domicile has the short version.

Why Ireland and Luxembourg

Most UCITS funds sold across Europe are domiciled in one of two places, and the reasons are structural rather than accidental:

  • Passporting. UCITS is an EU framework. A fund authorised in one member state can be marketed to retail investors in all the others, so a manager needs only one EU domicile and picks the one with the best infrastructure.
  • Early specialisation. Both countries built a fund-administration industry around UCITS from the early 1990s: administrators, depositaries, transfer agents, auditors and law firms concentrated there, which makes launching and running a fund cheaper.
  • Tax neutrality at fund level. Neither jurisdiction taxes the fund itself on its investment income the way a corporate would be taxed; investors are taxed in their own country instead.
  • Treaty access. How much withholding tax a fund suffers on dividends from the companies it holds depends on treaties between its domicile and the source country. Irish funds are often noted for the treatment of US dividends under the Ireland–US treaty, one reason so many US-equity UCITS ETFs are Irish. This is a fund-level, structural effect that can influence tracking difference; it says nothing about any investor's own tax position and is not tax advice.
  • Market habit. Luxembourg historically attracted continental European active managers and multi-class fund ranges; Ireland attracted ETF issuers and managers with UK or US roots. Neither rule is absolute.

Many large issuers use both: see the coverage pages for iShares (mostly IE) and Amundi (LU and FR, with some IE).

What the ISIN prefix tells you

PrefixDomicileTypical legal wrappersRetail disclosure documentNotes
IEIrelandICAV, investment company (plc), unit trustPRIIPs KIDDominant for UCITS ETFs
LULuxembourgSICAV, FCPPRIIPs KIDDominant for cross-border active UCITS
FRFranceSICAV, FCPPRIIPs KIDMany domestic funds; some cross-border ranges
DEGermanySondervermögen managed by a KVGPRIIPs KIDStrong domestic market; German UCITS ETFs exist
GBUnited KingdomOEIC (ICVC), authorised unit trust, ACSUCITS KIID (UK UCITS)Outside the EU passport since Brexit
USUnited StatesRegistered investment company under the 1940 ActSummary prospectusNot UCITS; different document set entirely

Two caveats. First, the prefix is the country of the numbering agency that issued the code, which for funds is almost always the domicile — treat it as a strong hint and confirm from the prospectus for anything that matters. Second, it says nothing about where the fund is listed or sold; the ISIN guide covers the rest of the code.

ICAV vs SICAV, briefly

You will see these acronyms in fund names and prospectuses constantly.

  • SICAV (société d'investissement à capital variable) is the Luxembourg open-ended investment company; a UCITS SICAV is authorised under Part I of the Luxembourg fund law of 2010. Most Luxembourg umbrella ranges — dozens of sub-funds and hundreds of share classes, such as those of J.P. Morgan Asset Management, Franklin Templeton, Schroders or Robeco — are SICAVs. France, Italy and Spain use the same acronym for similar vehicles under their own laws.
  • ICAV (Irish Collective Asset-management Vehicle) is a corporate vehicle introduced in Ireland in 2015 specifically for funds. It is now the default for new Irish funds because it has a simpler corporate framework than a plc and can elect its US tax classification. Older Irish funds, including many large ETF umbrellas, remain investment companies (plcs).

Both are open-ended, both can be umbrellas with segregated sub-funds, both issue share classes with their own ISINs. For data purposes the difference is cosmetic: the document set and the UCITS rules are the same. FundFacts API reports the wrapper as structure, so you do not have to parse it out of the name.

UK-domiciled OEICs

Before Brexit, UK funds were EU UCITS like any other. Since then they are UK UCITS: the same rules in substance, but no EU passport, and — as discussed in the KID explained — still using the UCITS KIID rather than the PRIIPs KID while the UK finalises its own disclosure framework. The common wrapper is the OEIC (open-ended investment company, legally an ICVC), alongside authorised unit trusts. UK managers such as abrdn and Schroders often run parallel ranges: a GB-domiciled OEIC for UK investors and a LU or IE range for the rest of Europe, with matching strategies but different ISINs, fees and documents.

US 40-Act funds

US mutual funds and ETFs are registered investment companies under the Investment Company Act of 1940, hence "40-Act funds". Their disclosure set is a summary prospectus, statutory prospectus, statement of additional information and periodic reports filed with the SEC. There is no KID, no ongoing charges figure in the UCITS sense (the closest is the expense ratio in the fee table), no SRRI or SRI and no UCITS-style factsheet template.

That is why a US-prefixed ISIN behaves differently in a fund data pipeline: the fields exist, but they come from different documents with different definitions. It is also why a US 40-Act ETF cannot be sold to EU retail investors — without a PRIIPs KID, retail distribution is not permitted — and why US managers such as Vanguard, SPDR (State Street) and Invesco run separate Irish UCITS ranges for European clients. SPDR S&P 500 UCITS ETF Dist (IE00B6YX5C33) tracks the same index as its US sibling but is a completely separate legal entity with its own documents.

Routing by prefix in code

Because the prefix predicts the document set, it is a useful pre-processing step: you can decide which fields to display and give the user a sensible message when a domicile is outside your coverage.

typescript
type Regime = "eu-ucits" | "uk-ucits" | "us-40act" | "other";
const PREFIX_REGIME: Record<string, Regime> = {
IE: "eu-ucits", LU: "eu-ucits", FR: "eu-ucits", DE: "eu-ucits",
NL: "eu-ucits", BE: "eu-ucits", AT: "eu-ucits", IT: "eu-ucits", ES: "eu-ucits",
GB: "uk-ucits",
US: "us-40act",
};
export function regimeFor(isin: string): Regime {
return PREFIX_REGIME[isin.slice(0, 2).toUpperCase()] ?? "other";
}
export async function loadFund(isin: string) {
const regime = regimeFor(isin);
const res = await fetch(`https://fundfactsapi.com/api/v1/funds/${isin}`, {
headers: { Authorization: `Bearer ${process.env.FUNDFACTS_API_KEY}` },
});
if (res.status === 404) return { regime, fund: null };
if (!res.ok) throw new Error(`FundFacts API ${res.status}`);
const fund = await res.json();
return {
regime,
// SRI for EU KIDs, SRRI for UK KIIDs — label it so the UI can say which.
riskScale: regime === "uk-ucits" ? "SRRI" : regime === "eu-ucits" ? "SRI" : null,
fund,
};
}

Extend the mapping for the markets you serve. The response itself carries data.structure and data.keyFacts.currency, so once the fund is loaded you can confirm the wrapper and currency from the documents instead of the prefix alone.

Practical notes for data teams

  • Do not deduplicate across domiciles. A LU and an IE fund with the same name and index are different securities with different NAVs, fees and histories. Keep them as separate rows keyed by ISIN.
  • Expect different "as of" cadences. Some domiciles and wrappers publish holdings daily, others monthly. The dataAsOf field tells you what the documents actually said.
  • Reporting currency is not domicile currency. Luxembourg funds report in EUR, USD, GBP, CHF and more. Use keyFacts.currency, not the prefix, for currency logic.
  • Same strategy, different risk indicator. A UK OEIC and its Irish sibling may show different risk numbers purely because one prints an SRRI and the other an SRI. Label the scale before comparing them.

Whatever the prefix, a single request to FundFacts API returns the structured factsheet — key facts, holdings, exposures, risk indicator, fees and performance — read from the documents the fund house publishes, refreshed every 24 hours. Create a free key and try an IE, LU and GB ISIN side by side.

Try it on your own ISINs

One request returns key facts, holdings, risk and performance as JSON. Free plan, no card.