VB-PUO Validator: check a SIVI message in your browser

What is checked: JSON syntax, the JSON schema of the chosen message and release (mandatory fields, types, formats, lengths, decimals, unknown fields, entityType), the AFD code lists (AFDIDP, AFDRES, AFDCOA, AFDSWI, ISOVAL; for AFDCOA and AFDSWI also via the code-list file next to the schema) and consistency checks based on the manual: startAge and endAge, reporting period, reserve fields, chunking, afdDefinitionVersion and IBAN/BIC format. For Release 2027 also: the fixed afdDefinitionName of the final release, reserveType with reserveIndicator = true, in messages 2 and 3 one breakdown per scheme (per cohort or per investment portfolio; the total under the scheme applies in both routes), in message 2 at least one cashflow per scheme and a netAmount per cohort that adds up to the netAmount at scheme level, in message 3 exactly one breakdown per scheme, in message 5 exactly one of tradeAmount and tradeQuantity per order and exactly one steering order per switch, in message 6 quantity × price = amount, and positive amounts. Warnings are given for what the standard does not prescribe in so many words, such as a scheme total in message 1 that does not reconcile with the cohort sum, inflow or outflow per cohort that does not add up to that of the scheme, a netAmount that is not the balance of contributionAmount and withdrawalAmount, a resend (function 54) without originalMessageId, a switch order without a reference or without its counterpart in the message, and a switch in message 6 whose amounts in the same currency differ. Every item of an array is checked against the definition of its entityType; the published schema only counts the items that satisfy it and ignores the rest (SIVI issue #63), so a generic JSON Schema validator does not report errors in those items.