CustomerPaymentReversalV05

Scope
The CustomerPaymentReversal message is sent by the initiating party to the next party in the payment chain. It is used to reverse a payment previously executed.
Usage
The CustomerPaymentReversal message is exchanged between a non-financial institution customer and an agent to reverse a CustomerDirectDebitInitiation message that has been settled. The result will be a credit on the debtor account.
The CustomerPaymentReversal message refers to the original CustomerDirectDebitInitiation message by means of references only or by means of references and a set of elements from the original instruction.
The CustomerPaymentReversal message can be used in domestic and cross-border scenarios.

Message Identifier: pain.007.001.05

Elements

Name	Type	Multiplicity	Definition
GroupHeader	GroupHeader56	[1..1]	Set of characteristics shared by all individual transactions included in the message.
OriginalGroupInformation	OriginalGroupHeader3	[1..1]	Information concerning the original group of transactions, to which the message refers.
OriginalPaymentInformationAndReversal	OriginalPaymentInstruction11		Information concerning the original payment information, to which the reversal message refers.
SupplementaryData	SupplementaryData1		Additional information that cannot be captured in the structured elements and/or any other specific block.

Validation Rules

GroupReversalAndPaymentInformationNotPresentRule: If GroupHeader/GroupReversal is true, then OriginalPaymentInformationAndReversal is not allowed.

GroupReversalAndReasonRule: If GroupHeader/GroupReversal is true, then OriginalGroupInformation/ReversalReasonInformation/ReversalReason must present.

GroupReversalAndNumberOfTransactionsGuideline: If GroupHeader/GroupReversal is false and OriginalPaymentInformationAndReversal[*]/PaymentInformationReversal is false, then NumberOfTransactions must equal the number of occurrences of OriginalPaymentInformationAndReversal[*]/TransactionInformation.

GroupReversalAndPaymentInformationPresentRule: If GroupHeader/GroupReversal is false, then at least one occurrence of OriginalPaymentInformationAndReversal must be present.

SupplementaryDataRule: The SupplementaryData building block at message level must not be used to provide additional information about a transaction. The SupplementaryData element at transaction level should be used for that purpose.