2026-07 · Schema version001.05 · Pre-release
VB-PUO v1.4.0: Release 2027, pre-release (17 July 2026; final expected September 2026)
The biggest change since the first publication. The schemas migrated to JSON Schema draft 2020-12 (definitions to $defs, http to https); message 15 Corporate Actions was added; messages 7, 8, 9, 11 and 12 were discontinued; the ACB role disappeared; the switch was replaced by switchfrom and switchto; in message 6 fields became optional; in message 10 the cohort-pool layer disappeared; message 13 got a simpler NAV structure; the feedback message (schema 001.02) handles duplicate messageIds and knows party.sender and party.receiver; OpenAPI 1.0.11.
Changes
- JSON Schema draft 2020-12, $defs, https references to code lists.
- New: message 15 Corporate Actions (00557), code list AFDCAE (becoming AFDCOA).
- Discontinued: 00551, 00552a, 00552b, 00554, 00555a.
- ACB role discontinued; filled by BA or PUO.
- switch replaced by switchfrom/switchto with positive amounts.
- Message 6: tradeQuantity, tradePrice, counterparty, broker, interestAmount, commissionAmount, clearingBroker and clearingBrokerCashAccount optional.
- Message 10: cohort-pool layer and fields dummyCashId, tradeQuantity, unitPrice, currencyExchangeRate removed.
- Message 13: NAV simplified.
- Fill-in patterns SPR route and FPR route described.
- Feedback 001.02: duplicate messageId, party.sender and party.receiver, Orderconfirmation type.
- OAS 1.0.11.
Impact
Every FPR model 2 implementation must be rebuilt around messages 5, 6, 10, 13, 14 and 15; validators must handle draft 2020-12 and external code lists. Open points in the pre-release: renaming AFDCAE to AFDCOA (#137), preliminaryUnitValueAmount (#136), IBAN length (#135), sender of messages 10 and 14 (#142), 00557 missing from originalMessageType in the feedback schema.