Yearly Maintenance Process (for existing messages) Users Submitting Organisation (SO) Registration Authority (RA) (Lead) Standards Evaluation Group (SEG) or SubSEG that approved the current version SEG Evaluation Team (ET) Prepare change request (CR) By June 1 Reject Check completeness Accept Publish CR From Jun 1 to 7 Initial screening and prioritisation of CRs Re-establishment of ET to validate CRs By Jul 7 * Publish and assign candidate CRs to SO By Jul 7 Prepare maintenance change request (MCR) By Aug 21 Reject Check completeness Accept * By Sep 1 Approve/reject each change in MCR Validate MCR By Oct 1 By Oct 1 Publish MCR * Develop new version of ISO 20022 message models and Message Definition Report (MDR Part 1) By Dec 1 Reject Check models Registration; generation & publication of evaluation documentation From Dec 1 to Jan 1 * Correct models Reject Verify documentation Validate documentation By Feb 1 By Mar 1 * Registration of corrections Accept * Finalize MDR Part 1 and message examples Publish full documentation (February - May) * By May 1 Collect implementer’s feedback (need for patches) Review implementer’s feedback Update ISO 20022 message documentation * * Indicates that the status of the submission will be updated by the RA in the ‘Log History’ spreadsheet of the related entry in the ‘Status of Submission’ table.