Chain agreements: feedback, correction, chunking, transport, releases
Release policy and version management: annual cycle, three active releases and afdDefinitionVersion
SIVI issues the standard in annual releases. According to the release policy (manual section 2.9.2) a pre-release appears at the end of June and the final release at the end of September; Release 2027 came later, as a pre-release on 17 July 2026 and as the final release on 12 October 2026. Three annual releases are active at the same time. Every message carries in commonFunctional the afdDefinitionVersion of the schema it was built with (001.04 for Release 2026, 001.05 for Release 2027), so the receiver picks the right schema. The pre-release and the final Release 2027 both carry 001.05: a message built on the pre-release can therefore state the right version and still fail.
Steps
- Pre-release (Release 2027: 17 July 2026)SIVIPre-release with release notes on GitHub; chains assess impact.
- Final (Release 2027: 12 October 2026)SIVIFinal release on GitHub. The manual is a website (stichting-sivi.github.io/VBPUOdsk-docs-prepare); SIVI announces a PDF. For Release 2027 SIVI moved tag v1.4.0 to the final version; the pre-release has since been tag v1.4.0-prerelease.
- MigrationChain partnersAgree per link when to move to the new afdDefinitionVersion; support two versions temporarily. Re-test messages built on the pre-release against the final schemas.
Rules and consistency checks
- Change requests run via GitHub issues in the format prescribed by the wiki (sample JSON, UML, consistency checks).
- Changes are only made through the formal process; derived versions require approval from SIVI or the Pensioenfederatie.
Source: Handleiding paragraaf 2.8 en 2.9.2; GitHub README; release notes v1.4.0 (12 oktober 2026)