Framesoft Structured Products (FSP) · Regulatory documents
Produce KIDs from the same product record you issue from.
PRIIPs Key Information Documents are generated, reviewed and distributed as part of the FSP issuance process, not as a parallel publishing exercise. Framesoft Contract Repository (FCR) and Framesoft PRIIPs KID Generator (FPG) are covered below.
Benefits
- Tied to FSP product data
- Template structure following the KID regulation
- One template, many languages
- White-label KIDs for intermediaries where permitted
- Workflow, versioning and audit
Disclosure that cannot drift
The PRIIPs KID Generator (FPG) is how Framesoft produces Key Information Documents. It sits on Framesoft Structured Products, so the KID is generated from the same product record used for issuance. When that record is the source, disclosure stays aligned with what was approved. Verification can check the published document against it.
What a KID has to contain
Manufacturers and distributors of packaged retail and insurance-based investment products have to give investors a Key Information Document under Regulation (EU) No 1286/2014. FPG models the template in the sequence the regulation sets out, and the same tools can be reconfigured when the rules change. A manufacturer can also white-label product KIDs and supply them to intermediaries where that is legally permitted.
- Header with product name, issuer information, market-specific names and language
- Objectives and how they are achieved, including underlyings, reference values and markets
- Risk section: summary risk indicator, maximum loss, performance scenarios, taxation
- Issuer default risk
- Costs the investor can expect
- Recommended holding period and restrictions
- Summary risk indicator on a scale from 1 to 7, with unfavourable, moderate and favourable scenarios
- What happens if the manufacturer cannot pay out, including compensation schemes
- One-off and ongoing costs, and how they affect returns
- How to complain, and where to find further information
- One template generated in several languages; a template change is reflected in every language
Built on FSP
Template sections can be copied and reused. The template hierarchy is stored in the database, and amendments to the regulation are applied with the template editor and scripting tools. FSP supplies the template editor, multi-language text-block assembly, the extendable product data model, static data, a web-service interface for generation requests, audit trail, archive, approval workflow and role-based privileges. Creating or updating a KID template can require a four-eye approval before it is used for automated generation. Generation can be driven from a sales pricer or risk system, and from FCR where master agreements apply. Distribution channels, including email, are configurable.