RA ID: CR0030

Change Request

for the update of ISO 20022 financial repository items

  1. Origin of the request:

A.1 Submitter: SWIFT Standards

A.2 Contact person:

Vincent Kuntz

/

Frank Van Driessche

Tel: +32 2 655 3353

/

Tel:+32 2 655 4126

Mail:

/

Mail:

A.3Sponsors: N/A

  1. Related messages:
  1. Payments Initiation messages set:

  • pain.001.001.03
/ CustomerCreditTransferInitiationV03
  • pain.002.001.03
/ CustomerPaymentStatusReportV03
  • pain.007.001.02
/ CustomerPaymentReversalV02
  • pain.008.001.02
/ CustomerDirectDebitInitiationV02
  1. Payments Clearing and Settlement messages set:

  • pacs.002.001.03
/ FIToFIPaymentStatusReportV03
  • pacs.003.001.02
/ FIToFICustomerDirectDebitV02
  • pacs.004.001.02
/ PaymentReturnV02
  • pacs.007.001.02
/ FIToFIPaymentReversalV02
  • pacs.008.001.02
/ FIToFICustomerCreditTransferV02
  • pacs.009.001.02
/ FinancialInstitutionCreditTransferV02
  1. Mandate messages set:

  • pain.009.001.01
/ MandateInitiationRequestV01
  • pain.010.001.01
/ MandateAmendmentRequestV01
  • pain.011.001.01
/ MandateCancellationRequestV01
  • pain.012.001.01
/ MandateAcceptanceReportV01
  1. B2C Cash Management messages set:

  • camt.052.001.02
/ BankToCustomerAccountReportV02
  • camt.053.001.02
/ BankToCustomerStatementV02
  • camt.054.001.02
/ BankToCustomerDebitCreditNotificationV02
  1. Bank Account Management messages set:

  • acmt.007.001.01
/ AccountOpeningRequestV01
  • acmt.008.001.01
/ AccountOpeningAmendmentRequestV01
  • acmt.009.001.01
/ AccountOpeningAdditionalInformationRequestV01
  • acmt.010.001.01
/ AccountRequestAcknowledgementV01
  • acmt.011.001.01
/ AccountRequestRejectionV01
  • acmt.012.001.01
/ AccountAdditionalInformationRequestV01
  • acmt.013.001.01
/ AccountReportRequestV01
  • acmt.014.001.01
/ AccountReportV01
  • acmt.015.001.01
/ AccountExcludedMandateMaintenanceRequestV01
  • acmt.016.001.01
/ AccountExcludedMandateMaintenanceAmendmentRequestV01
  • acmt.017.001.01
/ AccountMandateMaintenanceRequestV01
  • acmt.018.001.01
/ AccountMandateMaintenanceAmendmentRequestV01
  • acmt.019.001.01
/ AccountClosingRequestV01
  • acmt.020.001.01
/ AccountClosingAmendmentRequestV01
  • acmt.021.001.01
/ AccountClosingAdditionalInformationRequestV01
  1. CAI/VAI messages set:

  • acmt.022.001.01
/ IdentificationModificationAdviceV01
  • acmt.023.001.01
/ IdentificationVerificationRequestV01
  • acmt.024.001.01
/ IdentificationVerificationReportV01
  1. Exceptions & Investigations messages set:

  • camt.007.002.03
/ RequestToModifyPaymentV03
  • camt.026.001.03
/ UnableToApplyV03
  • camt.027.001.03
/ ClaimNonReceiptV03
  • camt.028.001.03
/ AdditionalPaymentInformationV03
  • camt.029.001.03
/ ResolutionOfInvestigationV03
  • camt.030.001.03
/ NotificationOfCaseAssignmentV03
  • camt.031.001.03
/ RejectInvestigationV03
  • camt.032.001.02
/ CancelCaseAssignmentV02
  • camt.033.001.03
/ RequestForDuplicateV03
  • camt.034.001.03
/ DuplicateV03
  • camt.035.001.02
/ ProprietaryFormatInvestigationV02
  • camt.036.001.02
/ DebitAuthorisationResponseV02
  • camt.037.001.03
/ DebitAuthorisationRequestV03
  • camt.038.001.02
/ CaseStatusReportRequestV02
  • camt.039.001.03
/ CaseStatusReportV03
  • camt.055.001.01
/ CustomerPaymentCancellationRequestV01
  • camt.056.001.01
/ FIToFIPaymentCancellationRequestV01

Note: decisions for the date of implementation of the change may differ from message set to message set depending on the decision of the SEG.

  1. Description of the change request:

In concordance with the resolution 10/126 (BIC identifier in the Repository) approved by the RMG at the Tokyo meeting of May 2010, the following rules will be followed:

  • To identify financial institutions, only the newly created data type BICFIIdentifier can be used (iso BICIdentifier).
  • To identify non-financial institutions, only the newly created data type BICNonFIIdentifier can be used (iso BEIIdentifier).
  • The updated AnyBICIdentifier datatype can still be used where either a financial institution or a non-financial institution may be present.
  • The corresponding recommended message element names are BICFI, BICNonFI and AnyBIC, unless more specific names are used.
  • There should no longer be any reference to BEI in either artefacts names or definitions.

This change request, if approved by the Standards Evaluation Group, should only be applied, if additional change requests are impacting the same message sets (see list of message set above).

  1. Purpose of the change:

The purpose of this change request is to align the existing set of messageswith the resolution 10/126 (BIC identifier in the Repository).

  1. Urgency of the request:

For inclusion in the next ISO 20022 maintenance release.

  1. Business examples:

Elements like the BranchAndFinancialInstitution4 or ParytIdentification32 make reference to BIC and/or BEI. The elements making reference to those components must be updated to comply with the 10/126 resolution.

  1. 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 / X / Timing
- Next yearly cycle: 2010/2011
(the change will be considered for implementation in the yearly maintenance cycle which starts in 2010 and completes with the publication of new message versions in the spring of 2011) / Priority:
high
medium
low
- 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) / X
- Urgent unscheduled
(the change justifies an urgent implementation outside of the normal yearly cycle)
- Other timing:

Comments:

The SEG approves the progressive implementation at message set level whenever a message set is to be maintained for business reason, but at the latest within 3 years.

Reject

Reason for rejection:

CR0030_SWIFT_BICBEI_Payments_v3Produced by SWIFT on 1 June 2010Page 1