By Sopact · Updated September 12, 2026

Map portfolio and investee data to IRIS+, GRI, or ESRS by comparing definitions, not matching metric names. Start with one governed data dictionary that records each field's population, unit, reporting period, boundary, calculation method, and disaggregation. Then classify each mapping as an exact match, a related-but-modified relationship, or an organization-specific measure. A single source field may support more than one framework disclosure — but only when each framework's requirements are met and any differences are documented. Use AI to generate candidate mappings, and have a qualified person validate every one against the current official standard before it reaches investor, regulatory, or assurance-ready reporting.

Continue from the portfolio onboarding lesson. Bring one approved reporting agreement and three measures from your portfolio. Leave with a small mapping register that states what can be combined, what must stay separate and who approved the decision.

CSRD is not a separate metric standard. It is the EU's Corporate Sustainability Reporting Directive, under which organizations in scope report using ESRS — the European Sustainability Reporting Standards drafted by EFRAG and adopted by the European Commission (European Commission). So the frameworks you actually map metrics to are IRIS+, GRI, and ESRS; CSRD is the regime that makes ESRS mandatory for companies within the applicable CSRD scope.

This chapter is for a portfolio or impact manager at a fund, foundation, or DFI who receives data from many investees or grantees, has to make it comparable, and must report it into the frameworks LPs and regulators expect — and it rests on one principle worth stating before the process rather than after it: a shared label is not a shared definition, so two investees can each report 40 jobs created under different rules. Adding those figures hides differences in what was counted.

The eight-step portfolio mapping process

Standards mapping is not just code-matching — for ESRS it begins with scope and materiality. Work in this order; the later sections explain the steps that need judgment. If your organization does not yet have stable field definitions, begin with how to build a shared data dictionary before attempting standards mapping.

1. Determine reporting purpose, scope, and materiality. Confirm who must report, which framework and version applies, the reporting boundary, and — for ESRS — which sustainability matters are material. Mapping cannot decide these for you (EFRAG).
2. Define every internal metric once in one governed dictionary — population, unit, period, boundary, calculation method, disaggregation.
3. Identify the correct authoritative standard and version for each metric (frameworks change; record which version you used).
4. Classify the mapping strength — Exact, Related-but-modified, or Organization-specific.
5. Document boundary and methodology differences — population, period, units, disaggregation, calculation.
6. Collect comparable source data using the small shared core and documented local-field mappings. Partners can keep additional questions relevant to their work.
7. Validate and approve mappings — a qualified person signs off against the current standard.
8. Produce framework-specific disclosures with traceability — each number traces to its source field and standard reference.

IRIS+, GRI, ESRS, and CSRD — what's the difference?

They are not four peer metric catalogs, and they should not be treated as interchangeable code lists.

The framework: Exact, Related, or Organization-specific

For each candidate relationship, use three working categories to describe the match. Keep incomplete comparisons marked as pending rather than forcing a category. This is a Sopact governance method for documenting how closely a field corresponds to an external standard — not an official classification issued by GIIN, GRI, or EFRAG. Sopact's branded shorthand for the three is Direct / Adapted / Complementary.

The value of the test is honesty: a reader can see instantly which figures carry a standard code on identical terms, which are related-but-modified and need a caveat, and which are your own definition — so nothing is quietly presented as standards-compliant when it is an adaptation.

Worked example 1 — a workforce dictionary mapped to IRIS+

Here is an illustrative workforce-development dictionary mapped to selected IRIS+ metrics, each tagged candidate exact, Related, or Organization-specific. They are "candidate" because an internal label alone does not prove exact equivalence — confirm each against the complete IRIS+ version 5.2 definition, unit, calculation, and reporting period before approving it as Exact.

Illustrative dictionary; fields are for demonstration. IRIS+ codes are real GIIN metrics linked to IRIS+ version 5.2; the Exact/Related/Org-specific tags are the Sopact classification above, not a GIIN designation. A candidate exact mapping becomes approved as Exact only after the internal field definition is verified against the complete current IRIS+ definition, unit, calculation, and reporting period.

Worked example 2 — why similar IRIS+, GRI, and ESRS labels don't establish equivalence

