The ISDA Optimal Future State Collateral Blueprint is a working document that represents the industry’s collective vision of an ideal collateral processing framework. The fundamental purpose is to design and agree a blueprint that the industry can work towards, which meets the changing demands and challenges of the collateral process. This blueprint is governed by a set of design principles and processing best practices, which are intended to serve as an industry target processing, architectural and control operating model. This will maximize accessibility by market participants while maintaining industry vision. Subsequent iterations of this document may be published to include additional factors based on changing business trends, regulatory changes or other unforeseen circumstances that were not considered at the start of the blueprint’s development.
Documents (1) for A Blueprint for the Optimal Future State of Collateral Processing
Latest
Managing Assets in an Uncertain World: Remarks
Managing Assets in an Uncertain World April 28, 2026 Opening Remarks: The Shift to Digital – Steps to Tokenization Scott O’Malia, ISDA Chief Executive Good afternoon – thanks for joining us for our exclusive Managing Assets in an Uncertain...
Four Directors Join ISDA Board
ISDA has announced that two directors have been elected to the ISDA board and two new directors have been appointed, as ISDA’s 40th Annual General Meeting gets underway in Boston. The newly appointed directors are: Tom Ceusters, Director and Chief...
Episode 56: Countdown to Treasury Clearing
With less than nine months to go until the first US Treasury clearing mandates come into force, BlackRock’s Tyler Wellensiek and BNY’s Nate Wuerffel discuss industry progress. Please view this page via Chrome to access the recording.
Response to Eurosystem Consultation on Appia
On April 22, ISDA responded to the Eurosystem consultation on the Appia roadmap. ISDA broadly supports the roadmap and its high level principles, while recommending that the principle on market access and integration should be expanded to explicitly address interoperability...
