A check on the coherence between fields or messages that goes beyond the schema, for example: an order fills exactly one of tradeAmount and tradeQuantity, or the cohort amounts in message 2 add up to the amount at scheme level (both laid down in the Release 2027 manual). Not every reconciliation is a consistency check of the standard: whether the cohorts in message 1 add up to the scheme total is left by the manual to what the parties agree. SIVI announces machine-readable consistency checks (JMESPath); the validationRules files in the repository are still empty.
Source: glossary of the VB-PUO manual (8.1 and 8.2), explanation by WTP Data Lab
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