A single label — "training hours," "diversity," "employment" — often maps to a different population in each framework. The rows below are failed or partial crosswalk candidates, not one source value reporting cleanly across three frameworks — each with the match quality and the caveat that keeps it honest. This teaching example uses IRIS+ v5.2 and the 2023 ESRS disclosure numbering reflected in the GRI–ESRS Interoperability Index (Nov 2024); confirm complete definitions and the applicable edition before relying on any mapping. The table is not a crosswalk for the revised 2026 ESRS.

Read it: none of these is a clean 1:1. The training row concerns employees in all three references, but still requires checking totals versus averages and disaggregation. The other rows compare client measures with own-workforce disclosures. Check each row separately; IRIS+ includes both client and organizational measures. The portfolio dictionary can govern both populations, but it should not collapse them into one field. Record one governed source value, document the transformations and framework-specific caveats separately, and remember: that is the difference between a metric match and reporting compliance.

Can the same data point support IRIS+, GRI, and ESRS at once?

Sometimes — but not automatically. One governed data field may support multiple framework disclosures when its definition, boundary, period, unit, and required disaggregation satisfy each framework. Where those requirements differ, keep one source value but document the transformations, supplementary fields, and disclosure-specific caveats separately.

A shared value can reduce duplicate data entry, but it does not by itself make a figure compliant with each standard. Differences that commonly break a naive one-to-many mapping include entity and value-chain boundaries, reporting period, definitions of employees vs. clients vs. beneficiaries, required disaggregation, units and calculation methodology, materiality, and the narrative and methodology disclosures each framework expects. And note: a field's similarity to an ESRS datapoint does not determine whether the corresponding sustainability matter is material, or whether the disclosure is required at all.

Practice: decide whether three partners’ numbers can be combined

Use this self-contained three-organization portfolio. The figures below are fictional. All three partners report “placements,” but their agreements use different definitions.

Your task: write one dictionary entry for job starts and a separate entry for six-month employment. Compare the job-start definition with the dated IRIS+ PI3527 definition. Record the population, period, numerator, denominator and supporting evidence. A placement rate cannot be calculated from the placement count alone.

Check your answer: 120 is not an approved portfolio total. B requires clarification and C answers a different question. A is a candidate for the starts measure, not automatically a verified standard match. Keep unresolved values visible rather than replacing them with zero.

Keep a mapping register alongside the dictionary

Test the dictionary against the next quarterly submission. If a partner changes its definition, retain the prior version and decide whether earlier figures need restatement. Do not quietly rewrite historical results.

How AI generates — and humans validate — candidate mappings

Use semantic mapping to generate candidate relationships between dictionary fields and standard disclosures — then validate the definition, scope, unit, period, calculation method, disaggregation, and framework version before approving any mapping. Semantic similarity cannot establish compliance; two labels can sound alike while using different populations, units, or boundaries.

You are a standards-mapping assistant for a portfolio manager. Generate CANDIDATE
mappings only — a human validates before use.

For each metric in my data dictionary below, propose a mapping to [IRIS+ / GRI /
ESRS] and classify it:
- EXACT — same population, unit, period, calculation. Return the metric name + code.
- RELATED / MODIFIED — a related standard metric exists but subject/population/
  boundary/calculation differs. Return the code AND the difference a reader needs.
- ORGANIZATION-SPECIFIC — no suitable mapping has been established. Explain the search scope; do not claim the entire catalog has been exhausted.
- UNMAPPABLE — no plausible relationship.
- UNVERIFIED CANDIDATE — a plausible match, but a required comparison attribute is
  missing from either definition. Use this instead of forcing uncertainty into EXACT.

RULES
- Never fabricate a code. Cite the official source URL and framework version for
  every proposed code.
- Do NOT classify a mapping as EXACT unless every required comparison attribute
  (population, unit, period, boundary, calculation, disaggregation) is explicitly
  available in BOTH the internal definition and the standard definition. If either
  is incomplete, classify it UNVERIFIED CANDIDATE.
- Flag any field too ambiguous to map and say which definition detail is missing.

INPUT (field · definition · population · unit · period · disaggregation):
<<< [paste here] >>>

OUTPUT (one HTML-ready table): Field | Framework metric & code (+ source/version) |
Class | Population/unit/period match? | Verification needed.

Put the dictionary to work in each reporting cycle

