A PRIIPs KID is no longer than three sides of A4. One of them is a manageable piece of work. The trouble starts when you multiply it.
Take a range of 40 funds, each with six share classes, sold in five languages. That’s 1,200 documents. Every one has to be reviewed at least once every 12 months, and revised without undue delay whenever something significant changes. And in the UK the documents themselves are being replaced, so for a while many firms may be producing two kinds.
Below we look at where manual KID production breaks down, how to keep documents current as the data underneath them moves, and what automating the process involves in practice.
Where manual KID production breaks down
Few firms design their KID process. It grows. A Word template, a spreadsheet of review dates, figures copied in from the risk team’s calculations, and a compliance reviewer working through a PDF with a pen.
For a handful of funds, that holds up. The first production run usually goes smoothly too, because it gets project attention and a deadline everyone knows about. The trouble comes with the refresh.
A KID draws on several owners. The summary risk indicator comes from one calculation, the performance scenarios from another, the costs from a third, and the narrative from product and legal teams. Each input changes on its own timetable. When the process relies on someone noticing that an input has changed and then finding every document it touches, documents go stale quietly, and nobody sees it until a distributor, an investor or a regulator does.
Volume arrives in bursts, too. Annual reviews fall in the same few weeks, so a team that copes comfortably for most of the year can find itself rebuilding hundreds of documents at once.
Keeping documents current when the data moves
The regulatory requirement is straightforward. A PRIIPs KID must be reviewed at least every 12 months, and whenever changes significantly affect, or are likely to significantly affect, its contents. Where revisions are necessary, they must be made without undue delay.
That’s a data problem first. If each KID is linked to the data and content it was built from, a change to any input can be traced to every document that uses it. A revised ongoing charge for one share class should flag that share class’s KID in every language it’s published in, and nothing else. A reworded risk warning should flag every document that carries it.
Our Content-Aware Reporting works on this principle. When data, text or other content changes, all the affected documents are identified and re-rendered automatically, ready for review. The team’s time goes on checking and approving documents the system has already re-rendered.
Producing multiple languages without doubling the work
A fund distributed across several EU markets needs a KID in a language each local regulator accepts. Done by hand, every language version becomes a separate document with its own copy of the figures, so every data change is made five times and checked five times.
The fix is to separate what needs translating from what doesn’t. Figures, dates and risk classes come from data and are formatted for each language automatically. Narrative is translated once, approved and reused. A change then reaches every language version at the same moment. We cover this in more depth in our piece on KIID and KID production across a multi-language fund range.
The UK is replacing KIIDs and KIDs with product summaries
The real benefit of automation isn’t simply producing 1,200 documents faster. It’s ensuring that changes to underlying data or reporting requirements are consistently reflected across every affected document, without manual intervention.
This provides a strong argument for future-proofing: a reporting platform should be able to accommodate changing regulatory requirements, including the introduction of CCI Product Summaries, without requiring an entirely new implementation project.
The EU KID is changing as well
In December 2025, the European Parliament and Council reached political agreement on the Retail Investment Strategy, including changes to PRIIPs Key Information Documents (KIDs). These include a new “Product at a glance” summary, making key investment information easier to understand, alongside future requirements for machine-readable information.
The revised PRIIPs rules are expected to apply 18 months after publication of the legislation in the EU’s Official Journal, with machine-readable requirements following a separate timetable.
For firms producing hundreds or thousands of KIDs, regulatory changes of this kind can represent a significant operational challenge.
With Opus Nebula’s Reporting as a Service, changes to document layouts and content can be made centrally through configuration, then applied consistently across the entire document range. Rather than manually updating hundreds of individual documents, a single template change can be deployed across every applicable fund, share class and language.
This is one of the key advantages of a future-proofed reporting platform: adapting to changing regulatory requirements without the cost, complexity and disruption of a traditional reporting system development project.
What automated KID production looks like
“Automated” gets used loosely, so here’s what it should mean in practice:
- Documents produced from approved templates and data feeds, at fund or share-class level, with the right footnotes and disclaimers applied by rule
- Data validation checks before report production that flag missing data, content or data outside of a tolerance
- Scheduling for annual reviews and automated triggers for required intra-year refreshes, so a deadline never depends on someone’s calendar reminder
- Exception-based dashboards, so the team spends its time on the documents that need attention
- A full audit record of the inputs, changes, approvals and distribution behind every version
- Publication to your website and distribution to intermediaries once a document is approved
People stay in charge of sign-off. Compliance can review on a sample basis and view exceptions, as required.
What this means for operations teams
KID production never finishes. Every fund launch, cost change, risk recalculation and new market adds to it, and in the UK the format itself is changing. The firms that stop it swallowing their operations team run it as a data-driven production line, with people approving the output.
That’s how Opus Nebula’s Reporting as a Service produces UCITS KIIDs, PRIIPs KIDs and product summaries: dynamic templates across funds, share classes, regions and languages, automated validation and scheduling, and a full audit trail, all on a pay-per-use basis.
Frequently asked questions
How often does a PRIIPs KID need to be updated?
At least every 12 months from first publication, and without undue delay whenever there is a change that significantly affects its content. In practice that means a scheduled annual review, plus updates during the year when something like a cost figure or the risk indicator moves.
What’s the difference between a UCITS KIID and a PRIIPs KID?
The UCITS KIID is a two-page disclosure for UCITS funds. The PRIIPs KID is a three-page document for packaged retail and insurance-based investment products. In the UK both documents are now being replaced by the CCI product summary.
Does a KID have to be produced in every language a fund is sold in?
In the EU, the KID must be written in an official language of the member state, or the part of it, where the product is distributed, or in another language that member state’s regulator accepts. Requirements vary, so each fund’s language list depends on where it’s marketed.
Can KID production be automated without losing compliance oversight?
Yes. Automation builds, validates and schedules documents from approved data and templates. Compliance and product teams still review and sign off before anything is released, and the audit trail records who approved what, and when.