FIToFIPaymentStatusReportV06

Scope
The FinancialInstitutionToFinancialInstitutionPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction.
Usage
The FIToFIPaymentStatusReport message is exchanged between agents to provide status information about instructions previously sent. Its usage will always be governed by a bilateral agreement between the agents.
The FIToFIPaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance) of a credit transfer instruction, a direct debit instruction, as well as other intra-agent instructions (for example FIToFIPaymentCancellationRequest).
The FIToFIPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction.
The FIToFIPaymentStatusReport message can be used in domestic and cross-border scenarios.

Message Identifier: pacs.002.001.06

Elements

Name	Type	Multiplicity	Definition
GroupHeader	GroupHeader53	[1..1]	Set of characteristics shared by all individual transactions included in the status report message.
OriginalGroupInformationAndStatus	OriginalGroupHeader1		Original group information concerning the group of transactions, to which the status report message refers to.
TransactionInformationAndStatus	PaymentTransaction52		Information concerning the original transactions, to which the status report message refers.
SupplementaryData	SupplementaryData1		Additional information that cannot be captured in the structured elements and/or any other specific block.

Validation Rules

GroupStatusAcceptedRule: If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to ACTC, ACCP, ACSP, ACSC or ACWC, then TransactionInformationAndStatus/TransactionStatus must be different from RJCT.

GroupStatusPendingRule: If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to PDNG, then TransactionInformationAndStatus/TransactionStatus must be different from RJCT.

GroupStatusRejectedRule: If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RJCT, then TransactionInformationAndStatus/TransactionStatus, if present, must be equal to RJCT.

GroupStatusReceivedRule: If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RCVD, then TransactionInformationAndStatus/TransactionStatus is not allowed.

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.

OriginalGroupInformationAbsenceRule: If OriginalGroupInformationAndStatus is absent, then TransactionInformationAndStatus[*]/OriginalGroupInformation must be present.

OriginalGroupInformationSinglePresenceRule: If OriginalGroupInformationAndStatus is present and only once, then TransactionInformationAndStatus[*]/OriginalGroupInformation must be absent.

OriginalGroupInformationMultiplePresenceRule: If OriginalGroupInformationAndStatus is present and multiple times (Occurrence > 1), then TransactionInformationAndStatus[*]/OriginalGroupInformation must be present.