On 24 July 2026, financial.com published its latest newsletter on the KVG/SCD-Fondsdatenschnittstelle, together with version 5.4 of the Datenanforderung and an updated technical specification. While market attention is increasingly directed towards the major version 6.0 release planned for January 2027 (see our May 2026 article), version 5.4 demonstrates that the interface continues to evolve between major releases — and several of the changes require a concrete review of existing fund data. The common theme of the release is a continued move away from fallback reporting towards precise instrument classification.

Loan reporting: the end of the catch-all category

The most significant change concerns the reporting of Fremdfinanzierungen (loan financings), a topic of particular relevance for real estate fund managers. Until now, loans whose interest fixation period ended before final maturity — for example loans with rate reset agreements or step-up coupons — had to be reported under the catch-all category "Fremdfinanzierung (Sonstige)" (230). Under version 5.4, these positions must be allocated to the specific categories 231–237 and reported with the interest rate applicable in the current rate period, while the maturity date continues to reflect the full contractually agreed term. Whenever the interest rate changes — for instance upon reaching the next step-up tier — the position must be re-delivered under a new internal WPID with the then-applicable rate.

The same logic now applies to fix-to-float loans, which previously could not be mapped cleanly to the loan categories: the fixed phase is reported under category 231, and the transition to the floating phase triggers a delivery under category 232 with a new WPID. Notably, this treatment deviates from the established handling of fix-to-float ISINs — for loans, the maturity date must not be shortened to the rate-switch date.

In practical terms, asset managers should review their fund data for loans currently reported under category 230 and migrate them to the appropriate categories. Category 230 remains available strictly as a fallback for loans that cannot be assigned to any of the categories 231–237.

Index-CDS: no longer a matter of interpretation

Version 5.4 also resolves a long-standing ambiguity around Credit Default Index Swaps. The previous wording in chapter 9.14 of the technical specification ("can be reported") was occasionally interpreted as optional, while chapter 6.14 still described Index-CDS as "not mappable". Both chapters have been revised, and the rule is now unambiguous: Index-CDS on the Positivliste (whitelist) must be reported as category "Credit Default Index Swap (Positivliste)" (105) with a synthetic underlying; reporting under the generic category 100 is no longer permitted. Asset managers using CDS index overlays should verify their current deliveries accordingly.

Further refinements and operational updates

The release also introduces a number of smaller clarifications. The instrument descriptions for futures, options and swaptions now explicitly specify the settlement logic (physical delivery versus cash settlement), and interest rate futures (520) are restricted to bonds or cheapest-to-deliver (CTD) bonds as underlyings; contracts on money market rates such as Euribor are not permitted. In addition, the domain values were updated, including new currency crosses (BRL/MXN and DKK/CAD).

Beyond the technical changes, the newsletter reports the connection of several new Kapitalverwaltungsgesellschaften to the interface, including managers active in private markets and real estate — a further indication of the interface’s continued expansion beyond traditional securities funds.

Our perspective

Version 5.4 fits the pattern we have described in our earlier analyses of the KVG-Schnittstelle: frequent, incremental revisions that appear manageable in isolation but cumulatively demand continuous monitoring, robust data quality management and regular re-testing. For this release, the required actions are concrete: automating WPID re-assignments upon rate changes, migrating legacy loan mappings without altering contractual maturities, and keeping master data aligned with the current domain codes.

If you would like to discuss the implications for your reporting setup, please contact us.