ILPA 2.0 is not just a new template – it is a new standard
In January 2025, ILPA released an updated ILPA Reporting Template and a new ILPA Performance Template after a multi-year industry effort known as the Quarterly Reporting Standards Initiative (QRSI).
For LPs, the goal is straightforward:
- Make it easier to compare managers on fees, expenses, and performance.
- Reduce the need to negotiate bespoke reporting rights with every GP.
For GPs and their fund admins, the implications are deeper:
- More granular data is needed at the fund, investor, and investment level.
- The link between reported numbers and underlying documents must be tighter.
- "Good enough" bespoke reporting will increasingly be judged against this standard.
If you treat ILPA 2.0 as a cosmetic template redesign, you will struggle. You need an operating model.
What actually changed
At a high level, the updated ILPA Reporting Template:
- Expands and clarifies fields around fees and expenses, including offering and syndication costs, placement fees, and GP/LP sharing mechanics.
- Aligns more closely with regulatory expectations under the SEC's Private Fund Adviser rules.
- Provides more structured fields so LPs can ingest data into their own systems.
The new ILPA Performance Template:
- Standardizes how performance is presented, including net and gross returns, cash flows, and benchmark comparisons.
- Is designed to be used alongside the Reporting Template, not as a separate exercise.
Together, they encode what "baseline professional reporting" should look like going forward.
Common mistakes in "implementing" ILPA 2.0
Based on conversations with managers, admins, and advisors, three patterns show up repeatedly.
Mistake 1: Treating ILPA as a formatting exercise
If your approach is "we'll hire someone to rebuild our PDFs," you will:
- End up with pretty templates backed by the same messy spreadsheets.
- Struggle to keep them up to date across funds and vintages.
- Be one personnel departure away from losing the knowledge of how it all fits together.
ILPA 2.0 is a data standard, not a visual standard.
Mistake 2: Manual mapping every quarter
Some teams create complex mapping sheets from internal systems to ILPA tables and then:
- Manually reconcile differences each quarter
- Rebuild macros when anything changes
- Fight spreadsheet corruption and versioning issues
This works for one or two funds, once or twice. It does not scale.
Mistake 3: Ignoring alignment with LPAs and policies
ILPA's emphasis on fees, expenses, and performance puts a spotlight on:
- How your actual practices align with your LPAs and side letters
- Where carve-outs and bespoke terms exist
- Whether your internal allocation and valuation policies are implemented consistently
If your ILPA outputs tell a story that does not match your documents, you have a governance problem, not just a reporting problem.
An operating model for ILPA-aligned reporting
A sustainable approach starts with one premise:
"We will treat the ILPA templates as views on our data model, not as standalone artifacts."
In practice that means:
1. Map ILPA fields to your data model
For each ILPA Reporting and Performance Template field:
- Identify its conceptual meaning (for example, management fees, organizational costs, transaction fees, net asset value, contributed capital).
- Map it to a source in your systems: fund accounting, portfolio data layer, CRM, or a calculated field.
- Note any transformations (currency, aggregation, look-through logic).
This mapping becomes the backbone of both automation and QA.
2. Capture fee and expense data at the right granularity
To populate fee and expense sections accurately, you need:
- Detailed records of fees and expenses at the fund and portfolio company level.
- Clear allocation rules between LPs and, where applicable, co-investors.
- A way to tag costs according to ILPA categories.
Many managers discover here that their current general ledger structure is not fine-grained enough. Fixing that is part of implementation.
3. Structure performance data for the Performance Template
For performance:
- Ensure you have a clean record of cash flows (contributions, distributions, recallable amounts) by fund and by investor.
- Maintain a valuation history with dates, methods, and key assumptions.
- Align internal IRR and multiple calculations with ILPA's definitions.
If you already track performance rigorously, this step is mostly mapping. If not, the ILPA Performance Template will reveal gaps.
Designing the data layer for ILPA templates
Many of the same concepts that matter for an internal portfolio data layer also matter here:
- Entities: funds, investors, investments, vehicles
- Documents: LPAs, side letters, fee schedules, valuation memos
- Metrics: capital balances, fees, expenses, valuations, returns
Your goal is to create structured tables that can populate ILPA views directly:
- Fee and expense tables with categories aligned to ILPA's taxonomy
- Performance tables with cash flows, valuations, and benchmark links
- Investor-level tables for capital accounts and disclosures
Once that exists, generating the templates becomes a reporting job, not a forensic accounting project.
Integrating ILPA with your broader reporting
ILPA templates will likely become the baseline for many LPs. On top of that, you will still need:
- Strategy-specific or region-specific commentary
- Customized exposure and ESG reporting for certain investors
- Internal views for IC, boards, and management
Rather than building separate pipelines, design your reporting stack so that:
- ILPA templates, custom LP reports, and internal packs all draw from the same underlying data.
- Differences between them are about layout and emphasis, not underlying numbers.
This makes it far easier to answer the inevitable question, "Why does this number look different here than over there?"
Implementation roadmap – and pitfalls to avoid
A realistic path for a mid-market manager might look like:
Phase 1 – Design (0–3 months)
- Map ILPA fields to your current systems and data.
- Identify data gaps and GL changes needed.
- Decide on whether to build internal capabilities, lean on your admin, or adopt an AI-enabled portfolio data platform.
Phase 2 – Build (3–9 months)
- Implement data model changes and ILPA-aligned GL tagging.
- Stand up extraction and data pipelines for any fields currently trapped in documents.
- Work with your admin or platform provider to generate draft ILPA templates from the new data.
Phase 3 – Rollout (9–18 months)
- Roll ILPA templates out across funds, starting with those closest to LP demand or regulatory focus.
- Train internal teams and LPs on how to read and use the templates.
- Iterate based on feedback and evolving ILPA guidance.
Pitfalls to watch for:
- Trying to go "all funds, all at once" without a pilot.
- Leaving fund admin partners out of the design process.
- Letting ILPA become a separate, parallel reporting universe instead of integrating it into your core data layer.
The upside of getting ILPA 2.0 right
If you do this properly, the benefits go beyond "we ticked the box":
- LPs will experience your reporting as clear, consistent, and professional.
- You will spend less time arguing about numbers and more time talking about strategy.
- Your team will have a data foundation that makes valuations, fundraising, and regulatory interactions more efficient.
ILPA 2.0 is not just another compliance chore. It is an opportunity to bring your reporting, data, and governance up to the level your investors already assume you have.
The question is not whether you will implement it. The question is whether you will use it to upgrade your operating model.
Want to see how GoodStream helps funds operationalize ILPA reporting? Book a demo and we will show you how it works.
