RA ID: CR0366
Change Request
for the update of ISO 20022 financial repository items
A. Origin of the request:
A.1 Submitter: Robert Marchal, from Swift, based on feedback from Samba testing
A.2 Contact person:
A.3 Sponsors: Samba Financial, Riyadh (Majed Al-Enezi)
B. Related messages:
The list of ISO 20022 messages which would be impacted by the change, including the Message IDs as shown in the Catalogue of ISO 20022 messages.
For changes to the Baseline
o tsmt.009.001.04 BaselineAmendmentRequestV04
o tsmt.012.001.04 BaselineReSubmissionV04
o tsmt.019.001.04 InitialBaselineSubmissionV04
otsmt.018.001.04 FullPushThroughReportV04
For changes to the Other Certificate data set
otsmt.014.001.04 DataSetSubmissionV04
o tsmt.017.001.04 ForwardDataSetSubmissionReportV04
C. Description of the change request:
In the current messages, there are two 2 predefined certificate types + 2 undefined for the “Other Certificate” data set. These are:
BENE for Beneficiary Certificate
SHIP for Shipping line certificate
UND1 Undefined 1
UND2 Undefined 2
The value of the type of Other Certificate must be an element of this predefined list and only one certificate of a given type may be required in a transaction, for example, it is impossible to require two beneficiary certificates
The purpose of this change request is to remove these constraints and allow more flexibility.
This can be achieved with very limited changes, and more precisely:
- Replace the list of 4 codes by a field of 4 uppercase letters or digits that can be defined freely by the submitter of the baseline. This will also ensure backward compatibility. If the submitter requires a beneficiary certificate, it could still specify BENE. If it requires two beneficiary certificates of a different kind, it could specify them as BEN1 and BEN2. It could also specify any type of other certificate by a combination of uppercase letters and digits.
- A free text field of 140 characters next to the code allows describing which kind of certificate is required (in words). Today this is not possible.
These two changes must be made in the block “OtherCertificateRequired” in the baseline.
In the Other Certificate data set, a simple format change is required, i.e. replace the 4 letter code from a code list by a four character field.
D. Purpose of the change:
Remove the limitation of 2 predefined certificate types + 2 undefined for the data set “Other Certificate”
E. Urgency of the request:
Normal.
F. Business examples:
Here is a business example illustrating the change request:
A trade transaction requires the following “other certificates”
- Packing list
- Beneficiary certificate confirming that test certificate is in duplicate
- Beneficiary certificate stating that shipping advice has been sent to applicant within 3 days of shipment
- A certificate issued and signed by the owner, agent or company of the vessel appended to B/L (shipping line certificate)
This cannot be achieved within the current constraints. It is not possible to specify more than one BENE certificate. And the packing list could be mentioned as UND1, but its meaning must be agreed outside of tsmt messages, which is very inconvenient and goes against automation and STP.
G. SEG 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.
Consider / Timing- Next yearly cycle: 2014/2015
(the change will be considered for implementation in the yearly maintenance cycle which starts in 2014 and completes with the publication of new message versions in the spring of 2015)
- 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:
RejectReason for rejection:
CR0366_SWIFT_tsmt_BaselineOtherCertifLimitation_v1.doc Produced by SWIFT on 5 March 2014 Page 1