The VB-PUO pack
The VB-PUO standard (data exchange between asset management and pension administration), owned by the Pensioenfederatie and maintained by SIVI, is how Dutch pension administrators, fiduciary managers and asset administrators exchange information in the new pension system. Strovia’s VB-PUO pack covers it end to end.
Messages supported
| Message | Flow | Pack support |
|---|---|---|
| 1 Vermogen (0001a) | Pension administrator → fiduciary manager | Validate, generate, convert, cycle |
| 2 Cashflow (0001b) | Pension administrator → fiduciary manager | Validate, generate, convert, cycle |
| 3 Pensioenprojectie (0001c) | Pension administrator → fiduciary and LDI manager | Validate, generate, convert, chunk, cycle |
| 4 Rendementsinformatie (00002) | Asset administrator → pension administrator | Validate, convert, cycle |
| 5 Orderopdracht (00541) | Pension administrator → asset administrator | Validate, convert, cycle |
| 6 Orderconfirmation (00542) | Asset administrator → pension administrator | Validate, convert, cycle |
| 13 Waarde-informatie beleggingspool (00555b) | Asset administrator → pension administrator / fiduciary manager | Validate, convert, cycle |
| Feedback Message | Receiver → sender | Validate, generate, all six scenarios |
| 10, 14, 15 | FPR | Validation; templates on request |
What’s included
Releases side by side. Release 2026 and Release 2027 are both supported. Strovia selects the right schema from the version declared in each message, so you can handle the 1 January changeover without a big-bang switch.
Strict validation. Structure, types, lengths, mandatory fields, code lists and the standard’s validation rules. Strovia also checks every item in every repeating list (every cohort, every payment), not just the message as a whole.
Templates. Cohort-level Excel or CSV extract to 0001a, 0001b and 0001c; SIVI to Excel, CSV or your own XML layout; feedback messages (accepted or rejected).
Chunking. Message 3 is often 10–15 MB and can exceed 40 MB. Large messages are split at the size agreed with each counterparty, with presets for the standard’s 4 MB default and the commonly agreed 10 MB. Every chunk is a complete, valid message, and all chunks share one messageId. Incoming chunks are reassembled in any order, and if one chunk fails, the whole message is treated as failed, as the standard requires.
Feedback. All six scenarios defined for the standard’s API: synchronous acceptance (200), synchronous rejection (400 with feedback), asynchronous acceptance or rejection (202 then callback), and the two “panic” cases where the callback itself is refused.
The official API. Messages are exchanged through the standard’s OpenAPI specification, with mutual TLS, OAuth 2.0 client credentials and optional digital signatures (JWS).
Scheme-aware cycles. Tell Strovia whether a scheme is SPR or FPR, and whether it has a collective payout phase. It then knows which messages to expect, in which order and by when. For example, Messages 2 and 4 aren’t expected in the FPR accumulation phase, but are with a collective payout phase.
Platform controls. Optional checks beyond the standard, clearly labelled as such: scheme totals against the sum of cohorts, hedged against projected amounts, overlapping age bands, order confirmations against orders.
Counterparty agreements. Message size, chunk limits, feedback mode, signing, empty-cohort convention and service windows are recorded per counterparty.
Bron: SIVI – VB-PUO Standaard. Strovia is independent and is not endorsed by SIVI or the Pensioenfederatie.