Compare
Building or buying VB-PUO validation
Every PUO, fiduciary and custodian has to validate SIVI messages before they touch the administration. The question is not whether, but where that validation lives: in the core system, in own scripts, or in a layer beside it.
What building yourself really costs
Schema validation with AJV is an afternoon's work. The cost is in what follows: registering the code lists from sivi.org, supporting two JSON Schema drafts (2019-09 for Release 2026, 2020-12 for Release 2027), writing yourself the consistency checks SIVI does not yet deliver machine-readably, processing the pre-release every June and the final release every September, and producing reports an auditor or the counterparty understands. KPMG built a bespoke solution for one asset manager in 2026; that is the price class.
What buying delivers
A validation layer beside the core system does not touch the administration, therefore passes the outsourcing and IT-risk assessment quickly, and delivers per message a report that can go to the counterparty. Maintenance of releases and code lists sits with the supplier. The trade-off is governance: you buy time and demonstrability, not a replacement of your administration.
Our advice
Build yourself if you have one link and a development team willing to follow the SIVI cycle. Buy if you serve several counterparties or funds, or if you need demonstrable control before 1 January 2028 without changing the core system. In both cases: start with the free validator next door to see where your messages break today.