The next planned version of openfunds is expected to be version 2.13.0 of openfunds. This will be released in Q1 2026. You will find here a list of fields already planned to be included and other upcoming changes. These fields may be used by members in advance of official publication, with the caveat that they are not yet finalised.
Identifier concept – compatibility with FinDatEx
To enable a 1:1 alignment with the identifier approach adopted by FinDatEx, openfunds will introduce an alternative to its current identifier model. At present, each identifier is represented by a dedicated openfunds field (e.g., OFST020000 “ISIN”, OFST020040 “SEDOL”, OFST020010 “Valor”, OFST020015 “WKN”).
Under the new option, openfunds will mirror the FinDatEx structure, using one field to specify the identifier type and a second field to capture the identifier value.
The current openfunds model is optimised for database architectures in which each identifier is stored in its own dedicated table. In contrast, the FinDatEx approach supports the use of multiple identifiers – one per instrument, but of different types – captured and transmitted within a single column rather than distributed across multiple fields.
Fund Names
As part of a broader review, the whitepaper on fund names has been updated. To ensure clarity and consistency, corresponding adjustments will also be made to certain field descriptions, specifically OFST010020 “Legal Fund Name Including Umbrella” and OFST020060 “Full Share Class Name.”
Private Markets – Redemption Gates
One of the outcomes of the ongoing openfunds working group “Private Markets” who is reviewing the applicability of field definitions for private market instruments – such as private equity and venture capital funds – is the topic of redemption gates. In addition to the existing field OFST010270 “Has Redemption Gates”, openfunds will introduce three additional fields to further specify the relevant modalities:
- OFST010272 Redemption Gate Type:
Indicates how the redemption gate is executed. Only applies if “OFST010270 Has Redemption Gate” is “yes”. - OFST010273 Redemption Gate Description:
Optional free text information to give details how the redemption gate (“OFST010272 Redemption Gate Type”) is applied. - OFST010274 Redemption Gate Method:
Defines how redemption orders are treated once the gate is active. Only applies if “OFST010270 Has Redemption Gate” is “yes”.
– Cancel and resubmit: Orders are cancelled and must be re-entered once gates reopen.
– Pending until re-open: Orders are held and automatically executed when the gate lifts.
– Pro-rata: Redemptions are partially processed on a pro-rata basis.
– First in, first out: Orders are queued chronologically and processed as capacity allows (also called FIFO Queue).
– Board Discretion: The fund board determines the handling case-by-case.
Optimization of Subscription/Redemption fields
To accommodate use cases in which subscription and redemption information is linked not to the Valuation Date but to the dealing/trade date, as is common for semi-liquid instruments, openfunds will update the concept of the field groups described in the whitepaper Execution Fields: Notification and Settlement. An updated version of this whitepaper will be published alongside a comprehensive revision of the existing fields. In addition, two new string fields will be introduced to indicate whether subscription or redemption information refers to the Valuation Date or the trade date. For clarity, “dealing date” will be treated as a synonym for “trade date.”
- OFST410030 Subscription Reference Basis
- OFST410040 Redemption Reference Basis