SFDR Article 6, 8 and 9 explained for product teams

If you build anything that lists European funds, sooner or later a product manager will ask for an "ESG filter", and the first thing anyone reaches for is the fund's SFDR article. It is a reasonable place to start, as long as the team understands what the classification actually is — and, more importantly, what it is not. This post explains the three categories, where the information lives in fund documents, and how to model it so that a future reclassification does not break your screener.

What SFDR is

The Sustainable Finance Disclosure Regulation is an EU regulation that has applied to asset managers and financial advisers since March 2021. It requires them to disclose how they consider sustainability risks and impacts at two levels: the entity (the management company) and the product (each fund). The product-level rules are the ones that produce the "Article 6 / 8 / 9" shorthand you see on factsheets and fund selectors. The glossary entry for SFDR has the one-paragraph version; this article goes deeper.

The point that matters for product teams is in the name. SFDR is a disclosure regulation. It tells a fund what it has to say about itself depending on what it claims; it does not certify that the claim is true, and it does not rank funds. A fund chooses which article it discloses under, and the regulator checks that the disclosures match the strategy — it does not hand out a badge.

The three articles

Three clarifications that prevent most misunderstandings:

• Article 6 is the default, not a penalty. Every fund that is not Article 8 or 9 is Article 6. A plain global equity index tracker is Article 6 because it does not promote anything; that says nothing about the sustainability profile of its holdings.
• Article 8 is a very wide bucket. It ranges from funds that exclude a handful of sectors to funds with substantial sustainable-investment commitments. Two Article 8 funds can have almost nothing in common.
• Article 9 has a high bar. Since the detailed Level 2 rules took effect at the start of 2023, an Article 9 fund is generally expected to hold sustainable investments (as defined by the regulation) almost exclusively, outside cash and hedging. That is why a wave of funds moved from Article 9 to Article 8 around that time.

Because the categories describe disclosure obligations, "Article 8" is not a synonym for "sustainable". Regulators have said as much repeatedly, and it is the single most common misuse in fund apps.

Where the classification appears

The article number is not always printed as "Article 8" in bold, so knowing where to look helps.

• Prospectus and pre-contractual annex. The most authoritative source. Article 8 and 9 funds attach a standardised template to the prospectus or supplement that starts with the question "Does this financial product have a sustainable investment objective?" and a tick-box answer.
• Fund name. Terms such as "ESG", "Sustainable", "SRI", "Climate", "Transition" or "Paris-Aligned" hint at Article 8 or 9, but a name is not a classification. ESMA's fund-naming guidelines constrain when these terms may be used, which has led some funds to rename or reclassify.
• Factsheet and KID. Many factsheets carry an "SFDR: Article 8" line in the key facts box. The PRIIPs KID's objectives section often contains the promotion language, which is why the investmentObjective text returned by FundFacts API frequently includes it. See the KID explained for what else that document holds.
• Website disclosures. SFDR requires a dedicated sustainability section per Article 8 or 9 product on the manager's site, plus a periodic annex in the annual report.
• EET file. The European ESG Template that distributors exchange carries the classification as a coded field. If you receive EETs you already have a machine-readable source.

How to store it

Treat SFDR classification as a categorical field with provenance, never as a boolean "is ESG" flag and never as a derived score.

typescript
type SfdrArticle = "article_6" | "article_8" | "article_9" | "unknown";
​
interface SfdrRecord {
  isin: string;
  article: SfdrArticle;
  /** Where the value was read from: prospectus, factsheet, EET, manual. */
  source: "prospectus" | "factsheet" | "eet" | "manual";
  /** Date of the document the value was read from. */
  asOf: string;
  /** Previous value and date, so a reclassification is auditable. */
  previous?: { article: SfdrArticle; until: string };
}

Why this shape:

1. Enumerated values. Forcing one of four values stops "Art. 8", "8", "Article Eight" and "light green" from coexisting in the same column.
2. Explicit unknown. Non-EU funds, and funds whose documents have not been read yet, are not Article 6. Storing them as such is a data quality error that produces a misleading filter.
3. Provenance and date. When a fund reclassifies, you want to know when you learned it and from which document. Reclassifications in both directions happen every year.
4. Not part of a score. Do not fold the article into a composite ESG rating. It measures a different thing, and combining it with holdings-based metrics blurs both.

A screener built on this model can offer a straightforward "SFDR article" facet next to the fund's asset class and risk band without pretending to know more than the disclosure says. The fund screener use case shows the surrounding facets.

Combining it with fund data

FundFacts API returns the structured factsheet for a share class — objectives, top holdings, sector and country exposure, risk indicator, fees and performance — from one request. Keep the SFDR article in your own table keyed by ISIN, then join at query time:

python
import os
import httpx
​
API = "https://fundfactsapi.com/api/v1/funds"
HEADERS = {"Authorization": f"Bearer {os.environ['FUNDFACTS_API_KEY']}"}
​
def fund_row(isin: str, sfdr: dict) -> dict:
    r = httpx.get(f"{API}/{isin}", headers=HEADERS, timeout=200)
    r.raise_for_status()
    d = r.json()["data"]
    return {
        "isin": isin,
        "asset_class": d["keyFacts"]["assetClass"],
        "risk_rating": d["riskRating"],
        "ter": d["headlineMetrics"].get("ter"),
        "objective": d["investmentObjective"],
        "sfdr_article": sfdr.get(isin, {}).get("article", "unknown"),
    }

The generous timeout is deliberate: a cold ISIN can take one to three minutes to load the first time, after which the cached response returns in milliseconds and is refreshed every 24 hours.

Caveats to design for

• Reclassifications. Funds move between Article 8 and 9, occasionally from 6 to 8 after a strategy change. Re-read the classification whenever the prospectus date changes, and show the "as of" date in the UI.
• Share classes share the classification. SFDR applies at the fund (sub-fund) level, so every share class of the same sub-fund has the same article. If your model is keyed by ISIN, denormalise carefully or key SFDR by sub-fund.
• Non-EU funds. UK, Swiss and US funds are outside SFDR. The UK has its own Sustainability Disclosure Requirements with labels rather than articles. Keep these in a separate field rather than forcing them into the SFDR enum.
• The regime is under review. The European Commission has been reviewing SFDR, including whether the current self-classification into Articles 8 and 9 should be replaced or supplemented by formal product categories. The outcome and timing are not settled at the time of writing. Do not hard-code "Article 8" into UI copy, database constraints or marketing material as if it were permanent; the enum above is easy to extend, and the provenance field means you can migrate historical records honestly.
• Not investment advice. An SFDR article says what a fund discloses. Presenting it as a recommendation, or as a quality judgement, is both misleading and, for regulated firms, a compliance problem. See the compliance monitoring use case for how teams keep disclosure data auditable.

Summary

Article 6, 8 and 9 tell you which set of disclosure templates a fund has committed to. Store the article as a small enum with a source and a date, treat "unknown" as a real value, keep it separate from holdings-based metrics, and expect it to change. Everything else — objectives, exposures, risk, cost and performance — is available from the fund's published documents through a single FundFacts API call, so your screener can show the disclosure and the underlying data side by side without confusing the two.