FIToFIPaymentStatusReportV08

pacs.002.001.08

Scope The FIToFIPaymentStatusReport 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. The FIToFIPaymentStatusReport may also be sent to the receiver of the payment in a real time payment scenario, as both sides of the transactions must be informed of the status of the transaction (e.g. either the beneficiary is credited, or the transaction is rejected).

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% FIToFIPaymentStatusReportV08 recursion level 0 with max 0
FIToFIPaymentStatusReportV08 *-- "1..1" GroupHeader53 : GroupHeader
FIToFIPaymentStatusReportV08 *-- "0..1" OriginalGroupHeader7 : OriginalGroupInformationAndStatus
FIToFIPaymentStatusReportV08 *-- "0..1" PaymentTransaction80 : TransactionInformationAndStatus
FIToFIPaymentStatusReportV08 *-- "0..1" SupplementaryData1 : SupplementaryData
  

Now, we will zero-in one-by-one on each of these building blocks.

GroupHeader building block

Set of characteristics shared by all individual transactions included in the status report message. Set of characteristics shared by all individual transactions included in the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% GroupHeader53 recursion level 0 with max 1
class GroupHeader53{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
GroupHeader53 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : InstructingAgent
GroupHeader53 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : InstructedAgent
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
  

GroupHeader53 members

Member name Description Data Type / Multiplicity
MessageIdentification Point to point reference, as assigned by the instructing party, and sent to the next party in the chain to unambiguously identify the message. Usage: The instructing party has to make sure that MessageIdentification is unique per instructed party for a pre-agreed period.
CreationDateTime Date and time at which the message was created. IsoISODateTime - Required 1..1
InstructingAgent Agent that instructs the next party in the chain to carry out the (set of) instruction(s).
InstructedAgent Agent that is instructed by the previous party in the chain to carry out the (set of) instruction(s).

OriginalGroupInformationAndStatus building block

Original group information concerning the group of transactions, to which the status report message refers to. Provides details on the original group, to which the message refers. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% OriginalGroupHeader7 recursion level 0 with max 1
class OriginalGroupHeader7{
    OriginalMessageIdentification IsoMax35Text
    OriginalMessageNameIdentification IsoMax35Text
    OriginalCreationDateTime IsoISODateTime
    OriginalNumberOfTransactions IsoMax15NumericText
    OriginalControlSum IsoDecimalNumber
    GroupStatus ExternalPaymentGroupStatus1Code
}
OriginalGroupHeader7 *-- "0..0" StatusReasonInformation9 : StatusReasonInformation
OriginalGroupHeader7 *-- "0..0" NumberOfTransactionsPerStatus5 : NumberOfTransactionsPerStatus
%% StatusReasonInformation9 recursion level 1 with max 1
class StatusReasonInformation9{
    AdditionalInformation IsoMax105Text
}
StatusReasonInformation9 *-- "0..1" PartyIdentification43 : Originator
StatusReasonInformation9 *-- "0..1" IStatusReason6Choice : Reason
%% NumberOfTransactionsPerStatus5 recursion level 1 with max 1
class NumberOfTransactionsPerStatus5{
    DetailedNumberOfTransactions IsoMax15NumericText
    DetailedStatus ExternalPaymentTransactionStatus1Code
    DetailedControlSum IsoDecimalNumber
}
  

OriginalGroupHeader7 members

Member name Description Data Type / Multiplicity
OriginalMessageIdentification Point to point reference, as assigned by the original instructing party, to unambiguously identify the original message. IsoMax35Text - Required 1..1
OriginalMessageNameIdentification Specifies the original message name identifier to which the message refers. IsoMax35Text - Required 1..1
OriginalCreationDateTime Date and time at which the original message was created. IsoISODateTime - Optional 0..1
OriginalNumberOfTransactions Number of individual transactions contained in the original message. IsoMax15NumericText - Optional 0..1
OriginalControlSum Total of all individual amounts included in the original message, irrespective of currencies. IsoDecimalNumber - Optional 0..1
GroupStatus Specifies the status of a group of transactions. ExternalPaymentGroupStatus1Code - Optional 0..1
StatusReasonInformation Provides detailed information on the status reason. StatusReasonInformation9 - Unknown 0..0
NumberOfTransactionsPerStatus Detailed information on the number of transactions for each identical transaction status. NumberOfTransactionsPerStatus5 - Unknown 0..0

TransactionInformationAndStatus building block

Information concerning the original transactions, to which the status report message refers. Provides further details on the original transactions, to which the status report message refers. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PaymentTransaction80 recursion level 0 with max 1
class PaymentTransaction80{
    StatusIdentification IsoMax35Text
    OriginalInstructionIdentification IsoMax35Text
    OriginalEndToEndIdentification IsoMax35Text
    OriginalTransactionIdentification IsoMax35Text
    TransactionStatus ExternalPaymentTransactionStatus1Code
    AcceptanceDateTime IsoISODateTime
    AccountServicerReference IsoMax35Text
    ClearingSystemReference IsoMax35Text
}
PaymentTransaction80 *-- "0..1" OriginalGroupInformation3 : OriginalGroupInformation
PaymentTransaction80 *-- "0..0" StatusReasonInformation9 : StatusReasonInformation
PaymentTransaction80 *-- "0..0" Charges2 : ChargesInformation
PaymentTransaction80 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : InstructingAgent
PaymentTransaction80 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : InstructedAgent
PaymentTransaction80 *-- "0..1" OriginalTransactionReference24 : OriginalTransactionReference
PaymentTransaction80 *-- "0..0" SupplementaryData1 : SupplementaryData
%% OriginalGroupInformation3 recursion level 1 with max 1
class OriginalGroupInformation3{
    OriginalMessageIdentification IsoMax35Text
    OriginalMessageNameIdentification IsoMax35Text
    OriginalCreationDateTime IsoISODateTime
}
%% StatusReasonInformation9 recursion level 1 with max 1
class StatusReasonInformation9{
    AdditionalInformation IsoMax105Text
}
StatusReasonInformation9 *-- "0..1" PartyIdentification43 : Originator
StatusReasonInformation9 *-- "0..1" IStatusReason6Choice : Reason
%% Charges2 recursion level 1 with max 1
class Charges2{
    Amount IsoActiveOrHistoricCurrencyAndAmount
}
Charges2 *-- "1..1" BranchAndFinancialInstitutionIdentification5 : Agent
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% OriginalTransactionReference24 recursion level 1 with max 1
class OriginalTransactionReference24{
    InterbankSettlementAmount IsoActiveOrHistoricCurrencyAndAmount
    InterbankSettlementDate IsoISODate
    RequestedCollectionDate IsoISODate
    PaymentMethod PaymentMethod4Code
}
OriginalTransactionReference24 *-- "0..1" IAmountType4Choice : Amount
OriginalTransactionReference24 *-- "0..1" IDateAndDateTimeChoice : RequestedExecutionDate
OriginalTransactionReference24 *-- "0..1" PartyIdentification43 : CreditorSchemeIdentification
OriginalTransactionReference24 *-- "0..1" SettlementInstruction4 : SettlementInformation
OriginalTransactionReference24 *-- "0..1" PaymentTypeInformation25 : PaymentTypeInformation
OriginalTransactionReference24 *-- "0..1" MandateRelatedInformation11 : MandateRelatedInformation
OriginalTransactionReference24 *-- "0..1" RemittanceInformation11 : RemittanceInformation
OriginalTransactionReference24 *-- "0..1" PartyIdentification43 : UltimateDebtor
OriginalTransactionReference24 *-- "0..1" PartyIdentification43 : Debtor
OriginalTransactionReference24 *-- "0..1" CashAccount24 : DebtorAccount
OriginalTransactionReference24 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : DebtorAgent
OriginalTransactionReference24 *-- "0..1" CashAccount24 : DebtorAgentAccount
OriginalTransactionReference24 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : CreditorAgent
OriginalTransactionReference24 *-- "0..1" CashAccount24 : CreditorAgentAccount
OriginalTransactionReference24 *-- "0..1" PartyIdentification43 : Creditor
OriginalTransactionReference24 *-- "0..1" CashAccount24 : CreditorAccount
OriginalTransactionReference24 *-- "0..1" PartyIdentification43 : UltimateCreditor
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
  

PaymentTransaction80 members

Member name Description Data Type / Multiplicity
StatusIdentification Unique identification, as assigned by an instructing party for an instructed party, to unambiguously identify the reported status. Usage: The instructing party is the party sending the status message and not the party that sent the original instruction that is being reported on.
OriginalGroupInformation Point to point reference, as assigned by the original instructing party, to unambiguously identify the original message. OriginalGroupInformation3 - Optional 0..1
OriginalInstructionIdentification Unique identification, as assigned by the original instructing party for the original instructed party, to unambiguously identify the original instruction. IsoMax35Text - Optional 0..1
OriginalEndToEndIdentification Unique identification, as assigned by the original initiating party, to unambiguously identify the original transaction. IsoMax35Text - Optional 0..1
OriginalTransactionIdentification Unique identification, as assigned by the original first instructing agent, to unambiguously identify the transaction. IsoMax35Text - Optional 0..1
TransactionStatus Specifies the status of a transaction, in a coded form. ExternalPaymentTransactionStatus1Code - Optional 0..1
StatusReasonInformation Provides detailed information on the status reason. StatusReasonInformation9 - Unknown 0..0
ChargesInformation Provides information on the charges related to the processing of the rejection of the instruction.
AcceptanceDateTime Point in time when the payment order from the initiating party meets the processing conditions of the account servicing agent. This means that the account servicing agent has received the payment order and has applied checks such as authorisation, availability of funds. IsoISODateTime - Optional 0..1
AccountServicerReference Unique reference, as assigned by the account servicing institution, to unambiguously identify the instruction. IsoMax35Text - Optional 0..1
ClearingSystemReference Unique reference, as assigned by a clearing system, to unambiguously identify the instruction. IsoMax35Text - Optional 0..1
InstructingAgent Agent that instructs the next party in the chain to carry out the (set of) instruction(s).
InstructedAgent Agent that is instructed by the previous party in the chain to carry out the (set of) instruction(s).
OriginalTransactionReference Key elements used to identify the original transaction that is being referred to. OriginalTransactionReference24 - Optional 0..1
SupplementaryData Additional information that cannot be captured in the structured elements and/or any other specific block. SupplementaryData1 - Unknown 0..0

SupplementaryData building block

Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
  

SupplementaryData1 members

Member name Description Data Type / Multiplicity
PlaceAndName Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. IsoMax350Text - Optional 0..1
Envelope Technical element wrapping the supplementary data. IsoSupplementaryDataEnvelope1 - Required 1..1

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the FIToFIPaymentStatusReportV08 implementation follows a specific implementaiton pattern. First of all, FIToFIPaymentStatusReportV08 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, FIToFIPaymentStatusReportV08Document implements IOuterDocument. Because FIToFIPaymentStatusReportV08 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type FIToFIPaymentStatusReportV08.

classDiagram
    class IOuterRecord
    FIToFIPaymentStatusReportV08 --|> IOuterRecord : Implements
    FIToFIPaymentStatusReportV08Document --|> IOuterDocument~FIToFIPaymentStatusReportV08~ : Implements
    class IOuterDocument~FIToFIPaymentStatusReportV08~ {
        FIToFIPaymentStatusReportV08 Message
     }
  

Document wrapper for serialization

The only real purpose FIToFIPaymentStatusReportV08Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:pacs.002.001.08’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using FIToFIPaymentStatusReportV08.ToDocument() method. The returned FIToFIPaymentStatusReportV08Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    FIToFIPaymentStatusReportV08Document *-- FIToFIPaymentStatusReportV08 : Document
  

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.08">
    <FIToFIPmtStsRpt>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <!-- OriginalGroupInformationAndStatus inner content -->
        </OrgnlGrpInfAndSts>
        <TxInfAndSts>
            <!-- TransactionInformationAndStatus inner content -->
        </TxInfAndSts>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </FIToFIPmtStsRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_YZfuYWXiEeap-P22vGV91g"
  nextVersions="_AOwWO11tEeehlLdFiIrRgQ"
  previousVersion="_akmerTqxEeWZFYSPlduMhw"
  name="FIToFIPaymentStatusReportV08"
  definition="Scope&#xD;&#xA;The FIToFIPaymentStatusReport 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.&#xD;&#xA;Usage&#xD;&#xA;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.&#xD;&#xA;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).&#xD;&#xA;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.&#xD;&#xA;The FIToFIPaymentStatusReport message can be used in domestic and cross-border scenarios.&#xD;&#xA;The FIToFIPaymentStatusReport may also be sent to the receiver of the payment in a real time payment scenario, as both sides of the transactions must be informed of the status of the transaction (e.g. either the beneficiary is credited, or the transaction is rejected)."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="FIToFIPmtStsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_YZfuY2XiEeap-P22vGV91g"
    nextVersions="_AOwWPV1tEeehlLdFiIrRgQ"
    previousVersion="_akmerzqxEeWZFYSPlduMhw"
    name="GroupStatusAcceptedRule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to ACTC (AcceptedTechnicalValidation), ACCP (AcceptedCustomerProfile), ACSP (AcceptedSettlementInProcess), ACSC (AcceptedSettlementCompleted) or ACWC (AcceptedWithChange), then TransactionInformationAndStatus/TransactionStatus must be different from RJCT (Rejected)."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;NotWithInList&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[*]/TransactionStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleRejected1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[*]/GroupStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[*]/GroupStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleStatus1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[*]/TransactionStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <constraint
    xmi:id="_YZfuZWXiEeap-P22vGV91g"
    nextVersions="_AOwWP11tEeehlLdFiIrRgQ"
    previousVersion="_akmesTqxEeWZFYSPlduMhw"
    name="GroupStatusPendingRule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to PDNG (Pending), then TransactionInformationAndStatus/TransactionStatus must be different from RJCT (Rejected)."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;NotWithInList&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[*]/TransactionStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleRejected1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[*]/GroupStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[*]/GroupStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRulePending1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[*]/TransactionStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <constraint
    xmi:id="_YZfuZ2XiEeap-P22vGV91g"
    nextVersions="_AOwWQV1tEeehlLdFiIrRgQ"
    previousVersion="_akmeszqxEeWZFYSPlduMhw"
    name="GroupStatusRejectedRule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RJCT (Rejected), then TransactionInformationAndStatus/TransactionStatus, if present, must be equal to RJCT (Rejected)."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[*]/TransactionStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleRejected1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[*]/GroupStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[*]/GroupStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleRejected1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[*]/TransactionStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <constraint
    xmi:id="_YZfuaWXiEeap-P22vGV91g"
    nextVersions="_AOwWQ11tEeehlLdFiIrRgQ"
    previousVersion="_akmetTqxEeWZFYSPlduMhw"
    name="GroupStatusReceivedRule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RCVD (Received), then TransactionInformationAndStatus/TransactionStatus is not allowed."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[*]/TransactionStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[*]/GroupStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[*]/GroupStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleReceived1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[1]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <constraint
    xmi:id="_YZfua2XiEeap-P22vGV91g"
    nextVersions="_AOwWRV1tEeehlLdFiIrRgQ"
    previousVersion="_akmetzqxEeWZFYSPlduMhw"
    name="SupplementaryDataRule"
    definition="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."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_YZfubWXiEeap-P22vGV91g"
    nextVersions="_AOwWR11tEeehlLdFiIrRgQ"
    previousVersion="_akmeuTqxEeWZFYSPlduMhw"
    name="OriginalGroupInformationAbsenceRule"
    definition="If OriginalGroupInformationAndStatus is absent, then &#xD;&#xA;TransactionInformationAndStatus[*]/OriginalGroupInformation must be present."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[*]/OriginalGroupInformation&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[*]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <constraint
    xmi:id="_YZfub2XiEeap-P22vGV91g"
    nextVersions="_AOwWSV1tEeehlLdFiIrRgQ"
    previousVersion="_akmeuzqxEeWZFYSPlduMhw"
    name="OriginalGroupInformationSinglePresenceRule"
    definition="If OriginalGroupInformationAndStatus is present and only once, then TransactionInformationAndStatus[*]/OriginalGroupInformation must be absent."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[*]/OriginalGroupInformation&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[1]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[2]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <constraint
    xmi:id="_YZfucWXiEeap-P22vGV91g"
    nextVersions="_AOwWS11tEeehlLdFiIrRgQ"
    previousVersion="_akmevTqxEeWZFYSPlduMhw"
    name="OriginalGroupInformationMultiplePresenceRule"
    definition="If OriginalGroupInformationAndStatus is present and multiple times (Occurrence &gt; 1), then TransactionInformationAndStatus[*]/OriginalGroupInformation must be present."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/TransactionInformationAndStatus[*]/OriginalGroupInformation&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus[2]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <messageBuildingBlock
    xmi:id="_YZfuc2XiEeap-P22vGV91g"
    nextVersions="_AOwWTV1tEeehlLdFiIrRgQ"
    previousVersion="_akmevzqxEeWZFYSPlduMhw"
    name="GroupHeader"
    definition="Set of characteristics shared by all individual transactions included in the status report message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="GrpHdr"
    complexType="_s7WrkFkyEeGeoaLUQk__nA_-536954472" />
  <messageBuildingBlock
    xmi:id="_YZfudWXiEeap-P22vGV91g"
    nextVersions="_AOwWT11tEeehlLdFiIrRgQ"
    previousVersion="_akmewTqxEeWZFYSPlduMhw"
    name="OriginalGroupInformationAndStatus"
    definition="Original group information concerning the group of transactions, to which the status report message refers to."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="OrgnlGrpInfAndSts"
    complexType="_oRlBYWXiEeap-P22vGV91g" />
  <messageBuildingBlock
    xmi:id="_YZfud2XiEeap-P22vGV91g"
    nextVersions="_AOwWUV1tEeehlLdFiIrRgQ"
    previousVersion="_akmewzqxEeWZFYSPlduMhw"
    name="TransactionInformationAndStatus"
    definition="Information concerning the original transactions, to which the status report message refers."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="TxInfAndSts"
    complexType="_U-2sQ2XlEeap-P22vGV91g" />
  <messageBuildingBlock
    xmi:id="_YZfueWXiEeap-P22vGV91g"
    nextVersions="_AOwWU11tEeehlLdFiIrRgQ"
    previousVersion="_akmexTqxEeWZFYSPlduMhw"
    name="SupplementaryData"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="pacs"
    messageFunctionality="002"
    flavour="001"
    version="08" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.