Strovia: Governed data exchange for pensions & finance. Secure, connect, transform, deliver.

What changes in Release 2027

Release 2027 of the VB-PUO standard was published by SIVI in October 2026 (GitHub release v1.4.0) and takes effect on 1 January 2027. These are the changes that matter most for implementers.

Version numbers

  • Content messages: afdDefinitionVersion 001.05 (Release 2026: 001.04).
  • Feedback Message: 001.02.
  • File names still say 001.00; they are frozen so the OpenAPI references don’t break. Always use afdDefinitionVersion in the message, never the file name, to decide which schema applies.

JSON Schema Draft 2020-12

The schemas move from Draft 2019-09 to Draft 2020-12: definitions becomes $defs, internal references change accordingly, and external code-list references point to new 2020-12 paths. The meaning of the messages doesn’t change, but validators and tooling need updating.

Message set

  • New: Message 15, Corporate Actions (00557), from the fiduciary manager or asset administrator to the pension administrator.
  • Discontinued: Messages 7, 8, 9, 11 and 12 from the FPR layered order model.
  • Active: ten content messages plus the Feedback Message.

Feedback Message

The Feedback Message is extended. It includes an optional sender and receiver block in commonTechnical for routing, and Message 15 is added to originalMessageType.

Code lists

Several code lists are updated, for example reserve types (AFDRES) and pension provider codes (AFDIDP), and corporate action types (AFDCOA) are added.

What to do

  1. Load both releases and select the schema by the declared version, so 2026 and 2027 messages can coexist around the changeover.
  2. Update your validator to JSON Schema 2020-12.
  3. Check your mappings against the changed fields and code lists.
  4. Agree the cut-over date and any test window with each counterparty.

Source: VB-PUO GitHub release v1.4.0 and manual §7.5. Bron: SIVI – VB-PUO Standaard.