Knowledge base MessagesEntitiesAttributesCode listsErrors and fixesProcessesRolesReleasesGlossaryEcosystemCompare Validator NL EN

Consistency check

Scheme with both cohorts and portfolios, or without a breakdown or cashflow (messages 2 and 3)

Symptom

Schema-valid, but the receiver cannot assign the flows or the projection to the right route. The WTP Data Lab validator reports an error at the scheme.

Cause

The final Release 2027 lays down a structure rule for messages 2 and 3 in section 6.3.1 (explained in section 3.2.5): under a scheme the breakdown is per cohort (SPR route) or per investment portfolio (FPR route); a message that uses both within one scheme is "niet geldig" (not valid). In message 3 each scheme uses exactly one breakdown. In message 2 the breakdown is optional, but every scheme carries at least one cashflow. What sits directly under the scheme (the cashflow of message 2, the payments of message 3) falls outside the rule and applies in both routes. The pre-release also forbade a portfolio next to the cashflow under the scheme in message 2; the final release no longer does.

Fix

Choose one breakdown per scheme. In message 3 put cohorts or portfolios under every scheme, and in message 2 give every scheme at least one cashflow, with netAmount 0 if needed. In a message in chunks the last two rules apply to the merged message.

Wrong and right

Wrong

{ "entityType": "scheme", "refKey": "REG-01", "pension": [ { "entityType": "cohort", "refKey": "C-30" } ], "investment": [ { "entityType": "portfolio", "refKey": "PF-01" } ] }

Right

{ "entityType": "scheme", "refKey": "REG-01", "financialTransaction": [ { "entityType": "cashflow", "netAmount": 33000.00, "netDate": "2027-01-15" } ], "investment": [ { "entityType": "portfolio", "refKey": "PF-01" } ] }

Check your own message for this and all other errors with the free validator: schema, code lists and consistency checks in one report. Validate a message

Attribution. Source: SIVI – VB-PUO Standard. Schemas, attribute descriptions and code lists are taken unchanged from the VB-PUO Standard (owned by the Pensioenfederatie, managed by SIVI) and shown with their release and version. Explanations, examples, error descriptions and translations are by WTP Data Lab and are not part of the standard. GitHub Stichting-SIVI/VBPUOdsk · Manual · sivi.org