RA ID : CR0665
CHANGE REQUEST
FOR THE UPDATE OF ISO 20022 FINANCIAL REPOSITORY ITEMS
A. Origin of the request:
A.1 Submitter: ISITC.
A.2 Contact person: person(s) who can be contacted to get additional information on the
request (name, e-mail, telephone)
Steve Sloan
[email protected]
972-471-5262
A.3 Sponsors:
B. Related messages:
Seev.039 CACN Message
C. Description of the change request:
To enhance the CACN message to provide two enhancements
1. The ability to expand narrative information on the CACN message. Currently the
Cancellation Reason field has only 140 characters and is not repeatable. This request is to
expand this capability by allowing the qualifier or to repeat. This expanded narrative is
required due to narrative regarding the cancellation and the new event which may also be
created.
2. The ability to have the Additional Business Process Indicator and the Change Type
indicator in the CACN. Certain events such as Name Change or Partial Prerefunding utlize
the ADDB or Change type qualifiers to further describe the event from the CAEV code. By
having both attributes, it becomes consistent with the CANO messsage in the event structure.
While not required for matching purposes, these two fields are helpful if having to read a
cancellation message. Only the four highlighted values are required for ADDB and the
NAME would be required for the Change Type.
CR0665_ISITC_seev039_Enhancements_v1 81916225Produced by ISITC on 30 May
Page 1
RA ID : CR0665
D. Purpose of the change:
The need for the Additional Text attribute in the cancellation message is due to the fact that
certain event details are only known once the event is being cancelled and should be on the
cancel message. Only ADTX is required as this should be a straight-thru message as such
these comments are critical in naturel. Currently DTCC uses extension detail to handle this
CR0665_ISITC_seev039_Enhancements_v1 81916225Produced by ISITC on 30 May
Page 2
RA ID : CR0665
case and would prefer that such comments utilize the standard ADTX tag the Core message
so as to conform to market practice.
The Change Type field (NAME) and the ADDB code with the four values of PPRE, FPRE,
CONS and PPUT are being requested so as to provide consistent logic between the CANO
and the CACN message regarding event classification.
E. Urgency of the request:
Next maintenance cycle 2017-2018
F. Business examples:
Examples illustrating the change request.
G. SEG/TSG recommendation:
This section is not to be taken care of by the submitter of the change request. It will be
completed in due time by the SEG(s) in charge of the related ISO 20022 messages or the
TSG for changes related to the BAH.
Consider
Timing
- Next yearly cycle: 2017/2018
(the change will be considered for implementation in the
yearly maintenance cycle which starts in 2017 and
completes with the publication of new message versions in
the spring of 2018)
- At the occasion of the next maintenance of the
messages
(the change will be considered for implementation, but
does not justify maintenance of the messages in its own
right – will be pending until more critical change requests
are received for the messages)
- Urgent unscheduled
(the change justifies an urgent implementation outside of
the normal yearly cycle)
- Other timing:
Comments:
Reject
Reason for rejection:
CR0665_ISITC_seev039_Enhancements_v1 81916225Produced by ISITC on 30 May
Page 3