You can build the dictionary and draft mappings in any capable tool. At portfolio scale, a key challenge is continuity — one shared dictionary across dozens of investees, re-run each cycle, with every rolled-up number traceable to its source field and standard reference. When evaluating Sopact for this workflow, test the collection, document analysis and linked reporting records against your own agreements. Confirm how version history, approvals and framework-specific views will be configured; do not assume a connector or an automatic compliance check.

Standards mapping supports reporting preparation; it does not by itself establish legal or assurance compliance. ESRS reporting also involves materiality, policies, actions, targets, narrative disclosures, reporting boundaries, governance, digital tagging, and assurance requirements.

Frequently asked questions

How do you map portfolio data to IRIS+, GRI, and ESRS?

Compare definitions, not labels. Define each metric once in a governed dictionary (population, unit, period, boundary, calculation, disaggregation), classify each mapping Exact / Related / Organization-specific, document the differences, and validate every mapping against the current official standard before use. AI can generate candidate mappings; a qualified person approves them.

What is the difference between CSRD and ESRS?

CSRD is the EU directive that establishes who must report sustainability information; ESRS are the standards those in-scope organizations report against, drafted by EFRAG and adopted by the European Commission. You map metrics to ESRS; CSRD is the legal regime, not a metric catalog.

What is the difference between a metric match and reporting compliance?

A mapping records how an internal field relates to a standard metric. Even an exact metric match does not establish reporting compliance: applicable boundaries, materiality, narrative disclosures and other requirements still need review. A shared value can support several disclosures, but only when each framework's requirements are met and the differences are documented.

Why doesn't a similar label establish equivalence?

Because the same word can measure a different population. IRIS+ v5.2 OI7877, GRI 404-1, and the 2023 ESRS S1-13 reference all concern employee training in their standard contexts, but an impact program may be collecting training hours for external trainees or beneficiaries. Applying those employee measures to program participants changes the population, so it should be classified as related — not equivalent — and not reported as the standard metric.

Can beneficiary impact metrics be used for ESRS reporting?

Sometimes they may support value-chain or affected-community analysis, but beneficiary metrics do not automatically satisfy ESRS disclosures about the reporting entity's own workforce. First determine the relevant ESRS topic, reporting boundary, affected stakeholder group, materiality, and disclosure requirement. Keep client, beneficiary, employee, worker, and community populations explicitly separated in the data dictionary.

How do you manage changing framework versions?

Record the framework and version behind every mapping, keep versioned mapping records, re-validate when a standard is revised, and distinguish a newly adopted version from the version legally applicable to the reporting period. State the versions used in your report so a reviewer can trace which edition each disclosure was mapped against.

Should you trust an AI-generated standards mapping?

Treat it as candidate mappings, not a filing. A capable model proposes codes and caveats quickly, but a qualified person must validate each against the current standard before it reaches an LP, regulator, or assurance provider. AI can help prepare comparisons; its proposed mappings still require review.

Sources & versions

• GIIN IRIS+ metric catalog, version 5.2: PI4060 · PI8330 · PI3527 · OI7877 · OI1120. Confirm each full definition, unit, calculation, and period before approving a mapping.
• GRI–ESRS Interoperability Index (Nov 2024): globalreporting.org. For specific ESRS datapoints, consult EFRAG's ESRS datapoint implementation guidance rather than disclosure-requirement labels alone.
• CSRD & ESRS overview — European Commission; EFRAG.
• Build the dictionary first: How to build a data dictionary for program and impact data.

Technical references reviewed September 12, 2026. The examples are instructional; verify the applicable standard and reporting requirements before using a mapping.

Apply the mapping in your portfolio module

Take your approved definitions into the related lesson: frame outcomes at portfolio level. Decide which shared questions the portfolio can answer while keeping each organization’s outcomes and evidence visible.

• Need the field-by-field foundation? Build a data dictionary.
• Read the guide: how to write an impact report.
• Explore impact report examples.

Add this part to your plan

On workbook page 5, define a common measure and a C-12-specific outcome. State whether each can be aggregated and what source supports it.

Self-check: Can a contributor and a reviewer explain the same measure the same way?

Questions you may have

Does IRIS+ mapping make a metric reliable?

A reference can clarify the intended definition. Reliability still depends on how the data was collected, checked and interpreted.

Do all portfolio outcomes need one score?

No. Keep meaningful differences and explain the evidence that supports each decision.

Apply the method to your work

Use the five-part plan to assess the sources, analysis and permissions your team needs. The solution page shows where a connected platform can support that workflow.